A single incorrect piece of data entered into the British air traffic control system may be behind the chaos that this week left thousands of canceled flights and hundreds of thousands of affected passengers. The initial investigations suggest that the failure suffered on Tuesday, September 8, by NATS, the air traffic control provider in the United Kingdom, was triggered after the system received anomalous information related to the flight plan of a military aircraft.
The problem affected the flight data processing system, a fundamental infrastructure for managing the plans used by controllers. The failure lasted approximately four hours and forced a drastic reduction in operational capacity, causing cancellations, delays, and diversions at airports such as Heathrow, Gatwick, Manchester, Stansted, and Birmingham.
NATS insists that air safety was not compromised. Precisely, when a critical system stops functioning correctly, the response is to reduce the number of aircraft that can be safely managed. The result can be enormous chaos for passengers without implying that the planes that continue flying are operating without control.
A military aircraft appears at the origin of the problem
The definitive cause has not yet been officially published, but the investigation has taken an important turn.
According to information from the Financial Times and The Times, NATS officials have explained to the sector that the failure would have begun when a military aircraft transmitted “spurious” or anomalous flight data that the system failed to process correctly. This information triggered the blockage of the platform used to manage flight plans.
This does not necessarily mean that the pilot or the British Army made a mistake.
The British Ministry of Defence has indicated that it has no evidence of a failure attributable to a military aircraft and has requested to wait for the conclusions of the NATS investigation. Therefore, the key piece of information is not yet who entered incorrect information, but why a critical system was unable to isolate it without causing a failure of such magnitude.
What exactly stopped functioning
NATS constantly receives and processes the flight plans of the aircraft that cross or use British airspace.
Those plans contain, among other elements, the origin and destination, the planned route, waypoints, altitude, and other information necessary for controllers to know which aircraft will enter each sector.
On Tuesday, the problem occurred in the Flight Data Processing System, responsible for transforming that enormous amount of information into data usable by the air traffic control network. NATS publicly identified from the early hours that the incident was localized in its flight processing system.
When that system stopped functioning normally, NATS had to restrict the amount of traffic it could accept, which immediately caused airports to start accumulating grounded aircraft.
Why four hours caused several days of chaos
The duration of the failure may seem relatively limited compared to the impact it produced.
The problem is that commercial aviation operates through an extremely tight chain. The same aircraft can make several flights during a day and the same crew connects different routes. If the first flight is blocked for hours, the aircraft and the workers may subsequently find themselves at the wrong airport.
When NATS managed to resolve the incident, the technical infrastructure could function again, but the air network was already completely disorganized.
Heathrow even suspended arrivals for the rest of the day and airlines had to reallocate aircraft, crews, and passengers. The consequence was that cancellations continued to accumulate the next day despite the fact that the computer failure had already been corrected.
Between Tuesday and Wednesday, more than 2,000 flights ended up canceled, in addition to numerous delays and diversions.
The most concerning fact: there was no identical backup
The investigation must especially clarify another element: why the system could not continue functioning through an equivalent backup platform.
The known information suggests that NATS is undergoing a modernization of its systems and that the affected processing system did not have a completely duplicated second system capable of immediately taking on the entire load. Creating that replica would be particularly costly and complex.
This point is fundamental to assess the risk of a new failure.
Critical infrastructures usually incorporate redundancies to prevent the failure of a single piece from paralyzing the entire service. But having backup systems does not necessarily mean having an identical copy that can automatically replace any platform in a matter of seconds.
Precisely, one of the questions that the investigation will have to answer is whether the available alternatives were sufficient for an infrastructure that manages one of the most congested airspaces in the world.
Something similar happened in 2023
The concern of the airlines is explained because it is not the first major recent failure of NATS.
On August 28, 2023, a flight plan with an exceptional combination of data caused another failure in the automatic processing system. The incident forced a temporary switch to manual procedures and ended up affecting about 700,000 passengers, with an estimated cost for travelers and the industry of between 75 and 100 million pounds.
An independent investigation conducted later made 34 recommendations directed at NATS, the Civil Aviation Authority, airlines, airports, and the British Government.
NATS claimed to have implemented the measures that corresponded to it, and in July 2025 the Government reported that many had already been verified by the regulator.
That is why the new incident has generated a particularly harsh reaction among airlines: a problem related again to the processing of flight plans has managed to produce another national disruption despite the reforms undertaken after 2023.
Ryanair and Wizz Air question the reliability of NATS
The criticisms have been particularly strong from low-cost airlines.
Ryanair has called for the resignation of NATS CEO, Martin Rolfe, while Wizz Air considers a deep reform of the British air traffic control provider necessary. Both companies argue that a critical national infrastructure should not repeatedly cause disruptions of this magnitude.
NATS has defended that its systems are safe and has apologized for the consequences of the failure.
Rolfe initially acknowledged that they still did not know exactly what had caused the problem and stated that a complete investigation would be necessary before establishing responsibilities.
Can it happen again?
Yes, technically a failure can occur again, although it is still too early to determine if the exact same failure could be repeated.
Two issues must be distinguished.
If the investigation confirms that a specific data format caused the blockage, NATS can develop filters or software modifications to prevent that same combination from bringing down the system again. Something similar happened after the incident in 2023.
But the real underlying problem is another: no complex computer system can guarantee that it will never suffer an unexpected failure. The question is whether there is enough redundancy so that the error of one platform does not end up affecting the entire network.
The absence of a completely equivalent backup and the recurrence of incidents in a few years are precisely the elements that regulators will now examine.
The Civil Aviation Authority opens an independent review
The British government has given NATS one week to deliver a detailed report on what happened.
In addition, the Civil Aviation Authority (CAA) will conduct an independent review to determine not only the technical cause but also whether NATS currently has an infrastructure sufficiently resilient against future failures.
The regulator will need to analyze the operation of alternative systems, the procedures used during the crisis, the speed of recovery, and the company's ability to prevent a localized error from spreading throughout the network.
What is still unknown
In the absence of the final report, several questions remain unanswered.
It still needs to be clarified what specific data triggered the failure, why the software failed to reject it, what exact relationship the indicated military aircraft had, and why the alternative mechanisms did not allow for maintaining a greater traffic capacity.
It cannot yet be stated that there is an identical defect to the one that caused the 2023 crisis.
What is clear is that the incident on September 8 has made NATS's technological resilience the center of the debate. The system avoided compromising safety by reducing traffic, but it did so at the cost of grounding thousands of flights.
And that is precisely the issue that the investigation will need to resolve: not only why a machine failed, but why the failure of that machine was able to paralyze such an important part of British aviation for hours.