Skip to content

Atlas / NTSB / WPR12CA352

NTSB CAROL · Event

Event WPR12CA352

2012-08-12 Upland, California, United States Airport · CCB None 1 aircraft Status: Completed

Aircraft involved

Probable cause & findings

The pilot’s failure to maintain directional control of the airplane during the landing roll in gusting wind conditions.

Factual narrative

The pilot reported that after touching down the airplane tracked the centerline of the runway but eventually began to track to the right. After correcting left and back to the centerline the airplane tracked straight. Subsequently, a wind gust from the right caused the right wing to lift, which resulted in the airplane tracking to the left and eventually exiting the left side of the runway. With a fence now directly in his path and an impending collision imminent, the pilot initiated a go-around by applying full power and retracting the flaps from 40 degrees to 10 degrees. The pilot added that even though the airplane was now airborne, he was unable to climb over the fence. The airplane impacted the top of the fence with its main landing gear and tail wheel before coming to rest wedged between a rock pile and the fence. The pilot reported no mechanical anomalies with the airplane that would have precluded normal operation. The pilot reported that after touching down the airplane tracked the centerline of the runway but eventually began to veer to the right. After correcting back to the centerline, a wind gust from the right caused the right wing to lift, which resulted in the airplane tracking to the left and eventually exiting the left side of the runway. With a fence now directly in the path and a collision imminent, the pilot initiated a go-around by applying full power and retracting the flaps from 40 degrees to 10 degrees. The pilot added that even though the airplane was airborne, he was unable to climb over the fence. The airplane impacted the top of the fence with its main landing gear and tailwheel before coming to rest wedged between a rock pile and the fence; it sustained substantial damage to the wings, fuselage, and horizontal stabilizer. The pilot reported no mechanical anomalies with the airplane that would have precluded normal operation. 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 Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Directional control-Not attained/maintained - C
  • C Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - C
  • C Environmental issues-Conditions/weather/phenomena-Wind-Gusts-Response/compensation - C
  • Environmental issues-Physical environment-Object/animal/substance-Fence/fence post-Contributed to outcome

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