Event ERA12CA464

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

Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or 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