AirlineOperations Archives - Page 2 of 4

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

Incidents

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

Delhi, India: An Air India Boeing 777-300ER operating flight AI173 from Delhi to San Francisco was forced to return to Delhi after suffering a technical malfunction mid-flight, remaining airborne for more than eight hours before landing safely at Indira Gandhi International Airport. The incident occurred on May 27 and involved approximately 230 passengers onboard the long-haul flight bound for the United States. According to airline officials and flight-tracking data, the aircraft had already spent over three hours in the air and entered Chinese airspace when the crew decided to discontinue the journey and return to Delhi in accordance with safety procedures. Initial reports stated that the issue involved the aircraft’s Traffic Collision Avoidance System (TCAS), a critical airborne safety system designed to prevent mid-air collisions by enabling aircraft to electronically detect and communicate with nearby traffic. The system operates independently of ground-based air traffic control and is considered mandatory for certain long-haul international operations, including trans-Pacific and North Atlantic routes. While Air India did not officially disclose the exact nature of the malfunction in its initial public statement, it is suspected that the aircraft experienced problems linked to the TCAS equipment during the flight. Some aviation reports and social media aviation monitoring pages further claimed that both TCAS channels onboard the aircraft became unavailable, though the airline has not publicly confirmed those specific details. Flight-tracking platforms showed the Boeing 777-300ER reversing course while over Chinese airspace before commencing the lengthy return sector to Delhi. Due to the aircraft’s weight, fuel load, and operational requirements for a safe landing, the jet remained airborne for several additional hours before touchdown. Air India confirmed that the aircraft landed safely and would undergo a detailed technical inspection in line with the carrier’s maintenance and safety protocols. The airline also stated that alternative arrangements were made for affected passengers, including hotel accommodation, refreshments, rebooking support, and rescheduling options. “The aircraft landed safely and will undergo technical inspection in line with Air India’s safety standards,” the airline said in its statement while expressing regret over the inconvenience caused to passengers. No injuries were reported during the incident, and passengers were safely deboarded after the aircraft’s arrival back in Delhi.

Incidents

Air India Flight To San Francisco Returns To Delhi After Mid-Air Technical Malfunction

Aviation Today News Desk / May 29, 2026

Delhi, India: An Air India Boeing 777-300ER operating flight AI173 from Delhi to San Francisco was forced to return to

Airlines

FAA Proposes Penalty Against Alaska Airlines Over Alleged Intoxicated Passenger Boarding

Aviation Today News Desk / May 29, 2026

Washington, United States: The U.S. Federal Aviation Administration (FAA) has proposed a civil penalty of $165,000 against Alaska Airlines after

Cape Town, South Africa: South African Airways (SAA) is facing mounting scrutiny after allegations emerged that the airline delayed reporting a serious fuel emergency involving two flights at Cape Town International Airport, prompting calls for a Parliamentary inquiry into aviation safety oversight in South Africa. The controversy centres on SAA flights SA313 and SA327, which were affected by severe weather conditions over Cape Town on 11 May 2026. According to reports, the airline allegedly took eight days to notify the South African Civil Aviation Authority (SACAA) about the incidents, despite regulations requiring such events to be reported within 72 hours. The issue has triggered criticism from South Africa’s opposition Democratic Alliance (DA), which has formally requested an urgent hearing before Parliament’s Portfolio Committee on Transport. The party said the delay raises concerns about SAA’s safety management systems, regulatory compliance, and transparency. Chris Hunsinger, Democratic Alliance spokesperson on transport, said the incident reflects what he described as a broader pattern of failures within the country’s aviation oversight framework. He warned that repeated operational incidents, delayed reporting, and questions surrounding accountability were eroding public confidence in aviation safety. According to aviation sources cited in local reports, flight SA313, operated by an Airbus A320 from Johannesburg to Cape Town, encountered severe weather during its arrival into Cape Town amid gale-force north-westerly winds, heavy rain, low cloud, and dangerous windshear conditions. The aircraft reportedly conducted a missed approach after receiving onboard windshear alerts. Pilot and aviation analyst Duncan Gillespie stated that a second landing attempt at Cape Town would likely have left the aircraft without sufficient reserves to divert safely to its nominated alternate airport, George Airport. The aircraft subsequently diverted to George, but deteriorating weather conditions there allegedly prevented a safe landing. The aircraft later continued to Gqeberha, where reports claim it landed with fuel reserves below internationally accepted minimum levels. Gillespie alleged the aircraft may have landed with less than 15 minutes of fuel remaining. Under international aviation regulations, commercial aircraft are generally expected to land with approximately 30 minutes of final reserve fuel, and crews are normally required to declare a fuel emergency if projected landing fuel falls below that threshold. Questions have also been raised over whether the crew declared a formal “Mayday Fuel” emergency during the incident. Gillespie noted there was no visible indication on public flight-tracking systems that the aircraft had transmitted the emergency transponder code commonly associated with a Mayday declaration. SAA spokesperson Mphilo Dlamini did not directly address questions regarding the alleged fuel emergency, remaining fuel levels after landing, or whether the crew had declared an emergency. Instead, the airline stated that severe weather conditions affected operations across the Western Cape on 11 May and maintained that SAA followed all required aviation safety procedures and reporting protocols. The SACAA had also not publicly responded to detailed media questions at the time several reports were published. The DA said it intends summoning SAA, SACAA, Air Traffic and Navigation Services (ATNS), and the Department of Transport before Parliament to explain the delayed reporting, oversight concerns, and broader operational issues affecting South African aviation. The party also highlighted ongoing problems within ATNS, including the suspension of 326 instrument flight procedures. The DA further pointed to concerns over regulatory independence, arguing that SACAA investigates entities operating under the same government department, potentially creating conflicts of interest in aviation oversight.

