ERA12CA464
2012-07-16 · Brevard, North Carolina, United States · None · 1 aircraft · Status: Completed
Airport 3NR3
Aircraft involved
Probable cause & findings
The pilot’s failure to execute a go-around following an approach that was high and fast, which resulted in a runway overrun.
Factual narrative
***This report was modified on October 29, 2012. Please see the docket for this accident to view the original report.*** While on approach to a runway, the pilot of the airplane attempted to avoid 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 were 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. 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. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
FAA avdata. C = Cause, F = Factor.
- C Personnel issues-Action/decision-Action-Lack of action-Pilot - C
- — Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Descent/approach/glide path-Not attained/maintained
Verbatim from NTSB's published report. Source file
NTSB_2012_ERA12CA464.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Search this event elsewhere
External sources are reported, not agency: signal that something happened, not fact about what happened.
- TallyAero Live Wire Aviation press
- NTSB CAROL Agency ↗
- NTSB Docket Agency ↗
- Aviation Safety Network Aviation press ↗
- Kathryn's Report Aviation press ↗
- Aviation Herald Aviation press ↗
- AVweb Aviation press ↗
- Pilots of America Community ↗
- Reddit /r/flying Community ↗
- FlightAware Aviation press ↗
- AOPA accident database Aviation press ↗
- Google News News ↗
- DuckDuckGo News ↗
Related research
Matched on aircraft type or causal vocabulary (go-around). All research papers
- NASA NTRS 2025 · Conference Paper A Training Study to Improve Monitoring During A Go-Around
As part of an FAA program to improve go-around (GA) safety, we were asked to determine if we could improve the performance of the Pilot Monitoring (PM) during a GA maneuver.
- Flight Safety Foundation 2024 · FSF / AeroSafety World Go-Around Safety Forum Findings
Foundation Go-Around Safety Forum technical findings — examines why pilots fail to execute go-arounds when criteria are met (stabilized approach gate not met, energy state out of envelope, traffic con…
- Semantic Scholar 2022 · Article (Journal of Safety Research) Go-around accidents and general aviation safety.
INTRODUCTION Changes in General Aviation (GA) accident rates, specifically in the go-around phase, are examined by comparing the number of accidents, the proportion of fatal accidents, and the proport…
- Semantic Scholar 2021 · Article (Aerospace) Classification and Analysis of Go-Arounds in Commercial Aviation Using ADS-B Data
Go-arounds are a necessary aspect of commercial aviation and are conducted after a landing attempt has been aborted. It is necessary to conduct go-arounds in the safest possible manner, as go-arounds …
- NASA NTRS 2021 · Accepted Manuscript (Version with final changes) Go-Around Criteria Refinement for Transport Category Aircraft
Presently, airline pilots are trained to go around if, when lower than 500 ft above the ground, they are outside of a handful of parameters such as airspeed, position, and rate of descent.
- NASA NTRS 2019 · Conference Paper Validation of Proposed Go-Around Criteria Under Various Environmental Conditions
This paper evaluates the effects of environmental conditions on touchdown performance under varying approach states and validates proposed go-around criteria developed using data from a previously con…