NTSB CAROL · Event
Event ERA12CA111
Aircraft involved
Probable cause & findings
The pilot did not attain the proper touchdown point during landing, which resulted in a runway overrun.
Factual narrative
According to the pilot, he was on the final approach leg of the traffic pattern at 80 mph and landed on the 2,590-foot, turf runway. During the rollout, the pilot applied the brakes, but the airplane continued off the end of the runway, impacted a fence, and came to rest in a nose low position. During the accident sequence, the airplane incurred substantial damage to the wing spars. A subsequent examination of the wreckage revealed no preaccident mechanical malfunctions or failures that would have precluded normal operation of the airplane. According to the Ercoupe Instruction Manual, the landing approach airspeed should be "between 60 and 70 mph." According to the pilot, he was on the final approach leg of the traffic pattern at 80 mph. During the landing roll on the 2,590-foot, turf runway, the pilot applied the brakes, but the airplane continued off the end of the runway, impacted a fence, and came to rest in a nose-low position, sustaining substantial damage to the wing spars. Examination of the wreckage, which included an operational check of the wheel braking system, revealed no preaccident mechanical malfunctions or failures that would have precluded normal operation of the airplane. According to the Ercoupe Instruction Manual, the recommended landing approach airspeed was "between 60 and 70 mph." The instruction manual also indicated that landing the airplane at a higher airspeed and applying the brakes "will require decidedly less overall distance than it would if the airplane were held off the ground until minimum speed had been reached." A published landing distance table for the airplane indicated that, with an approach speed of 75 mph, the landing distance over a 50-foot obstruction on a paved runway would be about 1,800 feet. 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-Incorrect action performance-Pilot - C
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Descent/approach/glide path-Not attained/maintained - C
Verbatim from NTSB's published report. Source file
NTSB_2011_ERA12CA111.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.