Skip to content

Atlas / NTSB / ERA16CA233

NTSB CAROL · Event

Event ERA16CA233

2016-06-28 Farmington, Pennsylvania, United States Airport · PA88 Minor 1 aircraft Status: Completed

Aircraft involved

Probable cause & findings

The pilot's failure to obtain the proper touchdown point and failure to perform a go-around once a safe landing on the runway could not be accomplished.

Factual narrative

The pilot reported that during his first attempt to land on the 3,950-foot-long asphalt runway, the airplane touched down too long and he performed a go-around. During the second attempt, the airplane touched down on the first one-third of the runway, when a gust of wind forced the airplane back into the air and it subsequently touched down further down the runway than during the first attempt. The pilot thought a go-around would be too dangerous at that point and applied brakes, but the airplane traveled off the end of the runway and struck and asphalt berm. The pilot further stated that the airplane landed with a headwind of 15 knots, gusting to 25 knots. A witness, who worked at the airport, stated that the airplane was still airborne as it flew over the runway numbers at the departure end of the runway. Examination of the accident site by a Federal Aviation Administration inspector did not reveal any skid marks on the runway; however, the inspector observed skid marks in the grass beyond the runway. The inspector did not observe any preimpact mechanical malfunctions with the airplane, nor did the pilot report any. The inspector added that during the impact, the airplane sustained damage to the firewall and lower fuselage. The pilot reported that during his first attempt to land on the 3,950-foot-long asphalt runway, the airplane touched down too long and he performed a go-around. During the second attempt, the airplane touched down on the first one-third of the runway, when a gust of wind forced the airplane back into the air and it subsequently touched down further down the runway than during the first attempt. The pilot thought a go-around would be too dangerous at that point and applied brakes, but the airplane traveled off the end of the runway and struck and asphalt berm. The pilot further stated that the airplane landed with a headwind of 15 knots, gusting to 25 knots. A witness, who worked at the airport, stated that the airplane was still airborne as it flew over the runway numbers at the departure end of the runway. Examination of the accident site by a Federal Aviation Administration inspector did not reveal any skid marks on the runway; however, the inspector observed skid marks in the grass beyond the runway. The inspector did not observe any preimpact mechanical malfunctions with the airplane, nor did the pilot report any. The inspector added that during the impact, the airplane sustained damage to the firewall and lower fuselage. 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
  • C Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - C

Verbatim from NTSB's published report. Source file NTSB_2016_ERA16CA233.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 ↗