Plane CrashesVersion 5

Trainer aircraft goes off runway at Baramati Airport; no injuries reported

Reports differ on the aircraft type, the phase of flight and the time of the August 9, 2026 runway excursion in Pune district, Maharashtra.

2 reports on this incident · first at Aug 9, 2026, 8:28 p.m. ET

By AI ReporterFirst reported Feb 28, 2026, 11:24 a.m. ETUpdated Aug 10, 2026, 8:40 p.m. ET

A went off the runway at Baramati Airport in Pune district, Maharashtra, on August 9, 2026, sustaining minor damage, according to Hindustan Times, idrw.org, the Free Press Journal and the International Business Times India. Reports of the time differ: idrw.org gave IST, while the Free Press Journal and the International Business Times India gave , and prahaar.in gave . Those four outlets reported no injuries. Accounts of the aircraft differ and none outweighs the others: idrw.org described a , the Free Press Journal a , and The Hindu businessline reported on a . idrw.org and Hindustan Times reported the registration as and named the operator as the ; the International Business Times India described the operator only as a . The aircraft crossed the threshold of Runway 29, reaching around 20 feet beyond the runway end, and went off the extended paved surface to the right side beyond the runway, per Pune Rural Superintendent of Police Sandeep Singh Gill. Reporting described the flight as a Circuit and Emergencies training exercise with people on board — identified in the coverage as a flight instructor and a cadet, both reported safe. According to the reporting, the aircraft lined up on the Runway 29 threshold and the was aborted, then lined up on the Runway 11 threshold where the was aborted again; it was unable to stop within the paved surface and veered off beyond the threshold of Runway 29 to the right, coming to rest in a grassy area. Prima facie damage was reported to the propeller, engine cowling and nose gear. Accounts of the phase of flight differ: the Free Press Journal and the International Business Times India reported , Hindustan Times, idrw.org and prahaar.in reported , and The Hindu businessline reported . Accounts of where the inquiry stands also differ and none outweighs the others: idrw.org reported an investigation open, with a DGCA Air Safety team proceeding to the site to conduct a investigation; The Hindu businessline reported the matter at the stage; the International Business Times India reported the cause as unknown. Casualty accounts diverge and the disagreement should not be collapsed: the Free Press Journal and idrw.org reported no fatalities, the better-supported figure; The Hindu businessline reported fatalities, souls on board and passengers among them, in its reporting on the January crash. The Aircraft Accident Investigation Bureau's report into the crash of a 45 near Baramati airport flagged poor visibility — below the required level — but assigned no cause, The Hindu businessline reported. According to that account, the jet first approached Runway 11 and then initiated a go-around; on the second the crew reported the runway in sight and were cleared to land. A distress transmission was heard seconds before the aircraft crashed "about 50 metres" to the left of Runway 11 near the threshold, striking trees. The report recorded the aircraft as indicated airworthy with valid certificates and no MEL items pending, and the pilots as appropriately licensed, medically fit and with negative breath analyser tests. Flight data recorder data has been downloaded and is under analysis; the cockpit voice recorder sustained thermal damage and will be examined with assistance from the US National Transportation Safety Board. The report stopped short of assigning a final cause. Maharashtra's then Deputy Chief Minister and Finance Minister Ajit Pawar was among those killed when the private charter plane carrying him and four others crashed at Baramati on January 28, 2026, according to The Hindu businessline, Hindustan Times, the Free Press Journal and the International Business Times India; the reporting listed the others as a security officer, an air hostess and the flight crew. The AAIB is expected to submit its final report by January next year. Investigators noted faded runway markings and loose gravel, the absence of a windsock on the Runway 11 side, no perimeter boundary wall and no in-house aircraft rescue and firefighting unit, according to the reporting. Baramati is described as an uncontrolled airfield without a certified meteorological facility or instrument systems, with the air traffic function handled from temporary towers operated by flying training organisations. The AAIB recommended that the DGCA ensure prescribed safety standards at uncontrolled airfields. Hindustan Times and the Free Press Journal 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. The Free Press Journal described the August event as the second plane crash incident in the Baramati region this year, while other reporting counted it as the third aircraft accident at Baramati in 2026, between January 28 and August 9, 2026; outlets reported that on May 13, 2026 a of a different crash landed near the Baramati airstrip following a technical snag with no casualties, and that in May another crashed near Gojubavi village adjacent to the airstrip, with the trainee pilot escaping safely. Those earlier events say nothing about the cause of any other.

Earlier reports

Aug 9, 2026, 8:28 p.m. ETFirst report
Trainer aircraft crash-lands at Baramati Airport, no injuries reported
A trainer aircraft operated by a private company crash-landed at Baramati Airport in Pune district at around 12:35 pm, 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 landing. 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 Learjet 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

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.
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.
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.
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.
Version 110 Aug 2026, 00:53
First published.
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.