# Accident 20000516043569A: Cessna 172N, Tappahannock, VA, May 16, 2000

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: May 16, 2000, 12:18 local time
- Place: Tappahannock, VA
- Airport: Tappahannock Municipal Airport
- Damage: Substantial damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 37.9190° N, 76.8591° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=37.9190&lon=-76.8591&mi=10
- Aircraft: N1655E, a cancelled registration (https://openairdocs.org/deregistered/N1655E-2005-02-04) (OpenAirDocs)
- Registry model: Cessna 172N (registry code 2072434, https://openairdocs.org/model/cessna-172n) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172N
- Reported engine: LYC O320H2AD
- Fatal injuries: 0
- Pilot certificates: Student
- Pilot flight hours: 60 total, 31 in this make and model, 25 in the last 90 days
- NTSB investigation: [NTSB IAD00LA043](https://openairdocs.org/ntsb/IAD00LA043) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20000516043569A

## Narrative

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

(-23) THE PILOT STATED TO TROOPER CAPTAIN THAT HE BLACKED OUT ON THE FINAL APPROACH. WHEN HE CAME TO, THE AIRCRAFT WAS IN A RIGHT TURN. HE APPLIED POWER TO GO AROUND. THE AIRCRAFT MADE A HARD RIGHT TURN FROM RUNWAY 20, WENT OVER A CHAIN LINK FENCE THROUGH THE POWER LINES SPINNING AROUND 180 DEGREES AND COMING TO REST ON TOP OF A MOBILE HOME. DAMAGE TO THE AIRCRAFT WAS SUBSTANTIAL, AND THE PILOT RECEIVED MINOR INJURIES. AFTER REMOVING THE AIRCRAFT FROM THE MOBILE HOME AND CHECKING THE DAMAGE, INSPECTOR MIKE COOK AND I RAN THE ENGINE AND FOUND IT TO BE IN SERVICEABLE CONDITION WITH NO MALFUNCTIONS.

## 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 IAD00LA043](https://openairdocs.org/ntsb/IAD00LA043), May 16, 2000: Cessna 172N (N1655E), Tappahannock, VA, substantial damage. Probable cause: the pilots's inability to maintain aircraft control after a loss of consciosness.

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.