News

Civil Aviation

Pilot Training

Flight School Analysis

Aviation Jobs

Training

Services

About Us

Incidents

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.

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 hours

Tokyo Court Sentences ANA Captain To Prison For Sexually Assaulting Flight Attendant

Aviation Today News Desk July 15, 2026

Tokyo, Japan: An All Nippon Airways (ANA) captain has been sentenced to prison by a Japanese court after being found guilty

Shannon, Ireland: United Airlines Flight UA509, a Boeing 767-400ER operating from Rome Fiumicino Airport (FCO), Italy, to Newark Liberty International Airport (EWR), New Jersey, was forced to divert to Shannon Airport (SNN), Ireland, on July 11 after the flight crew reported right-engine vibrations and an unusual odor in the cabin while crossing the North Atlantic. The aircraft was carrying 227 passengers and crew, and all landed safely with no injuries. The aircraft, registered N76065, departed Rome at 1:36 p.m. local time for the scheduled transatlantic service to Newark. Approximately three hours into the flight, while cruising at FL340 (34,000 feet) over the Atlantic and around 400 kilometres south of Ireland about 550 kilometres from Shannon Airport the pilots detected abnormal vibrations from the aircraft's right General Electric CF6 engine. The crew also reported a noticeable smell inside the cabin, prompting them to discontinue the oceanic crossing and request an immediate diversion to Shannon, one of the primary diversion airports for North Atlantic flights. According to reports, the affected engine remained operational but was reduced to idle thrust as a precaution. Air traffic controllers cleared the aircraft to divert, after which the crew descended from cruise altitude to facilitate the approach into Shannon. Because of the amount of fuel still onboard, the pilots advised they would be conducting an overweight landing, a procedure in which an aircraft lands above its normal maximum landing weight when an immediate landing is considered the safest course of action. At Shannon Airport, emergency procedures were activated before the aircraft's arrival. Airport authorities alerted their fire and rescue service after the crew requested emergency vehicles to be positioned alongside the runway. The Boeing 767 landed safely on Runway 06 at approximately 3:57 p.m. local time after more than four hours in the air. Fire and rescue vehicles escorted the aircraft along the runway before it stopped briefly on a taxiway, where firefighters carried out a visual inspection of the right engine. Given the overweight landing, emergency personnel also examined the aircraft's undercarriage and landing gear to ensure there was no overheating caused by the heavier-than-normal touchdown. Following the inspections, the aircraft taxied under its own power to the terminal while accompanied by emergency vehicles. United Airlines confirmed that the diversion was carried out "to address an issue with one engine." The airline said all 227 occupants disembarked safely without injury. Passengers were provided with hotel accommodation, compensation where applicable, and were rebooked on the next available flights to their destinations. Flight tracking data showed the aircraft remained on the ground in Shannon following the incident while maintenance personnel conducted inspections to determine the cause of the reported engine vibrations and cabin odor. The remainder of Flight UA509 to Newark was cancelled. As of the latest available updates, aviation authorities had not released findings on the cause of the technical issue, and the aircraft continued to undergo maintenance evaluation before returning to service.

United Boeing 767 Diverts To Shannon After Engine Vibrations On Rome-Newark Flight

Aviation Today News Desk July 14, 2026

Shannon, Ireland: United Airlines Flight UA509, a Boeing 767-400ER operating from Rome Fiumicino Airport (FCO), Italy, to Newark Liberty International Airport

London, United Kingdom: British Airways experienced two separate precautionary turnbacks involving Boeing 777-200ER aircraft operating transatlantic services to the United States on consecutive days, with both flights returning safely to London Heathrow after crews reported technical issues. No injuries were reported in either incident, and the airline arranged alternative travel for affected passengers while engineers inspected the aircraft. The first incident occurred on July 9, involving Flight BA229 from London Heathrow (LHR) to Baltimore/Washington International Airport (BWI). The service was operated by a Boeing 777-200ER. After departing Heathrow and proceeding westbound over the Atlantic, the crew elected to discontinue the flight because of a technical issue and returned to Heathrow as a precaution. The aircraft landed safely without further incident, and passengers were transferred to alternative flights after the aircraft was handed over to maintenance engineers for inspection. British Airways said safety remained its highest priority and apologized for the disruption. A day later, on July 10, Flight BA183 from London Heathrow to New York John F. Kennedy International Airport (JFK) also returned to Heathrow following a separate technical problem. The flight, likewise operated by a Boeing 777-200ER, turned back after departing the UK and tracking over Ireland before the crew decided to return as a precaution. The aircraft landed safely at Heathrow, where engineering teams carried out inspections. Passengers were rebooked onto later services to continue their journeys. British Airways stated that both flights returned to Heathrow as a precaution following technical issues, emphasizing that safety is always its foremost priority. The carrier apologized to customers for the inconvenience and said it worked to minimize disruption by arranging replacement aircraft or alternative travel wherever possible. While flight tracking data showed both aircraft reversing course before reaching North America, the airline has not publicly disclosed the specific nature of the technical issues affecting either flight. Engineers subsequently inspected both aircraft in accordance with standard maintenance procedures before any return to service.

