Skip to content

Atlas / NTSB / ERA13CA369

NTSB CAROL · Event

Event ERA13CA369

2013-08-11 Verona, New York, United States Airport · NONE None 1 aircraft Status: Completed

Aircraft involved

Probable cause & findings

The pilot’s delay in applying power after a bounced landing, resulting in collision with terrain during a go-around.

Factual narrative

The pilot stated after takeoff while en route to the destination airport he elected to fly to a private airstrip (Bates Field) located in rolling farmland. He lined up onto base leg for landing to the northwest on the upslope grass runway, and turned onto final approach. With 40 degrees of flaps extended he identified the intended touchdown point and flared but then climbed to attain the intended touchdown point. He landed, “but too hard and bounced up…” then touched down on the runway but drifted off the runway into 6 to 8 inch high grass. He added power to abort the landing but impacted a knoll at the top of a crest of a hill, then continued climbing. While safely airborne he assessed the condition of the airplane noting the pilot and co-pilot doors were ajar, but did not find any other damage. He flew over the private airstrip and did not observe any damage then elected to proceed to his destination airport, where he landed uneventfully. While taxiing after landing he noticed the left landing gear was out of position. He further stated there was no preimpact mechanical failure or malfunction that caused the hard landing. Inspection of the airplane by a Federal Aviation Administration inspector revealed damage and distortion to structural tubing in the cockpit, and wrinkles in the fabric adjacent to the left main landing gear. The pilot stated after takeoff while en route to the destination airport he elected to fly to a private airstrip (Bates Field) located in rolling farmland. He lined up onto base leg for landing to the northwest on the upslope grass runway, and turned onto final approach. With 40 degrees of flaps extended, he identified the intended touchdown point, flared, and then climbed to attain the intended touchdown point. He landed, “but too hard and bounced up…,” touched down on the runway, and drifted off the runway into 6 to 8 inch high grass. He added power to abort the landing but impacted a knoll at the top of a crest on a hill, then continued climbing. While safely airborne he assessed the condition of the airplane noting the pilot and co-pilot doors were ajar, but did not find any other damage. He flew over the private airstrip and did not observe any damage then elected to proceed to his destination airport, where he landed uneventfully. While taxiing after landing he noticed the left landing gear was out of position. He further stated there was no preimpact mechanical failure or malfunction that caused the hard landing. Inspection of the airplane by a Federal Aviation Administration inspector revealed damage and distortion to structural tubing in the cockpit, and wrinkles in the fabric adjacent to the left main landing gear. 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-Delayed action-Pilot - C
  • C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Climb rate-Not attained/maintained - C
  • Environmental issues-Physical environment-Terrain-Mountainous/hilly terrain-Contributed to outcome

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