Airlines

SAA Faces Scrutiny Over Delayed Reporting Of Alleged 2 Fuel Emergency Incidents

Aviation Today News Desk / May 28, 2026

Cape Town, South Africa: South African Airways (SAA) is facing mounting scrutiny after allegations emerged that the airline delayed reporting

Washington, United States: A United Airlines flight bound for Guatemala City made an emergency diversion to Washington Dulles International Airport after a passenger allegedly attempted to open a cabin door at cruising altitude and assaulted another traveler, according to air traffic control communications and federal authorities. The incident involved United Airlines Flight 1551, operated by a Boeing 737 MAX 8, which departed from Newark Liberty International Airport on Thursday evening carrying 145 passengers and six crew members. The aircraft had been en route to Guatemala City when the crew declared an emergency and diverted to Washington Dulles International Airport in Virginia. According to audio between the flight crew and air traffic controllers, the pilot informed controllers that the disruptive passenger attempted to open Door 2L while the aircraft was cruising at approximately 36,000 feet. The pilot also reported that the passenger later assaulted another individual onboard. During the exchange, the tower asked the crew which door the passenger had attempted to access. The pilot responded: “Door 2L at 36,000 feet and then [the passenger] assaulted a fellow passenger.” When controllers asked whether there were any injuries onboard, the pilot replied: “Not to our knowledge.” The aircraft landed safely at Washington Dulles at approximately 8:38 p.m. local time. Law enforcement and emergency personnel met the aircraft upon arrival. The FBI later confirmed that agents responded to the incident at the airport, although the agency did not immediately release additional details regarding the passenger’s identity, possible charges, or whether the individual was taken into federal custody. Flight tracking data showed the aircraft remained airborne for a period before diverting toward the Washington region instead of continuing south toward Guatemala. The diversion temporarily disrupted the scheduled international service but no injuries among passengers or crew were officially reported. United Airlines had not issued a detailed public statement at the time of publication regarding the circumstances surrounding the diversion or the status of the passenger involved. Federal authorities are expected to review crew reports, passenger statements, and onboard evidence as part of the investigation.

Incidents

United Flight Diverts After Mid-Flight Cabin Door Opening Attempt And Passenger Assault

Aviation Today News Desk / May 22, 2026

Washington, United States: A United Airlines flight bound for Guatemala City made an emergency diversion to Washington Dulles International Airport

Bangalore, India: An Air India Airbus A321 operating flight AI2651 from Delhi to Bengaluru suffered a tail-strike incident while landing at Bengaluru’s Kempegowda International Airport on Thursday morning, prompting the airline to ground the aircraft for detailed technical inspections. The incident occurred during the landing phase of the domestic service arriving from Delhi. According to airline officials and multiple media reports, the aircraft landed safely and all passengers and crew members disembarked normally without injuries. The aircraft encountered wake turbulence while approaching the runway at Bengaluru airport. The turbulence was reportedly generated by a departing wide-body aircraft operating nearby at the time of the approach. As the Airbus A321 approached for landing, the pilots initiated a precautionary go-around manoeuvre after experiencing unstable conditions caused by the wake turbulence. During the manoeuvre, the aircraft’s rear lower fuselage reportedly made contact with the runway, resulting in the tail strike. Air India confirmed the occurrence in an official statement, saying the aircraft “experienced a tail-strike during landing.” The airline added that the aircraft has since been withdrawn from service for comprehensive inspections and engineering assessments. The aircraft involved was a narrow-body Airbus A321 operating the Delhi–Bengaluru sector as AI2651. Flight-tracking data also identified the aircraft as an Airbus A321neo variant typically deployed on high-density domestic routes. The aircraft was carrying 181 people, including crew members onboard during the incident. Following the incident, Air India cancelled the return Bengaluru–Delhi service AI2652. The airline stated that alternative travel arrangements were being made for affected passengers while ground staff in Bengaluru were assisting travellers with rebooking and support services. The airline further said the incident would be investigated in coordination with relevant aviation regulatory authorities and under established operational safety procedures.

