Ahmedabad Plane Crash
On June 12, 2025, Air India Flight 171—a Boeing 787-8 Dreamliner (registration VT-ANB)—took off from Ahmedabad at 1:39 PM IST en route to London Gatwick. However, just 30 seconds after takeoff, the aircraft failed to gain altitude, subsequently sent out a MAYDAY call, and tragically crashed into a medical-college hostel near the airport. As a result, the plane burst into flames, killing 241 of 242 onboard and 28 people on the ground. Consequently, the Ahmedabad plane crash marked India’s deadliest single-plane disaster. Following this, investigators retrieved the flight data and cockpit voice recorders. Moreover, the Indian AAIB, along with the U.S. NTSB, U.K. AAIB, and Boeing, launched a joint investigation.
🔍 Possible Causes
1. Faulty Flap and Gear Configuration
Video footage shows the aircraft retracted its flaps too early while, at the same time, leaving the landing gear down. Consequently, this configuration reduced lift and increased drag, which, in turn, likely caused the aircraft to lose climb performance. Furthermore, investigators suspect either a mechanical failure in the flap system or a pilot configuration error. Since the Boeing 787 relies heavily on automation, therefore, even small mistakes can result in disastrous consequences.
2. Bird Strike or Engine Failure
Bird activity around Ahmedabad airport raises the possibility that a bird strike damaged one or both General Electric engines. A collision could have led to thrust loss. Investigators will analyze engine damage and test bird remains to determine this.
3. Hot Weather Performance Issues
Ahmedabad’s extreme midday temperatures—reaching nearly 40°C (104°F)—could have contributed to the crash. High temperatures reduce air density, which in turn lowers lift. Reports indicate the aircraft may not have used the full runway, which would have limited its ability to reach takeoff speed and climb safely. Investigators will review runway usage logs and calculate whether weather and payload affected performance.
4. Pre-Existing Technical Faults
Passengers on previous flights reported cabin issues like malfunctioning lights, air-conditioning, and inflight systems. These signs may have pointed to deeper faults in the aircraft’s electrical or control systems. Investigators will examine maintenance records and match those issues with onboard data to confirm any link.
5. Pilot Error Under Pressure
Though the captain logged over 8,000 hours of flying time, crew members may have struggled to manage unexpected system failures or aircraft behavior. Investigators believe the pilots possibly misjudged the situation during takeoff and failed to correct it in time. They will analyze voice recordings to reconstruct the flight crew’s actions and decisions.
🕵️ Ongoing Investigation
Authorities have already begun analyzing the flight data recorder and cockpit voice recorder to reconstruct the sequence of events—such as when the flaps retracted, when the gear lowered, and what alarms sounded. Boeing and GE engineers are inspecting the engine remains, while airport authorities are reviewing radar data, bird activity, and ATC communications. The AAIB and supporting teams are working to determine how all these factors may have combined to cause the crash.
✨ Conclusion
At this stage, investigators are considering multiple possible causes: improper flap or gear handling, bird strike, high temperature performance issues, technical malfunctions, or pilot error. The investigation team will release a full report once they complete their analysis of flight data, aircraft systems, and cockpit conversations. The findings will help authorities improve safety measures and prevent such tragedies in the future.
Related searches:
About The Author
