More news on this day
London Gatwick Airport experienced widespread disruption on Friday 4 September when a departing long haul aircraft became stranded on the main runway, forcing a temporary closure that grounded flights and triggered delays across the busy single runway hub.
Get the latest news straight to your inbox!
Runway Closure Follows Rejected Take Off
Publicly available information indicates that the disruption began when a Norse Atlantic UK Boeing 787-9 operating flight Z0701 from Gatwick to New York JFK rejected its take off and came to a halt on the runway on the afternoon of 4 September 2026. Flight tracking data and aviation coverage state that the aircraft then remained disabled on the runway while airport teams arranged for it to be towed clear of the active surface.
Reports from multiple news outlets describe the incident as a technical issue affecting the departing aircraft rather than a wider systems failure at the airport. The affected jet was identified in specialist tracking coverage as registration G-CKOF, with images from services such as Flightradar24 showing the wide body aircraft stationary on Gatwick’s single main runway while other flights circled in holding patterns nearby.
Local and national media summarised statements from the airport indicating that the runway closure lasted for around 50 minutes before the stranded aircraft was removed and a safety inspection was completed. During that period, no arrivals or departures were able to use Gatwick’s primary runway, creating an immediate backlog at an airport that relies heavily on tight scheduling to manage high volumes of traffic.
Coverage from radio and online outlets highlighted that passengers already at the airport initially faced limited real time information while the situation unfolded. Travellers were advised via public channels to continue to arrive on time for their flights but to check directly with airlines for the latest details as the operational picture evolved.
Knock On Delays and Diversions Across the Network
Because Gatwick operates in practice as a single runway airport for routine operations, the 50 minute closure quickly translated into wider disruption across the late afternoon and evening schedule. Local news reports and flight tracking data show that a number of inbound flights were placed in holding stacks south of London while decisions were made on whether to wait for the runway to reopen or divert to other airports.
Several flights diverted to alternate airports including Luton, Stansted and other regional hubs, according to live tracking platforms and user reports from affected passengers. At the same time, departures scheduled to leave Gatwick during the closure window remained at stands or were held on the ground, contributing to a build up of delays that extended well beyond the time the runway reopened.
Historic flight performance data published for 4 September shows multiple services from airlines such as easyJet operating with extended departure or arrival delays of around 40 minutes to more than an hour as the airport worked through the backlog. In some cases, later services in the schedule appear to have been cancelled entirely as airlines adjusted their operations to fit available runway slots after the incident.
Passenger accounts shared on travel and aviation forums describe long waits in departure lounges, late evening arrivals and missed onward connections as a result of the earlier runway closure. Some travellers reported that aircraft were ready at the gate but could not secure a new landing or take off slot at Gatwick once the evening peak of rescheduled flights and normal operations converged.
Gatwick’s Single Runway Operating Model Under Scrutiny
The incident has once again focused attention on Gatwick’s dependence on a single main runway for most commercial operations. Reference material on the airport’s infrastructure notes that Gatwick is one of the world’s busiest single runway hubs, typically handling hundreds of movements per day on its primary 3,316 metre strip. This operating model allows high levels of efficiency but leaves limited margin when the runway is blocked by an incident involving a single aircraft.
Even short interruptions can therefore have a disproportionate effect on the schedule, as demonstrated by the relatively brief 50 minute closure on 4 September generating hours of downstream disruption. Air traffic management documentation and previous case studies of runway blocking events show similar patterns, with holding, diversions and later cancellations often required to restore balance to the network.
The latest disruption follows other runway related events at Gatwick in recent months that have generated debate about capacity and resilience. Aviation community discussions have referenced earlier occasions where aircraft with landing gear issues or technical faults came to a stop on the runway, triggering temporary closures and prompting multiple inbound flights to declare fuel emergencies due to extended holding patterns over the south of England.
Government and planning documents note that Gatwick has received approval to make more regular use of its northern runway in the future, a development framed as a way to increase capacity and improve operational flexibility. However, the northern strip is currently used only in specific circumstances, and Friday’s incident occurred on the existing main runway that handles the majority of day to day traffic.
Advice for Travellers After the Incident
By early evening on 4 September, publicly available information from Gatwick and flight tracking platforms indicated that the runway had fully reopened and that arrivals and departures were operating again, albeit with residual delays. Local media reported that the affected Norse Atlantic aircraft had been towed from the runway and that a safety inspection found no wider damage to the surface.
Passengers planning to travel through Gatwick over the subsequent hours and into the weekend were advised through airline channels and online travel updates to check the status of their flights before setting off for the airport. While the immediate closure was limited to under an hour, recovery from such a disruption can take several hours as aircraft, crew and stands return to their planned positions in the schedule.
Travel industry commentators often recommend that during such events passengers keep digital boarding passes and airline apps updated, monitor airport websites for live departure and arrival boards, and allow extra time for security and boarding when services resume. Even when a runway has fully reopened, aircraft displaced to other airports or operating significantly late can create knock on effects across an airline’s entire network for the rest of the day.
For those who experienced cancellations or severe delays linked to the Gatwick runway closure, guidance from consumer bodies suggests reviewing airline communications and applicable regulations to understand what assistance or compensation may be available. Published commentary around the 4 September disruption notes that some evening flights were reportedly cancelled due to lingering air traffic flow restrictions, underlining the complexity of assigning responsibility when a single technical issue cascades through a tightly scheduled air traffic system.
https://www.lbc.co.uk/article/gatwick-airport-chaos-flights-grounded-5Hjdgyh_2/
https://nz.news.yahoo.com/gatwick-runway-shuts-flight-york-141639793.html