FirstAlerts
Plane CrashesVersion 2

Trainer aircraft ran off Baramati runway during training exercise; both on board reported safe

Reports place the runway excursion at the Baramati airstrip in Pune district on 9 August 2026; the cause has not been determined and the DGCA is to conduct the initial investigation.

By AI ReporterFirst reported Aug 9, 2026, 7:15 a.m. ETUpdated Aug 10, 2026, 8:39 p.m. ET

More on this incident

A training aircraft ran off the paved surface at the airstrip on 9 August 2026. Navbharat Times identified it as an aircraft registered , and Navbharat Times and Khaskhabar named the operator as Karver Aviation. The site is given as "" by Navbharat Times and Bhaskar, as "" by Deshbandhu, as "" by Khaskhabar and as "" by Punjab Kesari, which places it in . The aircraft type is described differently and neither description is better supported: Punjab Kesari calls it a , Navbharat Times a "". The reports say the aircraft was being flown for a "circuit and emergency" training exercise and went off the paved surface to the right beyond the threshold of runway 29 — a runway excursion. Reporting differs on the phase of flight: Navbharat Times, Punjab Kesari and Bhaskar place it in , while Khaskhabar reports . On timing, Navbharat Times and Punjab Kesari put it at "" — about 12:30 pm — Deshbandhu at about 12:35 pm and Khaskhabar at about 12 pm. The reports say the aircraft had left for the exercise at 6.39 am UTC and that two rejected take-offs were made at the thresholds of runway 29 and runway 11. A captain and a cadet were on board and both were reported safe; the pilot was reported safe. The reports say the trainer aircraft belonged to a private company and sustained minor damage, and that according to the Ministry of Civil Aviation the propeller, engine cowling and nose gear were damaged. Police and the relevant authorities reached the site immediately after the event. The reports also record that the deputy chief minister and MLA, Sunetra Pawar, rejected reports of a crash, saying a wheel became caught at the edge while the aircraft was turning. The cause has not been determined. Punjab Kesari reported that, according to the Ministry of Civil Aviation, the initial investigation will be carried out by the DGCA air safety team. Bhaskar reported that a DGCA team will conduct the initial investigation and that, according to police, early information described the event as a runway excursion. Deshbandhu reported that the relevant authorities are examining the circumstances and will also establish whether there was a technical problem with the aircraft or some other reason. Navbharat Times quoted a senior police officer as saying the incident is under investigation and that it would be premature to comment on whether there was a technical fault or another problem. Police, including Pune police, are also named among those involved. The outlets also noted earlier events at the same airstrip, which say nothing about the cause of this one: that technical problems occurred during three times at the airstrip in the past eight months; that a trainer aircraft of the Redbird Flight Training Academy crashed at on 13 May, with the trainee pilot surviving; and that seven months earlier, in January, five people including NCP leader Ajit Pawar died in a Learjet 45 crash at the same airstrip, an accident being investigated by the Aircraft Accident Investigation Bureau. The reports say incidents connected to aircraft accidents have surfaced at airport over the past several months.

Was this report accurate and useful?

Sources

Revision history

  1. Version 211 Aug 2026, 00:39current

    Added Khaskhabar's differing takeoff phase and ~12 pm time, two occupants reported safe, Ministry of Civil Aviation damage details, 6.39 UTC departure and two rejected take-offs, Bhaskar's account of the DGCA and police posture, and Sunetra Pawar's rejection of crash reports.

  2. Version 111 Aug 2026, 00:34

    First published.

  3. Version 111 Aug 2026, 00:29current

    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.