Pilotium Editorial Team
Jul 4, 2026
More than a year after Air India Flight 171 went down seconds after takeoff from Ahmedabad, the final accident report has still not been published — but the picture emerging from the investigation has shifted significantly. Evidence that surfaced through 2026 increasingly points away from the theory that a pilot deliberately shut down the engines, and toward a technical failure. For the professional flying community, this is more than a news story. It is a case study in how investigations work, why they take the time they do, and how the system is meant to protect crews rather than convict them.
Here is where things stand, and why it matters for anyone who flies the line.
What is not in dispute
The factual spine of the accident is established and grounded in flight-recorder data. Shortly after a normal takeoff roll, the aircraft rotated at around 155 knots and lifted off. Within seconds of becoming airborne — as the aircraft reached its maximum recorded airspeed of roughly 180 knots — both engine fuel control switches transitioned from RUN to CUTOFF, one second apart. Both engines shut down and stopped producing thrust. The aircraft, barely airborne and with almost no altitude or energy to trade, began descending and could not recover.
Two further facts have become central. First, the cockpit voice recording captured one pilot asking the other why he had performed the cutoff, and the other replying that he had not done so. Second, the aircraft's Ram Air Turbine — the emergency wind-driven turbine that deploys automatically when the aircraft loses its normal sources of electrical or hydraulic power — was seen deployed in CCTV imagery almost immediately after liftoff, at a strikingly low altitude.
Those two details sit at the heart of everything that has followed.
Why the evidence is shifting the narrative
For much of the period after the crash, public discussion — fuelled by anonymous briefings and online speculation — gravitated toward a disturbing theory: that one of the pilots had intentionally moved the fuel switches to CUTOFF. It is worth being blunt about how damaging that framing is to a profession, and how thin the basis for it was.
The newer analysis cuts the other way. The timing of the RAT deployment is the key. The RAT does not deploy on the ground and does not deploy without cause — it comes out in response to a genuine loss of power (dual engine failure, or a significant electrical or hydraulic failure). Independent timeline analysis of the CCTV imagery suggests the RAT was already deploying at an altitude of only tens of feet, essentially the instant the aircraft left the ground. That points to a triggering failure that was already in progress at or before rotation — not an action taken deliberately in the seconds after liftoff.
This matters because it corroborates the cockpit exchange. If the crew was reacting to an event they did not cause — asking each other what had happened — rather than one pilot concealing a deliberate act, then the evidence and the voice recording tell the same story. It is important to be careful here: the official cause has not been published, and responsible analysis avoids leaping ahead of the investigators. But the direction of travel in the evidence has clearly moved toward a systems explanation.
The fuel-control-switch question
There is a piece of history that every 787 crew should understand. In December 2018, the U.S. Federal Aviation Administration issued a Special Airworthiness Information Bulletin advising operators of Boeing 787 models of the potential for disengagement of the fuel control switch locking feature. The bulletin was advisory, not mandatory — and according to submissions made to investigators, the recommended inspections on the accident aircraft were never carried out, precisely because they were not required.
The significance of the "advisory, not mandatory" distinction is enormous, and it is a theme that recurs throughout aviation safety. An advisory bulletin flags a known potential issue but leaves action to the operator's discretion. A mandatory airworthiness directive compels it. The gap between the two is where latent risk can live for years.
This is not an isolated concern. In February 2026, a separate Air India 787 had a fuel switch move from RUN to CUTOFF twice on the ground before a flight, prompting the airline to ground that aircraft pending investigation. Whatever the final report concludes about AI171 specifically, the fuel-control-switch mechanism on the 787 family has drawn scrutiny that will not simply evaporate — and with over 1,100 Dreamliners in service worldwide, any systemic finding carries global weight.
Why the report is late — and why that is not a scandal
Under ICAO Annex 13, the international framework governing accident investigation, the state leading an investigation is expected to publish a final report within twelve months of the accident. Where that is not possible, it must issue an interim statement documenting progress and any safety issues identified. On the first anniversary of the crash, India's Aircraft Accident Investigation Bureau did exactly that: it confirmed the investigation was ongoing and that the final report would be released on completion, without committing to a date.
In the weeks since, the picture has been one of a probe in its final stages. GE Aerospace delivered its engine analysis reports to the AAIB in late June 2026, and India's civil aviation minister described the investigation as nearing completion, with the report expected once all investigative activities and the international review and consultation process required under Annex 13 are finished.
It is worth defending the timeline rather than treating delay as failure. A rushed report that assigns blame on incomplete evidence serves no one — least of all the crews and families who need the truth. Complex investigations routinely run past twelve months; IATA data has noted that a substantial share of accident investigations are not completed within the deadline. The purpose of Annex 13 is explicitly the prevention of future accidents, not the assignment of legal blame or liability. A final report built on verified evidence and sound analysis, even if late, is worth far more than a fast one built on assumption.
What this means for crews
For those who fly, several threads are worth drawing out.
Investigations are designed to protect the system, not to scapegoat crews. The Annex 13 framework exists to find causes and prevent recurrence. The drift of the AI171 evidence — from a pilot-blame narrative toward a technical explanation, supported by recorder data and physical evidence — is the process working as intended, even when public speculation ran ahead of it.
The advisory-versus-mandatory distinction deserves your attention. Every pilot operates aircraft governed by a layered system of bulletins, service letters, and airworthiness directives. Understanding which items are compulsory and which are discretionary — and how your operator tracks them — is part of professional airmanship. AI171 is a stark reminder that a known, documented issue left to discretion can remain latent for years.
Resist the pull of early speculation. In the year after this crash, confident theories circulated widely and, on the current evidence, may prove to have been wrong — and unjust to the two pilots at the controls. The discipline of waiting for verified findings, rather than amplifying the narrative of the moment, is one the whole profession benefits from modelling.
System knowledge is not academic. The RAT, the fuel control switches, the electrical and hydraulic architecture of your type — these are the very systems at the centre of this investigation. Deep familiarity with what deploys when, and why, is exactly the knowledge that lets a crew understand a degrading situation in real time.
The bottom line
AI171 remains, formally, an open investigation, and the final report will be the authoritative word on what happened. But the evidence that has accumulated over the past year has meaningfully shifted the likely picture — away from deliberate action and toward a technical failure that the crew appears to have been reacting to, not causing. The delay in publishing is a feature of a thorough process, not a failure of one.
For the flying community, the enduring lessons are the ones that outlast any single report: investigations exist to make flying safer, the line between advisory and mandatory can carry real consequences, and the professionalism of a crew is not something to be surrendered to speculation while the evidence is still being weighed.
We will cover the final report when it is published.
Pilotium publishes aviation industry analysis for professional pilots and cabin crew. This article reflects publicly reported information as of July 2026; the AI171 investigation is ongoing and the official final report had not been published at the time of writing. Nothing here should be read as a conclusion as to cause, which is a matter for the official investigation. pilotium.com
