The report on Britain’s September 8 air-traffic-control failure is unusually specific. A high-priority flight-data request interrupted the routine allocation of an aircraft identifier—the four-digit “squawk” used by controllers—at exactly the wrong point in the process. The interruption lasted less than a millisecond; the resulting software state contributed to more than 2,000 cancellations or serious disruptions. The Guardian’s account of the report
NATS initially restored the system, then a second incident forced it to operate at reduced capacity for roughly six hours while controllers handled more traffic manually. The operator says safety was never compromised and found no malicious cause. It has put an interim mitigation in place while testing a permanent repair; the Civil Aviation Authority has opened a six-month independent review. Reuters, September 18
The failure is a useful reminder of what “legacy risk” can actually mean. The defect was not a slow machine or an unsupported language. It was an obscure interaction between priorities inside a system whose recovery procedure then became part of the event. Britain has now had three major NATS disruptions since 2023, so the consequential question is whether the fix removes this state transition or merely prevents the exact sequence that produced it.