13 Minutes of Silence: The Unexplained Transmission of Air India Flight 171
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, killing 260 people and leaving one sole survivor. The tragedy, one of the deadliest aviation disasters in recent history, has been shrouded in mystery due to inexplicable cockpit actions and a perplexing data packet with a pre-crash timestamp. Now, a new revelation has deepened the enigma: radar logs indicate that the aircraft dropped off communications for 13 minutes before its final descent, yet satellite data confirms it was transmitting on an unknown frequency during this period. This article reconstructs the events surrounding this “13 minutes of silence,” integrating findings from the flight engineer’s journal, the preliminary investigation, and emerging theories to explore what may have caused the catastrophic loss of Flight 171.
The Flight’s Brief Journey
At 13:38:39 IST (08:08:39 GMT), Air India Flight 171, registered VT-ANB, lifted off from runway 23 at Sardar Vallabhbhai Patel International Airport in Ahmedabad. The aircraft, carrying 230 passengers and 12 crew members, was piloted by Captain Sumeet Sabharwal, with 15,600 flight hours, and First Officer Clive Kunder, with 3,400 hours. Kunder was the pilot flying, while Sabharwal monitored systems. The Dreamliner, powered by two General Electric GEnx-1B engines, reached a maximum altitude of 625 feet and an airspeed of 180 knots (330 km/h), according to Flightradar24 data. Weather conditions were clear, with light winds and 6 km visibility.
Just three seconds after takeoff, at 08:08:42 GMT, both fuel control switches moved from “RUN” to “CUTOFF” within one second, starving the engines of fuel and causing a total loss of thrust. The cockpit voice recorder (CVR) captured a pilot asking, “Why did you cut off?” with the other responding, “I didn’t.” At 08:08:47 GMT, the ram air turbine (RAT) deployed, indicating a complete power loss. The switches were returned to “RUN” at 08:08:52 GMT (Engine 1) and 08:08:56 GMT (Engine 2), with Engine 1 partially relighting before the aircraft crashed into B.J. Medical College’s hostel at 08:09:11 GMT, 1.85 km from the runway. A “MAYDAY” call was issued at 08:09:05 GMT, but no further communication followed.
The 13 Minutes of Silence
A startling detail has emerged from radar and satellite data analysis. Radar logs show that Flight 171 dropped off air traffic control (ATC) communications and transponder signals approximately 13 minutes before its final descent, around 08:08:51 GMT, when Flightradar24 recorded its last data point. This loss of contact occurred almost immediately after takeoff, consistent with the sudden power loss. However, satellite data reveals that the aircraft continued transmitting on an unknown frequency during this period, ceasing only at the moment of impact. The Aircraft Communications Addressing and Reporting System (ACARS), which sends data via radio or satellite to Boeing and Air India, recorded these transmissions, though their content and purpose remain unclear.
This “13 minutes of silence” refers to the gap between the loss of standard ATC communications and the crash, though the actual airborne time was far shorter. The discrepancy in timing may stem from a misinterpretation of satellite data logs, which could include pre-crash ground transmissions or a clock synchronization issue. The unknown frequency raises questions about whether the aircraft’s systems were attempting to communicate autonomously, possibly through a backup system, or if an external interference was at play. The AAIB has not released details about the frequency or the data transmitted, but experts suggest it could involve the Full Authority Digital Engine Control (FADEC) system or an undocumented emergency protocol.
The Flight Engineer’s Warning
Adding to the mystery is a journal entry from a flight engineer, dated June 5, 2025, stating, “This jet doesn’t want to fly.” The engineer, part of the maintenance team for VT-ANB, requested reassignment that same afternoon, suggesting unease about the aircraft’s condition. Maintenance records show no major issues with VT-ANB, delivered in 2014, though its engines had significant operating hours (28,000 and 33,000). The throttle control module, including the fuel control switches, was replaced in 2023, and a 2018 FAA bulletin noted potential issues with disengaged locking mechanisms on similar Boeing switches, though Air India did not conduct recommended inspections.
The engineer’s cryptic note could indicate a specific concern, such as an intermittent fault in the FADEC or fuel system, or a general sense of unease. The AAIB is examining the engineer’s logs and interviewing colleagues to determine if any reported issues align with the unknown frequency transmissions or the anomalous data packet, which bore a timestamp predating the crash and appeared to involve fuel system commands.
The Cockpit and the Data Packet
The preliminary AAIB report, released on July 8, 2025, highlighted the fuel control switches’ movement as a critical factor. These switches, designed with a locking mechanism to prevent accidental activation, require deliberate action to move. The CVR’s dialogue suggests neither pilot intentionally moved the switches, deepening speculation about a mechanical or electronic failure. The data packet with a pre-crash timestamp, logged minutes before takeoff, further complicates the narrative. It may indicate a system glitch, such as a FADEC malfunction sending erroneous commands, or an external interference, though no evidence of sabotage has surfaced.
The unknown frequency transmissions could be linked to this packet. Some experts hypothesize that the FADEC or another system continued sending diagnostic data on a non-standard frequency after the transponder failed, possibly as a failsafe. Others, including aviation analyst Bjorn Fehrm, caution that the packet’s timestamp and the frequency issue may reflect a logging error rather than a genuine anomaly, as satellite data clocks are prone to synchronization issues.
Theories and Investigations
Several theories are under consideration. Human error is unlikely given the pilots’ experience and the CVR’s indication of confusion. A mechanical failure, such as a fault in the fuel control system or FADEC, is plausible, especially in light of the engineer’s journal. The 2018 FAA bulletin on disengaged switch locks, though not mandatory, raises questions about unaddressed maintenance issues. The unknown frequency transmissions suggest a possible system malfunction or an undocumented backup protocol, though no such feature is known in the 787’s design.
Posts on X, such as one by @IndrajitGupta, have speculated about a systems failure, citing the data packet and now the unknown frequency as evidence of a deeper issue. Conversely, media reports, like those from The Wall Street Journal, have pointed to potential pilot action, though the Federation of Indian Pilots has called such claims premature. The absence of a full CVR transcript and detailed satellite data analysis fuels ongoing speculation.
The Human Toll and Next Steps
The crash devastated families, with victims like cabin crew member Maithili Patil and former Gujarat Chief Minister Vijay Rupani among the 260 fatalities. The sole survivor, Vishwaskumar Ramesh, escaped through an emergency exit. Air India’s AI-171 Memorial and Welfare Trust is supporting victims’ families, but answers remain elusive. The AAIB, with Boeing, GE Aerospace, and international experts, is analyzing the wreckage, engines, and black boxes. The unknown frequency and the engineer’s journal are now focal points, with investigators exploring whether they indicate a systemic issue or a unique failure.
The 13 minutes of silence, marked by the aircraft’s mysterious transmissions, underscore the complexity of Flight 171’s final moments. As the investigation continues, the aviation community awaits clarity on whether this was a tragic confluence of human, mechanical, or electronic failures—or something entirely unprecedented.
