NATS blames millisecond flight-data glitch for UK airspace disruption

What happened

NATS, the UK's main provider of air traffic services, has published a preliminary report into the technical failure that disrupted flights on Tuesday 8 September. The report was requested by Transport Secretary Heidi Alexander and covers both the cause of the problem and how it was resolved; a fuller report is expected to follow.

Chief Executive Martin Rolfe confirmed that the incident was unrelated to NATS' major system outage in August 2023, and rejected speculation that military activity played any part.

A one-millisecond fault

According to NATS, the disruption stemmed from a software defect in a small component of the National Airspace System (NAS), the platform that underpins the management of UK airspace. The affected software assigns identification codes to individual aircraft when those codes are requested manually rather than allocated automatically. The codes are what allow controllers to identify flights on radar once they are airborne.

The sequence of events, as described in the report, was unusually brief. While a manual request for an aircraft code was being processed, the system received a message relating to a higher-priority activity, which caused the code request to be paused. When processing resumed, the defect prevented it from resuming correctly. The output was corrupted, and some subsequent flight data updates were affected — all within roughly a millisecond.

Rolfe characterised the problem as a software issue traced to a small subsection of code, and said mitigation is already in place while a permanent fix is safety tested and deployed.

Why restrictions went UK-wide

With less information available to controllers, NATS introduced restrictions on air traffic to preserve safety. Although the faulty software only affected flights handled by the London Area Control centre — which manages higher-level traffic, operating mainly above 24,500 feet — the restrictions had to be applied across the whole of the UK so that NAS could be restarted and its flight data reloaded.

The restrictions remained in place for around six hours. NATS says operations returned to normal the same evening, but it took more than two days to clear the resulting backlog, with hundreds of thousands of passengers seeing their travel plans disrupted.

Rolfe apologised again to those affected, saying the operator is "devastated" when it fails to get people where they want to go, while stressing that safety was never in question at any point during the incident.

Investment and next steps

NATS notes that it has invested well over £1 billion in systems and technology over the past ten years, and that it will shortly submit plans to the Civil Aviation Authority to invest a further £1 billion by the end of 2033.

Why it matters

The report is a compact case study in how a single defect in critical national infrastructure can cascade. A fault that manifested in about a millisecond, in one subsystem, at one control centre, forced a UK-wide shutdown of normal traffic handling simply because the safe recovery procedure required restarting the whole airspace system and reloading its data.

It also illustrates a classic failure mode in concurrent software: state that is paused mid-operation and then resumed incorrectly. That hazard exists in any system that handles interleaved requests, not just aviation, and it is notable here that the trigger was an ordinary priority-based interruption rather than anything exotic.

Finally, it shows the trade-off operators of safety-critical systems accept — when data integrity is in doubt, availability is sacrificed immediately. The open question the full report will need to address is whether the restart-and-reload recovery path, which turned a local fault into a national outage and days of passenger disruption, can be made faster or more contained.