# Accident 19950512011499A: Cessna 172F, Tappahannock, VA, May 12, 1995

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: May 12, 1995, 17:25 local time
- Place: Tappahannock, VA
- Airport: Tappahannock Municipal Airport
- Damage: Destroyed
- Phase of flight: Roll-Out (Fixed Wing)
- Operating rules: General operating rules (Part 91)
- Location: 37.9209° N, 76.8609° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=37.9209&lon=-76.8609&mi=10
- Aircraft: N5238F, a cancelled registration (https://openairdocs.org/deregistered/N5238F-2013-04-08) (OpenAirDocs)
- Registry model: Cessna 172F (registry code 2072414, https://openairdocs.org/model/cessna-172f) (OpenAirDocs)
- Registry engine: Continental 0-300 series (registry code 17022, https://openairdocs.org/engine/continental-0-300-series) (OpenAirDocs)
- Reported make and model: CESSNA 172F
- Reported engine: CONT O300D
- People aboard: 1
- Fatal injuries: 1
- Pilot flight hours: 62 total, 62 in this make and model
- NTSB investigation: [NTSB BFO95FA050](https://openairdocs.org/ntsb/BFO95FA050) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19950512011499A

## Narrative

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

SOLO CROSS COUNTRY. BECAME LOST. LANDED. CFI OK CONTINUE. LOST AGAIN. OVER SHOT RUNWAY LANDING. HIT FENCE AND POST.

## 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 BFO95FA050](https://openairdocs.org/ntsb/BFO95FA050), May 12, 1995: Cessna 172F (N5238F), Tappahanock, VA, destroyed, 1 fatal. Probable cause: The student pilot's misjudgment of distance/speed during the approach to land, and her failure to go around while there was still sufficient runway remaining. Factors related to the accident were:…

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.