EXCLUSIVE CONNECTION: Air India Flight 171’s Fuel Cutoff Mirrors Potomac Mid-Air Collision Timeline

The catastrophic crash of Air India Flight 171 on June 12, 2025, which killed 241 of 242 passengers and crew and 19 people on the ground, has sent shockwaves through the aviation world. The Boeing 787-8 Dreamliner, registered as VT-ANB, plummeted into a residential area in Ahmedabad, India, just 32 seconds after takeoff, following an inexplicable movement of both fuel-control switches to the “CUTOFF” position. This caused a total loss of engine thrust, eerily reminiscent of the 1982 Potomac River mid-air collision involving Air Florida Flight 90, where a Boeing 737 lost control at approximately 3,200 feet due to icing and crew error. The parallels between these tragedies—both involving rapid loss of control shortly after takeoff—have sparked fierce comparisons, raising questions about pilot actions, mechanical reliability, and systemic failures. As investigators probe Flight 171’s haunting cockpit voice recorder (CVR) details, including a pilot’s plea, “Take care of papa,” and a cryptic whisper, “There’s someone else here,” the similarities to the Potomac crash demand a closer look.

Air India Flight 171: A Swift Descent

Flight 171 departed Sardar Vallabhbhai Patel International Airport at 13:38 IST (08:08 UTC) under clear skies, piloted by Captain Sumeet Sabharwal, 56, and First Officer Clive Kunder, 32, who was flying the aircraft. The plane reached a maximum altitude of 625 feet before both fuel-control switches moved from “RUN” to “CUTOFF” three seconds after liftoff, starving the engines, according to the preliminary report by India’s Aircraft Accident Investigation Bureau (AAIB) released on July 8, 2025. The CVR captured one pilot asking, “Why did you cut off?” and the other replying, “I did not do so,” with no identification of the speakers. A mysterious whisper, “There’s someone else here,” and Sabharwal’s earlier plea to family, “Please, take care of papa,” have deepened the mystery. The switches were returned to “RUN” within 10 seconds, but only one engine partially restarted before the plane crashed into the B.J. Medical College hostel complex, 1.5 kilometers from the runway. The sole survivor, Vishwaskumar Ramesh, escaped the wreckage.

Potomac River Crash: A Historical Parallel

On January 13, 1982, Air Florida Flight 90, a Boeing 737-222, crashed into the Potomac River in Washington, D.C., shortly after takeoff from Washington National Airport, killing 74 of 79 passengers and crew and four people on the ground. The flight, bound for Fort Lauderdale, struggled to gain altitude in snowy conditions, reaching approximately 3,200 feet before colliding with the 14th Street Bridge and plunging into the icy river. The National Transportation Safety Board (NTSB) determined that the crash resulted from ice buildup on the wings, improper de-icing procedures, and pilot errors, including failure to activate the engine anti-ice system and premature advancement of thrust levers, leading to a loss of lift and control.

The Potomac crash, like Flight 171, involved a rapid loss of control shortly after takeoff, though the causes differ. While Flight 90’s failure stemmed from environmental factors and crew misjudgments, Flight 171’s fuel cutoff suggests a cockpit-initiated or mechanical anomaly. Both incidents, however, highlight critical moments where seconds determined the outcome, with pilots unable to recover from sudden, catastrophic failures.

Comparing the Timelines: Striking Similarities

The timelines of Air India Flight 171 and Air Florida Flight 90 reveal uncanny parallels in their brevity and loss of control:

Takeoff and Immediate Failure: Flight 171 lifted off at 13:38:39 IST, and three seconds later, at 13:38:42, both fuel switches moved to “CUTOFF,” triggering engine shutdown. Flight 90 took off at 16:00 EST, and within 30 seconds, ice-induced stall warnings and loss of lift were evident, with the plane reaching 3,200 feet before stalling. Both aircraft faced near-instantaneous crises post-takeoff.

Altitude and Duration: Flight 171 peaked at 625 feet and crashed 32 seconds after liftoff. Flight 90 reached 3,200 feet in roughly 30 seconds before descending, crashing 90 seconds after takeoff. The higher altitude in 1982 allowed slightly more time, but both incidents left pilots with minimal reaction windows.

