Skip to content

Atlas / NTSB / ERA16CA308

NTSB CAROL · Event

Event ERA16CA308

2016-08-29 Simsbury, Connecticut, United States Airport · 4B9 None 1 aircraft Status: Completed

Aircraft involved

Probable cause & findings

The student pilot’s failure to attain the proper touchdown point, which resulted in a runway overrun.

Factual narrative

The student pilot reported that he was preparing for his private pilot check ride and after about 90 minutes of flying, he approached the airport and entered the traffic pattern for runway 21, a 2,205 ft-long runway. While established on "short final," he elected to perform a go-around because he was not "comfortable" with the approach. On the second landing attempt, the airplane floated past the intended touchdown point, before landing on the runway, and the student pilot was unable to stop the airplane before it went off the departure end. Subsequently, the airplane struck a perimeter fence and an embankment, which resulted in the nose landing gear collapsing and substantial damage to the fuselage and left wing. The student pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation. The winds reported at an airport 4 miles east of the accident location were from 320 degrees true at 7 knots. The student pilot reported that he was preparing for his private pilot check ride, and after about 90 minutes of flying, he approached the airport and entered the traffic pattern for runway 21, a 2,205-ft-long runway. The student pilot added that, while established on "short final," he chose to perform a go-around because he was not "comfortable" with the approach. On the second landing attempt, the airplane floated past the intended touchdown point before landing on the runway, and the student pilot was unable to stop the airplane before it went off the departure end. Subsequently, the airplane struck a perimeter fence and an embankment, which resulted in the nose landing gear collapsing and substantial damage to the fuselage and left wing. The student pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation. The winds reported at an airport 4 miles east of the accident location were from 320° at 7 knots. 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-Info processing/decision-Decision making/judgment-Student/instructed pilot - C
  • C Personnel issues-Task performance-Use of equip/info-Aircraft control-Student/instructed pilot - C
  • C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Descent/approach/glide path-Not attained/maintained - C
  • C Aircraft-Aircraft oper/perf/capability-Aircraft capability-Landing distance-Capability exceeded - C
  • Environmental issues-Physical environment-Object/animal/substance-Fence/fence post-Contributed to outcome

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

Related research

What the literature says.

Academic papers and agency reports matching this event's aircraft type or causal vocabulary (go-around). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.

Browse the full corpus — academia portal ↗