British Airways Boeing 777 US Flights Turn Back On Consecutive Days Over Technical Issues

Aviation Today News Desk July 13, 2026

London, United Kingdom: British Airways experienced two separate precautionary turnbacks involving Boeing 777-200ER aircraft operating transatlantic services to the United States

Thessaloniki, Greece: A Ryanair flight bound for Germany was forced to make an emergency return to Thessaloniki shortly after take-off on July 10, 2026, after a cabin window became dislodged during flight, triggering a rapid depressurization and injuring a passenger seated beside the window. The Boeing 737 Next Generation aircraft had departed Thessaloniki Airport in Greece on a scheduled service to Memmingen, Germany, when the incident occurred during the initial climb. Preliminary reports indicate the aircraft had climbed to between 16,000 and 20,000 feet when the crew declared an emergency and turned back toward Thessaloniki. According to multiple media reports citing investigators and aviation officials, the emergency is believed to have begun with a reported uncontained failure of the aircraft's right CFM56 engine. Investigators are examining whether debris from the engine struck the fuselage and dislodged a passenger window, causing a sudden loss of cabin pressure. The sequence of events remains under investigation and has not yet been confirmed by authorities. The rapid decompression caused passenger oxygen masks to deploy automatically. Videos recorded inside the cabin and shared on social media showed masks hanging from the ceiling and a damaged window after the incident. A 61-year-old Serbian passenger, who was seated next to the affected window and was wearing his seatbelt, was partially pulled through the opening created by the dislodged window during the decompression. Fellow passengers, including his wife, immediately grabbed him and managed to pull him back into the cabin before the aircraft landed safely. Reports state he suffered non-life-threatening injuries, including friction burns, and was transported to hospital after landing. Authorities have not publicly identified the hospital where he was treated. The aircraft landed safely back at Thessaloniki Airport approximately 10 to 20 minutes after departure. Emergency services met the aircraft on arrival, and the injured passenger received medical treatment. The remaining passengers later continued their journey to Memmingen aboard a replacement Ryanair aircraft. The aircraft involved has remained grounded for technical inspection following the incident. The investigation is being led by North Macedonia's Accident Investigation Committee, with assistance from the U.S. National Transportation Safety Board (NTSB), Boeing and engine manufacturer CFM International, reflecting the multinational nature of the aircraft, engine and operator involved. In a statement, Ryanair confirmed the in-flight occurrence, saying: "A window became dislodged during the flight." The airline added that the aircraft returned to Thessaloniki and landed normally, and that passengers were returned to the terminal before continuing their journey on a replacement aircraft. Ryanair has not confirmed media reports suggesting the passenger was partially pulled outside the aircraft, while the cause of the window failure remains under investigation. The Irish Aviation Authority (IAA) also confirmed it is aware of the occurrence and said it is coordinating with the relevant Greek and Maltese aviation authorities as the investigation continues.

Ryanair Returns To Thessaloniki After Cabin Window Breaks Mid-Air, Injuring Passenger

Aviation Today News Desk July 13, 2026

Thessaloniki, Greece: A Ryanair flight bound for Germany was forced to make an emergency return to Thessaloniki shortly after take-off on

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.

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 International

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

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 of

