More news on this day
London Gatwick Airport has reopened its main runway after a Norse Atlantic Boeing 787-9 Dreamliner bound for New York rejected its take off on Friday afternoon, briefly halting departures and arrivals and causing residual delays across one of Europe’s busiest single-runway hubs.
Get the latest news straight to your inbox!
Brief Runway Closure Follows High-Speed Rejected Take Off
Publicly available flight and operations data indicate that the incident occurred on the afternoon of 4 September 2026, when Norse Atlantic UK flight Z0 701 was accelerating for departure from runway 26L en route from London Gatwick to New York JFK. The Boeing 787-9, registered G-CKOF, aborted its take off at high speed and came to a stop on the runway, prompting the immediate suspension of movements at the airport.
Specialist aviation incident trackers report that the crew rejected the take off at around 120 knots over the ground following an apparent issue with the aircraft’s nose landing gear. The aircraft remained on the runway for an extended period while checks were carried out, effectively blocking Gatwick’s only active runway and forcing inbound flights into holds over southeast England.
Reports from aviation media and eyewitness accounts shared on flight-tracking forums describe emergency service vehicles attending the aircraft as a precaution. There have been no reports of injuries to passengers or crew, and initial coverage suggests that the event was contained to the runway environment without wider safety consequences.
According to multiple operational summaries, the 787 was later towed clear of the runway, allowing a full pavement inspection before traffic resumed. The aircraft is expected to undergo detailed engineering checks before returning to service.
Runway Reopens After Safety Inspection
Coverage from regional and aviation outlets indicates that Gatwick’s main runway was closed for around 50 minutes while the Norse aircraft was immobilised and recovery operations were undertaken. During that time, departures were held at gates and inbound flights were placed into holding patterns or diverted to other London-area airports.
Public information issued after the event describes the runway as having reopened only once a complete safety inspection was carried out and the aircraft had been removed. This sequence is consistent with standard practice following a high-speed rejected take off, where potential tyre, brake or debris risks must be ruled out before operations can safely resume.
Arrivals and departures gradually restarted once the runway was declared available again, although knock on disruption persisted into the evening as airlines worked through backlogs. Data from live flight-tracking services showed extended delays on short-haul services around peak Mediterranean and European leisure markets, alongside transatlantic departures that pushed back later than scheduled.
For passengers, publicly available advisories recommended monitoring airline apps, airport screens and carrier websites for revised departure times and potential rebooking options where connections were affected by the temporary closure.
Knock On Disruption Across Busy Late-Summer Schedule
The incident unfolded at a busy period for Gatwick, which handles a dense mix of short-haul European flights and long-haul leisure services, including Norse Atlantic’s transatlantic network. With most traffic funneled through a single operational runway, even a relatively short closure can quickly cascade into wider disruption.
Travel reporting from the region notes that flights to and from Spain and other popular holiday destinations were among those most affected, with some services holding for extended periods before landing, and others diverted to airports such as London Luton or Stansted. Low-cost carriers and leisure airlines with tight aircraft utilization schedules were particularly exposed to the resulting delays.
The timing of the rejected take off, in mid-afternoon ahead of the evening peak, meant that schedules had limited slack to absorb the interruption. As a result, delays of 60 to 90 minutes were reported on some routes through the remainder of the day, with a small number of flights cancelled or retimed into the next available operating window.
For Norse Atlantic, the incident adds operational complexity at a time when the carrier is continuing to build out its Gatwick-based long-haul offering with a fleet of Boeing 787-9s, split between own-brand routes and charter or wet-lease activity. Passengers booked on the New York service involved were advised through public channels to check updated timings once a replacement aircraft and crew plan could be confirmed.
Rejected Take Offs and Aircraft Performance Safety
A rejected take off is a standard safety procedure in commercial aviation, used when a significant technical or operational issue is detected during the take off roll before the aircraft becomes committed to flight. Training and regulatory guidance emphasise that crews should stop the aircraft if there is any doubt about its ability to take off safely, particularly prior to reaching the decision speed known as V1.
Aviation safety literature notes that at speeds near but still below V1, stopping distances remain sufficient for most large airliners to come to a controlled halt using maximum braking and, where fitted, automatic rejected take off systems. Inspecting the runway and the aircraft’s landing gear, tyres and braking systems afterward is routine, especially if there are indications of component overheating or damage.
While high-speed rejected take offs can be disruptive, industry data show that they are relatively rare compared with the overall volume of commercial departures at major hubs. When they do occur, operators typically prioritise conservative safety margins, even if that leads to extensive short-term operational impacts such as runway closures and diversions.
The use of modern widebody aircraft such as the Boeing 787-9, with advanced brake and monitoring systems, supports this safety-first approach by providing flight crews and engineers with detailed data on aircraft performance during and after such events.
Single-Runway Constraints Highlighted at Gatwick
The incident has again highlighted the operational sensitivity of Gatwick’s single-runway configuration. Although a second parallel runway exists, published information indicates that the airport ordinarily operates as a single-runway hub, with closely managed arrival and departure flows that maximise capacity but leave limited room for unexpected interruptions.
Recent corporate updates from Gatwick describe ongoing plans to bring its northern runway into more regular use in the coming years, a project that has progressed through planning and legal stages. Proponents argue that an expanded dual-runway operation would provide greater resilience to disruptions arising from incidents, weather or airspace constraints, by giving controllers and airlines more flexibility to re-route traffic when part of the airfield is unavailable.
Events such as the Norse Atlantic rejected take off underline how dependent current operations are on the continuous availability of a single strip of pavement. Any blockage, even if resolved within an hour, can swiftly result in extended airborne holding, diversions and crew scheduling challenges that spill over into subsequent waves of flights.
For now, the resumed use of Gatwick’s main runway, combined with standard recovery measures by air traffic control and airlines, is gradually returning operations to normal. However, analysts and local observers are likely to view the disruption as another case study in the balance between efficiency and resilience at busy single-runway airports.