More news on this day
Flights at London Gatwick were temporarily grounded on Friday 4 September after a Norse Atlantic Boeing 787 rejected its takeoff and became stuck on the airport’s single runway, triggering diversions and delays for hundreds of passengers.
Get the latest news straight to your inbox!
Runway closure after aborted takeoff
Publicly available flight tracking data and aviation incident reports indicate that the disruption began when a Norse Atlantic UK Boeing 787-9, operating flight Z0701 from Gatwick to New York JFK, accelerated for departure on runway 26L and then carried out a high-speed rejected takeoff due to a problem with the nose landing gear. The widebody jet came to a halt on the main runway and was unable to vacate under its own power, effectively blocking the airport’s only active runway.
Specialist aviation coverage describes how the aircraft, registered G-CKOF, was accelerating at roughly 120 knots over the ground when the crew abandoned the takeoff, after which the jet remained disabled on the runway while airport ground teams and emergency vehicles surrounded the aircraft and assessed the situation.
Reports from multiple outlets note that London Gatwick, which normally operates as a single-runway hub, declared an immediate stoppage on movements while the aircraft was secured and prepared for towing. With no parallel runway available for arrivals or departures, even a relatively short closure quickly translated into widespread schedule disruption.
Aviation incident summaries state that the jet was eventually towed clear of the active runway once its landing gear issue had been stabilized, allowing safety inspections of the surface and reopening of the airfield for regular operations.
Fifty-minute shutdown triggers diversions
According to published coverage from aviation news sites and general news outlets, the runway at Gatwick remained closed for around 50 minutes on the afternoon of 4 September while specialists worked to remove the stranded aircraft and confirm the condition of the pavement. During that period, departures were held on the ground and inbound flights were either placed in holding patterns or diverted to alternative airports.
Reports referencing live air traffic data show that several aircraft bound for Gatwick diverted to other London-region airports while the runway was unavailable, reflecting how little slack exists in the schedule at one of Europe’s busiest single-runway airports. Social media posts highlighted long lines of aircraft waiting on taxiways, with ground vehicles clustered around the disabled 787.
Coverage from travel-focused outlets explains that once the Norse aircraft was towed away and the runway surface inspected, movements resumed, but the earlier grounding left a backlog of flights. Even after the official reopening, knock-on delays continued into the evening as airlines worked to recover their schedules.
Analysis in aviation publications notes that a sub-one-hour stoppage at a hub such as Gatwick can take many hours to unwind, particularly on a busy Friday schedule in early September when load factors and frequencies remain high following the summer peak.
Impact on passengers and airlines
Travel reports and passenger accounts on social media describe queues in both terminals as travelers faced delayed departures and uncertain arrival times. Some passengers reported sitting on parked aircraft that had already boarded but were unable to push back while the runway remained closed. Others indicated that they missed onward connections or had to rebook onto later flights after diversions.
Consumer and travel coverage notes that flights to popular leisure destinations, including services to Spain and other European holiday spots, were particularly affected because many were due to depart during the afternoon closure. With departure slots tightly managed at Gatwick, some flights experienced extended delays while airlines waited for new departure windows to be allocated once operations restarted.
Commentary from aviation analysts quoted in published reports suggests that airlines affected by cancellations or long delays will need to manage rebooking and, in certain cases, duty-of-care obligations for stranded passengers under applicable air passenger regulations. Where flights diverted away from Gatwick during the closure, travel advice pieces emphasize that carriers remain responsible for transporting customers to the destination listed on their ticket.
Travel-industry reporting also highlights the operational challenges for airlines using long-haul aircraft, such as the Boeing 787 involved in the incident. Disruption on an outbound transatlantic rotation can echo through subsequent services, potentially affecting aircraft positioning and crew schedules for days after the original event.
Why a single runway magnifies disruption
Background information on London Gatwick’s operations shows that the airport handles a high volume of traffic using essentially one main runway for scheduled commercial movements. While a closely spaced standby runway exists, it is generally not used for routine operations and regulatory and infrastructure constraints limit its use as a simultaneous parallel runway.
Industry reports and historical performance documents for Gatwick have long highlighted the vulnerability of single-runway airports to temporary blockages, whether caused by disabled aircraft, runway inspections or debris removal. Even a short interruption can quickly generate queues of arrivals and departures, as there is no ability to shift traffic to a second independent runway.
Aviation analysts writing about the latest incident point out that high levels of runway utilization leave little margin for recovery. During busy periods, aircraft are often sequenced with narrow spacing to maximize throughput, so any unexpected stoppage requires controllers to break that sequence, hold or divert aircraft and then gradually rebuild the flow once the runway is available again.
Travel and infrastructure commentators note that similar events at Gatwick in previous years, including earlier nose-wheel steering issues on other aircraft, have periodically forced short runway closures and delays. The latest disruption reinforces ongoing debates about resilience at capacity-constrained UK airports and the trade-offs between maximizing runway use and maintaining operational flexibility.
Ongoing reviews and advice for future travelers
Aviation safety databases indicate that the Norse Atlantic incident will now be subject to detailed technical and operational review, focusing on the performance of the aircraft’s nose landing gear, the crew’s decision-making during the rejected takeoff and the effectiveness of the airport’s response procedures.
Travel news outlets report that services at Gatwick have since returned to normal patterns, but schedules on the evening of 4 September and the morning of 5 September still displayed residual delays and some aircraft operating out of their usual rotations. Passengers on affected flights were advised through airline channels and airport information platforms to monitor their booking status closely.
For travelers with upcoming journeys through Gatwick, travel experts quoted in consumer reporting recommend allowing extra time at the airport during periods of heightened disruption risk, such as peak holiday travel dates, and ensuring that contact details with airlines are up to date so that any schedule changes can be communicated quickly.
Analysts commenting in industry publications add that while high-profile runway blockages are relatively rare events, they underline the importance of flexible travel planning, including considering travel insurance with disruption cover and opting, where possible, for itineraries with sufficient connection times at busy single-runway hubs.
Norse Atlantic Boeing 787 rejected takeoff coverage
Runway closure and reopening timeline