News

Civil Aviation

Pilot Training

Flight School Analysis

Aviation Jobs

Training

Services

About Us

Contact Us

AircraftOperations

New Delhi, India: India's Aircraft Accident Investigation Bureau (AAIB) has released its preliminary findings into the serious incident involving a Swiss International Air Lines Airbus A330-343 that suffered a left-engine failure during takeoff at Delhi's Indira Gandhi International Airport, forcing the crew to reject takeoff and conduct an emergency evacuation. The incident occurred shortly after 1:27 a.m. local time on April 26, 2026, when Swiss flight LX147 was preparing to depart Delhi for Zurich with 245 people onboard, including 232 passengers and 13 crew members. According to the AAIB report, the aircraft involved was a 2012-built Airbus A330-343, registered HB-JHK, powered by Rolls-Royce Trent 772B-60 engines. The aircraft had arrived in Delhi earlier that day, operating flight LX146 from Zurich. Investigators noted that the inbound Zurich–Delhi flight was uneventful. While seven maintenance complaints were logged after arrival, all were described as routine and unrelated to the aircraft's engines, flight controls, serviceability, or controllability. The reported issues were addressed before the aircraft was cleared for the return flight to Switzerland. No abnormalities were detected during pre-flight inspections before LX147's departure from Delhi. The aircraft, parked at Stand A14, received pushback and startup clearance before taxiing to Runway 28 via taxiway J6. At 01:25:56 IST, air traffic control cleared the flight for takeoff with light winds reported from 210 degrees at one knot. Moments later, during the takeoff roll, the aircraft accelerated to approximately 106 knots. According to cockpit reports cited by investigators, the crew heard a loud bang as the No. 1 engine experienced a failure. Pilots reported seeing a large flame projecting forward from the left engine and observed the aircraft veering left. The crew immediately rejected the takeoff and brought the aircraft to a stop on Runway 28 between taxiways G1 and G2. After stopping, the flight crew informed air traffic controllers of the engine failure and requested emergency services. Communications recorded by investigators show that airport vehicles and crash fire tenders responded rapidly. Initially, responders observed smoke around the aircraft. As emergency personnel continued assessing the situation, reports indicated smoke near the left landing gear and subsequently fire near the right landing gear area. Fire crews began firefighting operations while coordinating with air traffic controllers and the flight crew. At approximately 01:35 IST, a full airport emergency was declared. Following confirmation of smoke and fire indications, both engines were shut down. Emergency evacuation procedures were initiated directly on the runway. Seven of the aircraft's eight evacuation slides were deployed and used to evacuate passengers and crew. All occupants successfully exited the aircraft. Four passengers sustained injuries during the evacuation and were transported for medical treatment. Airport responders reported that the fire had been completely extinguished by approximately 01:50 IST. The aircraft was later towed from the runway and parked at a remote stand. The airport terminated the full emergency status at 04:50 IST. Data obtained from the aircraft's post-flight report showed the first recorded warning was an "ENG 1 Stall" message at 01:27 IST during the takeoff roll. This was followed by multiple system messages including "ENG 1 FAIL," "AIR PACK 1+2 FAULT," "F/CTL RUD TRIM 1 FAULT," and "ENG 1 REV UNLOCKED." An "ENG 1 SHUTDOWN" message was subsequently recorded after the aircraft came to a stop. Investigators conducted an external inspection of the aircraft and found metallic debris near the exhaust section of the left engine along with soot and burn marks on the engine pylon behind the exhaust area. Notably, no damage was observed on the engine fan blades, and investigators reported no significant structural damage to the aircraft apart from minor dents likely caused during emergency slide deployment. A borescope inspection of the failed engine revealed extensive internal damage. Investigators discovered broken bolts and spacers from the high-pressure/intermediate-pressure bearing support assembly within the thrust reverser ducts. High-pressure bleed valves were also partially blocked by debris. Further examination identified significant damage to components within the engine core, including the High Pressure Turbine, Intermediate Pressure Turbine, Low Pressure Turbine, and High Pressure Compressor sections. Both the high-pressure and intermediate-pressure shafts were seized, preventing complete inspection. The AAIB stated that although severe internal engine damage was identified, investigators were unable to determine the precise cause of the engine failure during the initial borescope examination because the engine's rotating assemblies could not be fully inspected. Importantly, investigators found no evidence of an uncontained engine failure. The failed Rolls-Royce Trent 772B-60 engine was manufactured in 2009 and had accumulated more than 75,500 operating hours and 11,369 flight cycles. Records show the engine's last overhaul occurred in May 2016. Since that overhaul, it had accumulated nearly 40,000 additional flight hours before the incident. Both cockpit crew members were appropriately licensed and qualified on the Airbus A330. The captain had more than 18,600 total flight hours, while the first officer had accumulated more than 2,170 hours. AAIB investigators have removed and downloaded data from both the cockpit voice recorder and flight data recorder. Analysis of the recorded information is ongoing. The bureau said the damaged engine will be removed from the aircraft for a detailed examination aimed at identifying the root cause of the failure. Investigators are also reviewing maintenance records, operational documentation, air traffic control recordings, and witness statements. The investigation includes participation from international authorities and technical experts. France's Bureau d'Enquêtes et d'Analyses (BEA), Airbus, the European Union Aviation Safety Agency (EASA), Germany's BFU, the United Kingdom's AAIB, and Rolls-Royce representatives are assisting the Indian investigation under the provisions of ICAO Annex 13. The AAIB emphasized that the findings released so far are preliminary and subject to change as the investigation progresses. No interim safety recommendations have been issued at this stage.

