NATS Air Traffic Control Failure Cancels Nearly 300 UK Flights On September 8

AirMedia24 Home / News Neha · 7 min read · September 8, 2026 Photo Credit: nats.aero Metric Event Details System affected NATS flight processing system Date September 8, 2026 Flights cancelled Nearly 300, per Flightradar24 (up from around 200 earlier in the afternoon) Airports hit hardest Heathrow, Gatwick, Manchester, Stansted, Birmingham, East Midlands, Edinburgh, Glasgow, Aberdeen Also affected Dublin Airport, because many Irish routes run through UK-controlled airspace Root cause Fault in NATS's flight processing system; not yet confirmed if linked to the 2023 software failure Fix status Implemented around 16:40 BST; NATS says the system is "starting to recover" Casualties / injuries None reported Hardest-hit airline Ryanair, with more than 50 flights cancelled and over 65,000 passengers delayed NATS traced the problem to its flight processing system, the software that plans and sequences aircraft movements across UK airspace. Airspace itself stayed open. NATS did not stop flights outright. Instead, NATS reduced departure rates at major airports as a safety measure while engineers worked the fault. That single decision, spread across a full day of scheduled traffic, is what turned one software fault into a nationwide delay event. IMG SOURCE : nats.aero NATS has not said whether today's fault shares any code or infrastructure with the flight-plan processing failure that hit the network in August 2023. That earlier incident forced the cancellation of well over 1,000 flights and cost airlines more than £100 million in refunds and compensation, according to airline estimates reported by Reuters. The Civil Aviation Authority told NATS in 2024 to review its contingency plans after that failure. Which UK airports saw the worst delays? Heathrow took the heaviest hit. Departures paused around lunchtime and then resumed in a stop-start pattern through the afternoon. Gatwick, Manchester, Stansted, Birmingham, East Midlands, Edinburgh, Glasgow and Aberdeen all reported delays and cancellations of their own. Arrivals held up better in the early hours of the disruption, but some inbound flights were later held on the ground or diverted as the backlog spread. Dublin Airport felt the knock-on effect directly. Dozens of inbound and outbound flights out of Dublin were cancelled, not because of any Irish system fault, but because many routes between Ireland and continental Europe cross UK-controlled airspace. How many flights and passengers were affected? Flightradar24 put the cancellation count at close to 300 by late afternoon, a jump from roughly 200 earlier in the day. Ryanair alone reported more than 50 cancelled flights and over 65,000 delayed passengers, with some facing waits of up to eight hours. British Airways and easyJet both confirmed significant disruption without giving exact passenger numbers by the time of writing. IMG SOURCE : X Airlines are offering rebooking, refunds, meals and hotel accommodation where the rules require it. A NATS system failure of this kind typically counts as an extraordinary circumstance under UK/EU compensation rules, which limits cash payouts, though airlines still carry a duty of care for meals, hotels and rebooking regardless of the cause. What are Ryanair, British Airways and easyJet saying? Ryanair's response was the sharpest. Chief operating officer Neal McMahon called today's fault part of a repeated pattern and called on NATS chief executive Martin Rolfe to step down. McMahon pointed out that UK air traffic control charges paid by airlines have risen 28% since 2022, even as the network has suffered a string of failures since the major 2023 outage, including a June 2026 Bristol disruption. He argued that the government, the CAA and the NATS board should replace the airline's leadership. Transport Secretary Heidi Alexander struck a calmer tone, saying technicians had identified the fault and were fixing it, and apologizing to passengers for the disruption. She has not called for an inquiry or a change in NATS leadership. What passengers are reporting from the ground The pattern across dozens of traveler posts was remarkably consistent: long waits on the tarmac, thin communication from crew, and confusion over whether to stay on board or disembark. At Gatwick, one passenger, described sitting on the tarmac for three and a half hours with over 50 aircraft queued for takeoff, while their destination airport was due to close for the night at 10pm. That single post captures the core mechanic of today's disruption better than any official statement: a safety-driven slowdown at the source airport doesn't just delay one flight, it stacks up behind every aircraft scheduled after it. IMG SOURCE : nats.aero Other traveler accounts filled in details NATS and the airlines haven't addressed directly. A Malta-Gatwick flight boarded on time, sat for over ninety minutes, then had passengers disembark into an already crowded terminal once the delay stretched past a few hours. A Luton-bound crew reportedly warned passengers that forcing a return to the gate would trigger an outright cancellation rather than a further delay, a detail that points to crew duty-hour limits, not just the software fault, as a second constraint airlines were managing in real time. Several passengers at Gatwick and Stansted said they weren't offered water or food during multi-hour waits on board, and had to buy their own. Further out, an Almaty-bound Heathrow passenger woke up diverted to Frankfurt, and Arsenal's travelling squad had its flight to Naples for a Champions League fixture delayed by several hours, pushing arrival past 9:30pm local time. None of this is in the official NATS timeline. It's the texture of what a "reduced departure rate for safety" actually looks like for the people sitting on the aircraft, and it's the part of today's story wire coverage has largely left out. Is this part of a pattern of NATS failures? Today's fault is the third major NATS incident in three years: the August 2023 flight-plan processing collapse, a radar-related outage in 2025, and now a September 2026 flight processing fault. Ryanair has used near-identical language, a "pattern of repeated failure," after each one, including a smaller Bristol outage in June 2026. Independent aviation analysts had not published a detailed technical assessment of the September 8 fault by the time of writing; most public reaction so far has come from airlines, the Transport Secretary, and comparisons back to the 2023 incident rather than a fresh diagnosis. NATS has confirmed only that the fault sat in its flight processing system and that a fix is in place. There is no official confirmation of a cyber-related cause, despite some speculation circulating on social media. The open question industry voices keep returning to isn't really about today's specific bug. It's whether NATS's backup capacity and manual processing limits are still too thin for a network this busy, given that this is the third time in three years a single software fault has cascaded into hundreds of cancellations. What should affected passengers do next? Passengers with bookings today or tomorrow should check directly with their airline's app or website rather than NATS, since NATS doesn't handle rebooking. Recovery into September 9 will depend on where aircraft and crews ended up overnight, which means delays can carry over even after the underlying software fault is resolved. Anyone who was denied meals, water or a hotel during a qualifying delay should keep receipts and raise a claim with their airline directly.