Event ERA12CA020

Factual narrative

The pilot stated that he proceeded to the destination airport and entered the traffic pattern for runway 36, which is a 2,420 foot-long asphalt runway that was dry. While on final approach with the flaps set to 30 degrees (full down) he reported that he was a little too fast (85 to 90 miles-per-hour) instead of 70 miles-per-hour. He stated that he did not perceive to float over the runway but after touchdown, he realized there was insufficient runway remaining to stop. He added power to go-around and raised the flaps incrementally; the engine responded. He continued ahead and while airborne, the airplane collided with trees. He confirmed there was nothing mechanically wrong with the airplane, and further stated that the accident could have been avoided by being on-speed. The pilot stated that, while on final approach to the 2,420-foot-long, dry, asphalt runway with the flaps set to 30 degrees (full down), the airplane was a little too fast at 85 to 90 mph, instead of 70 mph. He stated that he did not perceive that the airplane floated over the runway but that, after touchdown, he realized there was insufficient runway remaining to stop. He added power to go around, raised the flaps incrementally, and continued ahead, but the airplane collided with trees. The airplane sustained substantial damage to the empennage. The pilot stated that there was nothing mechanically wrong with the airplane and that the accident could have been avoided by being on speed. 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 Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Airspeed-Incorrect use/operation - C
• C Personnel issues-Action/decision-Action-Delayed action-Pilot - C