flight diversions

Crawley, United Kingdom: A Norse Atlantic Airways Boeing 787-9 rejected its takeoff from London Gatwick Airport on September 4, 2026 after a reported nose-gear problem, leaving the aircraft disabled on the runway and forcing the airport to temporarily halt flight operations. The aircraft, a Boeing 787-9 Dreamliner registered G-CKOF, was operating Norse Atlantic flight Z0701 from London Gatwick (LGW) to New York John F. Kennedy International Airport (JFK). It was accelerating for departure from Runway 26L when the crew rejected the takeoff at about 120 knots over the ground, according to preliminary aviation incident information. Reports said that the rejected takeoff followed a problem with the aircraft’s nose landing gear and that the nose wheels had turned about 90 degrees. The aircraft then stopped on the runway and became disabled. The precise technical cause of the nose-wheel movement has not been officially declared by the airline. The aircraft remained on Runway 26L while airport emergency teams responded. The incident did not result in any reported injuries among passengers or crew. A passenger onboard, Alice Kavanagh, described the moment the aircraft stopped as frightening, saying the pilot “slammed the brakes on” after a reported technical fault was detected. The Boeing 787 was subsequently removed from the runway. The aircraft blockage had an immediate effect on Gatwick because the airport effectively operates with one runway at a time. Although Gatwick has two runways, their proximity means they cannot normally be used simultaneously for independent operations. As a result, the closure of Runway 26L temporarily stopped both departing and arriving traffic. London Gatwick confirmed that the runway remained closed for 50 minutes because of the incident. “The runway was closed for 50 minutes this afternoon (Friday 4 September) due to a technical issue with a departing aircraft,” a Gatwick spokesperson said. “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.” The runway reopened after airport teams completed the required safety inspection. Subsequent reporting put the reopening at approximately 14:36 BST, although the airport’s official statement characterized it simply as reopening shortly after the aircraft was removed and the inspection was completed. The temporary closure created a wider disruption across Gatwick’s flight schedule. Several inbound flights were diverted to alternative airports, with London Luton and London Stansted among the destinations reported for diverted services. EasyJet flights were also affected by the disruption. Flight-tracking data later showed severe delays affecting more than 330 flights at Gatwick, with an average delay of about 57 minutes. The effects continued after the runway reopened because aircraft, crews and passengers had been displaced during the closure. For the incident, Gatwick has confirmed only that a technical issue involving a departing aircraft caused the runway closure. The more specific information concerning the nose gear and the reported 90-degree movement of the nose wheels remains preliminary. Further maintenance findings or an official investigation would be needed to establish the exact cause of the rejected takeoff.

Incidents

Norse Atlantic Rejects Takeoff At Gatwick After Reported Nose Gear Issue, Runway Closed

Aviation Today News Desk / September 5, 2026

Crawley, United Kingdom: A Norse Atlantic Airways Boeing 787-9 rejected its takeoff from London Gatwick Airport on September 4, 2026 […]

London, United Kingdom: A technical fault on a British Airways aircraft after landing at London Gatwick Airport in the early hours of 15 July 2026 triggered significant disruption across southern England, forcing the temporary closure of the airport's single runway and leading at least nine inbound passenger flights to declare emergencies as fuel levels became critical following prolonged airborne holding. The disruption began shortly after midnight when a British Airways flight arriving from Palma de Mallorca, Spain, landed safely at Gatwick at approximately 00:12 BST. After touchdown, the aircraft experienced what the airline later described only as a technical fault, leaving it unable to immediately vacate the runway. Airport rescue and firefighting vehicles were dispatched as a precaution while the aircraft remained stationary on the runway. British Airways confirmed that the aircraft landed safely and that passengers were not placed in danger. "Our flight landed safely and customers disembarked normally following reports of a technical fault with the aircraft," a British Airways spokesperson said. Although the airline has acknowledged the technical issue, it has not disclosed the nature of the fault, the aircraft type, or the aircraft registration. Gatwick Airport has likewise not released further technical information regarding the incident. Because Gatwick operates with a single main runway, the disabled aircraft temporarily prevented arriving flights from landing while emergency responders assessed the situation and efforts were made to clear the runway. During the closure, aircraft already inbound to Gatwick were instructed to enter holding patterns while air traffic controllers worked to manage the growing congestion. As delays lengthened, at least nine inbound flights declared emergency or urgency conditions after fuel reserves fell to operationally critical levels. Flight tracking data cited by multiple media outlets indicated the declarations were associated with low-fuel situations resulting from the extended airborne holding rather than mechanical problems aboard the affected aircraft. Nine flights squawked the 7700 emergency transponder code, reportedly due to low fuel after extended holding. An additional five flights were also diverted to alternate airports. Of the 14 affected flights, five landed at London Luton Airport, four at London Stansted Airport, and one at London Heathrow Airport. The remaining diversions were outside London, with three flights landing at Birmingham Airport and one at Bristol Airport. Several of the affected flights had departed popular Mediterranean holiday destinations, including Lanzarote, Rhodes and Tenerife, before being forced to abandon their approaches to Gatwick. Some aircraft diverted to London Stansted Airport, while others were rerouted to London Luton Airport after determining they no longer had sufficient fuel to continue holding safely. One passenger travelling from Tenerife, whose flight diverted to Stansted instead of Gatwick, posted on social media that passengers remained on board awaiting instructions while airline staff determined the next steps. The traveller said the journey had become considerably longer than normal because of the diversion. The runway was eventually reopened after the British Airways aircraft was moved, allowing Gatwick to resume normal operations. However, the temporary closure caused knock-on delays affecting arrivals and departures during the overnight and early morning operating period. No injuries have been reported in connection with either the British Airways aircraft or any of the diverted flights. Authorities have not announced an investigation beyond the airline's technical inspection of the aircraft, and the exact cause of the fault remains unknown. As of the latest available updates, British Airways has not released additional operational details.

