UK air traffic control failures raise systemic concerns amid mounting pressure

Hundreds of thousands of passengers affected across multiple incidents; some left sleeping on airport floors, others stranded in foreign airports.
Critical national infrastructure keeps letting customers down
Jet2's chief executive on the pattern of repeated air traffic control failures affecting hundreds of thousands of passengers.
Mark

So we've had four major failures in two years. Are we looking at equipment that's just old and breaking down, or is this something else?

Mimi

It's not entirely clear yet, which is part of the frustration. The two failures in September alone had different causes—a software flaw in one case, a connectivity issue in the other. But the pattern suggests the system doesn't have enough redundancy or resilience built in.

Luke

Right, but we should be careful here. Nats is handling 8,000 flights a day through some of Europe's busiest airspace. Complex systems fail sometimes. The question is whether these failures are statistically unusual or whether they're revealing genuine neglect.

Mimi

That's fair. But what's notable is that airlines are saying resources aren't being put in to prevent this. And passengers are the ones paying the price—literally sleeping on airport floors.

Mark

Why hasn't the government forced a change in leadership?

Mimi

The Transport Secretary called it unacceptable, but there's no appetite for removing the chief executive. Instead, they've ordered a six-month independent review.

Luke

Which means no action for half a year. That's the real story—not just that the system failed, but that the response is slow while people keep getting stranded.

Mark

And Rolfe himself won't resign?

Mimi

No. He's arguing that in systems this complex, obscure faults are nearly impossible to prevent, and when they happen, they're hard to diagnose quickly.

Luke

That's a fair technical point, but it doesn't address whether the system has been adequately resourced or maintained. Those are management questions, not just engineering ones.

Mark

So we're waiting for a report while the system keeps breaking?

Mimi

Essentially, yes. And the airlines are furious because they're absorbing the costs while the infrastructure provider faces no real consequences.

  • Two failures in two weeks — one catastrophic, one significant — left over 2,000 flights cancelled and hundreds of thousands of passengers stranded, some sleeping on terminal floors or abandoned abroad.
  • This is the fourth major incident in two years, and the pattern is eroding the industry's willingness to accept official assurances that each failure is isolated and unrelated.
  • Airlines are bearing the financial burden — refunds, hotel rooms, lost revenue — while Nats remains largely insulated from the consequences of its own system's fragility.
  • Ryanair has demanded the resignation of Nats chief Martin Rolfe; Rolfe has refused, arguing that in systems of genuine complexity, obscure faults are nearly impossible to fully prevent.
  • The government has commissioned a six-month independent review, but airlines and passengers are growing impatient with a timeline that offers no near-term accountability or remedy.

Twice in a single fortnight, Britain's air traffic control system faltered — grounding thousands of flights, stranding hundreds of thousands of passengers, and exposing what may be a deeper fragility at the heart of critical national infrastructure. The incidents, the fourth and fifth in two years, have forced a reckoning with a question that transcends any single software flaw or connectivity error: whether the systems societies build to move people safely through the sky are receiving the care and investment their complexity demands. An independent review is underway, but reviews take time, and the human cost of waiting accumulates with each disruption.

In the space of two weeks in September, Britain's air traffic control system failed twice. The first, at the Swanwick hub that manages approaches to Heathrow and Gatwick, was severe: more than 2,000 flights cancelled, hundreds of thousands of passengers grounded, some sleeping on airport floors or stranded in foreign cities. Nats attributed it to a software flaw that had lain hidden until a specific combination of circumstances triggered it. The second, at the Prestwick centre covering Scotland and northern England, was smaller but still substantial — 150 cancellations, tens of thousands more disrupted. Nats insisted the two were unrelated.

Few in the industry found that reassurance convincing. This was the fourth major incident in two years. In August 2023, a corrupted flight plan brought down a core system on a bank holiday weekend, affecting 700,000 passengers. A radar malfunction followed. Now, in September 2026, the failures were accelerating, and the question was no longer whether these were accidents but whether they pointed to something structurally wrong in how the system was built and maintained.

