UK Flight Chaos Erupts Again As Second Air Traffic Control Failure Hits In Two Weeks
Why UK Air Traffic Control Has Failed Again Just Two Weeks After A 2,000-Flight Meltdown
Another UK Air Traffic Control Failure Hits Thousands Of Passengers Just Days After NATS Report
Britain’s air traffic control system has suffered its second major technical failure in less than two weeks, cancelling at least 200 flights and reigniting an increasingly bitter dispute between airlines and National Air Traffic Services.
The latest incident struck NATS’ Prestwick control centre in Scotland on Monday, September 21, disrupting flights across Scotland, Northern Ireland and northern England. NATS said the fault had been fixed later in the morning, but airlines warned that cancellations and delays could continue as aircraft and crews were left out of position.
The timing could hardly have been more damaging.
Just 13 days earlier, a completely separate failure at NATS’ Swanwick operation triggered one of the most disruptive days British aviation has experienced in recent years, ultimately contributing to more than 2,000 cancelled flights and affecting hundreds of thousands of passengers.
NATS insists the two failures are technically unrelated.
For airlines and passengers, however, the distinction has done little to quiet a much broader question: why has critical UK air traffic infrastructure failed twice in such a short period?
What Happened To UK Air Traffic Control On September 21?
NATS said it experienced a technical problem at its Prestwick centre early on Monday morning.
The organisation initially imposed air traffic restrictions to reduce the volume of aircraft being handled while engineers investigated, a standard safety response when controllers cannot operate systems at full capacity.
NATS later identified the problem as a connectivity issue involving part of its systems network and said it was specific to its Scottish operation.
The organisation said the issue had been fixed and that it was working with airports and airlines to remove the remaining restrictions safely.
That recovery did not immediately restore normal schedules.
Aviation networks operate as tightly connected systems. When departures are held back, aircraft arrive late at subsequent airports, crews can exceed working-time limits, airport slots can be missed and passengers can miss connections.
Even a technical failure lasting a relatively limited period can therefore continue affecting schedules for hours after the underlying problem has been repaired.
At Least 200 Flights Cancelled
Early figures showed the disruption escalating rapidly.
Reuters initially reported that 24 flights had been cancelled by 08:58 GMT, with Manchester, Glasgow and Belfast among the airports experiencing delays. Gatwick and London City also warned of some disruption.
Later figures from aviation analytics company Cirium, reported by the Associated Press, put the number of cancelled UK arrivals and departures at at least 200 flights.
Manchester, Belfast International, Edinburgh and George Best Belfast City Airport were among the locations experiencing some of the most significant disruption.
Unlike the September 8 incident, however, NATS said airports south of Manchester were broadly unaffected.
That meant Heathrow and much of the London aviation system avoided the kind of widespread shutdown seen earlier in the month.
Ryanair Says 25,000 Passengers Were Disrupted
Few airlines responded more aggressively than Ryanair.
The carrier said more than 25,000 Ryanair passengers were expected to be affected by the failure and renewed its demand for NATS chief executive Martin Rolfe to leave his position.
Ryanair chief operations officer Neal McMahon accused NATS leadership of presiding over repeated failures and criticised what the airline sees as inadequate backup arrangements.
The airline has repeatedly attacked NATS following previous outages and has argued that airlines and passengers are carrying the financial and operational consequences of failures they did not cause.
Monday’s incident gave Ryanair another opportunity to intensify that argument.
The airline’s call for Rolfe to resign remains Ryanair’s position rather than an independent finding about responsibility for the failure.
EasyJet Questions The Resilience Of NATS
EasyJet also issued unusually strong criticism.
The airline said Monday's failure once again raised questions about the resilience of NATS systems and called for firm measures to prevent repeated disruption.
EasyJet cancelled a number of services as the disruption developed.
British Airways described it as disappointing that passengers were facing problems following another NATS technical fault, while Jet2 said customers and airlines needed greater accountability and resilience from the organisation.
That collective response matters.
Individual airlines frequently criticise infrastructure failures that disrupt their schedules, but the increasingly broad criticism of NATS suggests the argument is shifting beyond a single malfunction.
The focus is now increasingly on resilience: whether backup systems, recovery procedures and technology investment are sufficient to prevent isolated technical faults from producing repeated disruption across the aviation network.
Why This Failure Is Especially Awkward For NATS
The September 21 incident arrived at an exceptionally difficult moment for NATS.
Only three days earlier, on September 18, the organisation published its preliminary investigation into the enormous September 8 failure.
NATS said that earlier incident had been caused by a previously unidentified software defect affecting part of its National Airspace System.
Chief executive Martin Rolfe said the fault had been traced to a small subsection of code and that mitigation had been introduced while a permanent repair was being safety tested and deployed.
Then another NATS system experienced a failure.
NATS has stressed that Monday’s connectivity problem had nothing to do with the September 8 software defect.
Technically, that is an important distinction.
From a resilience perspective, however, two different faults occurring in two separate parts of the organisation within thirteen days potentially creates an even more uncomfortable question.
Rather than one defective component repeatedly malfunctioning, the organisation is now dealing with scrutiny over separate problems affecting different parts of its infrastructure.
What Caused The September 8 NATS Failure?
The earlier breakdown was far larger.
On September 8, NATS experienced a problem with its flight-processing system at its Swanwick centre.
Its preliminary investigation subsequently identified a software defect involving the system responsible for flight data, including codes used to identify aircraft on radar.
NATS said the problem had been traced to a very small piece of software and had not been caused by incorrect actions by air traffic controllers.
The failure forced restrictions across the UK aviation network while engineers attempted to diagnose and safely restore the system.
The consequences were enormous.
Around 1,750 flights were cancelled on September 8 alone, according to figures cited by The Guardian, with continuing disruption pushing the overall cancellation figure beyond 2,000.
Around 330,000 passengers were reported to have experienced cancellations or delays.
Heathrow, Gatwick, Manchester and Stansted were among the major airports affected.
Aircraft were diverted, passengers were stranded overseas and schedules remained disrupted after the technical system itself had been restored.
Two Different Failures — One Bigger Problem
NATS has therefore presented a clear technical distinction between the two September incidents.
The September 8 failure involved software at Swanwick.
The September 21 disruption involved connectivity within the systems network supporting the Prestwick operation.
There is currently no verified evidence showing that the two faults shared a common technical cause.
That does not necessarily end the resilience debate.
Critical infrastructure is not judged solely on whether two individual faults are identical.
It is also judged on redundancy, failover systems, recovery speed, contingency planning and the ability to continue operating when individual components fail.
That is why airlines are placing so much emphasis on resilience rather than simply asking for explanations of the specific fault.
What Does The Prestwick Centre Do?
Prestwick is one of the major centres through which NATS manages UK airspace.
Its operations are particularly important for aircraft travelling through Scotland and parts of northern UK airspace, as well as flights moving across parts of the North Atlantic network.
When capacity at such a centre is restricted, the effects can therefore extend beyond the airport nearest to the technical failure.
Aircraft heading into controlled northern airspace may be held, rerouted or delayed even when the airport from which they are departing remains fully operational.
That helps explain why Monday’s disruption affected airports across several regions rather than only Scottish airports.
Why Air Traffic Systems Do Not Simply Keep Running When Something Breaks
Aviation operates under an unusually strict safety philosophy.
If controllers lose access to information, communications or processing capabilities needed to manage normal traffic levels safely, capacity is deliberately reduced.
That can mean allowing fewer aircraft into particular sections of airspace or increasing the separation between flights.
From a passenger perspective, the result looks like an airport shutdown or unexplained delay.
From the air traffic system’s perspective, it is an intentional safety mechanism.
NATS said restrictions were introduced on Monday specifically to manage traffic demand while engineers investigated the Prestwick problem.
The immediate disruption therefore does not imply that aircraft already in the air were placed in unsafe situations.
Pressure On Martin Rolfe Intensifies
NATS chief executive Martin Rolfe was already under substantial pressure following the September 8 failure.
Ryanair and Wizz Air had previously called for him to resign following earlier disruption.
The UK government had also demanded detailed explanations of the September 8 breakdown, while Transport Secretary Heidi Alexander commissioned an independent Civil Aviation Authority review of NATS' resilience.
Monday’s failure intensified those pressures.
Ryanair renewed its resignation demand, while easyJet and other airlines called for stronger action.
Alexander said she understood that passengers would find the renewed disruption deeply frustrating following the previous incident.
The government owns 49% of NATS, making it the organisation’s largest shareholder. Other shares are held by airlines, airports, employees and private investors.
Whether leadership changes follow will ultimately depend on NATS' shareholders and government decisions rather than airline demands alone.
The CAA Review Has Become Even More Important
The Civil Aviation Authority was already reviewing the circumstances surrounding the earlier September failure and the wider resilience of NATS infrastructure.
That review now takes place against a markedly different backdrop.
When it began, investigators were examining one severe system breakdown.
They must now consider a second significant disruption occurring less than two weeks later, even if the underlying technical causes prove completely unrelated.
The central regulatory questions are likely to extend beyond the specific code or network component that failed.
They include whether contingency systems functioned as intended, whether investment levels are appropriate, whether ageing components pose additional operational risks and whether recovery procedures can be improved.
NATS Has Failed Before
The current controversy is also shaped by history.
A major NATS failure in August 2023 caused enormous disruption after an unusual flight-plan problem overwhelmed part of the automated processing system.
Reuters reported that the 2023 outage ultimately cost airlines about £100 million.
Further disruption has occurred since then.
That history explains why airlines are reacting so strongly to the latest incident.
A single unusual technical failure can potentially be treated as an exceptional event.
Repeated failures inevitably create questions about whether the underlying infrastructure, architecture and contingency arrangements are robust enough for a national transport network on which millions of journeys depend.
Can Passengers Claim Compensation?
Passengers affected by air traffic control failures face a frustrating distinction under UK passenger-rights rules.
The Civil Aviation Authority said following the September 8 breakdown that passengers were unlikely to qualify for the standard fixed financial compensation available for some delayed or cancelled flights because an air traffic control failure is generally regarded as an extraordinary circumstance outside an airline's control.
That does not mean airlines have no obligations.
Passengers can still have rights to assistance including food, refreshments, hotel accommodation where required and alternative transport or refunds depending on the circumstances.
The CAA reiterated during Monday's disruption that airlines remained responsible for looking after affected passengers even where standard delay compensation was unlikely to be payable.
Passengers should therefore keep receipts for reasonable expenses and contact their airline directly where assistance is not automatically provided.
Why A Short Failure Can Ruin An Entire Day Of Flights
One of the most confusing aspects of major aviation incidents is that delays frequently continue long after engineers announce that the technical problem has been repaired.
Aircraft operate through complex rotations.
A plane might begin the morning in Edinburgh, fly to London, continue to Spain and then return to Britain later that evening.
If the first flight is cancelled or delayed by several hours, every subsequent service using that aircraft can be affected.
Crew schedules create another constraint.
Pilots and cabin crew can only work defined periods before mandatory rest requirements apply.
An aircraft may therefore become available again while the crew originally scheduled to operate it legally cannot continue working.
Airport slot restrictions and connecting passengers can add further complications.
That is why restoring an air traffic control computer does not instantly restore the aviation network.
Could More Flights Still Be Affected?
NATS said the Prestwick problem itself had been fixed and restrictions were being removed.
That substantially reduces the risk of further disruption directly caused by the technical fault.
However, passengers travelling later on September 21 could still experience knock-on delays while airlines reposition aircraft and crews.
NATS advised passengers to continue checking directly with their airline for the latest information.
The scale of Monday’s incident remains considerably smaller than the nationwide shutdown on September 8.
Its significance lies partly in its timing.
The Bigger Question Is Now Resilience
The technical explanations matter.
One failure originated in software.
The other involved connectivity.
NATS says they are unrelated.
But Britain’s aviation industry is increasingly asking a different question.
How many independent technical failures can critical infrastructure experience before separate incidents become evidence of a wider resilience problem?
There is not yet enough evidence to conclude that the failures demonstrate one systemic technical defect.
The forthcoming investigations will need to establish whether they expose weaknesses in technology, investment, redundancy, maintenance or operational recovery — or whether two unusually timed but genuinely independent failures happened to occur within thirteen days of each other.
What is already clear is that confidence has been damaged.
Airlines are openly questioning NATS' resilience.
Ryanair is demanding leadership change.
Government and regulators are examining what happened.
And hundreds more passengers have now joined the hundreds of thousands already caught in September's air traffic disruption.
For NATS, fixing the Prestwick connectivity problem may prove to have been the straightforward part.
Restoring confidence that Britain’s air traffic control network can withstand the next technical failure could be considerably harder.
