Skip to content

Atlas / NTSB / ERA11CA350

NTSB CAROL · Event

Event ERA11CA350

2011-06-16 Sterling, Massachusetts, United States Airport · 3B3 None 1 aircraft Status: Completed

Registry · N99136

FAA Aircraft Registry record.

Make / Model

EIRIAVION OY PIK 20B

Seats / Engines

1 seats · 1 engine

Last airworthiness date

19770617

ADS-B equipped

Yes — Mode-S ADD93A

Registrant of record

WAHL JOHN F

Source: FAA Aircraft Registry (releasable master file).

Aircraft involved

Probable cause & findings

The pilot's misjudgment of the amount of flaps required to attain the proper touchdown point. Contributing to the accident was the pilot's limited experience in the high performance glider.

Factual narrative

According to the pilot, this was his first flight in this flap only, high performance glider. The glider was towed to 5,000 feet, where the pilot practiced pattern work as well as extending and retracting the flaps, from zero degrees to 90 degrees, while maintaining an adequate airspeed for landing. The pilot entered a tight traffic pattern at the airport and extended the flaps to 30 degrees. On the final leg of the traffic pattern, the glider was in line with the runway, and the pilot intended to extend the flaps to 45 degrees, but was unsure if he did so. When the glider was halfway down the runway, the pilot knew he had excessive airspeed and was going to land further down the runway than intended. Near the end of the runway, he pushed the controls forward in order to gain ground control, but the glider continued over trees past the end of the runway. Since the glider did not have enough altitude to safely turn back to the runway, the pilot landed in trees resulting in substantial damage to the fuselage. The pilot reported there were no preexisting mechanical anomalies with the glider and that he had never flown this make and model glider. According to the pilot, this was his first flight in this flap only, high performance glider. The glider was towed to 5,000 feet, where the pilot practiced pattern work as well as extending and retracting the flaps, from zero degrees to 90 degrees, while maintaining an adequate airspeed for landing. The pilot entered a tight traffic pattern at the airport and extended the flaps to 30 degrees. On the final leg of the traffic pattern, the glider was in line with the runway, and the pilot intended to extend the flaps to 45 degrees, but was unsure if he did so. When the glider was halfway down the runway, the pilot knew he had excessive airspeed and was going to land further down the runway than intended. Near the end of the runway, the pilot thought he landed so he pushed the controls forward in order to gain ground control, but the glider continued over trees past the end of the runway. Since the glider did not have enough altitude to safely turn back to the runway, the pilot landed it in trees resulting in substantial damage to the fuselage. The pilot stated that he accumulated 107 hours of total flight time in a glider, of which, no hours were in the same make and model as the accident glider. The pilot reported there were no preexisting mechanical anomalies with the glider. 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
  • F Personnel issues-Experience/knowledge-Experience/qualifications-Total experience w/ equipment-Pilot - F
  • C Aircraft-Aircraft systems-Flight control system-TE flap control system-Incorrect use/operation - C
  • C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Landing flare-Not attained/maintained - C

Verbatim from NTSB's published report. Source file NTSB_2011_ERA11CA350.txt. Findings + structured fields enriched from FAA avall.mdb. Full investigation docket on data.ntsb.gov ↗.