Black box data tells all about deadly flight Air India 171: Full sequence of events that ended in a tragic crash
Flight AI423 crashed shortly after takeoff due to a dual engine failure triggered by the fuel cutoff switches being inexplicably moved to the CUTOFF position. Despite attempts to relight the engines, the aircraft lost altitude and crashed outside the airport perimeter after a MAYDAY call went unanswered. Initial checks showed no issues with fuel, weight, or pilot fitness.
Hashtags
Try Our AI Features
Explore what Daily8 AI can do for you:
Comments
No comments yet...
Related Articles
The Hindu
3 days ago
- The Hindu
Need for a revamp: on the Ahmedabad air crash probe, aviation safety
The preliminary report flowing from the investigation into the crash of an Air India Boeing 787-8 at Ahmedabad, on June 12, 2025, has a focal point now. Released in the early hours of July 12, a month after the accident, the Aircraft Accident Investigation Bureau's 15-page document has highlighted the fuel control switches of 'Engine 1 and Engine 2' having 'transitioned from the 'Run' to the 'Cutoff' position, one after another, with a time gap of one second'. That this happened just after flight AI171 had begun to lift off from the 3,505-metre-long runway, leading to the engines beginning to decrease from their take-off values as fuel starvation hit, has accentuated another detail. How did two separate switches that are guarded by brackets, feature a metal stop locking mechanism and have separate systems for redundancy move to 'cutoff'? And why? The element of bafflement by one crew member, and denial by the other pilot, over the cutoff, has compounded the issue, more so in the absence of the full and raw transcript of the cockpit voice recording. However, in the midst of the crisis, what must be acknowledged was a display of airmanship, with a partially successful relighting of the GEnx-1B70/75/P2 engines, which ended with the call of May Day. While the key details in the report have evoked appeals by a pilot body for a revamped probe, especially to 'stop the bias towards pilot error', the investigation team must now stay the course to ensure that there is a sound, comprehensive and transparent investigation. There has also been focus on an FAA Special Airworthiness Information Bulletin of 2018 that concerns the potential for disengagement of the fuel control switch locking feature, and applicable to the Boeing 787 aircraft family. In a reaction to the preliminary report and its findings, there has been some expert commentary on the topic of crew well-being, but in a counter to this, the Indian Commercial Pilots' Association has said that 'pilots undergo extensive psychological and professional screening... and operate under the highest standards of safety'. However, the subject of Crew Resource Management and Line Oriented Flight Training may need to be revamped, more so with this being an unusual incident of dual engine failure. Finally, despite the preliminary report's pitch of there 'not being recommended actions that concern the aircraft type and the engine manufacturer', India's expanding civil aircraft fleet requires greater vigilance in terms of maintenance and operations. Airport funnel zones and obstacle limitations must be reviewed too as it is a given that air crew and passengers have safer flights.
Economic Times
4 days ago
- Economic Times
Black box data tells all about deadly flight Air India 171: Full sequence of events that ended in a tragic crash
Flight AI423 crashed shortly after takeoff due to a dual engine failure triggered by the fuel cutoff switches being inexplicably moved to the CUTOFF position. Despite attempts to relight the engines, the aircraft lost altitude and crashed outside the airport perimeter after a MAYDAY call went unanswered. Initial checks showed no issues with fuel, weight, or pilot fitness. Tired of too many ads? Remove Ads Flight AI423 had a Pilot Defect Report (PDR) entry for a status message: 'STAB POS XDCR' in the tech log. Troubleshooting was carried out, and the aircraft was released for flight. The pilots had adequate rest, underwent pre-flight breath analyser tests, and were found fit to operate the flight. Fuel on board was 54,200 kg, and the takeoff weight was 213,401 kg, which was within the maximum allowed limit of 218,183 kg. No dangerous goods were onboard the aircraft. The aircraft began its takeoff roll at 08:07:37. The air/ground sensors transitioned to 'air mode,' consistent with liftoff at 08:08:39. The aircraft achieved a maximum recorded airspeed of 180 knots IAS at approximately 08:08:42. Immediately after, Engine 1 and Engine 2 fuel cutoff switches were moved from RUN to CUTOFF positions, one after another, with a one-second gap. As fuel supply to the engines was cut off, both N1 and N2 values began to decrease from their takeoff values. In the cockpit voice recording, one pilot is heard asking the other, 'Why did you cut off?' The other pilot responded that he did not. CCTV footage from the airport showed the Ram Air Turbine (RAT) deploying during the initial climb, immediately after liftoff. No significant bird activity was observed near the flight path. The aircraft began to lose altitude before crossing the airport perimeter wall. According to EAFR data, both engines' N2 values dropped below the minimum idle speed, and the RAT hydraulic pump began supplying power at around 08:08:47. At approximately 08:08:52, Engine 1's fuel cutoff switch transitioned back from CUTOFF to RUN. At 08:08:56, Engine 2's fuel cutoff switch also transitioned from CUTOFF to RUN. When fuel control switches are moved from CUTOFF to RUN during flight, the Full Authority Dual Engine Control (FADEC) system automatically initiates a relight and thrust recovery sequence, including ignition and fuel reintroduction. Exhaust Gas Temperature (EGT) began rising for both engines, indicating relight. Engine 1's core deceleration stopped, reversed, and began recovering. Engine 2 managed to relight but could not stop the core speed deceleration. It kept reintroducing fuel in attempts to increase acceleration and achieve recovery. The EAFR recording stopped at 08:09:11. At around 08:09:05 UTC, one of the pilots transmitted: 'MAYDAY, MAYDAY, MAYDAY.' Air Traffic Control (ATCO) asked for the call sign but received no response. ATCO then observed the aircraft crash outside the airport boundary and immediately activated the emergency response. On June 12, tragedy struck as Air India Flight 171 crashed just moments after takeoff, despite no signs of mechanical issues or external threats like bird strikes. In a shocking chain of events, both engines shut down mid-air, cockpit confusion unfolded, and a desperate Mayday call went unanswered.A detailed sequence reconstructed from technical logs, cockpit voice recordings, and CCTV footage now reveals the terrifying final moments of the flight, offering a chilling look into what caused the deadly is the minute-by-minute breakdown of what exactly happened from takeoff to is the sequence of events leading to the deadly crash on June 12:
Time of India
4 days ago
- Time of India
Black box data tells all about deadly flight Air India 171: Full sequence of events that ended in a tragic crash
Synopsis Flight AI423 crashed shortly after takeoff due to a dual engine failure triggered by the fuel cutoff switches being inexplicably moved to the CUTOFF position. Despite attempts to relight the engines, the aircraft lost altitude and crashed outside the airport perimeter after a MAYDAY call went unanswered. Initial checks showed no issues with fuel, weight, or pilot fitness.
