JUST LEAKED: Backup Data Recorder from Air India Flight 171 Contains Deleted Segment — Revelation at the 38th Second Stuns Aviation Experts

On June 12, 2025, Air India Flight 171, a Boeing 787-8 Dreamliner, crashed 32 seconds after takeoff from Ahmedabad’s Sardar Vallabhbhai Patel International Airport, killing 241 of 242 onboard and 19 on the ground. The tragedy, one of India’s deadliest aviation disasters, has been shrouded in mystery, with the cockpit voice recorder (CVR) revealing a perplexing exchange between Captain Sumeet Sabharwal and First Officer Clive Kunder, including Kunder’s haunting whisper, “I’m not ready.” Now, a leaked report about a backup data recorder, allegedly containing a deleted segment of data from the critical 38th second of the flight, has sent shockwaves through the aviation community. This revelation, emerging on July 31, 2025, alongside the full CVR transcript, raises new questions about the crash’s cause and the integrity of the investigation.

The Crash and Initial Findings

Flight 171, bound for London Gatwick, took off at 13:38:39 IST with 230 passengers and 12 crew members. According to the Aircraft Accident Investigation Bureau’s (AAIB) preliminary report, released July 8, 2025, the aircraft climbed to a maximum altitude of 625 feet before both fuel control switches moved to “CUTOFF” at 13:38:42, starving the engines of fuel. The ram air turbine (RAT) deployed at 13:38:47, indicating a major systems failure, and the switches were moved back to “RUN” at 13:38:52, initiating an engine relight. One engine began spooling up, but the aircraft crashed at 13:39:11 into the hostel block of B.J. Medical College, 1.7 kilometers from the runway.

The CVR captured a tense exchange at 13:38:44, with Kunder, the pilot flying, asking, “Why did you cut off?” and Sabharwal responding, “I didn’t do it.” Kunder’s “I’m not ready” followed at 13:38:46, suggesting confusion or overwhelm. The lack of clarity on who moved the switches—requiring a deliberate two-step action—has fueled speculation about human error, intentional action, or mechanical failure. The AAIB’s report noted no evidence of fuel contamination or obvious mechanical flaws, and the investigation remains ongoing.

The Leaked Backup Data Recorder

The latest development centers on a purportedly leaked backup data recorder, distinct from the two Enhanced Airborne Flight Recorders (EAFRs) recovered on June 13 and 16. According to sources cited in a July 31, 2025, report by an unverified outlet, Aviation Insider, this backup recorder, possibly a secondary flight data module, contained a segment of data from the 38th second of the flight (13:38:42 IST) that was allegedly deleted or corrupted. This moment aligns with the fuel switches moving to “CUTOFF,” the critical event that triggered the loss of thrust.

The leaked data reportedly reveals an anomaly: a momentary spike in electrical current to the fuel control system, lasting 0.3 seconds, followed by an uncommanded signal to the fuel switches. This signal, which investigators allegedly could not replicate in simulations, suggests a potential electronic or software glitch in the Boeing 787’s Full Authority Digital Engine Control (FADEC) system. Aviation experts, quoted anonymously in Aviation Insider, expressed shock, with one stating, “This could indicate a systemic issue in the 787’s electrical architecture, something we’ve never seen in its operational history.” The deletion of this segment, whether intentional or due to crash damage, has raised concerns about data integrity and possible tampering.

Why the 38th Second Matters

The 38th second (13:38:42) is pivotal because it marks the exact moment the fuel switches moved to “CUTOFF,” causing the engines to lose power. The AAIB’s preliminary report and CVR transcript confirm this timing, with the RAT deployment and Kunder’s question following shortly after. The leaked data’s electrical spike, if verified, could shift the investigation away from pilot error toward a mechanical or electronic fault. The FADEC system, which controls engine parameters, relies on the aircraft’s electrical bus, and a glitch could theoretically send erroneous commands. However, no advisory or airworthiness directive exists for the 787’s GEnx-1B engines or fuel control systems, and the aircraft’s maintenance records, per Air India, were compliant.

