In a significant development in the Ajit Pawar plane crash case, NCP (SP) MLA and his nephew Rohit Pawar has registered a zero FIR in Bengaluru, invoking serious charges including criminal conspiracy and murder.
Sections invoked
BNS 61 – Criminal conspiracy
BNS 103 – Punishment for murder
BNS 105 – Culpable homicide not amounting to murder
BNS 106 – Causing death by negligence
BNS 125 – Act endangering life or personal safety of others
BNS 238 – Causing disappearance of evidence or giving false information to shield an offender
BNS 336(2) – Forgery
FIR not registered locally, claims Pawar
In his complaint, Pawar said he initially approached the Marine Drive Baramati police station to file an FIR, but it was not registered. He was subsequently informed by the Pune CID that authorities were examining the case only as an Accidental Death Report (ADR).
Allegations of larger conspiracy
Pawar has alleged that the crash was not an accident but part of a “larger criminal conspiracy” aimed at eliminating Maharashtra Deputy Chief Minister Ajit Pawar.
According to his FIR, the available material points to “systematic violations of aviation and safety regulations, deliberate falsification of records, and gross negligence in maintenance and operations,” which allegedly led to the crash.
Aircraft safety violations flagged
Pawar has raised concerns about the aircraft, identified as VT-SSK. He stated that it had logged around 4,915 flight hours—just 85 hours short of the mandatory engine Time Before Overhaul (TBO) limit of 5,000 hours.
Despite nearing this threshold, the aircraft was allegedly deployed for operations. More critically, Pawar claimed that the operator, VSR, under-reported flight hours in official logbooks, with credible information suggesting the aircraft may have exceeded 8,000 hours—well beyond certified limits.
Visibility norms allegedly ignored
The FIR also flags discrepancies in weather assessment on the day of the crash. Pawar said a flying training organisation reportedly assessed visibility at 3,000 metres using a hand-drawn chart, while Pune METAR data indicated visibility of around 2,000 metres with mist. Satellite imagery also showed fog patches over Baramati.
Under Indian Civil Aviation Requirements, aircraft cannot be cleared for landing under Visual Flight Rules if visibility is below 5 km. Despite this, landing clearance was allegedly granted.
Questions over pilot fitness
Pawar has also raised concerns about the fitness of Chief Pilot Sumit Kapoor, alleging a history of alcohol-related violations. According to the FIR, Kapoor tested positive for alcohol prior to flights in 2010 and 2017, leading to a three-year suspension by the DGCA.
He was also reportedly asked to discontinue advanced Learjet training in the United States due to excessive alcohol consumption. Pawar alleged that despite this, he was later appointed Chief Pilot and assigned to operate the Deputy Chief Minister’s flight.
Suspicious decisions during landing
The FIR points to anomalies in cockpit decisions. Pawar said the crew initially requested Runway 29, considered safer, but switched to Runway 11—a tabletop runway—within two minutes, without apparent operational justification.
He also noted that no second go-around was attempted despite indications of a failed first approach. In the final recorded moments, the co-pilot was reportedly heard exclaiming “Oh shit, oh shit,” while the chief pilot remained silent, with no distress call or corrective action. Pawar suggested this could indicate either incapacitation or deliberate inaction.
Last-minute travel change under scrutiny
The FIR also flags what it calls “suspicious schedule anomalies.” Pawar claimed that Ajit Pawar was originally scheduled to travel to Pune by road on January 27, 2026, with a full motorcade arranged. However, he remained in Mumbai without a disclosed reason before eventually taking the flight.