Incidents

Air India A321 Suffers Tail Strike During Bengaluru Landing, Aircraft Grounded

Aviation Today News Desk / May 22, 2026

Bangalore, India: An Air India Airbus A321 operating flight AI2651 from Delhi to Bengaluru suffered a tail-strike incident while landing

Florida, United States: An Allegiant Air flight bound for Atlantic City was forced to return to Fort Lauderdale-Hollywood International Airport on Monday morning after the crew received an indication related to cabin pressurization during climb, prompting medical evaluations for multiple passengers and crew members. According to airline officials and emergency responders, Allegiant Air Flight 3912 departed Fort Lauderdale at approximately 9:20 a.m. local time for Atlantic City International Airport with 187 people onboard, including passengers and crew. The aircraft involved was identified as a Boeing 737-8200, part of the Boeing 737 MAX family. Shortly after departure, the flight crew received an indication associated with cabin pressurization while the aircraft was climbing. Allegiant spokesperson Sonya Padgett said the pilots leveled the aircraft and elected to return to Fort Lauderdale “out of an abundance of caution” and in accordance with established procedures. The aircraft landed safely and normally back at Fort Lauderdale-Hollywood International Airport, where passengers deplaned at the gate. Following the landing, medical personnel from the Broward Sheriff’s Office Fire Rescue evaluated passengers and crew members as a precaution. Battalion Chief Michael Kane said paramedics treated a total of 13 people, most of whom complained of ear pain and related discomfort commonly associated with pressurization problems. Three individuals were transported to a hospital for further evaluation. Authorities said no serious injuries were immediately reported. Some passengers complained of ringing in their ears and head discomfort after the aircraft returned to the airport. Flight tracking data cited by regional media showed the aircraft performed a series of turns before eventually landing back at Fort Lauderdale around 11:08 a.m. Allegiant later rescheduled the flight, which subsequently departed Fort Lauderdale for Atlantic City at approximately 3:02 p.m., according to the airline’s operational data.

Incidents

Allegiant Air Flight Returns After Cabin Pressurization Issue; 13 Treated For Ear Pain

Aviation Today News Desk / May 20, 2026

Florida, United States: An Allegiant Air flight bound for Atlantic City was forced to return to Fort Lauderdale-Hollywood International Airport

Incidents

British Airways Flight Delayed After Accidental Slide Deployment At Heathrow

Aviation Today News Desk / May 18, 2026

London, United Kingdom: A British Airways transatlantic flight from London Heathrow to Washington Dulles was delayed for more than six

India

Delhi Slashes ATF VAT From 25% To 7% For Six Months Amid Rising Fuel Costs

Aviation Today News Desk / May 18, 2026

New Delhi, India: The Delhi government has reduced the Value Added Tax (VAT) on Aviation Turbine Fuel (ATF) from 25

AirlineOperations

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

Virgin Atlantic Flight Makes Emergency Landing In Ireland After Engine Malfunction

Air India Flight To San Francisco Returns To Delhi After Mid-Air Technical Malfunction

FAA Proposes Penalty Against Alaska Airlines Over Alleged Intoxicated Passenger Boarding

SAA Faces Scrutiny Over Delayed Reporting Of Alleged 2 Fuel Emergency Incidents

United Flight Diverts After Mid-Flight Cabin Door Opening Attempt And Passenger Assault

Air India A321 Suffers Tail Strike During Bengaluru Landing, Aircraft Grounded

Allegiant Air Flight Returns After Cabin Pressurization Issue; 13 Treated For Ear Pain

British Airways Flight Delayed After Accidental Slide Deployment At Heathrow

Delhi Slashes ATF VAT From 25% To 7% For Six Months Amid Rising Fuel Costs

Follow Us

Quick Links

Navigate

General Support

News Desk Support

Follow Us