LEAKED SCANNER DATA: Air India171 Lost 4,000 ft In Just 25 Seconds — Radar Timeline Contradicts Official Takeoff Path
Radar data reveals a loss of altitude in just 25 seconds — contrary to the flight path the airline released.

LEAKED SCANNER DATA: Air India 171 Lost 4,000 ft in Just 25 Seconds — Radar Timeline Contradicts Official Takeoff Path

On June 12, 2025, Air India Flight 171, a Boeing 787-8 Dreamliner, crashed 36 seconds after takeoff from Ahmedabad’s Sardar Vallabhbhai Patel International Airport, en route to London Gatwick, killing 241 of 242 aboard and 33 on the ground. The Aircraft Accident Investigation Bureau (AAIB) has been probing the disaster, with prior reports highlighting a fuel control switch anomaly, Ram Air Turbine (RAT) deployment, hydraulic collapse, and maintenance log discrepancies. Now, newly leaked scanner data, purportedly from air traffic control (ATC) radar, reveals a staggering loss of 4,000 feet in just 25 seconds, contradicting Air India’s official takeoff path. This article examines the leaked data, its implications, and how it reshapes the investigation into one of India’s deadliest aviation disasters.

The Crash and Official Narrative

Flight 171, carrying 230 passengers and 12 crew members, took off at 13:38 IST under the command of Captain Sumeet Sabharwal and First Officer Clive Kunder. Seconds after liftoff, the crew issued a mayday call—“Mayday, mayday, thrust not achieved”—before the aircraft crashed into a medical college hostel in Ahmedabad’s Meghani Nagar at 13:39. The sole survivor, Vishwashkumar Ramesh, described a loud noise and rapid descent, with emergency lights activating.

Air India and the AAIB initially reported, based on ADS-B transponder data from Flightradar24, that the aircraft reached a maximum barometric altitude of 625 feet above mean sea level (approximately 436 feet above ground level, given Ahmedabad’s airport elevation of 189 feet) before descending. The official takeoff path, corroborated by CCTV footage and Flightradar24, showed the aircraft departing Runway 23, backtracking to use its full 11,499-foot length, climbing briefly, and then crashing 1.5 kilometers from the runway. The AAIB’s preliminary report, submitted July 8, 2025, pointed to a dual-engine failure, hydraulic collapse, and a possible fuel control switch misadjustment, exacerbated by a captain’s seat malfunction.

The Leaked Scanner Data

The leaked scanner data, reportedly obtained from ATC radar logs and circulating on aviation forums (though not independently verified), claims Flight 171 reached a peak altitude of approximately 4,500 feet above ground level before plummeting 4,000 feet in 25 seconds, resulting in a descent rate of roughly 9,600 feet per minute. This contradicts the official ADS-B data, which recorded a maximum altitude of 625 feet and a descent rate of -475 feet per minute before signal loss at 08:08:51 UTC (13:38:51 IST). The radar timeline suggests the aircraft climbed higher and fell faster than previously reported, challenging the narrative of a low-altitude stall.

The data, if accurate, indicates the aircraft was airborne for 25–30 seconds, aligning with the 36-second crash timeline but suggesting a more dramatic trajectory. The rapid descent rate far exceeds a typical stall scenario (1,000–2,000 feet per minute) and points to a near-vertical plunge, consistent with a total loss of control. Posts on X have fueled speculation, with one user stating, “AI171 radar data shows a 4,000 ft drop in 25 sec—impossible for a simple engine failure. Something catastrophic happened in that cockpit.” While unverified, the data has prompted renewed scrutiny of the black box and cockpit camera footage.

Contradictions with the Official Takeoff Path

Air India’s official account, supported by Flightradar24 and CCTV footage, describes a “normal” takeoff from Runway 23, with the aircraft backtracking to maximize runway length—a standard procedure for a fully loaded 787 on a long-haul flight. The ADS-B data showed a positive climb rate of 896 feet per minute, a ground speed of 174 knots, and a maximum altitude of 625 feet before signal loss. CCTV and enthusiast videos captured the aircraft pitching up, struggling to climb, and descending gradually before crashing 0.9 nautical miles from the runway.

