Storm surge season is open: what the tide data — and the 2013 east coast surge — tell multi-site teams about coastal flood risk

Most of the flood risk conversation this year has been about rain — or the lack of it. But the UK's other major flood mechanism runs on an entirely different clock, and its season has just started. The storm surge season conventionally runs from the start of September to the end of February: the window in which large autumn and winter spring tides are most likely to coincide with deep Atlantic low-pressure systems. For any organisation with sites near the coast or a tidal estuary, this is the half of the year when the sea, not the sky, is the risk to watch.

This post looks at what actually drives coastal flood events, what the tide calendar says about the months ahead, and what the most severe recent event — the December 2013 east coast surge — teaches about preparing a multi-site portfolio.

The mechanics: three ingredients, one bad night

Coastal flooding in the UK is almost never caused by a single factor. It takes a stack:

A spring tide. Twice a month, around the new and full moon, the sun and moon pull together and tides run at their largest. The National Tidal and Sea Level Facility notes that spring tides are particularly large close to the equinoxes in March and September, when the sun sits over the equator. That is why the autumn tide tables deserve attention: published tidal coefficient data for 2026 shows strong spring tides in the 18–22 September window and again around 16–20 October — routine in themselves, but the top of the astronomical range on which everything else stacks.

A storm surge. A deep low-pressure system raises the sea surface beneath it and its winds push water against the coast. In the funnel-shaped southern North Sea, a northerly gale can drive a surge of a metre or more on top of the predicted tide. The surge is the wildcard: the astronomical tide is known years in advance, but the surge arrives with the weather, at days' notice at most.

Waves on top. Wind-driven waves overtop defences that the still water level alone would not. As the 2013 event showed, the wave climate can matter as much as the water level itself.

A big spring tide on a calm day is a spectacle. A moderate surge on a neap tide often passes unnoticed. It is the coincidence — surge and waves arriving on a high spring tide — that produces the events that make the history books. That's also why the season matters: between September and February, the large tides and the vigorous Atlantic storm track overlap.

December 2013: the modern benchmark

The surge of 5–6 December 2013 remains the most instructive recent case. Research comparing it with the catastrophic 1953 flood found that the 2013 event produced the highest still water levels on record at several east coast tide gauges, exceeding 1953 levels on east-facing coasts south of the Humber and along north-facing Norfolk.

By the standards of 1953 — still the benchmark for UK coastal disaster — the outcome was remarkable. The 2013 surge flooded around 720 properties, with 18–20 km of defences overtopped and four breach locations. Two differences explain the gap. First, the storms themselves: the 1953 storm tracked further south and drove 7–8 metre offshore waves onto the coast, while 2013's maximum significant wave heights off north Norfolk were around 3.8 metres — higher water, but far less wave energy. Second, and decisively, six decades of investment: the Environment Agency estimated that more than 800,000 homes were sheltered by flood defences during the 2013 event, and the engineered defences held, with damage confined to localised overtopping, breaching and back-barrier flooding.

The lessons for an operations team are double-edged. The defences work: the difference between 1953 and 2013 is one of the strongest arguments for the UK's coastal defence programme. But 720 properties still flooded behind the most heavily defended coastline in the country's history — because defences reduce risk, they do not remove it, and overtopping and breaches concentrate the residual risk on whoever happens to sit behind the weak point. The Environment Agency's updated National Flood Risk Assessment puts 6.3 million properties in England at risk from rivers, the sea or surface water; for the coastal share of any portfolio, the question is not "are we defended?" but "what happens at our site when a defence is overtopped for two hours either side of high water?"

Why surge risk suits monitoring better than almost any other flood type

Tidal flood risk has a property that operations teams should exploit: it is exceptionally forecastable in one dimension and volatile in the other.

The astronomical tide is known to the minute, years ahead. Every one of the season's high-tide windows can go in the operational calendar today. What changes at short notice is the meteorology — and the UK's forecasting infrastructure for that is mature: the Flood Forecasting Centre in England and Wales, and SEPA's Scottish Flood Forecast in Scotland, run surge models against every tide, and the agencies issue coastal flood alerts and warnings by named coastal area, in the same framework as fluvial warnings. We've written about what each warning level should trigger operationally; coastal warnings slot into exactly the same escalation structure, usually with more lead time than a convective downpour will ever give you.

Practically, that shapes a simple seasonal routine for any portfolio with coastal or estuarine exposure:

1. Know which sites are tidal. It sounds obvious, but estuarine exposure reaches a long way inland — tidal reaches of rivers can carry surge effects tens of kilometres from open coast. Geocode the portfolio properly against flood zones rather than judging by distance to the beach.

2. Put the spring tide windows in the calendar now. The mid-September and mid-October spring tide periods, and their successors through the winter, are the windows when a passing storm can escalate quickly. A tide calendar costs nothing and converts an abstract seasonal risk into specific dates a duty manager can look at.

3. Make the coastal warning feed part of the same picture as everything else. The failure mode for multi-site teams is fragmentation: fluvial warnings from one page, coastal from another, three different agencies across England, Wales and Scotland. FloodWatch pulls the official EA, NRW and SEPA warning feeds — coastal areas included — and live tidal gauge data into one portfolio dashboard on a 5-minute refresh, so a surge event shows up as "these four sites, this tide, this warning level" rather than as a scattering of agency pages someone has to remember to check. Our storm season readiness plan covers the wider preparation checklist that the first named storm of the season will test.

4. Rehearse the two-hour version. Coastal events are short and sharp: the danger window is typically the hour or two either side of predicted high water, repeated over successive tides while the storm lasts. Response plans built for slow-onset river flooding — with half-day timescales — need a compressed variant for tidal sites.

The season ahead

Nothing in the current data points to a specific coastal event — that is not how surge risk works, and this post is not a forecast. What the calendar guarantees is the astronomical half of the stack: a sequence of large spring tides through the autumn, starting with the equinoctial tides now and repeating into October and beyond, through the months when Atlantic storms are most active. Whether 2026–27 delivers a significant surge event will be decided by weather systems that do not yet exist.

That asymmetry is the whole argument for monitoring. The teams that handled December 2013 well were not the ones that predicted it in September; they were the ones whose warning feeds, site lists and response plans were already connected when the surge forecasts firmed up 48 hours out. See how FloodWatch brings coastal, river and rainfall monitoring into one view for portfolios across England, Wales and Scotland.