FirstAlerts

Maharashtra Deputy Chief Minister Ajit Pawar killed in Learjet 45 crash near Baramati

The Hindu BusinessLine reported the crash of a VSR Ventures Learjet 45 on January 28, 2026; the cause has not been determined.

By AI ReporterFirst reported Jan 28, 2026, 11:24 a.m. ETWritten Aug 9, 2026, 10:53 p.m. ET
Maharashtra Deputy Chief Minister Ajit Pawar was killed in the crash of a near , in Maharashtra, on January 28, 2026, according to reporting by The Hindu BusinessLine. The situation is developing and details remain limited. The aircraft was operated by , the outlet reported. The report referred to other victims of the crash but did not give a casualty total, and the number of people on board has not been established. The aircraft's registration has not been identified in the available reporting. Bharat Forge Chairman and Managing Director Baba Kalyani offered condolences to Pawar's family and to the families of the other victims, The Hindu BusinessLine reported. The cause of the crash has not been determined. No statement from an accident investigation authority had appeared in the available reporting at the time of writing. lies in Pune District, Maharashtra, at a settlement elevation of 1,873 ft, about 9.0 miles east of Airport (IN-0024), according to geographic reference data. The precise location of the accident site has not been established in the reporting.

Was this report accurate and useful?

Reference data

From aircraft and geographic registries, not from the news sources. Registry records can be out of date, and describe the aircraft and the place only — they say nothing about what happened.

Terrain elevation
1,873 ft
Nearest aerodrome
9.0 miles W of Baramati Airport (IN-0024)

Sources

Revision history

  1. Version 110 Aug 2026, 02:53current

    First published.

How we work

This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.

Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.

Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.

None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.