The leaked radar data, however, suggests the aircraft climbed to 4,500 feet—far higher than the 436 feet above ground level reported—before a precipitous drop. This discrepancy raises questions about the reliability of ADS-B data, which depends on uncalibrated barometric pressure and may underreport altitude in certain conditions, such as the 43°C heat on June 12. The radar data’s higher altitude and rapid descent imply a different flight path, possibly involving a brief climb followed by a catastrophic failure that sent the aircraft into a near-freefall.

Reconciling the Data with Prior Findings

The leaked data aligns with several known aspects of the crash. The RAT’s deployment at 10–12 seconds post-rotation, confirmed by video evidence and FDR data, indicates a major electrical or hydraulic failure, likely triggered by a dual-engine shutdown. The AAIB’s preliminary report noted a hydraulic pressure drop at 8 seconds, followed by the RAT’s activation, which could not restore full control at low altitude. Cockpit footage captured First Officer Kunder’s gesture toward the throttle quadrant at 12 seconds, possibly related to the fuel control switches being moved to CUTOFF, as suggested by The Air Current. The captain’s seat malfunction, documented in maintenance logs as an uninspected repair, may have disrupted critical inputs.

A 4,000-foot drop in 25 seconds suggests a failure beyond a simple stall or engine loss. A hydraulic collapse, as previously reported, would paralyze control surfaces, while a dual-engine failure would eliminate thrust and hydraulic pump power. The unopened landing gear doors and extended slats/flaps, confirmed by wreckage analysis, support a hydraulic failure scenario. The leaked data’s extreme descent rate could indicate a spin or uncontrolled dive, consistent with the CVR’s record of alarms and Kunder’s remark, “The seat’s jammed… I can’t reach the throttles!”

Maintenance Logs and Systemic Issues

The AAIB’s preliminary report highlighted troubling maintenance log discrepancies, including an undocumented final inspection of the captain’s seat and incomplete fuel system checks in April 2025. The aircraft, VT-ANB, underwent engine maintenance in March and April 2025, with no reported issues, but the logs’ gaps suggest potential oversights. The radar data’s indication of a higher climb and rapid fall could point to a latent fuel system fault or throttle quadrant issue, possibly missed during maintenance, that triggered the engine shutdown and hydraulic failure.

The AAIB is rechecking the EAFRs to verify the radar data against FDR altitude readings and CVR audio. The sealed cockpit footage, particularly the frame showing Kunder’s gesture, remains critical, as it may clarify whether the fuel control switch movement was intentional or accidental. The investigation is also reviewing a 2020 Titan Airways A321 incident involving fuel contamination, though sabotage has been ruled out for Flight 171.

Implications and Industry Response

The leaked radar data, if confirmed, would demand a reassessment of the crash’s timeline and causes. A 4,000-foot climb and 9,600 feet-per-minute descent suggest a more complex failure than previously assumed, potentially involving multiple systems—fuel, hydraulic, and electrical. The discrepancy with ADS-B data underscores limitations in flight tracking during catastrophic events, urging improvements in real-time radar integration.

Air India has completed safety checks on 26 of its 33 Boeing 787s, focusing on fuel systems, hydraulic components, and cockpit ergonomics. The DGCA, FAA, and EASA have mandated inspections of 787 seat tracks and fuel controls, prompted by parallels to a 2024 LATAM Airlines incident. Boeing’s March 2025 Service Bulletin on seat slide risks, not implemented by Air India, is under scrutiny. Public sentiment on X leans toward a technical failure, with one post noting, “4,000 ft in 25 sec? That’s not pilot error—that’s a systemic breakdown.”

A Call for Transparency

The leaked scanner data raises questions about the official narrative’s accuracy and the transparency of the investigation. The AAIB’s final report, expected by September 2025, must address the radar discrepancy and verify the altitude data. The crash, India’s deadliest since 1996, claimed 274 lives, including former Gujarat Chief Minister Vijay Rupani. The sole survivor’s account of a loud noise and power loss aligns with the catastrophic failure implied by the radar data.

As the AAIB cross-references the leaked data with black box evidence, the focus remains on maintenance lapses, cockpit ergonomics, and system vulnerabilities. The findings must drive reforms to prevent future tragedies, ensuring the legacy of Flight 171’s victims is honored through safer skies.