What Went Wrong? Insights from the Air India Boeing 787 Crash Investigation

A recent investigation into the Air India Boeing 787 crash has revealed alarming details about the events leading up to the incident. The preliminary report from the Aircraft Accident Investigation Bureau (AAIB) highlights critical failures in fuel control switches and pilot communications. As the aircraft took off, both engines experienced a dangerous deceleration, leading to a Mayday call just moments before the crash. This article delves into the findings of the AAIB report, providing insights into the sequence of events and the response from emergency services. Read on to uncover the full story behind this tragic aviation incident.
 | 
What Went Wrong? Insights from the Air India Boeing 787 Crash Investigation

Preliminary Findings of the Air India Crash


New Delhi: Just moments after takeoff, the fuel control switches on Air India’s Boeing 787-8 were turned off, leading to a critical situation. According to the Aircraft Accident Investigation Bureau (AAIB), one pilot questioned the other about the switch-off, to which the second pilot denied any action.


The AAIB's preliminary report, released a month post-incident, detailed that the switches were later reactivated, but the engine's deceleration could not be halted.


The report indicated that the aircraft's air/ground sensors shifted to air mode, confirming liftoff at 08:08:39 UTC.


The plane reached a peak airspeed of 180 knots at approximately 08:08:42 UTC, shortly before both Engine 1 and Engine 2 fuel cutoff switches were switched to the CUTOFF position, one second apart.


As the fuel supply was interrupted, the engines' N1 and N2 readings began to drop from their initial takeoff values.


The cockpit voice recording captured one pilot inquiring about the fuel cutoff, with the other asserting he had not done so.


CCTV footage from the airport revealed that the Ram Air Turbine (RAT) deployed during the initial climb right after takeoff.


The report noted no significant bird activity near the flight path, and the aircraft began descending before it crossed the airport's perimeter.


According to the Enhanced Airborne Flight Recorders (EAFR), Engine 1's fuel cutoff switch was switched back to RUN at around 08:08:52 UTC, followed by Engine 2 at 08:08:56 UTC.


When the switches are moved from CUTOFF to RUN during flight, the engines' full authority dual engine control (FADEC) automatically initiates a relight and thrust recovery sequence.


The report observed a rise in Exhaust Gas Temperature (EGT) for both engines, indicating a relight attempt. Engine 1's core deceleration halted and began to recover, while Engine 2 managed to relight but could not stop its core speed from declining.


The EAFR recording concluded at 08:09:11 UTC.


At approximately 08:09:05 UTC, one pilot declared a 'MAYDAY' call, but when the Air Traffic Controller sought clarification, there was no reply. The ATCO then witnessed the aircraft crash beyond the airport boundary and initiated an emergency response.


Emergency services, including the Crash Fire Tender, departed the airport at 08:14:44 UTC to assist with rescue and firefighting efforts.


News Hub