More news on this day
Passengers using London Gatwick on Sunday, September 6 are still encountering delays and a limited number of cancellations after a technical issue involving a departing aircraft blocked the airport’s single runway on Friday and led to widespread disruption.
Get the latest news straight to your inbox!
How Friday’s runway problem triggered a weekend ripple effect
Publicly available information indicates that the disruption began on Friday, September 4, when a Norse Atlantic Boeing 787 operating flight Z0701 to New York JFK rejected its take off on Gatwick’s main runway shortly after 14:00 local time. Aviation incident reports and live blogs describe the aircraft stopping on the runway with an apparent nose landing gear issue, prompting emergency vehicles to attend the scene and forcing an immediate ground stop at the single runway airport.
Coverage from UK news outlets states that the runway remained closed for around 50 minutes while the aircraft was towed clear and a full safety inspection was completed before operations were allowed to resume. During that window, all take offs and landings were paused, with multiple arrivals diverted to other London airports and departures held on the ground. Data collated by aviation tracking services shows departure delays of up to two hours for some short haul services on Friday afternoon and evening as the schedule was reset.
Travel industry reporting highlights that even after the runway reopened, the concentration of flights around peak afternoon and early evening banks meant aircraft rotation plans were disrupted, leaving some jets and crews out of position for later services. That operational imbalance is a key factor behind the lingering disruption now being seen on Sunday, as airlines work through backlogs and attempt to restore normal rotations heading into the new week.
The event has once again underlined the operational sensitivity of Gatwick’s single runway layout. With no parallel runway to absorb an incident, any blockage on the main strip can rapidly translate into cascading delays that extend well beyond the initial closure period.
Delays and cancellations recorded so far on Sunday
Regional news aggregation focused on London Gatwick reports that, by mid morning on Sunday, September 6, the airport was still seeing a mixture of minor and more pronounced delays across both North and South terminals. A snapshot of the departures and arrivals boards shows a pattern in which many flights are operating, but with schedule slippages typically ranging from 15 to 60 minutes for short haul services.
Flight tracking data for specific routes supports this picture. An Aurigny service from Gatwick to Guernsey, for example, departed around 15 minutes behind schedule on Sunday evening and arrived roughly 12 minutes late, indicative of modest but persistent knock on delays on regional sectors. Other services to Mediterranean leisure destinations and major European hubs are also shown operating with late departures and slightly pushed back arrival times.
Local coverage summarising the situation at Gatwick on Sunday notes a limited number of outright cancellations affecting both inbound and outbound services. These appear to be concentrated on flights where aircraft and crews were significantly displaced by Friday’s events or where airlines have opted to consolidate frequencies to rebuild resilience in their rosters. While the overall scale of Sunday’s disruption is far smaller than the near total halt seen on Friday afternoon, passengers are still being advised through public channels to check the latest status of their flight before travelling.
By early afternoon on Sunday, there were signs that punctuality was gradually improving as airlines worked through earlier delays. However, with aircraft still cycling through rotations that began after the runway incident, some degree of knock on impact is expected to persist through the end of the operational day.
Which routes and airlines have been most affected
Analysis of published flight data and media coverage points to a broad spread of disruption across Gatwick’s network following Friday’s runway closure. On the day of the incident, low cost carriers with dense Gatwick based operations, including large numbers of European city and holiday flights, experienced the most significant initial delays and diversions. Several short haul arrivals were rerouted to alternative London airports such as Luton and Stansted while the runway was unavailable, adding complexity to aircraft positioning for subsequent legs.
Long haul services were also affected by the closure and later knock on delays. Reporting from travel and aviation outlets notes that flights bound for North America and popular leisure destinations in Spain and the Mediterranean departed later than scheduled on Friday, with some arrivals into Gatwick on Saturday landing behind timetable. That contributed to further pressure on stand availability and turnaround times during one of the busier weekends of late summer travel.
By Sunday, the pattern of impact had shifted from acute disruption on specific carriers to a more generalised environment of minor delays across multiple airlines. Regional and island routes, such as services to the Channel Islands, provide clear examples of how a relatively short delay on departure can ripple into later evening schedules. Meanwhile, a small number of Sunday services appear to have been withdrawn entirely, likely as part of airline efforts to simplify rotations and restore operational stability ahead of Monday’s business travel peak.
Despite these challenges, the majority of Gatwick’s Sunday schedule is operating, with flight boards showing far more on time or slightly delayed services than cancellations. Passengers face inconvenience rather than widespread trip cancellation, although missed onward connections remain a risk where delays exceed an hour.
Advice and key takeaways for travellers using Gatwick
Public information from Gatwick and airlines serving the airport consistently emphasises the importance of checking flight status before departing for the terminal, particularly in the wake of significant operational incidents such as Friday’s runway closure. While the airport itself continues to function, aircraft and crew displacement can lead to last minute gate changes, equipment swaps, or schedule revisions that are best monitored through airline apps and official flight tracking tools.
Travel coverage of the incident notes that passengers whose flights were heavily delayed or cancelled on Friday and Saturday may be eligible for rebooking, refunds, or in some cases statutory compensation depending on the circumstances, airline and route involved. Those travelling on Sunday are less likely to encounter long multi hour delays directly tied to the technical issue, but should still build in extra time at the airport given the potential for longer queues at check in and security during recovery periods.
The events of the weekend have renewed attention on Gatwick’s infrastructure constraints. Industry commentary has repeatedly highlighted that the airport’s dependence on a single main runway leaves it particularly exposed when an aircraft becomes disabled on the strip, whether through a technical malfunction, tyre failure or rejected take off. Even a relatively short closure window, such as the approximate 50 minute stoppage seen on Friday, can translate into a full afternoon of delays and a multi day recovery as schedules are realigned.
For travellers planning to use Gatwick over the coming days, the most practical steps remain straightforward: monitor airline communications closely, allow additional time at the airport, and be prepared for minor timing changes even as the operation gradually returns closer to normal levels of punctuality.
Context: Gatwick’s recent history of disruption
The latest incident slots into a broader backdrop of operational challenges at London Gatwick in recent years. Reports on the airport’s performance have highlighted repeated bouts of disruption stemming from issues such as air traffic control staffing constraints, airline crew shortages and wider system problems including IT outages that have affected multiple carriers in peak travel periods.
Consultative committee minutes and independent analyses of Gatwick’s punctuality show that late running aircraft and overnight knock on delays have been recurring themes, particularly where schedules are densely packed on the single runway. During high season, even minor technical issues or short lived weather disruptions can lead to significant congestion as controllers and airlines attempt to recover lost time within limited spare capacity.
Friday’s technical issue involving the Norse Atlantic aircraft is distinct from these broader structural factors, but its impact has been magnified by the same underlying realities. With limited flexibility to reroute traffic within the airfield and a busy weekend programme already in place, the temporary runway closure quickly translated into diversions, extended holding patterns and late arrivals that are still echoing through Sunday’s timetable.
While full investigations into specific aircraft malfunctions sit with regulators and operators, publicly available information about the Gatwick incident underscores how quickly a localised technical problem can affect thousands of passengers when it occurs at a single runway hub operating near capacity. That dynamic is likely to remain a central consideration in planning discussions around Gatwick’s future resilience and capacity management.
ITV News Meridian coverage of the Gatwick runway closure
BBC report on planes grounded after aircraft stuck on runway
Airlive incident summary of the Boeing 787 rejected take off