Airlines were furious — not only at the disruption but at the asymmetry of consequence. They absorbed the costs of refunds and stranded passengers while Nats remained shielded from financial fallout. Steve Heapy of Jet2 called it a failure of critical national infrastructure. Easyjet demanded firm action. Ryanair went further, calling publicly for Nats chief executive Martin Rolfe to resign, or for Transport Secretary Heidi Alexander to remove him.

Rolfe declined to step down, arguing that in systems of genuine complexity, obscure faults are inherently difficult to prevent and even harder to diagnose quickly. Alexander called the disruption unacceptable but showed little appetite for forcing a leadership change. Instead, the Civil Aviation Authority was asked to conduct an independent review — a process expected to take six months. Thorough, perhaps. But thoroughness means delay, and in the meantime, the system that millions depend on to move them safely remains, in the eyes of those it has failed, unreliable.

In the span of two weeks in September, Britain's air traffic control system failed twice. The first failure, at the National Air Traffic Services hub in Swanwick, was catastrophic: more than 2,000 flights cancelled across two days, hundreds of thousands of passengers grounded, some sleeping on airport terminal floors, others abandoned in foreign cities. The second failure, at the Prestwick centre handling Scotland and northern England, was smaller in scale but still substantial—150 cancellations, tens of thousands more disrupted. Nats blamed the first on a previously hidden software flaw that triggered under a specific combination of circumstances. The second they attributed to a connectivity problem unique to the Scottish system. The company insisted the two were unrelated.

But the pattern was becoming impossible to ignore. This was the fourth major incident in two years. In August 2023, a single aircraft's flight plan corrupted a core system at Swanwick, affecting 700,000 passengers on a bank holiday weekend. Two years later, a radar malfunction disrupted traffic for four hours and cancelled 150 flights. Now, in September 2026, the failures were accelerating, and the question hanging over the industry was no longer whether these were isolated accidents but whether they revealed something fundamentally broken in how the system was built and maintained.

Nats operates some of Europe's busiest airspace. The Swanwick control centre alone handles up to 8,000 flights daily, managing the approaches to Heathrow and Gatwick among others. Walking through the facility, the scale is striking: hundreds of controllers seated before banks of radar screens, translating what appears to an outsider as visual chaos into coordinated movement. The work is genuinely complex. But complexity is not an excuse for repeated failure, and that distinction was sharpening the anger from airlines and passengers alike.

Steve Heapy, chief executive of Jet2, was direct: the system was critical national infrastructure, and it was failing people repeatedly. Easyjet said the latest incident exposed a fundamental lack of resilience and demanded firm action. Behind closed doors, according to sources within the industry, airlines were furious—not just at the disruption but at the cost they bore: refunding passengers, housing stranded travellers, absorbing the financial hit while Nats remained insulated from the consequences. The deeper concern was that the system simply was not receiving the resources needed to make it robust.

Some airlines went further. Ryanair called repeatedly for Martin Rolfe, Nats' chief executive, to step down, or failing that, for Transport Secretary Heidi Alexander to remove him. Rolfe, however, showed no sign of departing. On Friday, he made clear he would not resign. He argued that in systems of such complexity, obscure faults were nearly impossible to prevent entirely, and that when they did occur, they were inherently difficult to diagnose quickly. "We spent so much time making sure they work that anything that does happen of this nature is, by its very nature, going to be incredibly complicated and probably difficult to understand at the time," he said.

Alexander had called the early September disruption "completely unacceptable," but there appeared little appetite in government to force a leadership change. Instead, the government asked the Civil Aviation Authority to conduct an independent review of the first incident—a process expected to take six months. No action was likely before that report appeared, and the Monday failure did not seem to have altered that timeline. The review would be thorough, presumably, but thoroughness meant delay, and delay meant more flights, more cancellations, more passengers sleeping on floors while the system that was supposed to move them safely remained, in the eyes of those depending on it, fundamentally unreliable.

It is simply not good enough for this critical national infrastructure to keep letting customers down.
— Steve Heapy, chief executive of Jet2
In systems of such complexity, obscure faults are extremely hard to prevent, and when they do occur, they are inherently difficult to understand at the time.
— Martin Rolfe, Nats chief executive
Vuoi la storia completa? Leggi l'originale su BBC News ↗
Contattaci Domande frequenti