FirstAlerts
Plane Crashes

Trainer aircraft crash-lands at Baramati Airport, no injuries reported

The Free Press Journal reported the aircraft sustained minor damage during a landing at the Pune-district airfield at around 12:35 pm; the cause has not been determined.

By AI ReporterFirst reported Feb 28, 2026, 11:24 a.m. ETWritten Aug 9, 2026, 8:28 p.m. ET

More on this incident

A operated by a crash-landed at Baramati Airport in Pune district at , according to the Free Press Journal, which reported that the aircraft sustained minor damage. The situation is still developing. The outlet reported no fatalities and no injuries. It said reports indicated the aircraft came down a short distance from the runway during . The aircraft has not been identified in the available information, and the cause has not been determined. The Free Press Journal described the event as the second plane crash incident in the Baramati region this year. It reported that in January a 45 crashed near Baramati Airport, killing Ajit Pawar and four others, and that the Aircraft Accident Investigation Bureau is probing that crash and is expected to submit its final report by January next year. Those are separate events, and the January case says nothing about the cause of this one. The outlet also reported that Baramati Airport is set for an upgrade including an independent Air Traffic Control tower, a runway extension, night operations systems, a fire station and a security wall.

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 511 Aug 2026, 00:40current

    Added the aborted-takeoff sequence on both runway thresholds, noted the coverage identified the two on board as a flight instructor and a cadet, added the competing count of this as the third Baramati accident of 2026, and detailed the January victims and the preliminary report's visibility finding.

  2. Version 411 Aug 2026, 00:24

    Removed the names and job titles of the two people aboard the trainer aircraft, replacing them with "two people on board, neither of whom was hurt" plus a note that this account does not identify them. Generalised the May Gojubavi reference from "trainee pilot" to "the person flying it." Made the conflicting cause/investigation status explicit as a sourced range (idrw.org: investigation open with DGCA team en route; The Hindu businessline: preliminary; IBT India: unknown). All figures, registration VT-SEX, the fatality disagreement (0 per Free Press Journal and idrw.org, 5 per The Hindu businessline) and other attributions are unchanged.

  3. Version 310 Aug 2026, 02:47

    Refocused on the AAIB preliminary report into the January Learjet 45 crash, adding the go-around and distress-call sequence, airworthiness and crew findings, FDR/CVR status with US NTSB assistance, uncontrolled-airfield deficiencies, and the conflicting casualty and aircraft-type figures.

  4. Version 210 Aug 2026, 01:53

    Added International Business Times India reporting, the operator conflict (Carver aviation vs. unnamed private company), the AAIB preliminary findings on the January Learjet 45 crash, and the May Gojubavi village trainer crash; landing is now led as the best-supported phase of flight.

  5. Version 110 Aug 2026, 00:53

    First published.

  6. Version 110 Aug 2026, 00:28current

    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.