ON
← Back to feed
Flight chaos caused by 'millisecond' software defect, report says
United Kingdom🏛️ PoliticsCenter

Flight chaos caused by 'millisecond' software defect, report says

A software defect in the UK's air traffic control system caused significant flight disruptions in early September, resulting in over 2,000 canceled flights and affecting hundreds of thousands of passengers. The National Air Traffic Services (Nats) reported that the defect occurred in a millisecond, causing corrupted data and reducing the availability of critical information for air traffic controllers. Restrictions were imposed on UK airspace to ensure safety, and the system was not fully restored until late evening. Passengers faced challenges such as being stranded overseas or sleeping on airport floors, with many expressing frustration over inadequate support and potential lack of compensation. Nats CEO Martin Rolfe denied plans to resign, emphasizing the complexity of the systems and their extensive testing. Transport Secretary Heidi Alexander criticized the incident as 'completely unacceptable,' prompting calls for a review by the Civil Aviation Authority.

Flight chaos caused by a "millisecond" software defect in the UK's air traffic control system led to widespread disruptions, according to a report by National Air Traffic Services (Nats). The incident, which occurred on 8 September, resulted in more than 2,000 flight cancellations and affected hundreds of thousands of passengers. The software defect, described as "very, very obscure" by Nats chief executive Martin Rolfe, caused the system to produce corrupted data within a fraction of a second. This led to restricted airspace and manual interventions by air traffic controllers. Flights in and out of major UK airports such as Heathrow, Gatwick, Luton, and Glasgow were impacted. Passengers faced long delays, with some forced to sleep on airport floors or remain stranded abroad. The issue first emerged at 10:00 am, when the link between the National Airspace System (NAS) and the London area control system dropped. Engineers were notified shortly after, but the system reportedly recovered by 10:06 am. However, the problem resurfaced at 12:32 pm, prompting a declaration of a major incident. Controllers had to handle tasks manually, and flight restrictions were imposed by 12:45 pm. The system fully failed at 1:32 pm, with airlines informed of the restrictions at 1:40 pm. Nats began a system reboot between 2:50 pm and 4:09 pm, restoring full operations by 7:30 pm. Despite this, the backlog of disrupted flights persisted, taking more than two days to resolve. The disruption left many passengers stranded, with some reporting confusion upon arrival in unintended destinations. Rolfe apologized to those affected, stating that Nats was "devastated" by the incident. He emphasized that safety was never compromised during the event. "Our primary role is to keep our skies safe, and everyone who flies through them," he said. He noted that the system had been extensively tested, and the complexity of the issue made it challenging to address promptly. Transport Secretary Heidi Alexander called the disruption "completely unacceptable" and "frustrating" for passengers, airlines, and airports. She stated that the Civil Aviation Authority (CAA) would review the incident to determine why the issue was not resolved before causing chaos. A government source confirmed that the CAA review would assess whether Nats is fit for purpose. This marks the third major air traffic control failure in the UK in three years. In 2023, a computer shutdown during the August bank holiday weekend disrupted 700,000 passengers. Another smaller outage in 2025 caused 150 flight cancellations. Tim Alderslade, CEO of Airlines UK, criticized the lack of accountability, noting that airlines bore the cost of the disruption while Nats faced no real consequences. He urged for commitment and proof that the system is being improved. Airlines UK is set to demand immediate compensation and a credible plan to enhance system resilience. Passenger Addie Kitson, who was stranded in China, recounted being diverted to Sweden instead of landing in London. She expressed surprise upon learning of the airspace issues, highlighting the confusion and inconvenience experienced by travelers.

How this report was made. Objective News wrote this report from 2 source articles, using AI-assisted synthesis under our methodology. It is our own text, not a copy of any single outlet. Read our methodology.

Responsible editor: Matej BašaSpotted an error? Report it

Go to the primary sources (1)

The official sources this coverage is built on. Read them directly to bypass framing.

2 reports

BBC News (UK) logoBBC News (UK)State / PublicCenterFactual 95Objective 75
Flight chaos caused by 'millisecond' software defect, report says

