Tragic Learjet Crash Claims Life of Maharashtra Deputy CM Ajit Pawar

The tragic crash of a Learjet aircraft this Wednesday morning has resulted in the death of Maharashtra's Deputy Chief Minister Ajit Pawar and four other individuals. The aircraft's black box has been retrieved, which contains crucial data including the Flight Data Recorder and Cockpit Voice Recorder. A thorough examination of this device is set to unfold to uncover the circumstances surrounding the devastating crash.

The Learjet 45, operated by the Delhi-based VSR Ventures, went down while attempting a second landing at Baramati Airport at approximately 8:45 am. The ill-fated flight carried 66-year-old Ajit Pawar, his personal security officer, an attendant, and two pilots—Sumit Kapur, the pilot-in-command, and co-pilot Shambhavi Pathak. Unfortunately, none of the five aboard survived the incident.

Ajit Pawar had departed from Mumbai around 8 am to participate in several election rallies back in his hometown of Baramati, in anticipation of local body elections. In the wake of the crash, a specialized team from the Aircraft Accident Investigation Bureau has arrived on the scene to begin a forensic investigation into the accident.

Officials from the Directorate General of Civil Aviation (DGCA) reported that the last message from the cockpit indicated panicked communication, where the phrase “oh s***” was noted, signaling unexpected distress. Baramati airport's ground control, manned by pilot cadets from local aviation institutions, including Redbird Aviation and Carver Aviation, maintained contact throughout the attempt to land.

The Civil Aviation Ministry provided a rundown of events leading to the disaster: The aircraft, registered as VT-SSK, made contact with Baramati airport control at 8:18 am. The pilot, boasting over 15,000 flying hours, and the co-pilot, with approximately 1,500 hours, received weather updates, reporting visibility around 3,000 meters, and were granted freedom to land as they deemed fit.

As the Learjet neared Runway 11, the pilot noted that the runway was obscured, prompting instructions for a go-around—standard procedure when safe landing is not attainable. After circling back, the crew confirmed sight of the runway and received clearance for landing at 8:43 am. However, they failed to provide the required readback to confirm landing authorization.

At 8:44 am, air traffic control spotted flames in proximity to the runway, confirming the aircraft had crashed.

Ongoing investigations are crucial to discern the exact causes behind this heartbreaking incident, which has left the state and nation in shock.