NTSB CAROL · Event
Event ERA11CA040
Aircraft involved
Probable cause & findings
The pilot's failure to attain the proper touchdown point.
Factual narrative
According to the pilot, he departed on the personal flight for the purpose of having an annual inspection performed on his airplane at the destination airport. While approaching the airport, he observed the windsock indicating the wind was from the south, and he planned to land on runway 23. The pilot stated that he planned his approach to clear the fence at the end of the runway and still have enough room to stop on the 1,400-foot grass runway. He also stated that he knew that the terrain sloped upwards from the fence to the runway threshold, and that he "was aiming for the crest of the hill." As the airplane approached the runway, the pilot first added power to compensate for a "fast rate of decent," then reduced power when he felt he had the runway made. However, "the rise was greater than I thought, and the airspeed was lower than I thought." The airplane touched down about half way up the slope, the nose gear collapsed, and the airplane came to rest at the top of the slope. According to the Federal Aviation Administration inspector, the firewall was substantially damaged. The pilot reported that there were no mechanical malfunctions prior to the accident. According to the pilot, he departed on the personal flight for the purpose of having an annual inspection performed on his airplane at the destination airport. While approaching the airport, he observed the windsock indicating the wind was from the south, and chose the appropriate runway. The pilot planned his approach to clear the fence at the end of the runway and still have enough distance for the roll out on the grass runway. Knowing that the terrain sloped upward from the fence to the runway threshold, he aimed to touchdown on the crest of the hill. As the airplane approached the runway, the pilot added power to compensate for a fast rate of decent, then reduced power when he felt he had was aligned appropriately. The airplane touched down about half way up the slope and the nose gear collapsed; the airplane came to rest at the top of the slope. According to the Federal Aviation Administration inspector, the firewall was substantially damaged. The pilot reported that there were no mechanical malfunctions prior to the accident. 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-Descent/approach/glide path-Not attained/maintained - C
- C Personnel issues-Action/decision-Info processing/decision-Decision making/judgment-Pilot - C
Verbatim from NTSB's published report. Source file
NTSB_2010_ERA11CA040.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.