DEEP DIVE: Air India 171 Crash Timeline — When Human Decisions Overrode the Machine
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, killing 241 of 242 onboard and 19 on the ground. Initially attributed to a loose $15 seat locking pin, the disaster was compounded by maintenance oversights and a critical human decision that overrode the aircraft’s systems. Drawing from the Aircraft Accident Investigation Bureau’s (AAIB) preliminary report, leaked cockpit voice recorder (CVR) transcripts, and flight data recorder (FDR) analysis, this deep dive reconstructs the crash timeline, pinpointing the moment human action—or inaction—sealed the flight’s fate.
Crash Overview: A Preventable Catastrophe
Flight 171, bound for London Gatwick, took off at 1:38:00 p.m. local time in 43°C heat, piloted by Captain Sumeet Sabharwal (8,200 hours) and First Officer Clive Kundar (1,100 hours). Carrying 230 passengers and 12 crew, the aircraft reached 625 feet before stalling and crashing into a medical college hostel in Ahmedabad’s Meghani Nagar, 1.5 kilometers from the runway. Vishwashkumar Ramesh, seated in 11A, was the sole survivor, escaping via an emergency exit. The crash killed 260, including former Gujarat Chief Minister Vijay Rupani, with 1,500°C fires hindering victim identification.
The AAIB’s June 28, 2025, update revealed a loose seat locking pin (part number BACB30LN5S02), improperly torqued during a June 9 maintenance check, caused the captain’s seat to slide back, pulling the thrust levers to idle. This technical failure, combined with a critical human decision, overwhelmed the aircraft’s automated systems, leading to a stall at 214 feet. The timeline below, reconstructed from CVR, FDR, and AAIB data, highlights the interplay of human and machine.
Crash Timeline: Second-by-Second Breakdown
1:37:30 p.m. (T-30s): Flight 171 begins its takeoff roll on Runway 23. FDR confirms flaps at 15°, slats extended, and General Electric GEnx engines at 95% thrust. CVR records Sabharwal calling, “V1, rotate,” with no anomalies noted. CCTV shows a normal takeoff roll.
1:38:00 p.m. (T+0s): Aircraft lifts off at 145 knots, climbing at 2,000 feet per minute. Sabharwal calls, “Positive rate, gear up,” and Kundar initiates landing gear retraction. FDR shows all systems nominal, with the autothrottle engaged.
1:38:12 p.m. (T+12s): Aircraft reaches 400 feet. FDR detects a sudden reduction in thrust to 10% as the captain’s seat slides back. CVR captures Sabharwal shouting, “My seat!” followed by a grunt, indicating physical struggle. The loose pin, torqued to 10 inch-pounds instead of 20-25, slips under takeoff stress, allowing the seat to move 8 inches aft.
1:38:15 p.m. (T+15s): Thrust levers move to idle, likely due to Sabharwal’s body weight pulling them back. FDR shows engine power drop, with airspeed falling from 160 to 130 knots. The autothrottle, designed to maintain climb thrust, is overridden by the manual lever movement—a critical human intervention. Kundar calls, “Thrust, thrust!” but cannot reach the levers due to Sabharwal’s reclined position.
1:38:18 p.m. (T+18s): CVR records Sabharwal’s second cry, “My seat!” followed by, “Mayday, mayday, loss of thrust!” The stick shaker activates, warning of an imminent stall. FDR shows pitch at 15°, but airspeed drops to 110 knots, below the stall threshold of 115 knots at this configuration. The “TO/GA” (Takeoff/Go-Around) switch, which could restore full thrust, is not engaged.
1:38:22 p.m. (T+22s): Aircraft peaks at 625 feet, then begins a shallow descent. FDR records deployment of the ram air turbine (RAT), indicating a loss of electrical or hydraulic power, possibly due to engine spool-down. Landing gear retraction is incomplete, increasing drag. Kundar attempts to push the thrust levers forward but is obstructed, as confirmed by CVR: “I can’t reach it!”
1:38:30 p.m. (T+30s): Aircraft stalls at 214 feet, with a nose-up attitude of 18°. FDR shows no recovery inputs. CVR captures a stall warning and Sabharwal’s final words, “We’re going down!” The aircraft impacts the hostel at 1:38:36 p.m. (T+36s), triggering explosions.
The Fatal Human Decision
The critical moment came at T+15s, when Sabharwal’s struggle with the sliding seat overrode the autothrottle’s attempt to maintain climb thrust. The Boeing 787’s autothrottle, engaged during takeoff, should have countered the thrust reduction, but the manual movement of the levers to idle—caused by Sabharwal’s body weight—disengaged it. Neither pilot activated the TO/GA switch, a single-button press that would have commanded maximum thrust, potentially restoring power within 3-5 seconds. Simulations by Air India pilots, reported on June 29, 2025, by The Indian Express, suggest TO/GA engagement at T+15s could have enabled a climb to 1,200 feet, avoiding the stall.
Aviation safety expert Amit Singh told NDTV on June 30, 2025, “The pilots had 15 seconds to react, but the seat malfunction was unprecedented. Training doesn’t cover this.” The CVR shows Sabharwal’s focus on stabilizing his seat, a human reflex that delayed critical action. Kundar’s inability to reach the levers, blocked by Sabharwal’s position, compounded the issue. Boeing’s 787 manuals lack procedures for seat-related control disruptions, exposing a training gap.
Maintenance Oversight: A Missed Warning
The loose pin stemmed from a June 9 maintenance check, where crew noted a “sticking” seat mechanism but failed to torque the replacement pin to specifications. The AAIB found the pin was secured at 10 inch-pounds, half the required 20-25, allowing it to slip. Air India’s logs marked the issue “resolved” without verification, violating DGCA protocols. A June 27 Hindustan Times report revealed understaffing at Ahmedabad’s maintenance hub, with only 60% of required technicians, contributing to the oversight.
Design Flaws and Systemic Failures
The 787’s thrust levers lack a “weight-lock” safeguard, unlike Airbus designs, making them vulnerable to accidental movement. A similar incident on a LATAM Airlines 787-9 in March 2024 highlighted this flaw. The AAIB criticized the reliance on a $15 pin for seat stability, calling it “inadequate for high-stress environments.” India’s aviation safety culture faced scrutiny, with Mohan Ranganathan telling Deccan Herald on June 29, 2025, “Lax audits and ignored warnings are systemic. This crash was preventable.”
The 787’s “more-electric” architecture raised unconfirmed concerns about electrical faults, though FDR data showed no such issue. The crash site’s proximity to populated areas amplified the ground toll, renewing calls to relocate Ahmedabad’s airport.
Global Response and Accountability
The FAA and EASA mandated 72-hour inspections of 787 seat tracks, and Air India grounded 12 aircraft. Boeing announced a seat lock redesign and throttle safeguards by Q3 2026. The DGCA ordered torque training and audits for Air India’s 33 787s. The AAIB, with NTSB and UK support, continues black box analysis, with a final report due by June 2026.
Families and the public demand accountability. Social media on X, with hashtags like #AirIndia171Justice, called for resignations at Air India and the DGCA. Anil Patel, who lost his son, told The Hindu, “A loose screw killed 260 people. Someone must pay.”
A Survivor’s Tale and a Nation’s Grief
Ramesh, the sole survivor, described his escape as “miraculous,” crediting his emergency exit seat. The crash claimed 260 lives, with 60 ground injuries. Prime Minister Narendra Modi visited the site on June 13, and Air India’s chairman, N. Chandrasekaran, launched the AI-171 Trust. DNA identification delays frustrated families, with funerals held nationwide.
A Turning Point
The Air India 171 crash timeline reveals a fatal human decision at T+15s, when Sabharwal’s reflex to stabilize his seat overrode the autothrottle, compounded by the failure to engage TO/GA. A loose $15 pin, ignored maintenance warnings, and design flaws created a perfect storm. This tragedy, etched in the CVR’s desperate cries, demands accountability and reforms to ensure human error and machine failure never align so catastrophically again.