airport operations Archives

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.

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 […]

New Delhi, India: An Air India Airbus A320 operating flight AI2379 from Phuket, Thailand, to New Delhi encountered severe turbulence on Tuesday, August 4, leaving several passengers and cabin crew with minor injuries before the aircraft landed safely at Indira Gandhi International Airport (DEL). The incident occurred during the flight's final phase, although reports differ on the exact timing. While early media reports said the turbulence struck during the aircraft's descent into Delhi, Air India later clarified that the aircraft encountered turbulence while in cruise, resulting in a brief change in altitude. The Airbus A320, carrying 134 passengers, landed safely shortly after 11:00 a.m. IST. All passengers and crew disembarked normally after arrival, with Air India's airport and medical teams meeting the aircraft at the gate. According to PTI, 12 people, including passengers and cabin crew, sustained minor injuries during the turbulence event. Other reports indicated that around 10 passengers and two cabin crew members were taken to the Medanta medical facility at Delhi Airport for precautionary medical assessment. Seven passengers were later moved to Fortis Hospital in Vasant Kunj for further evaluation, scans, and observation. Air India said there were no serious injuries. Some early reports stated the aircraft experienced a sudden altitude drop of approximately 300 feet during the turbulence, causing unrestrained occupants to be thrown against the cabin interior and resulting in minor injuries. Air India, however, described the event as a "momentary change in altitude" without confirming the reported altitude deviation. Speaking to news agency ANI, a passenger on board the flight claimed the aircraft experienced a sudden jolt about an hour and a half into the journey while most passengers were asleep. According to the passenger, the aircraft abruptly dropped and swayed violently for nearly two to three minutes, leaving several people injured. In an official statement, Air India said, "The safety and well-being of our passengers and crew remain Air India's highest priority." The airline added that a small number of passengers and crew members requiring medical assessment were taken to the airport medical facility as a precaution and confirmed that it is providing all necessary assistance while cooperating with the relevant authorities reviewing the incident.

Incidents

Air India AI2379 Hits Severe Turbulence; 12 Injured Before Safe Landing In Delhi

Aviation Today News Desk / August 4, 2026

Update 05 August, 2026: Air India has since confirmed that flight AI2379 experienced a sudden loss of altitude during cruise

Chicago, United States: Southwest Airlines Flight 1243 experienced a landing incident at Chicago Midway International Airport on the morning of August 3 after both nose landing gear tires lost air pressure during touchdown, prompting an emergency response from airport and city fire crews. The aircraft was safely brought to a stop on the runway, and no injuries were reported. According to Southwest Airlines, Flight 1243 was operating from Southwest Florida International Airport (RSW) in Fort Myers, Florida, to Chicago Midway International Airport (MDW) when the incident occurred during landing. The airline said both nose landing gear tires lost air pressure while the aircraft was landing in Chicago. Chicago Fire Department crews responded to the aircraft shortly after it came to a stop on the runway. Video from the scene showed emergency vehicles surrounding the aircraft as first responders assessed the situation. The aircraft remained on the runway while emergency personnel and airline maintenance teams carried out initial inspections. Passengers described smelling burnt rubber and seeing light smoke after the aircraft stopped. Passenger Mya Castro told ABC7 Chicago, "I realized we stopped and we weren't close to getting off the plane, and then I could smell the burnt rubber." Another passenger, Brian Rigsby, said, "Once we did come to a stop, we could see smoke coming. Not excessive, but we knew something was wrong." Southwest Airlines confirmed that maintenance personnel replaced the damaged nose gear tires before the aircraft was towed from the runway to the terminal gate. The airline said passengers were able to deplane normally after the aircraft reached the gate. In a statement, Southwest Airlines said: "Both nose gear tires lost air pressure while landing in Chicago." The carrier added that mechanics replaced the tires and the aircraft was subsequently towed to the gate. The airline did not disclose what caused the loss of tire pressure, and no indication has been given that a mechanical failure beyond the tires was involved. The response was precautionary, and no evacuation was reported. Emergency crews completed their assessment without incident, and no injuries among passengers or crew were reported. Chicago Midway International Airport continued normal operations following the response, while Southwest worked to return the aircraft to service after replacing the affected tires. The incident remains under review, with Southwest yet to provide further details on what led to the loss of air pressure in both nose landing gear tires during landing.

Incidents

Southwest Flight 1243 Lands Safely At Chicago After Nose Gear Tires Lose Pressure

Aviation Today News Desk / August 4, 2026

Chicago, United States: Southwest Airlines Flight 1243 experienced a landing incident at Chicago Midway International Airport on the morning of

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

