UK air traffic failure causes fresh cancellations at Heathrow as recovery continues

A technical failure in the UK air traffic control system on 8 September has continued to disrupt schedules and prompted fresh cancellations at major airports, with Heathrow among the worst affected as airlines work through a growing backlog.

What happened and the immediate fallout

The disruption began when a technical fault affected the flight data processing system operated by National Air Traffic Services (NATS). After the air traffic control failure, around 1 300 flights were reported cancelled; the original report did not specify that all cancellations occurred on a single day.

NATS restored the system on Tuesday evening, but the recovery has been slower than expected as airlines reposition aircraft and crews and try to rebook thousands of disrupted passengers.

Continuing cancellations and Heathrow’s situation

By Wednesday, reports said another 177 flights had been cancelled, with Heathrow accounting for the majority; the original reporting did not explicitly attribute this figure to Flightradar24.

Heathrow suspended arrivals for the rest of Tuesday when the fault first struck, though departures later resumed. The airport warned that the backlog would take time to clear and urged passengers to check their flight status before travelling.

Heathrow and NATS issued statements saying teams were working to resolve the technical issue and to restore normal operations.

Airlines and passengers affected

Multiple carriers were disrupted. Reports said that British Airways, EasyJet and Ryanair were among the European airlines affected, and that long‑haul operators such as Air India and Qatar Airways also experienced knock‑on delays and diversions. Passengers faced long delays, diversions and stranded travellers as airlines adjusted schedules.

Impact on UK–South Africa routes

Flight trackers continued to list Wednesday’s BA55, BA57, VS449 and BA59 services as scheduled when checked on Wednesday morning, meaning there was no blanket cancellation of direct UK–South Africa flights at that time. The original report stated that only a small number of nonstop flights connect London with Johannesburg and Cape Town each day; on Wednesday’s schedule four direct Heathrow–South Africa services were due to operate: three to Johannesburg and one to Cape Town.

The original report recorded delays to some South Africa‑bound services. British Airways flight BA55 from Heathrow to Johannesburg departed more than three hours late, leaving the gate at 22:15 instead of its scheduled 19:00 departure. BA59 to Cape Town also left late, with an actual departure at 23:32 versus a scheduled 22:30 time.

Advice for travellers

Passengers should check their flight status directly with their airline before travelling. The original report stated that airlines are urging travellers to verify bookings and to allow extra time for disruption while carriers work through the backlog.

What airlines and authorities say

NATS said the immediate technical problem had been resolved when it restored the system, and Heathrow echoed that teams were addressing the situation. Airlines warned that repositioning aircraft and crews would prolong disruption even after systems were back online.

Ongoing risks

With only a handful of direct services between London and South African cities each day, cancellations or late departures on long‑haul legs can leave fewer alternatives for affected passengers. Connecting travellers also risk missing onward flights if earlier sectors are delayed or cancelled.

The original report stated that travellers affected by disruption should check with their airline for rebooking and further assistance.

Editor’s note: Attributions and timing clarified to match the original source wording.