A software defect in the UK's air traffic control system caused significant flight disruptions in early September, resulting in over 2,000 canceled flights and affecting hundreds of thousands of passengers. The National Air Traffic Services (Nats) reported that the defect occurred in a millisecond, causing corrupted data and reducing the availability of critical information for air traffic controllers. Restrictions were imposed on UK airspace to ensure safety, and the system was not fully restored until late evening. Passengers faced challenges such as being stranded overseas or sleeping on airport floors, with many expressing frustration over inadequate support and potential lack of compensation. Nats CEO Martin Rolfe denied plans to resign, emphasizing the complexity of the systems and their extensive testing. Transport Secretary Heidi Alexander criticized the incident as 'completely unacceptable,' prompting calls for a review by the Civil Aviation Authority.

Bias read (Center): The article presents a balanced account of the incident, quoting both Nats officials and the Transport Secretary. It includes perspectives from affected parties, such as passengers and airlines, without overtly favoring one side. The framing remains neutral, focusing on the technical cause and the各方

Why factuality (95): The article accurately reports the cause of the incident as a 'software defect' in the National Airspace System, aligning closely with the primary source document. It mentions the 'millisecond' timing, the corruption of flight data, and the impact on flights and passengers. However, it adds details

Why objectivity (75): The article includes quotes from Martin Rolfe and Heidi Alexander, maintaining a neutral tone overall. However, it introduces additional commentary such as 'questions over the resilience of Nats' systems' and 'some airlines questioned the position of Mr Rolfe,' which may introduce a slight bias towa

The Guardian (World) logoThe Guardian (World)IndependentCenterFactual 90Objective 70
Flight chaos for hundreds of thousands was caused in ‘millisecond’ by software error

A critical software defect in the UK's air traffic control system caused a six-hour outage on 8 September 2023, leading to widespread flight disruptions and cancellations across the UK and beyond. The error, described as a 'legacy and previously unknown' software defect, occurred within a 'millisecond' during the processing of an aircraft code request, corrupting flight data and triggering a major incident. National Air Traffic Services (Nats) reported the issue initially at 10am, with engineers noting a temporary recovery, but the problem resurfaced at 12.32pm, forcing manual operations and flight restrictions. Transport Secretary Heidi Alexander called for urgent investigation, while airlines demanded compensation and accountability, including calls for the resignation of Nats CEO Martin Rolfe. Rolfe stated the incident was unrelated to prior failures and attributed it solely to a software issue.

Bias read (Center): The article presents a factual account of a technical failure without overt ideological framing. While it highlights criticism from government officials and airlines, it does not take a clear partisan stance. The focus remains on the technical cause and consequences rather than political agendas. No

Why factuality (90): The article accurately summarizes the cause of the incident as a 'software defect' in the National Airspace System, matching the primary source. It correctly states the timeline of the incident, including the 10:00 am occurrence and the declaration of a major incident at 12:30 pm. However, it adds u

Why objectivity (70): The article presents both Nats' explanation and the government's response, maintaining a relatively balanced perspective. However, it emphasizes the need for the CAA to 'fundamentally investigate' Nats' fitness for purpose, which may imply skepticism toward Nats. The inclusion of airline demands for

How each side covered it

The same event, grouped by the political lean of the outlets covering it.

How each side covered it

Support independent, bias-aware news and unlock the social pulse, community voting, and every other Supporter feature.

Become a Supporter

Covered around the world

The same event as reported in other countries.

Covered around the world

Support independent, bias-aware news and unlock the social pulse, community voting, and every other Supporter feature.

Become a Supporter

Claims check

Key factual claims, and how many sources assert vs dispute each.

Claims check

Support independent, bias-aware news and unlock the social pulse, community voting, and every other Supporter feature.

Become a Supporter

Keep the news honest.

ObjectiveNews is reader-funded and ad-free — we show you the bias instead of hiding it. Support independent journalism for €4/month.

Become a Supporter

Related stories