Incidents

BA Technical Fault Shuts Gatwick Runway, Nine Flights Declare Low-Fuel Emergencies

Aviation Today News Desk / July 15, 2026

London, United Kingdom: A technical fault on a British Airways aircraft after landing at London Gatwick Airport in the early

Athens, Greece: A government-appointed investigation has concluded that last week’s eight-hour communications blackout in Greek airspace at Athens International Airport was caused by outdated and unsynchronised systems, not a cyberattack, exposing critical infrastructure vulnerabilities in one of Europe’s busiest flight regions. On January 4, radio communications across the Athens Flight Information Region (FIR) collapsed in a “blackout” that forced authorities to clear the airspace, ground departures and divert incoming flights for several hours. The incident left thousands of passengers stranded and triggered delays that rippled through European air traffic networks. According to the official report submitted to Infrastructure and Transport Minister Christos Dimas, the root cause was desynchronisation and “digital noise” in legacy telecommunications hardware supporting the Greek Civil Aviation Authority’s (HCAA) voice communication system. The systems rely on Synchronous Digital Hierarchy (SDH) technology no longer supported by manufacturers, leaving them vulnerable to failures without modern operational guarantees. The expert panel, which included representatives from the HCAA, national cybersecurity authority, telecom regulator and EUROCONTROL, confirmed there were no indications of a cyberattack or external interference. Full restoration occurred after telecommunications circuits were resynchronised and rerouted, with services returning to normal by approximately 16:53 local time. The incident was classified as “low risk” under aviation safety reporting criteria, with no breaches of minimum separation standards or evidence that aircraft were exposed to direct threat, according to the report. In the wake of the findings, HCAA governor Giorgos Saounatsos resigned at the request of Minister Dimas, who said the report underscored serious weaknesses in air traffic management infrastructure. Deputy governor Giorgos Vagenas will serve as interim head while the process to appoint a new administrator begins. The investigative committee recommended a rapid transition to Voice over IP (VoIP) communications, acquisition of nearly 500 new transceivers, and the establishment of a permanent joint crisis-response mechanism between the HCAA and national telecom provider OTE. It also called for improved remote monitoring, stronger spectrum oversight and relocation of critical facilities to reduce systemic risk. A ministry statement said plans to modernise Greece’s air traffic communications are underway but not expected to be complete before 2028, leaving systemic vulnerabilities in place as the nation prepares for its peak summer travel season. Air traffic controllers’ unions and aviation safety experts have long warned that ageing infrastructure and equipment obsolescence posed escalating operational risks. Following release of the committee’s findings, controllers stressed that safety on January 4 was maintained chiefly through manual procedures and emergency protocols, not because of robust systems. They have urged immediate action to align Greece’s air navigation capabilities with modern European standards.

Airports

Greek Government Report Links Jan 4 Athens Blackout To Outdated Systems, No Cyberattack

Aviation Today News Desk / January 21, 2026

Athens, Greece: A government-appointed investigation has concluded that last week’s eight-hour communications blackout in Greek airspace at Athens International Airport

Facebook-f Instagram Linkedin-in X-twitter Youtube

AVIATION TODAY brings the latest in aviation and aims to cater information to professionals and Aviation Enthusiasts about the Industry.

Quick Links

About Us
Contact Us
Services
Advertise
FAQ

Navigate

Latest News
Civil Aviation
Pilot Training
Flight School Analysis
Aviation Jobs
Training

General Support

info@aviationtoday.in

News Desk Support

news@aviationtoday.in

Facebook-f Instagram Linkedin-in X-twitter Youtube

Terms of Use
Privacy Policy
Disclaimer

About Us
Latest News
Aviation Today Perspectives
Aviation Jobs
Contact Us
Advertisement

Aviation Newsletter

Facebook Instagram Linkedin X-twitter Youtube