Probable cause
The pilot’s failure to execute a go-around following an approach that was high and fast, which resulted in a runway overrun.
NTSB analysis
While on final approach to land, the pilot noticed a tree that was located near the end of the runway. To avoid the tree, he “stayed high” until he cleared the approach end of the runway and then attempted to “drop quickly” to the field. The airplane touched down on the left main landing gear roughly 2,000 feet beyond the threshold of the 2,900-foot-long runway, and the pilot applied the brakes. The pilot was unable to stop the airplane before it overran the runway. The right main landing gear struck an airport sign, and the airplane came to rest in brambles 100 feet beyond the departure end of the runway. Postaccident examination of the airplane revealed that the airplane’s firewall was substantially damaged. During the examination, no evidence of any preexisting mechanical anomalies that would have precluded normal operation was discovered. During a postaccident interview, the pilot stated that, after the accident, he discovered that the tree he had attempted to avoid was actually located to the right of the runway.
Text from the NTSB. Open the NTSB docket for ERA12CA464 for the full record.
Event
- Date
- Jul 16, 2012
- Type
- Accident
- Place
- Brevard, North Carolina
- Nearest airport
- Transylvania County Airport (3NR3)
- Highest injury
- None
- Weather
- Visual (VMC)
- Light
- Day
Piper PA32-301FT
- N-number
- N813TC
- Category
- Airplane
- Damage
- Substantial
- Operating rule
- Part 91 (general aviation)
- Purpose of flight
- Personal
From the NTSB aviation accident database: N-registered aircraft, events since 2008, data through Oct 28, 2026. The file is published monthly, so the latest weeks are incomplete and recent records can change. The official source is the NTSB aviation investigation search. CheckAero is independent and not affiliated with the NTSB.