Fresno, United States: A Delta Air Lines regional flight operating from San Francisco International Airport (SFO) to Los Angeles International Airport (LAX) made an emergency landing at Fresno Yosemite International Airport (FAT) on Monday after the crew reported an engine-related issue. Delta Flight DL2725, diverted to Fresno as a precaution after experiencing engine problems during the short domestic flight. The aircraft landed safely at Fresno Yosemite International Airport shortly before 4:00 p.m. local time. According to Delta Air Lines, the aircraft taxied to the gate under its own power after landing. The airline confirmed that all 158 people on board 152 passengers and six crew members were safe, and no injuries were reported. Video from the airport showed the aircraft parked between two American Airlines aircraft following the emergency landing. Emergency response personnel were present as a standard precaution, but no evacuation was required. While initial reports described the event as being caused by engine issues, Delta later clarified that the diversion followed an engine indication warning. The airline has not disclosed the specific nature of the indication, and the aircraft has been removed from service for inspection by maintenance personnel. Passengers were safely deplaned after arriving at the gate, and Delta said it was working to re accommodate customers on alternate transportation to Los Angeles. The U.S. Federal Aviation Administration (FAA) is expected to review the incident as part of standard procedures for in-flight emergencies. The exact cause of the engine indication remains under investigation.

Delta Flight Bound For Los Angeles Diverts To Fresno After Engine Warning Mid-Flight

Aviation Today News Desk July 8, 2026

Fresno, United States: A Delta Air Lines regional flight operating from San Francisco International Airport (SFO) to Los Angeles International Airport

Bishkek, Kyrgyzstan: A TezJet McDonnell Douglas MD-83 carrying 181 people suffered a dramatic landing gear collapse during its takeoff roll at Manas International Airport in Bishkek, Kyrgyzstan, on Tuesday, July 7, forcing an emergency evacuation and temporarily shutting down the country's busiest airport. All passengers and crew escaped safely, with no fatalities or serious injuries reported, although several occupants sustained minor cuts, bruises and abrasions while evacuating via emergency slides. The aircraft was operating scheduled domestic flight K9117 from Bishkek to Osh when its left main landing gear collapsed while accelerating for departure on Runway 26. Airport authorities said the pilots were able to reject the takeoff because the aircraft was still travelling at a relatively low speed. After coming to a stop, the aircraft leaned sharply onto its left side, causing the left wing to scrape the runway and rupture, resulting in a jet fuel leak. Emergency crews, including airport firefighters, responded immediately as fuel spilled onto the runway. Despite the leak, there were no reports of a post-incident fire. The flight crew initiated an emergency evacuation using inflatable escape slides, allowing all 181 including 152 adults, 11 teenagers, and 18 children occupants to leave the aircraft safely. Authorities said several passengers suffered minor abrasions, cuts and bruises during the evacuation, but none required treatment for life-threatening injuries. No official breakdown of passengers by adults, children or infants has been released. Images from the scene showed extensive damage to the MD-83. The aircraft came to rest tilted onto its left wing, while the lower empennage (tail section) was torn away during the incident. Debris and spilled fuel were visible around the aircraft as emergency personnel secured the area. According to the state airport operator, Airports of Kyrgyzstan, Manas International Airport was temporarily closed following the occurrence while emergency responders removed the aircraft and ensured the runway was safe for operations. The airport later began restoring normal flight movements after the scene was secured. The aircraft involved was a McDonnell Douglas MD-83, a twin-engine narrow-body airliner from the MD-80 family. Aviation Safety Network identified the aircraft as operating TezJet Flight K9117 and reported that the incident occurred during the takeoff roll after the left-hand main landing gear collapsed. The MD-80 family, introduced in the 1980s, continues to serve with a limited number of operators worldwide despite its age. As of publication, neither TezJet nor Kyrgyz aviation authorities have announced the cause of the landing gear failure. An investigation has been launched to determine what led to the collapse, and investigators are expected to examine the aircraft's landing gear system, maintenance records and flight data before issuing preliminary findings.

TezJet MD-83 Landing Gear Collapses During Takeoff In Kyrgyzstan, 181 Evacuated

Aviation Today News Desk July 8, 2026

Bishkek, Kyrgyzstan: A TezJet McDonnell Douglas MD-83 carrying 181 people suffered a dramatic landing gear collapse during its takeoff roll at

