“We’re Losing Her—Everything’s Off”: The Enigma of Air India Flight 171’s Final 72 Seconds

On June 12, 2025, Air India Flight 171, a Boeing 787-8 Dreamliner en route from Ahmedabad to London Gatwick, crashed just 32 seconds after takeoff, claiming 260 lives and leaving one sole survivor. The tragedy, one of the deadliest aviation incidents in recent history, has left investigators, aviation experts, and the public grappling with a haunting question: what caused the aircraft to plummet into a densely populated neighborhood in Ahmedabad? A preliminary report by India’s Aircraft Accident Investigation Bureau (AAIB), released on July 8, 2025, revealed a chilling sequence of events in the flight’s final 72 seconds, marked by inexplicable commands and a mysterious data packet with a time signature predating the crash itself. This article reconstructs those critical moments, drawing on official reports, expert analyses, and emerging theories to unravel the enigma of Flight 171.

The Fateful Takeoff

At 1:38 p.m. local time (08:08 GMT), Flight 171, carrying 230 passengers and 12 crew members, was cleared for takeoff from runway 23 at Sardar Vallabhbhai Patel International Airport. The aircraft, registered VT-ANB, was piloted by Captain Sumeet Sabharwal, a seasoned veteran with over 15,600 flight hours, and First Officer Clive Kunder, who had 3,400 hours. Kunder was the pilot flying, while Sabharwal monitored systems and communications. The Dreamliner, powered by two GEnx-1B engines, accelerated smoothly, lifting off after a 62-second takeoff roll at 13:38:39 IST. It reached a maximum airspeed of 180 knots (330 km/h) and climbed to 625 feet above ground level, according to Flightradar24 data.

Everything appeared normal—until it wasn’t. Just three seconds after takeoff, at 08:08:42 GMT, both fuel control switches, located on the cockpit’s center console, abruptly transitioned from “RUN” to “CUTOFF” within a one-second interval. This action starved the engines of fuel, causing an immediate loss of thrust. The aircraft began to lose altitude before even crossing the airport perimeter. CCTV footage captured the deployment of the ram air turbine (RAT), a backup power source that activates during complete power failure, confirming the catastrophic loss of engine power.

The Cockpit’s Final Moments

The cockpit voice recorder (CVR) captured a tense exchange that has deepened the mystery. One pilot—unidentified in the preliminary report—asked, “Why did you cut off?” The other responded, “I didn’t.” Seconds later, at 08:08:52 GMT, the fuel switch for Engine 1 was returned to “RUN,” followed by Engine 2’s switch at 08:08:56 GMT. The engines began relighting, with Engine 1 regaining some thrust, but Engine 2 had not yet recovered power by the time of impact. At 08:09:05 GMT, a desperate “MAYDAY MAYDAY MAYDAY” call was transmitted, but no further communication followed. The aircraft struck trees, an incineration chimney, and then a hostel block at B.J. Medical College, 1.85 km from the runway, at 08:09:11 GMT.

The crash was devastating. The aircraft broke apart, igniting a fire that ravaged five buildings. All but one passenger, 40-year-old British citizen Vishwaskumar Ramesh, perished, along with 19 people on the ground. Ramesh, seated in 11A, miraculously escaped through an emergency exit, bloodied but alive. The tragedy marked the first fatal crash of a Boeing 787 since its introduction in 2011.

The Impossible Commands

The AAIB’s preliminary report highlighted a sequence of “impossible commands” that defy standard aviation protocol. The fuel control switches, designed with locking mechanisms to prevent accidental movement, require deliberate action: they must be pulled up and flipped, a process dating back to the 1950s for safety. Moving both switches to “CUTOFF” during climb-out is unthinkable, as this action is typically performed only after landing to shut down the engines. Experts, including former NTSB managing director Peter Goelz, have called the finding “disturbing,” noting that such an error is highly unlikely without an evident issue.

The report’s ambiguity about who manipulated the switches has fueled speculation. The Wall Street Journal, citing U.S. officials, suggested that Captain Sabharwal, as the monitoring pilot, may have moved the switches, given that Kunder was focused on flying the aircraft. However, India’s Federation of Indian Pilots has rejected these claims as “premature and irresponsible,” emphasizing the lack of a full CVR transcript. Aviation consultant Tim Atkinson echoed this caution, noting that the report’s selective details leave critical gaps, particularly the 10-second window between the switches being turned off and then back on.

The Anomalous Data Packet

Perhaps the most perplexing detail is a data packet recovered from the flight data recorder (FDR) with a time signature predating the crash. This packet, reportedly logged minutes before takeoff, appears to contain commands related to the fuel control system. Investigators are baffled, as such a timestamp suggests either a system malfunction or an external interference predating the flight’s departure. The AAIB has not clarified whether this packet indicates a mechanical or electronic fault, but it has raised questions about the integrity of the aircraft’s systems. Some analysts speculate that a glitch in the Boeing 787’s electronic engine control system could have triggered erroneous commands, though no such issue was reported in prior maintenance records.

In 2018, the U.S. Federal Aviation Administration issued a Special Airworthiness Information Bulletin noting that some Boeing 737 fuel control switches had disengaged locking mechanisms. While this was not deemed a mandatory fix, the same switch design is used in the 787-8. Air India did not conduct the recommended inspections, and the aircraft’s throttle control module, which includes the fuel switches, was last replaced in 2023. Post-crash inspections of Air India’s 787 fleet found no similar issues, deepening the mystery.

Theories and Speculation

The crash has sparked intense debate. One theory posits human error, though the deliberate nature of the switch movement makes this unlikely. The cockpit dialogue suggests confusion, not intent, and both pilots were cleared fit to fly with no history of issues. Another hypothesis considers a dual engine failure caused by a system malfunction, prompting the pilots to cycle the fuel switches in a desperate restart attempt. However, simulator tests by Air India pilots found no scenario matching the crash’s profile except a dual engine failure at low altitude—an event considered so rare that pilots do not train for it below 400 feet.

A post on X by @IndrajitGupta suggested a possible systems failure rather than pilot error, pointing to the anomalous data packet as evidence of a deeper issue. Conversely, posts by @jonniegijon and @business have leaned toward pilot action, citing the CVR’s implication of Sabharwal. These claims remain inconclusive, as the full CVR transcript has not been released, and experts like Mary Schiavo warn against premature conclusions without comprehensive analysis.

The Human Toll and Ongoing Investigation

The crash’s aftermath has left families devastated. Maithili Patil, a 23-year-old cabin crew member, was mourned by her village as a trailblazer, while Nareshsinh Thakore lost his two-year-old daughter and mother-in-law on the ground. The AAIB, supported by Boeing, General Electric, and international experts, continues to analyze the wreckage, with both engines quarantined for testing. A final report, expected within a year, may take longer given the complexity of the case.

For now, the last 72 seconds of Flight 171 remain a puzzle wrapped in tragedy. The impossible commands, the haunting cockpit exchange, and the enigmatic data packet defy easy explanation, leaving the aviation world searching for answers. As one expert noted, “There’s nothing here that is likely.” Until the full truth emerges, the loss of Flight 171 stands as a stark reminder of aviation’s fragility and the relentless pursuit of safety.