The investigation into the Air India 171 crash in Ahmedabad, which killed 260 people on June 12, 2025, has become increasingly contested as engineers, pilots, and aviation specialists question whether the sequence of engine “relight” described in early findings was physically possible. The Aircraft Accident Investigation Bureau (AAIB) had initially indicated that both engines lost power after fuel control switches moved from “RUN” to “CUTOFF,” and later suggested a relight sequence after the switches were restored. That interpretation quickly shaped public debate and early media narratives, which leaned toward cockpit action as a likely cause. However, a growing body of technical critique, including reporting cited by Frontline India, now challenges whether the aircraft’s systems could have supported such a restart at all.
At the centre of the dispute is the feasibility of relighting dual jet engines after a near-simultaneous shutdown under the flight conditions recorded in the AAIB report. The bureau’s preliminary timeline stated that engine core speeds dropped below minimum idle, followed by a partial recovery in one engine after fuel was reintroduced. Engineers familiar with turbofan dynamics argue that such a recovery requires either external power or sufficient internal rotational energy—conditions that may not have been present during a dual-engine power loss at low altitude. As noted by aviation professionals interviewed in Frontline India’s reporting, systems such as the Auxiliary Power Unit (APU), ground power units, or windmilling at higher airspeeds are typically required to reintroduce combustion stability. In this case, the APU was not yet fully operational during the critical seconds, and aircraft speed estimates cited in the report are argued to be insufficient to sustain a windmill relight of core engine components.
The controversy has been amplified by questions over what was actually heard in the cockpit voice recording. The AAIB report referenced a conversation in which one pilot asks why the other “cut off” the engines, and the response denies doing so. Early media coverage interpreted this as evidence of deliberate fuel cutoff, but engineers and legal representatives cited in Frontline India’s coverage argue that the conversation may have been mischaracterized. They suggest the exchange could just as plausibly have referred to an automation disconnect, such as autothrottle or takeoff/go-around mode disengagement, rather than fuel switches. A US attorney representing families of victims was quoted expressing concern that the technical ambiguity of the recording left room for oversimplified interpretations of pilot intent.
A more complex layer of disagreement concerns electrical system behaviour in the final seconds of the flight. Several engineers argue that cascading electrical degradation could have compromised flight control logic and engine management systems before the reported fuel switch events. According to these interpretations, Full Authority Digital Engine Control (FADEC) responses, which manage fuel flow and engine stability, may have been influenced by upstream electrical instability rather than manual inputs. Frontline India’s reporting highlights claims that multiple redundant systems, including flight control modules and power distribution units, were reporting faults in the minutes before takeoff and during the climb. These findings, while not independently verified in the AAIB’s public summaries, have fueled debate over whether the aircraft entered a degraded operational mode that could have affected both automation and engine response.
The implications of this technical disagreement extend beyond the cockpit narrative. If the relight sequence described in early reports is mechanically implausible under the conditions described, then the assumption of deliberate or inadvertent pilot-induced shutdown becomes less certain. Engineers cited in the debate argue that investigators may need to reassess whether automated systems initiated shutdown or whether cascading electrical faults triggered fuel cutoff logic within engine control software. This possibility shifts the focus from human action to system architecture, maintenance history, and software behaviour.
This debate is unfolding alongside a broader scrutiny of the Boeing 787 Dreamliner’s electrical systems and maintenance record. Frontline India’s reporting has highlighted prior technical issues involving power distribution units, stabiliser sensors, and fire suppression systems on the aircraft involved, suggesting a history of intermittent electrical faults. Maintenance records reportedly show repeated warnings and component replacements over several years, though aviation authorities have not publicly concluded that these issues were causally linked to the crash. Still, the presence of recurring electrical anomalies has intensified calls from pilot associations and safety experts for deeper systemic analysis rather than early attribution of blame.
The human dimension of the crash has also become part of the contested narrative. Pilots’ associations and legal representatives of the crew have pushed back against early insinuations of cockpit error, arguing that the technical complexity of modern fly-by-wire aircraft makes isolated human causation difficult to establish without a full systems reconstruction. The Federation of Indian Pilots has called for greater transparency and warned against premature conclusions. Families of the pilots, including that of Captain Sumeet Sabharwal, have similarly objected to what they view as reputational harm caused by early speculation.
Meanwhile, investigators are also examining the aircraft’s maintenance and operational history, including reports of prior electrical faults and system warnings in the days leading up to the crash. According to Frontline India’s investigation, these included alerts linked to power distribution systems and flight control modules shortly before departure. Engineers quoted in the report argue that such clusters of faults, if confirmed, could indicate broader system instability rather than isolated component failure.
The broader aviation community is now divided between competing interpretations: one centred on cockpit actions during a critical emergency, and another focused on cascading system failures that may have constrained pilot options. Experts caution that both human and technical factors may ultimately prove relevant, but the sequencing and causality remain unresolved. The AAIB’s final report, expected in June 2026, is likely to face pressure to reconcile these competing narratives while addressing gaps in available flight data and the physical limitations of post-crash reconstruction.
For now, the AI 171 crash investigation has evolved into more than a technical inquiry. It has become a test case in how modern aviation accidents are interpreted in an era of highly automated aircraft, complex electrical architectures, and rapid public narrative formation. As one aviation safety expert cited in Frontline India’s coverage noted, the key question is no longer only what happened in the cockpit, but whether the aircraft’s systems themselves were capable of behaving as early assumptions suggest. Until that is conclusively answered, the relight timeline and cockpit blame debate are likely to remain central—and deeply contested—features of the investigation.