Pilot Confusion: Flight 171’s CVR captured confusion, with one pilot questioning the fuel cutoff and the other denying responsibility. Flight 90’s CVR revealed similar disarray, with First Officer Roger Pettit noting, “We’re not right,” and Captain Larry Wheaton responding, “I know it,” as they struggled with erroneous engine readings and stall warnings. In both cases, crews faced unexpected anomalies without clear solutions.

Emergency Response: Flight 171’s pilots flipped the switches back to “RUN,” initiating an engine relight, and issued a “MAYDAY” call at 13:39:05 IST, six seconds before impact. Flight 90’s crew attempted to correct their climb but lacked the power to recover, with no recorded distress call. Both incidents saw desperate, futile efforts to regain control.

Key Differences and Investigative Focus

While the timelines align, the causes diverge. Flight 90’s crash was attributed to icing, a known hazard, and human error in failing to address it. Flight 171’s fuel cutoff, however, remains unexplained, with no evidence of mechanical failure, bird strikes, or fuel contamination. The AAIB noted a 2018 FAA advisory about disengaged locking mechanisms on Boeing 737 fuel switches, a design shared with the 787, but Air India did not inspect VT-ANB’s switches, as the advisory was non-mandatory. This oversight, combined with the switches’ design requiring deliberate action to move, raises questions about whether the cutoff was intentional, accidental, or caused by a software glitch, as seen in a 2019 All Nippon Airways 787 incident where software misread the plane’s status, triggering an automatic cutoff.

The Potomac crash investigation led to immediate safety changes, including improved de-icing protocols and crew training. Flight 171’s probe, involving the AAIB, Boeing, GE Aerospace, the NTSB, and the UK’s Air Accidents Investigation Branch, is ongoing, with a final report expected by June 2026. The absence of cockpit video, opposed by pilot unions like the Federation of Indian Pilots, and the AAIB’s vague preliminary report have fueled speculation, particularly after a Wall Street Journal claim, citing U.S. officials, that Sabharwal may have moved the switches, as Kunder was occupied with takeoff. The Indian Commercial Pilots’ Association has rejected pilot error claims, demanding a full CVR transcript.

Cockpit Stress and Human Factors

Both crashes highlight the role of cockpit stress. Flight 90’s pilots faced pressure from adverse weather and a rushed departure, leading to errors. Flight 171’s crew, cleared as fit with adequate rest, faced no environmental hazards, yet Sabharwal’s emotional plea, “Take care of papa,” and Kunder’s note, “I think I’ll finally know,” suggest personal stressors. The 1982 crash prompted reforms in crew resource management (CRM), but Flight 171’s 32-second timeline left no room for effective CRM. Aviation expert John Cox told Reuters that the 787’s fuel switches, with their locking mechanisms, cannot be accidentally moved, raising the question, “If they were moved by a pilot, why?”.

Systemic Implications and Industry Response

The Potomac crash exposed flaws in winter operations and led to FAA mandates. Flight 171’s similarities have renewed scrutiny of Boeing’s fuel switch design and Air India’s maintenance practices, especially given VT-ANB’s unverified 2014 decommissioning. Air India’s post-crash inspections of its 787 and 737 fleets found no switch issues, but the failure to act on the 2018 advisory is a point of contention. The crash, Air India’s first fatal incident since 1985 and the 787’s first hull loss, challenges the Tata Group’s efforts to restore the airline’s reputation post-2022 privatization.

Conclusion: A Call for Answers

The parallels between Air India Flight 171 and the Potomac River crash underscore the fragility of flight and the devastating impact of seconds-long failures. Both incidents involve rapid loss of control, pilot confusion, and unanswered questions about human or systemic errors. Flight 171’s fuel cutoff, combined with the haunting CVR details and the aircraft’s mysterious history, demands a thorough investigation to prevent future tragedies. As families, like that of Ayushi Christian, seek closure, and the sole survivor, Vishwaskumar Ramesh, recovers, the aviation world awaits the final report to unravel whether this was a tragic echo of past mistakes or a new, unsettling anomaly.