Planes Grounded at Gatwick After Jet Blocks Single Runway

Flights at London Gatwick were brought to a standstill on Friday afternoon after a departing long-haul aircraft became stuck on the airport’s single main runway, triggering a near hour-long suspension of operations and disruption for hundreds of passengers.

Runway closure halts take-offs and landings

Publicly available flight information shows that all movements at Gatwick were paused after a technical problem involving a departing aircraft blocked the runway shortly after 14:00 local time on 4 September 2026. The airport confirmed that the runway was closed while teams dealt with the stricken jet, which had come to a stop part way through its take-off roll.

Reports indicate that the interruption lasted for around 50 minutes before the aircraft was towed clear and the runway was declared safe to reopen. During the closure, no other planes were able to depart and arrivals were held in the air or rerouted to alternative airports.

Coverage from UK broadcasters and local outlets describes the situation as a full ground stop, with Gatwick’s status changing to show no departures able to leave and arriving flights either entering holding patterns or diverting away from the Sussex hub.

Norse Atlantic Boeing 787 involved in incident

Specialist aviation tracking sites and regional media identify the aircraft involved as a Norse Atlantic Airways UK Boeing 787-9, scheduled to operate flight Z0701 from Gatwick to New York JFK. Data from flight-tracking platforms indicates the twin-aisle jet accelerated along runway 26L before the take-off was rejected at high speed due to a problem with the nose landing gear.

The aircraft came to a stop on the runway and was initially unable to move under its own power, leaving it disabled on Gatwick’s only active strip. Images and accounts shared online describe a significant number of airfield vehicles clustered around the widebody jet as airport teams worked to secure and subsequently remove it.

According to published reports summarising the incident, the 787 was eventually towed from the runway and taken back to a stand for further inspection. There were no early indications of injuries, and the episode is being treated as a technical issue with the departing aircraft rather than a wider safety event at the airport.

Knock-on disruption and flight diversions

The runway closure quickly produced a ripple of disruption across Gatwick’s afternoon schedule. Regional news outlets report that several flights bound for the airport diverted to other UK airfields, including London Stansted and Birmingham, while others entered extended holding patterns over the south of England waiting for the runway to reopen.

Departing services were unable to leave during the 50-minute suspension, creating queues of aircraft on the ground once operations restarted. Travel coverage notes that delays were expected to continue into the evening as airlines worked through the backlog and repositioned aircraft and crews affected by diversions.

Guidance shared through airport and media channels advised passengers to continue travelling to Gatwick as normal but to check with their airlines for the latest information on specific flights. Travellers already in the terminal reported extended waits at departure gates as departure times were pushed back.

Single-runway vulnerability underlined

The incident highlights the operational sensitivity of Gatwick’s single-runway configuration. Unlike some other major European hubs that can switch traffic between multiple runways during an event, any blockage on Gatwick’s main strip has an immediate impact on the entire schedule.

Recent airport performance documents and community reports have noted that runway occupancy events, including aircraft with technical difficulties or precautionary inspections, remain a recurring cause of delays at busy periods. With Gatwick running a dense schedule of short- and long-haul services, even a short closure can quickly generate knock-on disruption for airlines and passengers.

Aviation analysts frequently point to such cases as examples of how high-intensity single-runway operations depend on rapid incident response and clear communication to limit the scale of disruption. Friday’s closure, while relatively brief, again demonstrated how an isolated technical fault can affect flights across the wider network.

What passengers should do next

Public information released in the aftermath of the closure indicates that Gatwick’s runway inspection was completed and operations resumed shortly after the Norse aircraft was removed. However, airlines warned that residual delays and potential cancellations were likely while schedules were reset.

Passengers due to travel through Gatwick in the hours following the incident are being advised in public guidance and media reports to monitor their airline’s app or website closely and to allow extra time at the airport. Those on diverted services are expected to be re-accommodated on later flights or provided with onward ground transport, depending on airline policies.

For travellers planning future trips, the event serves as a reminder to keep an eye on live departure and arrival boards and to build some flexibility into connections, particularly when travelling through large single-runway hubs during peak times.

BBC: Planes grounded at Gatwick after aircraft stuck on runway

ITV News Meridian: All flights grounded at Gatwick Airport due to technical issue

V2 Radio: Flights grounded at Gatwick after aircraft technical issue closes runway

Air Cargo Week: Gatwick flights grounded as Norse aircraft rejects take-off