Gatwick runway closure leaves flights grounded after aircraft incident

Flights at London Gatwick were brought to a standstill on Friday afternoon after a departing long-haul aircraft became stuck on the single main runway, forcing a temporary halt to all movements and triggering diversions across the southeast of England.

Runway closure halts operations for nearly an hour

Publicly available information indicates that the disruption began on the afternoon of 4 September 2026, when an outbound aircraft experienced a technical problem during its departure roll and came to a stop on Gatwick’s runway. Reports from multiple outlets describe the aircraft as a Boeing 787 operated by Norse Atlantic Airways, preparing to operate flight Z0701 from Gatwick to New York JFK.

Accounts from aviation tracking services show that the crew rejected take-off at high speed, reportedly due to an issue affecting the aircraft’s nose landing gear. The jet became disabled on the runway and could not vacate under its own power, leaving Gatwick’s primary runway blocked.

According to published coverage, the airport closed the runway for approximately 50 minutes while ground teams attended the aircraft and arranged for it to be towed clear. During this period, Gatwick’s status as an effectively single-runway airport meant that both arrivals and departures were paused, with inbound flights placed in holding patterns or diverted to other airports.

Once the aircraft had been removed, the runway underwent a safety inspection before operations resumed. Reports indicate that flights gradually restarted, but schedules remained disrupted into the evening as airlines worked through delays and repositioned aircraft and crew.

Passengers face delays, diversions and extended journeys

With the runway closed, aircraft inbound to Gatwick were unable to land and several were diverted to other London-area airports, including London Stansted and Birmingham. Flight-tracking data and local media reports show multiple aircraft breaking off approaches and rerouting as controllers worked around the sudden loss of capacity at one of the UK’s busiest airports.

Travellers reported extended time in the air as aircraft entered holding patterns over the southeast before a decision was made to divert or continue to wait for the runway to reopen. For some passengers, this meant arriving at a different airport from the one originally booked, with onward rail or coach connections required to reach Gatwick or central London.

Departing passengers at Gatwick faced a different kind of disruption. With the runway unavailable, aircraft already boarded remained at stands or holding areas, and check-in queues grew as departure times slipped. Public guidance from airport channels and local news encouraged travellers to continue to arrive in good time for their flights but to monitor airline updates closely, as departure boards were subject to rapid changes.

Even after the runway reopened, knock-on effects continued as aircraft, crew and stands were out of position. Travel industry coverage suggests that delays and a small number of cancellations remained likely into the evening period, underscoring how even a relatively short closure can ripple through a tightly scheduled operation.

Technical issue with departing aircraft under scrutiny

According to aviation incident summaries and specialist reporting, the aircraft involved was a Norse Atlantic Airways UK Boeing 787-9 operating as flight Z0701 to New York JFK. Data from flight-tracking platforms indicates that the aircraft accelerated for take-off on Gatwick’s runway when the crew initiated a high-speed rejected take-off, bringing the aircraft to a controlled stop but leaving it unable to vacate the runway.

Early technical reports point to a problem with the nose gear or its steering system. Some outlets describe the jet as suffering a nose gear issue that left it stuck on the runway, surrounded by airport emergency and maintenance vehicles while a tow was arranged. There have been no reports of injuries among passengers or crew, and the aircraft was later moved from the active runway to allow a full safety inspection of the surface.

Industry observers note that high-speed rejected take-offs are relatively rare but are a standard safety procedure when crews detect a potential issue that could affect the aircraft’s ability to fly safely. In such cases, stopping on the runway and requesting assistance is treated as a precautionary measure while the technical fault is investigated.

Formal findings on the precise cause of the malfunction are likely to depend on subsequent engineering inspections and, if required, official investigation processes. For passengers, the immediate impact was less about the technical details and more about the resulting shutdown of Gatwick’s only active runway at a busy time of day.

Single-runway constraints highlight vulnerability to disruption

The incident has again highlighted the operational sensitivities associated with Gatwick’s single-runway configuration. While the airport has two physical runways, only one is used for routine take-offs and landings under normal operations, which means that any blockage can have an outsized effect on punctuality and capacity.

Recent aviation analysis has underscored how previous runway-blocking events at Gatwick, including earlier occurrences involving nose gear issues on other aircraft types, have quickly led to a build-up of holding traffic over southeast England and, in some cases, a series of fuel-related emergency declarations as aircraft divert or extend their flight times. The latest disruption appears shorter in duration than some past episodes but still created immediate knock-on effects for airlines and passengers.

Operational documents and meeting papers published by the airport and local consultative bodies have previously identified runway occupancy and unexpected stoppages as prominent causes of go-arounds and diversions. The latest incident fits within that broader pattern, demonstrating how a single technical event on one aircraft can temporarily halt one of Europe’s busiest short-haul hubs.

For travellers using Gatwick in the coming hours, publicly available guidance continues to emphasise the importance of checking live flight information directly with airlines and the airport before setting out, as schedules may take time to return to normal after the afternoon’s interruption.

What travelers should know if flying via Gatwick

Travel industry sources recommend that passengers due to depart from or arrive into Gatwick on the day of the incident stay in close contact with their airline and use official online arrival and departure boards to confirm the latest status of their flights. Even once immediate operations resume, aircraft and crew displacement can create residual delays or last-minute gate changes.

Those whose flights are diverted to other airports are generally advised to follow airline instructions on onward transport and rebooking options. In previous disruption events, carriers have arranged ground transportation back to Gatwick or into central London, although arrangements can vary by operator and ticket type.

For travellers with tight connections, same-day rail or coach links between London’s main airports and the capital can provide alternatives if a flight is re-routed. However, consumer advocates often stress the importance of allowing generous connection times when planning itineraries through single-runway airports with limited redundancy.

While Friday’s incident appears to have been resolved within an hour, it reinforces the value of flexible planning during busy travel periods. Monitoring live updates, keeping airline apps enabled for notifications and building in buffer time for onward journeys can help reduce the stress associated with sudden, technical disruption at major hubs such as Gatwick.

BBC: Planes grounded at Gatwick after aircraft stuck on runway

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

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

Airportia: Norse B789 at London on Sep 4th 2026 rejected takeoff