Britain’s Air Traffic Control Has Failed Three Times Since 2023. Regulators Closed the Last of 34 Safety Fixes 81 Days Before This One.

A software fault inside the system that turns filed flight plans into departure clearances capped an entire country’s airspace on Tuesday afternoon. It was the third national air traffic disruption in the United Kingdom in just over three years.

NATS, the UK’s air traffic control provider, identified a fault in its flight processing system at 13:46 on Tuesday, September 8, 2026, and had a fix in place by roughly 16:40. In those three hours, the country’s departure rate collapsed.

More than 1,750 flights into and out of UK airports were cancelled, and the backlog was still working through 15 airports a day later.

The uncomfortable part is the calendar. On June 19, 2026, the Civil Aviation Authority formally closed the last of the 34 recommendations issued after the August 2023 NATS failure that disrupted more than 700,000 passengers. Eighty one days later, the system failed again.

What a Flight Processing System Actually Does

Before a commercial flight can leave the gate, a controller needs a processed version of its filed flight plan: the route, the cruising altitude, the speed, the call sign, the aircraft type.

The flight processing system is the software that ingests those plans, reconciles them against the airspace structure, and turns them into something a controller’s screen can work with. It runs at NATS’s Swanwick centre in Hampshire, which has controlled the airspace over most of England and Wales since January 2002.

When that software stops, controllers do not lose the airspace and they do not lose radar. They lose the automation, and they begin entering flight plans by hand.

Manual entry is slower than software by an enormous margin, and the only safe way to run a hand worked system is to put fewer aircraft into it. So the response is to throttle the flow rate, which is a polite way of saying most aircraft stay on the ground.

That is why a software fault in Hampshire stops departures in Edinburgh. NATS handles over 2.5 million flights in a typical year, and the UK works about a quarter of Europe’s air traffic inside roughly 11 percent of its airspace.

Three Failures, Three Different Causes

The 2023 failure has a documented root cause, and it is a genuinely strange one. A flight plan filed on August 28, 2023 contained two waypoints with identical names in different parts of the world, roughly 4,000 nautical miles apart, both outside UK airspace.

The subsystem that reads incoming plans, the Flight Plan Reception Suite Automated Replacement or FPRSA-R, had handled more than 15 million flight plans across five years without meeting that combination. When it did, it raised a critical exception and dropped into fail safe. So did its backup.

The CAA later estimated that more than 700,000 passengers were affected: roughly 300,000 by cancellations, 95,000 by delays of over three hours, and about 300,000 by shorter delays. Industry costs ran to around £100 million.

The second failure was not a flight plan problem at all. On July 30, 2025, a radar related fault at Swanwick restricted traffic for more than four hours and produced over 150 cancellations before controllers moved to a backup system.

Tuesday’s is the third, and NATS has not said what triggered it. Chief executive Martin Rolfe has ruled out a cyber attack, telling reporters the organisation does not believe it was one, and officials close to the investigation have pointed to an internal software malfunction rather than an external cause.

NATS has also said the fault was distinct from the technical problems behind the 2023 and 2025 stoppages. That is the whole difficulty. Three separate faults, in three separate places, produced the same national outcome.

Why Closing the Recommendations Did Not Close the Risk

The independent review of the 2023 failure, chaired by Jeff Halliwell, reported on November 14, 2024 with 34 recommendations. Twelve went to NATS, eleven to the CAA, six to airlines and airports, and five to government.

They ranged from software changes to contingency planning, earlier disruption warnings, and better support for stranded passengers. The CAA closed the last of them on June 19, 2026.

Closing those recommendations means the 2023 fault was addressed. It does not mean a different fault, somewhere else in the same processing chain, cannot cap the departure rate of an entire country. Tuesday is the evidence.

The structural issue is the size of the blast radius, not the individual bug. Compare it with a genuinely local outage: when a lightning strike knocked out Luton’s air traffic control in August 2026, the damage stopped at one airport’s traffic.

When the flight processing chain at Swanwick fails, the unit of disruption is the country, and it does not end when the fix goes in. Aircraft and crews finish the day in the wrong places, which is how one delay becomes tomorrow’s cancellation.

That is why Wednesday was worse than the outage itself for some operators. Ryanair, whose fleet is built around the Boeing 737-800, said around 65,000 of its passengers were disrupted, with delays running to eight hours and more than 50 flights cancelled.

One Week to Explain It

Transport Secretary Heidi Alexander summoned Rolfe to a meeting on Wednesday morning, raised significant concerns at the scale of the disruption, and gave him one week to complete a full investigation. The CAA expects a full report from NATS before it decides whether further reliability measures are needed.

The airlines are not waiting for it. Ryanair has demanded Rolfe’s resignation, and Wizz Air called NATS not fit for purpose.

Ryanair chief operations officer Neal McMahon put the frustration plainly in comments reported by AeroTime: “Following the 2023 collapse, we were told lessons would be learned. We were told resilience would improve. We were told the systems had been fixed. Yet here we are again.”

The disruption reached well beyond London. Gatwick, Stansted, Luton, London City, Manchester, Birmingham, Edinburgh, Glasgow, Aberdeen and Belfast City all took cancellations, and Dublin was hit because so much of its traffic crosses UK controlled airspace.

The question that week of investigation is likely to turn on is not really what broke on Tuesday. It is whether an entire country’s departure rate should still depend on one chain of software finishing its work.