WPR20WA002 · Cessna 172 R
Cessna 172 R · Accident: loss of control in flight on approach
Narrative check · The NTSB narrative appears to contradict this record's flight rules. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- WPR20WA002
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Unknown · led by another country; figures from NTSB notifications
- API-reported fatalities
- 1 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Not recorded
Cessna 172 R
- Aircraft type
- Cessna 172
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- VT-HRP
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation Narrative disagrees
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Approach · IFR final approach
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Loss of control in flight
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
No findings designated as a cause are recorded in the NTSB data yet.
Not plotted · Location withheld: coordinates are missing, conflicting, invalid, or have no accepted acquisition method. No substitute location has been invented.
NTSB narrative
On October 5, 2019, at 0628 coordinated universal time, a Cessna 172R airplane, VT-HRP, collided with a fence during approach at the Shirpur Airport, Maharashtra, India. The student pilot was fatally injured and the airplane was substantially damaged. The airplane was operated under the pertinent civil regulations of the Government of India.The investigation is under the jurisdiction of the Government of India. This report is for information purposes only and contains only information released by the Government of India. Further information pertaining to this accident may be obtained from:
The Aircraft Accident Investigation Bureau
Safdarjung Airport, New Delhi, India - 110003 Tel: 011-24658051 Fax: (91) 11 2469-3963 email: aaib.moca@nic.in
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record WPR20WA002
- Event ID
- 20191007X00010
- Case number
- WPR20WA002
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- No bulk values were replaced by the NTSB case API.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 232b0ad624d8c7a51f0c9ab851ff423c2ed264c8e5747f530097c337dc36787a; retrieved 2026-09-15T07:06:33.747Z.