- Gatwick Airport closed the runway for 50 minutes after a departing aircraft rejected takeoff on September 4, 2026.
- The disabled Norse Atlantic Airways Boeing 787-9 Dreamliner was operating flight Z0701 to New York JFK.
- More than 330 flights faced knock-on delays, while some services diverted to Stansted and Birmingham.
- A separate, larger failure hit Gatwick on September 8 — a NATS flight processing fault, not a runway blockage.
Gatwick Airport grounded all flights on Friday, September 4, 2026, after a departing aircraft developed a technical issue and blocked the runway. The closure lasted 50 minutes, temporarily stopping departures and arrivals while airport teams moved the aircraft.
The incident began when a long-haul aircraft rejected takeoff and could not clear the runway. The shutdown was temporary, but its effects continued after the runway reopened.
A London Gatwick spokesperson said the airport was working to restore operations while prioritizing safety and security.
“Due to a technical issue with a departing aircraft, our runway is currently closed. Our teams are working to move the aircraft and resume operations as quickly as possible. As always, safety and security is our number one priority.”
The aircraft belonged to Norse Atlantic Airways and was a Boeing 787-9 Dreamliner operating flight Z0701 to New York JFK. It remained disabled on the runway after rejecting takeoff.
A report said the problem was believed to involve the landing gear. The available account identifies the issue as technical and does not establish a confirmed cause beyond that description.
The runway reopened, but disruption continued across the schedule
Airport teams towed the aircraft clear before reopening the runway. A full safety inspection followed.
Some flights diverted to London Stansted and Birmingham Airport during the closure. The diversions added another layer of disruption for passengers whose planned arrival or departure airport changed during the incident.
The airport returned to operation after the aircraft was removed and the inspection was completed. Delays, however, continued to move through the timetable.
| Disruption measure | Reported figure |
|---|---|
| Runway closure | 50 minutes |
| Flights affected by knock-on delays | More than 330 flights |
| Average airport delay | 57 minutes |
The delay figure covers knock-on effects rather than only flights directly blocked by the runway closure. A flight scheduled after the reopening could still face a later departure if its aircraft, crew or airport handling schedule had been affected earlier.
That pattern explains why the operational interruption ended before the wider passenger disruption did. The runway could reopen once it was clear and inspected, while individual airline schedules still needed to recover.
The airport’s passenger guidance focused on airline updates rather than a single airport-wide schedule. Individual carriers were handling the flight information for their own services, including changes caused by diversions and later delays.
The affected service was a transatlantic departure to New York JFK. Its aircraft type, operating carrier and flight number gave passengers a way to identify the service involved, while travelers on other flights faced the wider consequences of the runway closure.
The temporary shutdown also affected arrivals. With the runway unavailable, aircraft could not use the normal operating sequence, and some services were sent to the two alternative airports identified in the reports.
Operations resumed after the aircraft was removed
The runway reopened on September 4, 2026, after the disabled aircraft was moved and the safety inspection was completed. The immediate obstruction ended, but passengers were left to monitor airline updates as the remaining delays worked through the day.
Gatwick was grounded again four days later, for a different reason
On Tuesday, September 8, 2026, Gatwick departures stopped again. The cause had nothing to do with the runway. A failure in the flight processing system run by NATS, the UK’s air traffic control provider, halted departures at around 15 airports including Heathrow, Stansted, London City, Manchester, Birmingham, Bristol, Edinburgh and Aberdeen.
| September 4 | September 8 | |
|---|---|---|
| Cause | Aircraft rejected takeoff and blocked the runway | NATS flight processing system failure |
| Scope | Gatwick only | Around 15 UK airports |
| Duration | 50-minute runway closure | Ground stop from 12:48, resolved 19:30 BST |
| Arrivals | Stopped — single runway blocked | Unaffected — only departures were held |
| Reported impact | 330+ flights delayed, ~20 diversions | ~425 UK flights cancelled; 281 Gatwick movements delayed |
The distinction matters for passengers making a claim. A runway blocked by a disabled aircraft and a national air traffic control failure are both treated as extraordinary circumstances under UK261, so neither produces cash compensation. In both cases the airline still owes you meals, refreshments, hotel accommodation if you are delayed overnight, and a choice between re-routing and a full refund if your flight was cancelled. Full detail on those rights is in our coverage of the September 8 air traffic control failure.
