# Incident 19860502024999I: Cessna 172P, Charleston, WV, May 2, 1986

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: May 2, 1986, 10:00 local time
- Place: Charleston, WV
- Airport: Yeager
- Damage: Minor damage
- Phase of flight: Forced/Precautionary Landing
- Operating rules: General operating rules (Part 91)
- Location: 38.3731° N, 81.5932° W: Placed by OpenAirDocs at Yeager Airport (CRW), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=38.3731&lon=-81.5932&mi=10
- Aircraft: N62960, registered now (https://openairdocs.org/aircraft/N62960) (OpenAirDocs)
- Registry model: Cessna 172P (registry code 2072436, https://openairdocs.org/model/cessna-172p) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172P
- Reported engine: LYC O320D2J
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 4,600 total, 2,600 in this make and model, 250 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19860502024999I

## Narrative

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

VIBRATION AND LOSS OF POWER ON TAKEOFF. LANDED ON REMAINING RUNWAY. EXHAUST VALVE STUCK.

## Other reports on N62960 (2)

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

- [Accident 20070516010919A](https://openairdocs.org/incident/20070516010919A), May 16, 2007: Cessna 172P (N62960), Harrah, OK, Substantial damage. (-23) On the first landing attempt, the pilot landed left of the center of the runway. Almost immediately on landing, the aircraft's left wing was in contact…
- [Accident 19910115000559A](https://openairdocs.org/incident/19910115000559A), Jan 15, 1991: Cessna 172P (N62960), Charleston, WV, Substantial damage. Lost power local flight. Nosed over landing in soft field. Accessory gear dowel pin sheared. Service b not complied

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.