# Incident 20011020031479I: Piper PA28RT201T, Charlottesville, VA, October 20, 2001

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: October 20, 2001, 15:05 local time
- Place: Charlottesville, VA
- Airport: Charlottesville-Albemarle
- Damage: Minor damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 38.1396° N, 78.4523° W: Placed by OpenAirDocs at CHARLOTTESVILLE-ALBEMARLE (CHO), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=38.1396&lon=-78.4523&mi=10
- Aircraft: N101NA, a cancelled registration (https://openairdocs.org/deregistered/N101NA-2012-05-07) (OpenAirDocs)
- Registry model: Piper PA-28RT-201T (registry code 7102817, https://openairdocs.org/model/piper-pa-28rt-201t) (OpenAirDocs)
- Registry engine: Continental TSIO-360 series (registry code 17019, https://openairdocs.org/engine/continental-tsio-360-series) (OpenAirDocs)
- Reported make and model: PIPER PA28RT201T
- Reported engine: CONT TSIO360FB
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 592 total, 459 in this make and model, 8 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20011020031479I

## Narrative

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

(-23) ON OCTOBER 20, 2001, MR. KROHN, AS PIC OF N101NA, BEGAN A NORMAL APPROACH FOR LANDING ON RUNWAY 21 AT CHARLOTTESVILLE-ALBERMARLE AIRPORT (CHO). WHILE IN THE FLARE, MR. KROHN NOTICED THAT HIS ALTITUDE DID NOT "FEEL" RIGHT AND HE INITIATED A GO-AROUND. AS THE POWER WAS APPLIED, THE PROPELLER STRUCK THE RUNWAY. MR. KROHN CONTINUED TO GO AROUND AND COMPLETED A NORMAL LANDING WITHOUT FURTHER INCIDENT.

## Other reports on N101NA (1)

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

- [Incident 19831124072939I](https://openairdocs.org/incident/19831124072939I), Nov 24, 1983: Piper PA28R201T (N101NA), Richmond, VA, Minor damage. Gear up forced landing on the runway after power loss. Bad fuel control unit. Vibration broke exhaust turbine clamp

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.