Two killed in Tecnam P2006T crash near Kanpur; AAIB and DGCA to investigate
A training flight crashed about five nautical miles from Kanpur Civil Airport on August 27, killing both people on board; the cause has not been determined.
2 reports on this incident · first at Aug 27, 2026, 5:36 a.m. ET
Earlier reports
Aug 27, 2026, 5:36 a.m. ETFirst report
Two killed in Tecnam P2006T crash near Kanpur; AAIB to investigate
A Tecnam P2006T aircraft crashed on the afternoon of August 27, 2026, about five nautical miles from Kanpur Civil Airport near Ganga Barrage, according to the Times of India. The two people on board were killed, the outlet reported.
The aircraft was operated by Garg Aviation Ltd and had registration VT-NBV, the Times of India reported. The cause of the crash has not been determined, and the investigation is open.
The Aircraft Accident Investigation Bureau (AAIB) has been informed and will undertake a detailed investigation in accordance with applicable rules, the Times of India reported. A team of three officials from the Directorate General of Civil Aviation (DGCA) will visit the crash site for regulatory oversight and coordination.
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
- Kanpur aircraft crash: AAIB to probe training flight that killed trainee pilot, instructortimesofindia.indiatimes.com
- DGCA flagged safety issues with Tecnam aircraft before Kanpur crashthehindubusinessline.com
Revision history
- Version 230 Aug 2026, 07:25current
Added registration, operator, time conflict, and DGCA safety flag details; clarified investigation roles.
- Version 127 Aug 2026, 09:39
First published.
- Version 127 Aug 2026, 09:36current
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.