What Two NATS Failures Mean for UK Air Travel Today

NATS suffered two unrelated system failures in 13 days this September, disrupting UK flights on a scale that makes “isolated incident” feel increasingly inadequate as a description of the passenger experience.

The failures had different causes and footprints. A software flaw at NATS’ main Swanwick control centre on September 8 led to more than 2,000 cancellations across two days. On September 21, a connectivity problem at its Prestwick centre produced a smaller, regional disruption, with aviation analytics company Cirium estimating about 150 cancellations.

Different faults can still expose the same operational weakness: when a critical air traffic system goes sideways, airlines and passengers have limited room to route around it. That does not prove one hidden defect links the incidents, or that NATS’ entire network is crumbling into a Windows error message. It does raise a fair question about resilience across several parts of the network.

What Failed at Prestwick

The September 21 problem affected part of the systems network used for NATS’ Scottish operation. NATS applied traffic restrictions while engineers investigated, a measure intended to manage demand and maintain safety.

The disruption concentrated on Scotland, Northern Ireland and northern England. AeroTime’s account of NATS’ statements listed delays at Liverpool, Manchester, Belfast International, Edinburgh and Glasgow Prestwick. Flights heading north could also be affected even when they departed from airports outside the main disruption zone.

Transport Secretary Heidi Alexander said around 10:30 local time that engineers had fixed the problem and systems were resuming. NATS later identified a connectivity issue and said it was unrelated to the Swanwick failure earlier in September. Restrictions took time to unwind after the repair, because an air traffic network cannot instantly swallow the flights held back during an outage. Aviation’s least glamorous superpower is turning one broken morning into an impressively complicated afternoon.

The effects varied even within the same region. Simple Flying reported delays of up to an hour at Manchester, with no outage-related cancellations reported there at that point. Belfast City experienced some cancellations, while City of Derry lost services to and from Glasgow. Belfast International reported delays without cancellations in that account.

For travellers, geography offered clues rather than guarantees. NATS said airports south of Manchester were broadly unaffected, but aircraft and crews circulate through a network. A delayed inbound plane can spoil an outbound schedule somewhere untouched by the original fault. NATS therefore directed passengers to their airlines for flight-level information.

Four Failures, Four Apparent Triggers

The recent history makes the resilience question harder to wave away.

In August 2023, a problem involving one aircraft’s flight plan caused a key Swanwick system to fail over a bank holiday weekend. Cancellations and delays affected 700,000 passengers. A radar-related issue in July 2025 then disrupted traffic for four hours and caused 150 cancellations.

September 2026 added two more entries. The September 8 failure involved a previously undetected software flaw triggered by circumstances that combined within a millisecond. A theory that a military flight plan caused that breakdown circulated afterward, but the Ministry of Defence denied it. The September 21 fault involved connectivity within the Scottish operation.

That gives the UK four reported NATS failures since August 2023, involving a flight-plan input, radar, software and network connectivity. The BBC’s incident history places them against a system that can handle up to 8,000 flights per day.

The variety cuts in two directions. It supports NATS chief executive Martin Rolfe’s argument that obscure faults inside complex systems can be extremely difficult to anticipate. Air traffic control contains enough moving parts to make a Swiss watch look like a spoon.

Yet four different triggers can also indicate that resilience must be assessed across the whole operation, rather than by patching whichever component failed last. The pattern alone cannot identify underinvestment, weak testing or poor management as the cause. No public evidence cited here establishes any of those conclusions. It does show that failures have reached several parts of the operation and repeatedly imposed disruption on airlines and travellers.

How the 2023 Breakdown Compares

The August 2023 failure remains the strongest domestic comparison because it shows how one narrow input problem can expand into a national travel mess. Its 700,000 affected passengers cannot be compared directly with September 2026’s cancellation totals, since one figure counts people and the other counts flights. Anyone dividing those numbers is committing spreadsheet vandalism.

The operational comparison is more useful. Both the 2023 and September 8, 2026 failures occurred at Swanwick and created broad disruption. Prestwick’s September 21 connectivity fault was more regional, with airports south of Manchester described as broadly unaffected. About 150 cancellations remain painful if one of them contains your non-refundable hotel booking, but the event did not approach the geographic reach reported after the earlier Swanwick breakdowns.

Scale and frequency therefore tell separate stories. The 2023 event produced the largest documented passenger impact in this recent sequence. September 2026 produced the tightest cluster, with two unrelated failures inside a fortnight. A smaller second outage does not become evidence of a common technical cause merely because it arrived quickly. It does shorten the period between reminders that multiple NATS systems can fail.

Accountability is Moving on a Slower Clock

Airlines have sharpened their criticism because they handle passengers and absorb costs when the air traffic system fails. Jet2 chief executive Steve Heapy said critical national infrastructure should not keep letting customers down. EasyJet called for action on the resilience of NATS’ systems. Ryanair has repeatedly sought Rolfe’s resignation or removal.

NATS’ response focuses on complexity, safety and damage control. Its position is that technology sometimes fails, obscure problems are difficult to prevent, and its responsibility during an incident is to minimise disruption without compromising safety. Rolfe has said he does not plan to resign.

The government has chosen investigation over an immediate leadership change. Alexander called the early September disruption “completely unacceptable,” while the Civil Aviation Authority was asked to conduct an independent review expected to take six months. The subsequent Prestwick incident had not changed that timetable in the BBC’s September 21 account.

A six-month review may be appropriate for software, procedures and governance that cannot be responsibly audited between lunch and boarding. The trade-off is obvious: passengers and airlines continue using the same broad system while investigators work. The available reporting identifies no interim investment programme, system overhaul or leadership change, although absence from those reports does not prove that internal work is absent.

That leaves travellers with a frustratingly modest playbook. Check directly with the airline, especially when travelling through Scotland, Northern Ireland or northern England after a Prestwick problem. Expect knock-on disruption outside the original fault area. Treat an operational fix as the start of recovery rather than a magic reset button.

The CAA review may eventually determine whether these were four unlucky failures in a fiendishly complicated system or signs that resilience needs broader repair. Until then, NATS can reasonably say the September faults were unrelated, while passengers can reasonably notice that unrelated failures still strand people just the same.