Rohit Pawar Claims ‘Strong Possibility Of Sabotage’ In Ajit Pawar Plane Crash, Lists Seven Grounds For Suspicion
Rohit Pawar Claims ‘Strong Possibility Of Sabotage’ In Ajit Pawar Plane Crash, Lists Seven Grounds For Suspicion
Mumbai, February 11, 2026: NCP leader Rohit Pawar on Tuesday alleged that the plane crash involving senior leader Ajit Pawar may have been the result of foul play, asserting that there is a “100 percent possibility of sabotage.” Addressing a detailed press conference, Pawar presented seven points which he said raised serious concerns about the circumstances leading to the fatal crash.
1. Sudden Changes In Schedule and Pilots
Pawar questioned last-minute alterations to the travel plan, including a change in departure time and the replacement of both pilots. The flight was initially scheduled for 7 am, and one of the pilots was expected to arrive by 6.30 am but reportedly cited traffic congestion. Pawar asked whether traffic at that early hour was plausible and demanded the release of call detail records (CDRs) and CCTV footage to verify the claim. He also sought clarity on where the pilots were coming from, whether both were stuck in traffic, and why both were replaced if only one was delayed. Questions were also raised about the new pilots’ duty hours, prior flights and whether mandatory tests were conducted before take-off.
2. Discrepancies in Official Timings
He pointed to inconsistencies between the Union Civil Aviation Ministry’s report and the Air Traffic Control (ATC) transcript. One document reportedly states the aircraft contacted Baramati ATC at 8:18 am, while another mentions 8:19 am. Pawar stressed that even a minute’s difference is critical in aviation, where seconds can determine survival.
3. Flight Radar Signal Loss
According to Pawar, flight radar data shows the aircraft’s signal was lost at 8:43:19 am—about a minute before the crash. He questioned whether the aircraft’s transponder was intentionally switched off.
4. Landing Despite Low Visibility
Pawar said that minimum visibility of 5 km is generally required for landing. He claimed ATC had communicated visibility conditions, yet the aircraft continued toward Baramati instead of diverting back to Pune when conditions were unclear.
5. Runway Selection Concerns
Baramati airport has Runway 11 and Runway 29. Pawar alleged that although clearance for Runway 29 was available, the aircraft sought to land on Runway 11 instead. He questioned why this preference was made, especially after a reported “go-around” attempt.
6. Early Descent of Aircraft
He further claimed that the aircraft began descending before reaching the appropriate distance required for a proper landing approach, increasing the risk of impact before the designated runway threshold.
7. Silence in the Final Minutes
Pawar also referred to reports that the co-pilot was heard reacting moments before the crash, while the main pilot reportedly remained silent in the last three to four minutes. He questioned the significance of this silence during a critical emergency.
Calling for a transparent and independent investigation, Rohit Pawar urged authorities to release all technical data, cockpit voice recordings, radar logs and surveillance footage to establish the exact cause of the crash.