Montreal, Canada: An Air Canada aircraft arriving from Los Angeles veered off a taxiway after landing at Montréal–Pierre Elliott Trudeau International Airport on Thursday, temporarily shutting down one of the airport's runways, disrupting flight operations and prompting an emergency response. No injuries were reported among passengers or crew. The incident occurred after the aircraft landed safely and was taxiing toward the terminal. While exiting the runway via a high-speed taxiway, the aircraft left the paved surface and came to rest with its landing gear in the adjacent grass. Images from the scene showed the aircraft upright with no visible signs of major structural damage or fire. Airport emergency vehicles responded immediately and surrounded the aircraft as a precaution while crews assessed the situation and ensured there were no fuel leaks or fire hazards. Passengers remained safe throughout the incident, and no injuries were reported. The aircraft remained stranded on the grassy area for several hours while recovery operations were carried out. The excursion forced Montréal-Trudeau Airport to temporarily close its north runway, reducing airport capacity and triggering delays, cancellations and operational disruptions across Air Canada's network. Several arriving aircraft were delayed or held while the affected runway remained unavailable. The disruption also impacted flights to and from several Canadian cities, including Vancouver, with airlines adjusting schedules as airport crews worked to remove the aircraft and restore normal operations. Although some reports noted wet weather and rain in the Montreal area around the time of the occurrence, aviation authorities have not indicated whether weather played any role in the incident. Likewise, there has been no official confirmation regarding any mechanical issue or flight crew-related factor. The event is being classified as a taxiway excursion rather than a runway accident. The aircraft landed safely before leaving the paved taxiway during ground movement, distinguishing the occurrence from an accident during takeoff or landing. The incident comes as airlines and airport operators continue to emphasize the importance of safe ground operations, where taxiway excursions, although relatively uncommon, can still cause significant operational disruption despite causing no injuries. Airport operations gradually resumed after recovery crews removed the aircraft and the affected runway was returned to service.

Incidents

Air Canada Jet Veers Off Taxiway After Landing At Montreal Airport, Disrupting Flights

Aviation Today News Desk / July 10, 2026

Montreal, Canada: An Air Canada aircraft arriving from Los Angeles veered off a taxiway after landing at Montréal–Pierre Elliott Trudeau

Mumbai, India: A potentially catastrophic runway collision was averted at Mumbai's Chhatrapati Shivaji Maharaj International Airport (CSMIA) on the night of July 8, 2026, after an Air India flight bound for Delhi was forced to abort its take-off roll when an Air India Express aircraft was still occupying the same runway following its landing, according to multiple media reports. The incident occurred on one of the airport's active runways during routine flight operations. According to aviation sources cited by several media outlets, the Air India aircraft had already begun accelerating for departure after receiving take-off clearance when its crew noticed an Air India Express aircraft ahead on the runway. The Air India Express flight had landed moments earlier but had not yet vacated the runway. Realising the runway was not clear, Air Traffic Control (ATC) immediately instructed the Air India crew to reject the take-off. The pilots carried out a rejected take-off (RTO), bringing the aircraft safely to a halt before reaching the Air India Express aircraft. The prompt response by both the cockpit crew and ATC prevented what could have become one of the most serious runway incidents at India's busiest airport. No passengers or crew members were injured in the incident, and neither aircraft sustained any reported damage. Airport operations continued after the aircraft were safely separated. While authorities have not officially disclosed the flight numbers involved, reports indicate that the departing aircraft was an Air India service from Mumbai to Delhi, while the other aircraft belonged to Air India Express and had just completed its landing at Mumbai. Initial information suggests the Air India Express aircraft had not vacated the runway before the departing Air India flight commenced its take-off roll, raising questions over runway occupancy and the sequencing of aircraft movements. Aviation authorities are expected to examine ATC clearances, communication between controllers and flight crews, runway occupancy procedures and the exact timeline of events to determine how both aircraft came to be on the same runway simultaneously. Earlier last month, on June 24, 2026, another face-to-face aircraft incident occurred at Ahmedabad's Sardar Vallabhbhai Patel International Airport when an Air India Airbus A320 arriving from Mumbai took a wrong turn while taxiing after landing and entered an active taxiway, where it came nose-to-nose with an IndiGo aircraft preparing for departure. ATC immediately halted both aircraft, no injuries or damage were reported, and the DGCA launched an investigation into the incident

Incidents

Air India And Air India Express Come Face-To-Face On Mumbai Runway; Take-Off Aborted

Aviation Today News Desk / July 10, 2026

