# Accident 20200701005319A: Cessna 172M, Chesapeake, VA, July 1, 2020

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: July 1, 2020, 09:00 local time
- Place: Chesapeake, VA
- Airport: Chesapeake Regional
- Damage: Substantial damage
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 36.6650° N, 76.3211° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=36.6650&lon=-76.3211&mi=10
- Aircraft: N9391H, a cancelled registration (https://openairdocs.org/deregistered/N9391H-2023-01-14) (OpenAirDocs)
- Registry model: Cessna 172M (registry code 2072418, https://openairdocs.org/model/cessna-172m) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172M
- Reported engine: LYCOMING 0-320 SERIES
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Student
- Pilot flight hours: 31 total, 31 in this make and model, 5 in the last 90 days
- NTSB investigation: [NTSB ERA20CA235](https://openairdocs.org/ntsb/ERA20CA235) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20200701005319A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

STUDENT PILOT ON SOLO FLIGHT CAME IN FOR LANDING AND UPON TOUCHDOWN, BOUNCED, DID NOT APPLY CORRECTION AND CONTINUED BOUNCING GETTING PROGRESSIVELY WORSE UNTIL ABOUT THE THIRD BOUNCE THE CONTROLS LOCKED UP AND THE AIRCRAFT EXITED THE RUNWAY TO THE LEFT.  WINDS WITHIN 30 DEGREES OF RUNWAY CENTERLINE AND 4-7 KNOTS.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB ERA20CA235](https://openairdocs.org/ntsb/ERA20CA235), Jul 1, 2020: Cessna 172 (N9391H), Chesapeake, VA, substantial damage. Probable cause: The student pilot's improper landing flare and failure to recover from the ensuing bounced landing, which resulted in a runway excursion.

## Other reports on N9391H (4)

Matched to the same aircraft by N-number and date.

- [Incident 20130314004029I](https://openairdocs.org/incident/20130314004029I), Mar 14, 2013: Cessna 172M (N9391H), Chesapeake, VA, Minor damage. The a/c was taxiing to depart runway 28 via the east approach end of runway 02, the landing light became inoperative. When the landing light became…
- [Accident 19850921051819A](https://openairdocs.org/incident/19850921051819A), Sep 21, 1985: Cessna 172M (N9391H), Fremont, OH, Substantial damage. Aircraft would not climb after an early liftoff. Mushed into a fence and a pasture off the runway end.
- [Incident 19791119044749I](https://openairdocs.org/incident/19791119044749I), Nov 19, 1979: Cessna 172M (N9391H), Atlanta, GA, Minor damage. Blinded by taxi lights of large jet pilot taxied off edge of pavement. Prop struck ground.
- [Accident 19780124003009A](https://openairdocs.org/incident/19780124003009A), Jan 24, 1978: Cessna 172M (N9391H), Substantial damage. No narrative

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.