- Heathrow stopped all departing flights at twelve forty-eight p.m. local time on September eighth, twenty twenty-six.
- The ground stop came after an air traffic control equipment failure affecting communications, while arrivals were not detailed.
- Gatwick was also mentioned, but live boards showed flights still operating there despite earlier disruption claims.
Heathrow halted every departing flight at 12:48 p.m. local time on Tuesday, September 8, 2026, after a technical failure hit air traffic control equipment. Airport management temporarily stopped outbound operations while technical teams worked to restore normal service. The ground stop affected departures, not an identified runway obstruction.
The failure involved an unexpected system issue affecting air traffic control communications and equipment. Technical staff began investigating the problem as the airport paused outgoing flights. Arrivals and the eventual lifting of the stop were not covered in the information available for this report.
Free toolB1/B2 Tourist Visa Stay Calculator online
A live report claimed that departures had also stopped at Gatwick. Public departure boards and flight-tracking data showed flights still operating there, as well as at the west London airport, rather than a complete shutdown at both sites.
One live flight-information page listed scheduled and recent departures on September 8, including British Airways and easyJet services. That activity conflicted with a claim that all flights had been grounded at the two airports.
The airport disruption followed a separate incident four days earlier. On Friday, September 4, 2026, a runway closed for 50 minutes after a departing aircraft developed a technical problem and rejected takeoff.
The Sussex airport has one runway. A disabled aircraft can therefore stop both arrivals and departures until crews remove it and complete a safety inspection.
The earlier runway closure sent aircraft to alternative airports
The September 4 incident involved a Norse Atlantic Airways Boeing 787-9 Dreamliner operating flight Z0701 from the airport to New York JFK. One account put the rejected takeoff at around 120 knots. The runway reopened at about 14:36 BST after the aircraft was towed away and the inspection finished.
The airport described the cause as “a technical issue with a departing aircraft” and said safety and security remained its “number one priority.”
The operational effects continued after the runway reopened. Friday delays ranged from 20 minutes to two hours, while tracking data later showed 90% of flights delayed, 8% cancelled and an average delay of 71 minutes.
Another account put the disruption at more than 330 flights severely delayed. It estimated roughly 3% cancellations and said around 20 flights due to land were diverted.
“While the runway at Gatwick is thankfully back up and running after earlier disruption, many passengers now find themselves displaced after some flights were forced to land at alternative airports.”
Which? said the disruption left some passengers displaced after flights landed elsewhere. The consumer group also said airlines remained responsible for completing the journey booked by affected passengers.
“If your flight was diverted as a result of the runway closure, your airline is responsible for ensuring you still reach the final destination on your ticket.”
That guidance concerns the September 4 runway event, not the September 8 air traffic control failure. The two incidents had different causes and separate timelines.
Recent airport disruptions came from different failures
| Incident | Cause or affected service | Reported outcome |
|---|---|---|
| September 3–4, 2026 | Signalling fault affecting the Elizabeth line and Heathrow Express | Reported at 15:22 on September 3 and cleared at 00:56 on September 4 |
| September 5, 2026 | Grass fire near the southern runway | Both runways were operational again after the fire was extinguished |
| September 8, 2026 | Air traffic control equipment failure affecting communications and equipment | All departing flights stopped at 12:48 p.m. local time |
The signalling fault affected rail links rather than aircraft movements. The grass fire also differed from the latest event because it occurred near a runway and was extinguished before both runways returned to operation.
The September 8 ground stop instead centered on control equipment. Airport management said technical teams were working to restore normal systems functionality while outbound flights remained paused.
The available flight data therefore supports a Heathrow-centered disruption rather than a simultaneous complete shutdown of both airports. The earlier single-runway closure caused its own delays, cancellations and diversions, but it was not the cause of the September 8 control-system failure.
