120 Knots and No Runway Left: Inside the Rejected Takeoff That Shut Gatwick's Only Runway
Shortly after 2 p.m. on Friday, September 4, 2026, the crew of Norse Atlantic Airways flight Z0701 did something every airline pilot trains for but almost never has to do for real: they aborted a takeoff at speed. The Boeing 787-9 Dreamliner, bound for New York's John F. Kennedy International Airport, was accelerating down Gatwick's runway 26L when an indication of a fault with the nose landing gear appeared in the cockpit. At roughly 120 knots — well above taxi speed and closing in on rotation speed for a widebody jet — the crew rejected the takeoff, brought the aircraft to a stop on the runway, and declared the situation to air traffic control.
No one was injured. The aircraft did not leave the paved surface, and passengers were not evacuated onto the tarmac; instead, the 787 was towed clear after the runway was inspected. But the incident had an outsized effect on one of Europe's busiest airports for a simple structural reason: London Gatwick has only one operational runway. When that runway is blocked, the airport effectively stops.
What happened on the runway
A rejected takeoff, sometimes called an aborted takeoff, is one of the more demanding maneuvers in commercial aviation. Pilots continuously monitor a set of speed thresholds during the takeoff roll — most critically "V1," the speed beyond which a takeoff should generally be continued rather than aborted, because there may not be enough runway left to stop safely. Below V1, if a crew detects an anomaly, standard procedure calls for an immediate rejection: throttles closed, brakes applied, and in most cases the aircraft's spoilers and thrust reversers deployed to shed speed as quickly as possible.
According to Norse Atlantic Airways, the crew of Z0701 rejected the takeoff "following an indication of a potential technical issue" associated with the aircraft's nose landing gear. The airline confirmed the aircraft "stopped safely and was subsequently towed from the runway." Reporting on the incident, drawing on flight-tracking and airport data, put the abort speed at approximately 120 knots (about 222 km/h) — fast enough that the maneuver would have subjected the aircraft's brakes and tires to significant heat and stress, a routine consequence of high-speed rejected takeoffs that is factored into aircraft design and maintenance checks.
Emergency crews responded to the runway as a precaution, which is standard practice following any high-speed rejected takeoff, regardless of whether a fire or other hazard is confirmed. No fire was reported, and the aircraft was towed to a stand rather than requiring passenger evacuation via slides.
Why one runway means one bottleneck
Gatwick's operational model is built around intensive single-runway scheduling — it has, at times, held the record for the world's busiest single-runway airport by passenger volume. That efficiency comes with a tradeoff: there is no second runway to fall back on when the primary one is blocked.
The moment Z0701 came to a stop on 26L, air traffic control at Gatwick imposed a ground stop, holding departures on the ground until the runway could be inspected and cleared. Inbound aircraft already airborne had to be held, diverted, or resequenced. The runway was closed for approximately 50 minutes while the 787 was towed away and safety inspectors checked the surface — a standard step to confirm no debris, fluid, or damage remained that could pose a hazard, known in aviation as a FOD (foreign object debris) check.
The knock-on effects were immediate. Departures scheduled during the closure window were delayed on the ground. Some inbound flights, including easyJet services headed to Gatwick, were diverted to nearby airports such as London Luton and London Stansted rather than holding indefinitely for the runway to reopen. Flights to and from Spain were among those reported delayed, reflecting Gatwick's heavy leisure-route traffic on a Friday afternoon in early September, still within the tail end of the peak summer travel season.
The response and what happens next
Rejected takeoffs, even high-speed ones, are treated by airlines and regulators as an expected part of the safety system working as designed — the entire purpose of V1 speed calculations and abort procedures is to give crews a clearly defined, briefed, and trained-for course of action rather than an improvised one. Norse Atlantic's public statement was consistent with that framing: it confirmed the technical indication, the rejected takeoff, and the safe stop, without speculating on the underlying mechanical cause.
Consistent with international norms for the investigation of aviation occurrences — including the principles set out in ICAO Annex 13 — the precise nature of the nose landing gear fault has not been publicly detailed, and any determination of cause would typically follow a technical review by the airline's engineers, the aircraft manufacturer, and, depending on jurisdiction and severity, national investigators. As of this writing, no formal investigation body has published findings, and this article does not speculate on a mechanical cause beyond what Norse Atlantic and airport authorities have confirmed.
"[We can confirm] the aircraft stopped safely and was subsequently towed from the runway," Norse Atlantic Airways said in its statement following the incident — a brief, single-source confirmation that has not yet been supplemented by an independent investigative account, and readers should treat it as the airline's own characterization pending any regulatory review.
Gatwick's runway reopened after the 50-minute closure, and normal operations resumed, though the ripple effects of ground stops and diversions typically take longer to clear from a schedule than the closure itself — delayed aircraft and crews out of position can affect a hub's on-time performance for the remainder of the day.
Rejected takeoffs in context
High-profile rejected takeoffs periodically make headlines because of their visible drama — an aircraft screeching to a halt partway down a runway — but aviation safety data generally treats a successful reject as evidence that safety margins performed as intended, not as a near-miss in the colloquial sense. The V1/rejected-takeoff framework exists precisely so that a technical fault detected in the final seconds before liftoff results in a controlled stop rather than an airborne emergency with a known defect.
That said, high-speed rejects do carry real risk: overheated brakes have, in rare historical cases, led to fires after the aircraft has already stopped, which is why fire crews are dispatched as standard procedure and why aircraft are typically held in place for a cooling period before being towed. There is no indication in current reporting that Z0701 experienced any such secondary event.
For passengers, the more immediate consequence of incidents like this one is logistical rather than physical: delayed departures, missed connections, and diversions to alternate airports, borne out at Gatwick on September 4 by the diverted easyJet flights and the broader schedule disruption tied to the single-runway closure.
Norse Atlantic Airways has not indicated when the affected aircraft will return to service, and the airline's statement did not specify a maintenance timeline. This article will be updated if further details on the cause emerge from Norse Atlantic, Boeing, or aviation authorities.
Sources
- Gatwick runway reopens after 50-minute closure following Norse aircraft incident
- Norse 787-9 Rejected Takeoff at Gatwick Closes Runway
- Norse Atlantic Flight Boeing 787-9 Aborts Take-Off, Triggering Runway Closure in London Gatwick
- BREAKING: London Gatwick airport currently closed following Boeing 787 stuck on runway
- Spain flights disrupted as Gatwick shuts down its only runway after Boeing 787 aborts take-off