More news on this day
Flight disruption across the UK is expected to ease as airlines rebuild schedules following a major technical issue at National Air Traffic Services (NATS), while renewed calls mount for chief executive Martin Rolfe to resign after days of cancellations and delays.
Get the latest news straight to your inbox!

What happened, and why the recovery is expected to improve
Published coverage indicates the disruption was triggered by a technical issue affecting NATS flight planning and processing systems, creating knock-on delays and cancellations across multiple airports. The incident hit at a busy point in the week, leaving airlines to reposition aircraft and crews while passengers faced missed connections and last-minute rebookings.
Airports including London Heathrow and London Gatwick were among those affected, along with other major UK hubs. With systems restored and traffic management measures easing, airlines have been working through backlogs, and schedules are expected to move closer to normal as the week progresses.
While the immediate technical fault has been addressed, the operational recovery can lag by a day or more because airlines must re-sequence aircraft rotations, comply with crew duty-time limits, and restore disrupted aircraft positioning. That means a return to normal timetables depends as much on airline logistics as on air traffic flow.
Pressure on NATS leadership intensifies
The outage has reignited scrutiny of NATS resilience and governance, with Martin Rolfe facing calls to step aside from prominent industry voices. Ryanair chief executive Michael O’Leary has been among the most outspoken figures pushing for leadership changes, arguing that repeated disruption warrants accountability at the top.
Political attention has also sharpened. Reports describe government ministers seeking rapid explanations and short timelines for initial reporting on the cause of the outage and what safeguards will follow. Publicly available coverage also indicates the incident was linked to NATS systems at the Swanwick site, a critical part of the UK’s air traffic management network.
NATS has been under particular pressure because previous large-scale disruptions have remained fresh in the public memory, raising questions about whether lessons were fully implemented and whether redundancy planning is adequate for peak travel periods. Even when an incident is unusual, repeated system-wide consequences can damage trust among airlines and travelers.
What passenger rights look like after an air traffic control failure
For travelers, the key question after large disruptions is often compensation. UK Civil Aviation Authority (CAA) guidance indicates that when delays or cancellations are caused by extraordinary circumstances outside an airline’s control, compensation is generally not due under UK passenger rights rules, even though airlines still have obligations to provide care.
In the wake of the NATS disruption, CAA messaging has pointed travelers toward a distinction that can surprise passengers: compensation is separate from the right to assistance. Even where a cancellation stems from air traffic control disruption, airlines are still expected to provide support such as meals, refreshments, hotel accommodation where needed, and alternative transport or rerouting options, depending on circumstances.
Travelers who incurred out-of-pocket costs during extended delays often look for reimbursement routes. CAA materials encourage passengers to keep receipts and to engage with airlines first, and then use dispute resolution routes where applicable if claims stall. The practical outcome can vary by carrier and the specifics of a journey, including whether flights were on a single booking or a self-transfer itinerary.
How airlines and airports are managing the return to normal
Even once the airspace system stabilizes, airlines must unwind a complex series of disruptions. Aircraft may be in the wrong city, crews may be out of position, and maintenance plans may need reshuffling. Airports also face terminal-side pressure, as passenger surges can appear at rebooking desks and security lanes when large numbers of travelers are moved onto later flights.
Operationally, airports can also experience delayed recovery due to gate availability and arrival sequencing. If inbound flights are late, turnaround times tighten, and that can create further delays later in the day. Published coverage has described scenes of passengers waiting in terminals, especially at major London airports, as the system moved from immediate disruption into the longer recovery phase.
Airlines have been emphasizing flight-status checks and advising passengers to confirm operations before traveling to airports, a standard approach during irregular operations. For travelers, that can mean monitoring carrier apps and airport departure boards closely, particularly for early-morning rotations that depend on late-arriving aircraft from the previous night.
What comes next for UK aviation oversight and system resilience
The disruption lands amid a broader UK policy discussion about aviation resilience, passenger protection, and enforcement. Public information from the UK government shows work underway on aviation legislation aimed at modernizing airspace and strengthening the enforcement toolkit available to the CAA, including the ability to act against operators that fail to meet passenger-support obligations.
At the same time, the NATS incident is likely to intensify scrutiny of technology governance, backup procedures, and stress-testing for peak demand. For travelers, the immediate concern is whether operations remain stable through the next high-volume travel period and whether airlines can keep recovery on track without rolling cancellations.
The leadership question at NATS is now interwoven with those operational and policy debates. Even as flight schedules normalize, the incident’s aftermath is likely to be measured in investigations, reporting deadlines, and the extent to which airlines, regulators, and government pursue structural changes rather than treating the outage as a one-off event.