Gatwick Airport Runway Reopens After Norse Aircraft Rejects Takeoff, Grounds Flights for 50 Minutes
Why It MattersSingle-runway airports remain fully exposed to one aircraft's rejected takeoff, showing how a brief technical stoppage can pause an entire operation until inspection clears it.
What happened
Gatwick Airport's runway was closed for approximately 50 minutes on Friday, September 4, after a departing Norse aircraft rejected takeoff while bound for New York's John F. Kennedy International Airport, leaving the plane stuck on the runway. All flights were temporarily grounded during the closure.
The airport confirmed the aircraft was subsequently towed from the runway, which reopened following a full safety inspection. A London Gatwick spokesperson said: "The runway was closed for 50 minutes this afternoon due to a technical issue with a departing aircraft. The aircraft was towed from the runway, which reopened shortly afterwards following a full safety inspection. As always, safety and security is our number one priority."
Industry impact & what to watch
A rejected takeoff is a standard abort procedure, but at an airport with a single operating runway it converts one aircraft's stoppage into a system-wide halt until the runway is inspected and cleared. Gatwick's 50-minute closure shows how quickly that inspection-and-tow sequence plays out when procedures work as designed.
What determines the next few days is whether Norse or investigators identify the technical issue that triggered the abort, and whether it points to an isolated fault or a pattern worth tracking across the airline's fleet.