Karachi, Pakistan: A Pakistan-registered K2 Airways cargo aircraft carrying five crew members went missing over the Arabian Sea late on July 7 after reporting a technical problem while en route from Sharjah in the United Arab Emirates to Karachi. As of the latest official update on July 8, authorities have not confirmed a crash, and an extensive multi-agency search and rescue operation remains underway. According to the Pakistan Airports Authority (PAA), the Boeing 737 freighter was operating a scheduled cargo service from Sharjah to Karachi when the crew reported a navigational system issue at 9:18 p.m. Pakistan Standard Time (PST). Air traffic controllers at the Karachi Area Control Centre (ACC) immediately began assisting the flight. In an official statement, the PAA said, "K2 Airways B737 of Pakistan Cargo Flight en route from Sharjah to Karachi at time 2118 PST reported a navigational system issue and was promptly guided by Karachi ACC." However, only three minutes later, the situation deteriorated rapidly. The authority said that at 9:21 p.m. PST, radar displayed the aircraft making a rapid descent along with a sharp change in heading before both radar and radio contact were lost. The aircraft's last known position was approximately 155 nautical miles (287 km/178 miles) west of Karachi over the Arabian Sea. The PAA stated, "However, at 2121 PST, aircraft were observed on radar rapidly descending and with rapid heading change, subsequently radar contact and communication was lost approximately 155 nautical miles west of Karachi." The missing aircraft was a Boeing 737 cargo aircraft operated by Karachi-based K2 Airways, a Pakistani cargo airline that commenced operations in late 2024. Early flight-tracking data reviewed by Flightradar24 showed the aircraft experiencing a series of abrupt altitude changes before entering a steep final descent. While those data have led to speculation that the aircraft may have crashed into the sea southwest of Karachi, Pakistani authorities have not officially confirmed a crash. Immediately after communication was lost, Pakistan activated its Rescue Coordination Center, launching a coordinated search operation in the Arabian Sea. The search involves multiple agencies, including the: Pakistan Navy Pakistan Air Force (PAF) Pakistan National Shipping Corporation (PNSC) Rescue Coordination Center Merchant vessels operating in the area According to official updates and Associated Press, the operation includes a Pakistan Navy frigate, a naval ATR maritime patrol aircraft, additional naval and air assets, and nearby commercial ships that have been directed to assist in locating the aircraft and its crew. The Pakistan Airports Authority said, "Following the occurrence, the Rescue Coordination Center was activated, and a coordinated Search & Rescue operation at sea was launched through various agencies to locate the missing aircraft." Authorities have confirmed that five crew members were on board. No passengers were being carried. K2 Airways has identified the five crew members on board as Pilot-in-Command Mohammad Rizwan Idrees, First Officer Faisal Mehmood, Load Master Muhammad Toufique Khan, and Engineers Arif Siddiqui and Mohammad Hamid. No wreckage, emergency locator beacon signals, debris, or survivors have been officially located, and the cause of the aircraft's disappearance remains unknown. K2 Airways said it is fully cooperating with investigators and government agencies. In a statement shared by the airline, it said, "We continue to pray, earnestly, for the safety of our colleagues." Aviation analyst Imran Aslam told the Associated Press that the aircraft's sudden descent was unusual, noting that even following an engine failure, an aircraft would typically continue gliding rather than descend so rapidly, adding further uncertainty about what may have occurred during the flight's final moments. The incident is now expected to be investigated by Pakistan's aviation authorities once the aircraft is located. Until then, officials have urged against speculation while search teams continue combing the Arabian Sea.

Pakistan Cargo Missing Over Arabian Sea With Five Crew On Board After Technical Issue

Aviation Today News Desk July 8, 2026

Karachi, Pakistan: A Pakistan-registered K2 Airways cargo aircraft carrying five crew members went missing over the Arabian Sea late on July

Incidents

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

Tokyo Court Sentences ANA Captain To Prison For Sexually Assaulting Flight Attendant

United Boeing 767 Diverts To Shannon After Engine Vibrations On Rome-Newark Flight

British Airways Boeing 777 US Flights Turn Back On Consecutive Days Over Technical Issues

Ryanair Returns To Thessaloniki After Cabin Window Breaks Mid-Air, Injuring Passenger

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

Delta Flight Bound For Los Angeles Diverts To Fresno After Engine Warning Mid-Flight

TezJet MD-83 Landing Gear Collapses During Takeoff In Kyrgyzstan, 181 Evacuated

Pakistan Cargo Missing Over Arabian Sea With Five Crew On Board After Technical Issue

Quick Links

Navigate

General Support

News Desk Support