Baramati Learjet Crash: Timeline Reveals Multiple Landing Attempts Amid Poor Visibility
NEW DELHI: The final moments of the Learjet 45 aircraft carrying Maharashtra deputy chief minister Ajit Pawar were marked by repeated landing attempts and challenging visibility conditions, culminating in a tragic crash and fire near the runway threshold at Baramati. Preliminary information from Union civil aviation minister Ram Mohan Naidu Kinjarapu indicates that poor visibility was a significant factor during the landing phase.
Detailed Timeline of the Fatal Approach
According to official accounts from the civil aviation ministry, the aircraft first contacted Baramati Air Traffic Control (ATC) at 8:18 am. The pilot reported being on the final approach for runway 11 but stated that the runway was not in sight, prompting an immediate go-around maneuver. After circling, the aircraft returned for another landing attempt, with the pilot confirming runway visibility at 8:43 am, after which ATC cleared it to land.
Moments later, at approximately 8:44 am, ATC personnel observed flames near the threshold of runway 11. The Directorate General of Civil Aviation (DGCA) confirmed the chartered plane, which originated from Mumbai, crash-landed around 8:45 am at the runway threshold in Baramati. The accident resulted in five fatalities, including Deputy CM Ajit Pawar, two personnel (one Personal Security Officer and one attendant), and two crew members.
Key Unanswered Questions in the Investigation
The Aircraft Accident Investigation Bureau (AAIB) has assumed control of the probe, aiming to reconstruct the final approach. As investigators delve into the details, several critical questions remain unresolved:
- What transpired after the final landing clearance? The aircraft received clearance at 8:43 am, but ATC recorded no read-back or acknowledgment from the pilot. Flames were spotted by 8:44 am, raising concerns about potential sudden systems failure, loss of control, or a cockpit emergency in the final seconds.
- Why proceed with landing amid poor visibility at an uncontrolled airfield? Preliminary reports highlight poor visibility during landing. Baramati operates as an uncontrolled airfield, where traffic information is typically shared by instructors or pilots from flying schools. Investigators are examining whether weather and airfield conditions warranted a diversion after the initial missed approach.
- What caused the abrupt radio silence post-clearance? The crew maintained active communication until the final clearance, requesting updates on wind and visibility. The sudden loss of response prompts inquiries into possible communication failures, crew incapacitation, workload overload, or avionics malfunctions.
- Did mechanical or engine failures occur during the go-around or final approach? The aircraft burst into flames at the runway edge, despite regulatory records indicating valid certifications and recent airworthiness reviews. Potential causes under scrutiny include engine failure, bird strikes, fuel leaks, electrical fires, or a hard landing triggering ignition.
- Was the landing approach stable and were standard procedures followed? The aircraft was advised to descend under visual meteorological conditions at the pilot’s discretion. Questions arise about whether the approach was stabilized according to Standard Operating Procedures (SOP) or if the aircraft arrived too high, too fast, or too late for a safe landing.
Investigation and Aftermath
AAIB investigators will now focus on retrieving and analyzing critical evidence, including flight data recorders, cockpit voice recordings, aircraft maintenance logs, and airfield weather reports. Maharashtra Chief Minister Devendra Fadnavis has announced a state holiday and three days of mourning in honor of Ajit Pawar’s passing. Until the investigation yields conclusive findings, the precise cause of this devastating crash remains shrouded in mystery, underscoring the complexities of aviation safety in adverse conditions.
