# Accident 20030304014009A: Piper PA32R300, Rogersville, TN, March 4, 2003

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: March 4, 2003, 17:30 local time
- Place: Rogersville, TN
- Airport: Hawkins County Airport
- Damage: Substantial damage
- Phase of flight: In Traffic Pattern-Circling
- Operating rules: General operating rules (Part 91)
- Location: 36.4575° N, 82.8850° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=36.4575&lon=-82.8850&mi=10
- Aircraft: N4135Q, registered now (https://openairdocs.org/aircraft/N4135Q) (OpenAirDocs)
- Registry model: Piper PA-32R-300 (registry code 7103213, https://openairdocs.org/model/piper-pa-32r-300) (OpenAirDocs)
- Registry engine: Lycoming TI0-540 series (registry code 41533, https://openairdocs.org/engine/lycoming-ti0-540-series) (OpenAirDocs)
- Reported make and model: PIPER PA32R300
- Pilot flight hours: 392 total, 34 in this make and model, 25 in the last 90 days
- NTSB investigation: [NTSB ATL03LA053](https://openairdocs.org/ntsb/ATL03LA053) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20030304014009A

## Narrative

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

(-23) INTERVIEW WITH THE PILOT IMMEDIATELY FOLLOWING THE ACCIDENT REVEALS THE FOLLOWING: PILOT WAS PRACTICING 180 DEGREE COURSE REVERSALS FROM PATTERN ALTITUDE BEGINNING AT A POINT ABEAM THE RUNWAY NUMBERS. THIS WAS IN PREPARATION FOR A COMMERCIAL PILOT CHECK RIDE TO BE ADMINISTERED THE FOLLOWING DAY. HE ADVISED THAT ALL WENT WELL AND THAT DURING HIS TURN TO FINAL HE NOTICED HE WAS NOT PROPERLY ALIGNED WITH THE RUNWAY CENTERLINE. UPON APPLYING CONTROL INPUTS TO GET BACK TOWARDS THE MIDDLE OF THE RUNWAY THE AIRSPEED BLEAD OFF AND THE AIRCRAFT STALLED AT AN ALTITUDE OF APPROXIMATELY 30 FEET. THE AIRCRAFT SLID OFF OF THE SIDE OF THE RUNWAY AFTER STRIKING THE RUNWAY SURFACE HARD WHICH COLLAPSED THE LANDING GEAR AND SUBSTANTIALLY DAMAGED THE WINGS OF THE AIRCRAFT. THE AIRCRAFT IS OWNED BY A FLYING CLUB OF WHICH MR. OERSTREICH IS A MEMBER. ^PRIVACY DATA OMITTED^

## 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 ATL03LA053](https://openairdocs.org/ntsb/ATL03LA053), Mar 4, 2003: Piper PA-32R-300 (N4135Q), Rogersville, TN, substantial damage. Probable cause: The pilot's improper landing flare which resulted in a hard landing.

## Other reports on N4135Q (1)

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

- [Incident 20000715035919I](https://openairdocs.org/incident/20000715035919I), Jul 15, 2000: Piper PA32R300 (N4135Q), Johnstown, PA, Minor damage. (-23) On July 15, 2000, a Piper PA32R, registered as N4135Q made a hard landing at the Johnstown airport(jst) on runway 33 ILS approach. Aircraft came to rest…

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.