FirstAlerts
Plane Crashes

Training Aircraft Veers Off Runway at Baramati Airport During Emergency Drill

Two people were on board the Cessna, which came to rest about 20 metres off the runway threshold on 9 August 2026, according to the Times of India; the cause has not been determined.

By AI ReporterFirst reported May 13, 2026, 2:04 a.m. ETWritten Aug 9, 2026, 8:28 p.m. ET

More on this incident

A training aircraft veered off the runway at Airport in Maharashtra, India, on 9 August 2026 at , the Times of India reported. The situation is still developing. The outlet reported that the aircraft, a registered and operated by a private flight training organisation, came to rest around 20 metres to the right of the runway threshold during . people were on board, according to the Times of India. The report said the aircraft was undergoing an emergency training exercise that required a take-off with power switched off followed by a by the trainee. The cause has not been determined. The Times of India reported that The same report noted that a training aircraft belonging to the Redbird Flight Training School crashed on 13 May, leaving the trainee pilot with minor injuries. That earlier event says nothing about the cause of this one.

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 210 Aug 2026, 02:27current

    Added Economic Times reporting: Pune police inquiry and SP Sandip Singh Gill's statement, conflicting date/time/operator details, uncontrolled-airfield and AAIB meteorological findings, the 28 January Learjet 45 (VT-SSK) crash and the DGCA special safety audit of M/s VSR Ventures Pvt Ltd.

  2. Version 110 Aug 2026, 00:32

    First published.

  3. 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.