AAIB Preliminary Report Finds No Evidence Of Uncontained Failure In Swiss A330 Engine Incident

Aviation Today News Desk / June 1, 2026

New Delhi, India: India’s Aircraft Accident Investigation Bureau (AAIB) has released its preliminary findings into the serious incident involving a

Virgin Atlantic Flight Makes Emergency Landing In Ireland After Engine Malfunction

Aviation Today News Desk / June 1, 2026

Shannon, Ireland: A Virgin Atlantic Airbus A330-900neo operating a scheduled service from London Heathrow to Montego Bay, Jamaica, made an

Minneapolis, United States: A United Airlines flight from Chicago to Minneapolis was met by law enforcement after a passenger allegedly attempted to breach the cockpit during the flight, triggering a major security response. The incident occurred on May 29, aboard a United Airlines service traveling from Chicago O'Hare International Airport (ORD) to Minneapolis–Saint Paul International Airport (MSP). During the flight, a passenger allegedly became disruptive and attempted to move toward the flight deck area, triggering an immediate response from cabin crew and flight personnel. Flight attendants and crew members reportedly intervened to prevent access to the cockpit, while the flight crew coordinated with air traffic control and law enforcement authorities. The aircraft subsequently landed safely, where police and security personnel met the flight upon arrival. Reports indicate that the situation prompted the activation of a heightened security response, with references made to a "Level 4" threat classification. However, U.S. aviation authorities and United Airlines have not publicly issued detailed statements explaining the specific classification or confirming the exact security designation. No injuries were immediately reported among the 147 passengers and six crew members and authorities took the passenger into custody following the aircraft's arrival. Investigations into the incident remain ongoing. A Level 4 threat generally refers to a severe security situation that requires immediate operational response and enhanced coordination among flight crews, airport authorities, law enforcement agencies, and federal security personnel. Such alerts may be associated with potential unlawful interference with flight operations, attempted cockpit intrusion, credible hijacking concerns, or situations that could pose a direct threat to aircraft safety. The exact terminology and classification systems can vary between agencies, airlines, airports, and security organizations. Earlier in May, United Airlines Flight 1837 operating to Newark Liberty International Airport experienced a security incident after a passenger allegedly attacked a flight attendant and attempted to gain access to the flight deck area. The aircraft landed safely and the passenger was detained by authorities. A separate United Airlines flight operating from Newark to Guatemala City was also forced to divert after a passenger allegedly attempted to open a cabin door during flight, prompting an emergency response and law enforcement action upon landing. Authorities have not announced whether federal charges will be filed in connection with the latest Chicago-Minneapolis incident. Investigators are expected to review crew reports, passenger statements, onboard security procedures, and any available cabin surveillance evidence as part of the inquiry. United Airlines has not publicly disclosed additional details regarding the passenger involved or the precise sequence of events leading to the reported cockpit breach attempt.

United Flight Hit By Security Scare After Alleged Cockpit Breach Attempt By A Passenger

Aviation Today News Desk / May 30, 2026

Minneapolis, United States: A United Airlines flight from Chicago to Minneapolis was met by law enforcement after a passenger allegedly

Narita, Japan: A Japan Airlines (JAL) Boeing 767 operating a domestic service from Tokyo Haneda Airport (HND) to Kagoshima Airport (KOJ) made an emergency landing at Narita International Airport (NRT) on May 29 after a suspected tire failure during takeoff prompted the crew to divert the aircraft. The aircraft, carrying 218 passengers and eight crew members, landed safely at Narita at approximately 11:55 a.m. local time. No injuries were reported among those on board. According to Japan's Ministry of Land, Infrastructure, Transport and Tourism (MLIT) and local media reports, the incident began shortly after departure from Haneda Airport when the crew detected a problem believed to be related to the aircraft's landing gear tires. As a precaution, the Boeing 767 discontinued its planned flight to Kagoshima and diverted to Narita, where emergency services were positioned ahead of the landing. The aircraft touched down without further incident and passengers later disembarked safely. Airport and transport authorities immediately launched an investigation into the occurrence. The incident resulted in temporary operational disruptions at both airports. Following the emergency landing, Narita Airport's Runway A was closed for approximately two hours while officials inspected the aircraft and conducted safety assessments. Airport operations later resumed after the runway was cleared for use. Meanwhile, officials at Haneda Airport discovered debris on Runway D, the same runway used by the JAL aircraft for departure. Authorities temporarily closed the runway beginning around 10:30 a.m. to determine whether the debris originated from the Boeing 767. After inspections were completed, Runway D reopened at approximately 1:45 p.m. However, investigators have not yet confirmed whether the debris was connected to the Japan Airlines aircraft. Further details indicated that the aircraft conducted a low approach inspection, during which damage was reportedly observed on two forward tires of the main landing gear. The report suggested the event may have involved more extensive tire damage than initially believed. There were no reported injuries among the 226 occupants onboard and the aircraft landed safely following the occurrence.

