A tiny coding error froze London’s air‑traffic hub on September 8, leaving hundreds of thousands of passengers stranded. NATS now offers a first look at what went wrong and how safety was restored.
The UK’s air-traffic services provider, NATS has today made public a provisional investigation into the cascade of delays that crippled the nation’s travel network earlier this month. The inquiry was commissioned at the request of the Secretary of State for Transport, Heidi Alexander and aims to outline the trigger, the immediate corrective actions and the roadmap to a comprehensive final analysis.
Chief Executive Martin Rolfe was quick to stress that the September incident bears no relation to the massive system outage that struck in August 2023, nor does it stem from any form of military interference. “We identified a software issue within a narrow fragment of our flight-data system.
A temporary mitigation is already active while a permanent, safety-certified fix is being rolled out,” he explained.
The September 8 incident that halted London-area flights
At 09:30 GMT on Tuesday 8 September, controllers at the London Area Control centre experienced a sudden loss of critical flight information, prompting the imposition of nationwide air-traffic restrictions.
The affected segment of the National Airspace System (NAS) supports the allocation of identification codes that allow radars to track aircraft in real time. When the system faltered, controllers were left with incomplete data, forcing them to limit departures and arrivals to preserve the safety envelope.
The restrictions lasted roughly six hours before normal operations resumed in the evening. Nevertheless, the backlog of delayed or cancelled services persisted for more than two days, disrupting the travel plans of hundreds of thousands of passengers across the UK. Although the fault primarily impacted flights managed by the London centre—typically those operating below 24,500 ft—the nationwide hold-up was essential to restart the NAS and reload the corrupted data sets.
Root cause: a minute-scale software defect
The malfunction originated in a small subsection of the software responsible for assigning flight identification codes. Under normal conditions, these codes are generated automatically, but a manual request can be made when the automatic pathway is unsuitable. Such manual entries are processed by a routine that, in this case, received a higher-priority message while it was still awaiting completion.
When the higher-priority activity interrupted the manual request, the routine attempted to resume after a brief pause. A hidden defect prevented the routine from re-initialising correctly, producing a corrupted output that cascaded into subsequent flight-data updates. The entire episode unfolded within a single millisecond, yet its ripple effect was enough to cripple the flow of information to air-traffic controllers.
Operational response, apologies and upcoming investment
In reaction to the anomaly, NATS imposed immediate traffic limits, performed a full NAS reboot and re-loaded the affected data streams. By the end of the day, normal operations were largely restored, though the passenger-service backlog required more than 48 hours to clear. Throughout the episode, NATS emphasized that safety remained uncompromised and that all procedural safeguards were observed.
Martin Rolfe issued a formal apology, stating, “Our core mission is to move people swiftly and safely; when we fall short, we are deeply remorseful. At no point was safety in doubt.” Over the past decade, NATS has invested over £1 billion in modernising its technology stack, and the regulator plans to seek an additional £1 billion of funding from the Civil Aviation Authority by the close of 2033 to further harden the system against similar failures.