Mumbai, India: A potentially catastrophic runway collision was averted at Mumbai’s Chhatrapati Shivaji Maharaj International Airport (CSMIA) on the night

India

IndiGo Airbus A320 Achieves India’s First Satellite-Based Landing On Commercial Jet

Aviation Today News Desk / July 2, 2026

Rajasthan, India: India has achieved a significant milestone in civil aviation after the Directorate General of Civil Aviation (DGCA) successfully

Ahmedabad, India: A potentially serious ground incident was averted at Ahmedabad's Sardar Vallabhbhai Patel International Airport after an Air India aircraft inadvertently entered an active taxiway following landing and came face-to-face with an IndiGo aircraft preparing for departure. Swift intervention by Air Traffic Control (ATC) prevented the situation from escalating, with both aircraft stopping safely before any collision occurred. The incident took place on the evening of June 24 while Air India flight AI2493, operating from Mumbai to Ahmedabad, was taxiing to its assigned parking stand after landing. According to Air India and aviation sources, the aircraft made an unintended turn while taxiing toward its designated bay, entering an active taxiway instead of following its assigned route. At the same time, IndiGo flight 6E5160, scheduled to operate from Ahmedabad to Mumbai, was taxiing for departure toward the runway. The unexpected movement brought the two Airbus A320-family aircraft onto the same taxiway, leaving them positioned directly opposite each other. According to officials, Air Traffic Control immediately instructed both flight crews to stop. The aircraft came to a halt with an estimated separation of around 200 metres, ensuring that no contact occurred between them. Authorities confirmed there were no injuries to passengers or crew and no damage to either aircraft. Following the incident, the Air India aircraft was assisted back to its designated parking bay with ground support, after which the IndiGo aircraft resumed taxiing and departed safely for Mumbai. The IndiGo flight subsequently landed safely at Chhatrapati Shivaji Maharaj International Airport in Mumbai. In an official statement, Air India acknowledged that flight AI2493 had taken an unintended turn during taxiing after landing at Ahmedabad on June 24. "We are aware of an incident where our flight AI2493 operating from Mumbai to Ahmedabad, after landing, inadvertently took a wrong turn during taxiing. There was no compromise on the safety of passengers or crew. The aircraft was subsequently moved to the correct parking bay with ground assistance," the airline said. Air India added that the matter had been reported to the Directorate General of Civil Aviation (DGCA), and an internal investigation had been initiated. IndiGo confirmed that its flight 6E5160 was taxiing for departure to Mumbai when another aircraft entered its taxi path. The airline said both aircraft were stopped immediately as a precaution in coordination with ATC. After the situation was resolved, the flight continued its departure and completed the journey safely. The Directorate General of Civil Aviation has been informed of the incident and has initiated an investigation to determine the circumstances that led to the taxiway deviation. Investigators are expected to examine the sequence of taxi instructions issued by ATC, cockpit communications, pilot adherence to taxi clearances, airport ground movement procedures and other operational factors that may have contributed to the incident. Authorities have not yet determined the cause of the wrong turn, and no findings have been released regarding whether the deviation resulted from pilot error, misunderstanding of taxi instructions, airport signage, or any other contributing factor.

Incidents

Potential Ground Collision With IndiGo Aircraft Averted After Air India Taxiway Error

Aviation Today News Desk / June 26, 2026

Ahmedabad, India: A potentially serious ground incident was averted at Ahmedabad’s Sardar Vallabhbhai Patel International Airport after an Air India