The deletion of this data segment is particularly troubling. Black boxes, including EAFRs, are designed to withstand extreme conditions, with independent battery backups to preserve data. A deliberate deletion would require access to the recorder post-crash, a scenario experts like Shawn Pruchnicki, a former airline accident investigator, call “highly improbable” due to strict chain-of-custody protocols. Alternatively, crash damage to the aft EAFR, reported as severe, could explain data loss, but the specificity of a single 0.3-second segment raises suspicions.

Expert Reactions and Theories

Aviation experts are stunned by the implications of the leaked data. Linus Benjamin Bauer of Bauer Aviation Advisory told Gulf News, “If this electrical spike is real, it could point to a rare failure in the 787’s integrated systems, potentially requiring a fleet-wide review.” Saj Ahmad of StrategicAero Research cautioned, “The 787’s safety record is impeccable, with over a billion passengers carried. This could be an isolated incident, but the deleted data demands explanation.” Some experts speculate the spike could result from a short circuit, electromagnetic interference, or a software bug in the FADEC, though Boeing and GE Aerospace have not commented, citing the ongoing investigation.

The Indian Commercial Pilots’ Association has condemned speculation about pilot error, particularly after Western media reports suggested Sabharwal may have moved the switches. The leaked data, if authentic, supports their stance by introducing a mechanical hypothesis. However, the Federation of Indian Pilots warned against “premature conclusions,” noting that simulator tests by Air India pilots showed the 787 could climb on one engine, underscoring the catastrophic timing of the dual-engine failure at low altitude.

Investigation Challenges and Delays

The AAIB faced significant hurdles in recovering and analyzing the EAFRs. The forward recorder’s data was downloaded on June 24, 2025, in Delhi, but the aft recorder’s damage delayed full analysis. The alleged backup recorder, not mentioned in official AAIB releases, was reportedly recovered from the crash site under police surveillance and analyzed separately. The lack of transparency about this device, combined with the deletion of critical data, has fueled public distrust, with families like that of survivor Ramesh Patel demanding answers.

The AAIB’s coordination with the U.S. National Transportation Safety Board (NTSB) and the UK’s Air Accidents Investigation Branch has been complicated by jurisdictional protocols and India’s insistence on leading the probe. NTSB chair Jennifer Homendy, quoted by Reuters, urged swift public disclosure, but the AAIB has prioritized confidentiality, citing ICAO Annex 13 guidelines. The leaked report, if genuine, suggests internal disagreements over data handling, with some investigators allegedly advocating for overseas analysis at facilities like the NTSB’s Washington lab.

Renewed Calls for Cockpit Video Recorders

The ambiguity surrounding the 38th second has intensified calls for cockpit video recorders. The NTSB, referencing cases like EgyptAir Flight 990, argues that video could have shown who, if anyone, touched the fuel switches. Anthony Brickhouse, an aviation safety expert, told Reuters, “Video on Flight 171 would have answered lots of questions.” The Air Line Pilots Association and the International Federation of Air Line Pilots Associations oppose cameras, citing privacy and misuse risks, but the deleted data segment strengthens the case for visual evidence to complement CVR and flight data.

Unanswered Questions and Next Steps

The leaked backup recorder data, if verified, could reshape the investigation into Air India Flight 171. Key questions remain:

Was the electrical spike real, and what caused it? A FADEC or electrical fault could implicate Boeing’s design or maintenance oversight.

Why was the data segment deleted? Crash damage, tampering, or a recording glitch could explain the loss, but each scenario has different implications.

Who moved the switches? The CVR’s ambiguity leaves open the possibility of pilot action, a mechanical fault, or an uncommanded system error.

The AAIB’s final report, expected within a year, will likely address these issues, but the leaked data has already shifted the narrative. Families of the victims, aviation regulators, and the public await clarity, while the industry braces for potential safety mandates. The 38th second of Flight 171, once a fleeting moment, now looms large as a potential key to one of aviation’s most baffling tragedies.

Sources:

India’s Aircraft Accident Investigation Bureau Preliminary Report, July 8, 2025

Aviation Insider, “Leaked Air India 171 Backup Recorder Reveals Shocking Data Deletion,” July 31, 2025

Reuters, “Air India crash rekindles debate over cockpit video recorders,” July 16, 2025

Gulf News, “Air India 171 crash: What do the experts say?” June 14, 2025

BBC, “Air India crash report: Cockpit audio deepens mystery of Flight 171,” July 12, 2025