A month after a tragic plane crash in Ahmedabad, the Aircraft Accident Investigation Bureau (AAIB) has released its preliminary report, shedding light on the critical moments just after take-off. The incident, which claimed the lives of nearly 260 passengers and crew, remains a chilling reminder of how rapidly aviation can turn tragic.

Key highlights from the report include sudden fuel shut-off to both engines, cockpit audio that captured tense exchange between the two pilots, and a brief Mayday call before control was lost. Read on for a detailed breakdown.

Timeline of the Incident

• Date & Flight: June 12, Ahmedabad → London (Gatwick), operating under Air India flight INR171.

• Occupants: 2 pilots (Captain and First Officer), 10 cabin crew, and 242 passengers.

• Crash Site: The aircraft crashed into a student hostel near Ahmedabad airport just seconds after take-off.

• Casualties: Around 260 fatalities, including residents of the damaged hostels. Only one passenger survived—the sole British national on board.

Aircrew Experience and Flight Preparation

• Captain Sumit Sabharwal: Holds an ATPL with approximately 8,200 flight hours.

• First Officer Clive Kundar: Holds a CPL with roughly 1,100 flight hours.

• Both pilots arrived in Ahmedabad the previous day and received adequate rest before the disaster flight. The first officer actively handled the take-off while the captain provided oversight.

Engine Failure: Fuel Cut-Off Switches Activated

According to the AAIB’s initial analysis:

1. Just after liftoff, the aircraft reached a maximum airspeed of 180 knots.

2. The fuel cut-off switches for both engines abruptly moved from ‘run’ to ‘cut-off’—one after the other, separated by just about one second.

3. Almost immediate engine power loss occurred due to the interrupted fuel supply, causing descending engine RPMs and triggering the crisis.

Tense Exchange Captured on Cockpit Voice Recorder

The CVR (Cockpit Voice Recorder) has revealed a chilling exchange:

• One pilot asks, “Did you cut it off?”

• The other responds, “I didn’t.”

• Shortly after, a frantic “Mayday! Mayday!” call was made to Air Traffic Control, but there was no time for any ATC acknowledgment before the aircraft lost lift and crashed.

Voice attribution to either pilot remains unclear in the report; determining responsibility remains a top priority.

The Unanswered Mayday Call

The Mayday distress call—sent to the airport’s tower—was never confirmed as received. Sources suggest radio contact was lost almost immediately after the crash commenced, leaving the pilots stranded in crisis without communication.

Impact on Hostel and Casualties

The aircraft plunged into a nearby medical student hostel, causing catastrophic destruction:

• Entire blocks (Atulya Hostels 1–4 & central mess) were leveled.

• The wreckage raised thick black smoke, witnessed by shocked residents.

• Internal rescue efforts were immediate, with survivors and first responders evacuated to local hospitals.

What the Report Doesn’t Reveal—Yet

• AAIB clarifies in its preliminary findings: It’s still undetermined if the fuel cut-off was caused by a human error (intentional or accidental) or a mechanical fault.

• Further investigation will rely on the Flight Data Recorder (FDR) to piece together switch positions and system behavior at each moment.

Air India Response

Air India issued a public statement expressing sympathy and cooperation:

“Air India stands with the victims’ families during this difficult time. We confirm receipt of the AAIB’s preliminary report dated July 12, 2025. We remain committed to full cooperation with the AAIB and other authorities, and requests regarding specific findings should be redirected to the AAIB.”

The airline has not yet commented on any specific technical details or pilot actions.

Flashback to June 12 Flight Path

• Scheduled Take-Off: Approximately 13:39 IST from Runway 23.

• Mayday: Called immediately after liftoff.

• Crash Zone: Hostel complex adjacent to the airport—a densely populated residential area.

What Investigators Will Focus On Next

The AAIB’s next steps include:

• Analyzing Flight Data Recorder (FDR) for technical performance and switch positions

• Distinguishing between human intervention vs. system malfunction

• Aligning CVR audio with recorded system data

• Interviewing support personnel and examining maintenance records

• Recommending new safety protocols if systemic faults are found

Implications for Aviation Safety

This tragic accident highlights critical areas of concern:

1. Fuel system safety: Emergency-proofing against accidental fuel cut-off

2. Cockpit protocols: Clarity on pilot roles and emergency procedures

3. Mayday procedures: Ensuring automated ATC overlap in the event of sudden communication drops

4. Crash-landing protocols in proximity to populated buildings

What Happens Next?

• AAIB Final Report: Expected later this year, with conclusive findings and recommendations.

• Industry Impact: Could lead to revised aviation safety guidelines in India and internationally.

• Pilot Training: Curricula may be updated to emphasize system error detection and recovery.

The Ahmedabad plane crash, as detailed in the AAIB’s preliminary report, tragically encapsulates how mechanical anomalies—intentional or accidental—can escalate into catastrophe within moments. Both engines shutting down post-takeoff and conflicting cockpit dialogue cataloged by the CVR provides unsettling clarity, but the full cause remains unknown.

The aviation community, victims’ families, and regulators now await the final AAIB report, which will determine if human error, equipment failure, or a combination led to one of India’s most jarring plane disasters.

Stay with KKNLive.com for real-time updates on crash investigations, pilot testimony, and aviation safety reforms.