Japan Airlines Diverts To Narita After Suspected Tire Failure On Takeoff From Tokyo

Aviation Today News Desk / May 30, 2026

Narita, Japan: A Japan Airlines (JAL) Boeing 767 operating a domestic service from Tokyo Haneda Airport (HND) to Kagoshima Airport

London, United Kingdom: A British Airways Airbus A380 operating flight BA285 en route from London Heathrow to San Francisco was forced to turn back to the UK after the crew identified a technical issue mid-flight, authorities and flight tracking data confirm. The double-deck superjumbo, registered as G-XLEK, departed Heathrow at approximately 11:43 GMT on Wednesday for the scheduled transatlantic service. Around four hours into the planned 10-hour journey, the flight began holding over northern UK airspace near Scotland and released fuel over a remote area off the west coast, a standard aviation practice to safely reduce landing weight. Flight tracking services showed BA285 circling at multiple flight levels for more than an hour before crews initiated the return to Heathrow. During this period the aircraft also became one of the most-tracked flights globally on FlightRadar24, highlighting the unusual nature of the diversion. British Airways subsequently confirmed the aircraft touched back down at Heathrow later the same day without declaring an emergency. In a statement to media, the airline said the diversion was due to a technical issue with the aircraft’s communication system and stressed that all on board landed safely with no injuries reported. Passengers affected by the disruption are being assisted with rebooking and ground support. The airline has apologised to customers for the inconvenience and encouraged travellers to check flight status information via official channels. A few days ago on December 8, a British Airways Airbus A320 flight from Edinburgh to London declared a mid-air emergency and returned safely to Edinburgh Airport earlier this week, after pilots reported a landing gear malfunction shortly after departure. Flight BA1443, bound for Heathrow, issued the internationally recognised 7700 emergency squawk code minutes after takeoff when the aircraft’s landing gear failed to retract properly, prompting the crew to hold over Stirling while troubleshooting before returning and landing without incident. The unscheduled return led Edinburgh Airport to temporarily suspend incoming and outgoing flights, with several services diverted to nearby airports during the disruption. No injuries were reported, and British Airways apologised to affected passengers as operations resumed after the technical issue was resolved.

British Airways A380 Returns To Heathrow After Mid-Flight Technical Issue

Aviation Today News Desk / December 12, 2025

London, United Kingdom: A British Airways Airbus A380 operating flight BA285 en route from London Heathrow to San Francisco was

California, United States: A scheduled trans‑Pacific trip by Delta Air Lines ended with an emergency diversion on the morning of November 19 after the crew detected a serious engine fault, authorities said. Flight DL 357 departed from Daniel K. Inouye International Airport (Honolulu) at approximately 11 :10 p.m. HST the previous evening, bound for Salt Lake City International Airport. On board were 212 passengers and eight crew members. Around four hours into the flight, cruising at 35,000 feet over open ocean, the flight crew reported a fault in one of the aircraft’s two engines and initiated a shutdown of that engine as a precaution. The crew declared an emergency, activating transponder code 7700, to secure priority handling from air‑traffic control. With the fault confirmed and the aircraft operating on a single engine, the decision was made to divert to the nearest suitable airport. The crew elected to land at Los Angeles International Airport (LAX), where full emergency and rescue resources could be readily mobilised. The aircraft touched down on Runway 7R just prior to 7:00 a.m. PST and taxied to Gate 3A in Terminal 3. A full fire‑and‑rescue vehicle presence met the aircraft on arrival. Emergency responders carried out an external inspection. No visible structural damage or fire was reported, and all passengers and crew disembarked safely, with no injuries reported. In the aftermath, the Federal Aviation Administration﹙FAA) opened an investigation into the incident, examining the engine fault and reviewing whether maintenance or manufacturing factors played a role. Initial commentary suggests the fault is believed to stem from a mechanical anomaly rather than a maintenance‑shortcoming.

Delta Flight DL 357 Diverts To Los Angeles After Mid-Air Engine Fault, Lands Safely

Aviation Today News Desk / November 20, 2025

California, United States: A scheduled trans‑Pacific trip by Delta Air Lines ended with an emergency diversion on the morning of November 19 after