# Accident 19960811022079A: Cessna 172P, Summersville, WV, August 11, 1996

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: August 11, 1996, 11:50 local time
- Place: Summersville, WV
- Airport: Summersville Airport
- Damage: Destroyed
- Phase of flight: To Init Climb(1st Pwr Reduct)
- Operating rules: General operating rules (Part 91)
- Location: 38.2808° N, 80.8408° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=38.2808&lon=-80.8408&mi=10
- Aircraft: N65632, a cancelled registration (https://openairdocs.org/deregistered/N65632-1997-03-06) (OpenAirDocs)
- Registry model: Cessna 172P (registry code 2072436, https://openairdocs.org/model/cessna-172p) (OpenAirDocs)
- Reported make and model: CESSNA 172P
- Reported engine: LYC O320D2J
- People aboard: 3
- Fatal injuries: 3
- Pilot flight hours: 64 total, 6 in this make and model
- NTSB investigation: [NTSB IAD96FA132](https://openairdocs.org/ntsb/IAD96FA132) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19960811022079A

## Narrative

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

TOO HIGH AND FAST NUMEROUS TIMES MAKING STEEP FINAL TURNS. LAST GO AROUND MADE EARLY STEEP TURN. STALLED SPUN IN.

## 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 IAD96FA132](https://openairdocs.org/ntsb/IAD96FA132), Aug 11, 1996: Cessna 172P (N65632), Summersville, WV, destroyed, 3 fatal. Probable cause: The pilot's improper flare, his delay in aborting a landing, and his failure to maintain adequate airspeed, which resulted in a bounced landing and a stall during climb out in an attempt to avoid…

## Other reports on N65632 (3)

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

- [Incident 19850317013869I](https://openairdocs.org/incident/19850317013869I), Mar 17, 1985: Cessna 172P (N65632), Lansing, WV, Minor damage. Landed downwind in gusty wind and ran off end of runway. Struck a wood post.
- [Incident 19850126005829I](https://openairdocs.org/incident/19850126005829I), Jan 26, 1985: Cessna 172P (N65632), Chesapeake, OH, Minor damage. Lost directional control on snow packed runway. Brakes may have been frozen at time of touchdown.
- [Incident 19840729041119I](https://openairdocs.org/incident/19840729041119I), Jul 29, 1984: Cessna 172P (N65632), Willamson, WV, Minor damage. Landed long and fast on second landing. Nose wheel broke due to heavy brake pressure.

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.