Kuala Lumpur, Malaysia: A Singapore Airlines (SIA) flight from Kuala Lumpur to Singapore was delayed by nearly six hours on June 21 after the aircraft operating an earlier sector suffered a tyre-related incident upon arrival in Malaysia, marking the second such occurrence involving the same route this month. According to Singapore Airlines, two tyres on a Boeing 737-8 operating Flight SQ114 from Singapore to Kuala Lumpur deflated after landing at Kuala Lumpur International Airport (KLIA) on June 21. The incident occurred after the aircraft had completed its arrival into Kuala Lumpur. There were no reports of injuries. Because the aircraft could not continue normal operations, it was towed to a remote parking bay. All 152 passengers and eight crew members onboard SQ114 disembarked via buses and were transported to the terminal. The affected aircraft had been scheduled to operate the return service, Flight SQ113, from Kuala Lumpur to Singapore later the same day. However, the tyre damage rendered the aircraft unavailable, forcing Singapore Airlines to dispatch a replacement aircraft from Singapore. As a result, SQ113, carrying 143 passengers and eight crew members, departed Kuala Lumpur at 8:27 p.m. local time instead of its scheduled 2:35 p.m. departure. The flight subsequently arrived in Singapore at 9:38 p.m. Passengers received multiple delay notifications throughout the afternoon. According to reports, the airline initially advised travelers that the departure had been postponed until 4:35 p.m. due to technical issues affecting the incoming aircraft. The flight was later delayed again, with Singapore Airlines citing adverse weather conditions in Singapore for the final postponement. Affected passengers were provided with refreshments, snack packs, meal vouchers and assistance with onward travel arrangements, including rebooking of connecting flights where necessary. Singapore Airlines apologized for the disruption, stating that passenger and crew safety remains its highest priority. The airline also confirmed that the damaged tyres had been replaced and that the aircraft would return to service after the necessary maintenance actions. The June 21 occurrence follows another tyre-related incident involving the same Singapore-Kuala Lumpur service on June 13. On that occasion, Flight SQ114, also operated by a Boeing 737 MAX 8, experienced a double tyre burst during landing at KLIA at approximately 1:27 p.m. local time. The aircraft became disabled on the runway, prompting airport authorities to temporarily close one of KLIA's three runways. The affected runway remained unavailable for about six hours while emergency crews and maintenance personnel worked to clear the aircraft and inspect the pavement. Malaysia Airports later confirmed that flight operations resumed after aviation authorities completed safety checks and granted clearance for reopening. Investigations and technical assessments are expected to determine whether the tyre failures resulted from operational factors, runway conditions, foreign object debris, maintenance issues, manufacturing defects or other causes.

Incidents

Singapore Airlines Flight Delayed For Hours After Two Tyres Deflated At KLIA

Aviation Today News Desk / June 24, 2026

Kuala Lumpur, Malaysia: A Singapore Airlines (SIA) flight from Kuala Lumpur to Singapore was delayed by nearly six hours on

Tokyo, Japan: A British Airways flight preparing to depart Tokyo Haneda Airport for London Heathrow was forced to return to its parking stand on Thursday, June 18, after a passenger's smartphone caught fire while the aircraft was taxiing for takeoff. According to Japan's Ministry of Land, Infrastructure, Transport and Tourism (MLIT), smoke was reported from the cabin at approximately 1:10 p.m. local time. The aircraft was operating a scheduled British Airways service from Tokyo Haneda Airport (HND) to London Heathrow Airport (LHR). Japanese transport officials said the smartphone is believed to have belonged to a passenger. Cabin crew responded immediately and extinguished the fire using onboard firefighting equipment before airport emergency personnel became involved. The aircraft returned to its stand where firefighters and airline personnel carried out safety inspections. No injuries were reported among the 211 passengers and crew members on board. Authorities said the incident occurred while the aircraft was taxiing for departure and had not yet taken off. Following inspections and confirmation that the situation was under control, the flight later departed after a delay of approximately one hour. The event marks the second British Airways lithium-battery-related cabin fire incident reported within days. On June 15, British Airways Flight BA271 from London Heathrow to Las Vegas experienced a cellphone fire while crossing the Atlantic. Air traffic control recordings captured the crew reporting that the device had "scorched the inside of the cabin," although the fire was quickly contained. The Boeing 787-9 landed safely at Harry Reid International Airport in Las Vegas and no injuries were reported. Airlines and regulators have increasingly strengthened guidance on the carriage and handling of lithium battery-powered devices following a growing number of onboard battery-related incidents in recent years. Japanese authorities have not released additional details regarding the smartphone involved, including its manufacturer or model, and no investigation findings have yet been announced.

Incidents

Passenger Smartphone Fire Forces British Airways Flight Back To Parking Stand In Tokyo

Aviation Today News Desk / June 19, 2026

Tokyo, Japan: A British Airways flight preparing to depart Tokyo Haneda Airport for London Heathrow was forced to return to

airport operations

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

Air India AI2379 Hits Severe Turbulence; 12 Injured Before Safe Landing In Delhi

Southwest Flight 1243 Lands Safely At Chicago After Nose Gear Tires Lose Pressure

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

Air Canada Jet Veers Off Taxiway After Landing At Montreal Airport, Disrupting Flights

Air India And Air India Express Come Face-To-Face On Mumbai Runway; Take-Off Aborted

IndiGo Airbus A320 Achieves India’s First Satellite-Based Landing On Commercial Jet

Potential Ground Collision With IndiGo Aircraft Averted After Air India Taxiway Error

Singapore Airlines Flight Delayed For Hours After Two Tyres Deflated At KLIA

Passenger Smartphone Fire Forces British Airways Flight Back To Parking Stand In Tokyo

Quick Links

Navigate

General Support

News Desk Support