Tecnam P2006T Crash Near Kanpur Under Investigation; DGCA Had Flagged Safety Concerns
A Tecnam P2006T operated by Garg Aviation crashed near Kanpur on August 27; the cause has not been determined.
2 reports on this incident · first at Aug 30, 2026, 3:47 a.m. ET
Earlier reports
Aug 30, 2026, 3:47 a.m. ETFirst report
Tecnam P2006T crash in Kanpur under investigation; AAIB to probe
A Tecnam P2006T aircraft crashed near Kanpur, India, on August 27, 2026, around 11:30 am, according to the Economic Times. The aircraft, registered VT-NBV, was operated by Garg Aviation. The cause of the accident has not been determined, and the investigation is ongoing.
The Ministry of Civil Aviation said the Aircraft Accident Investigation Bureau (AAIB) would conduct a detailed investigation, while a three-member Directorate General of Civil Aviation (DGCA) team would provide regulatory oversight and coordination, the Economic Times reported.
Registry records list the registered owner as Garg Aviation; the owner of record is not necessarily the operator of the flight.
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
- 430 ft
- Nearest aerodrome
- 3.0 miles WNW of Kanpur Civil Airport (Old) (VIKA)
Sources
- DGCA flagged Tecnam safety concerns weeks before fatal Kanpur crasheconomictimes.indiatimes.com
- Kanpur plane crash: DGCA flagged Tecnam aircraft safety concerns weeks before fatal crashtimesofindia.indiatimes.com
Revision history
- Version 230 Aug 2026, 08:51current
Added Times of India as a source; noted DGCA's prior safety concerns; clarified investigation status.
- Version 130 Aug 2026, 07:50
First published.
- Version 130 Aug 2026, 07:47current
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.