Skip to content

Atlas / NTSB / GAA15CA292

NTSB CAROL · Event

Event GAA15CA292

2015-09-29 Lake City, Colorado, United States Airport · CD32 None 1 aircraft Status: Completed

Aircraft involved

Probable cause & findings

The pilot's failure during takeoff to attain sufficient airspeed for conditions, and to maintain yaw control and a positive rate of climb, resulting in a loss of directional control, an uncontrolled descent, and collision with trees and terrain.

Factual narrative

The pilot of the tailwheel-equipped airplane was departing from a mountain airport situated in a valley. The pilot reported that during takeoff, he rotated about 52-54 miles per hour, and about 20 feet above the ground, a strong crosswind from the left pushed the airplane to right of the runway centerline. The pilot attempted to overcome the effect of the wind with control inputs, but the airplane collided with trees on the right side of the runway. The airplane sustained substantial damage to the wings, fuselage, and empennage. An FAA inspector who went to the accident site reported that the pilot rotated approximately 400 feet and impacted trees about 621feet from where the takeoff roll was initiated. The FAA inspector estimated there was at least an additional 2,000 feet of useable runway remaining. The field elevation was 9,300 feet MSL and density altitude was calculated as 12,600 feet. The performance charts for this airplane stop at 8000 feet and required extrapolation for the airport elevation and weather conditions. Calculations by the FAA inspector estimated a minimum takeoff roll of 425 feet before rotation under ideal conditions for weather and mixture setting. A witness reported the pilot was "hot dogging" and was trying to show off when the pilot took off in a very short distance and climbed at a steep angle. The witness reported that the airplane aerodynamically stalled, collided with trees and came to rest in a ditch. The witness also reported that the winds were calm at the time of the takeoff and accident. The airplane came to rest on private property that abutted the airport, and the witness reported that the landowner dragged the airplane onto airport property with a tractor. The airplane wreckage was not photographed by the FAA inspector before it was moved. Eight other airplanes of similar make and model departed the field about the time of the accident without incident. The pilot reported no preimpact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation. The pilot of the tailwheel-equipped airplane was departing from a mountain airport situated in a valley. The pilot reported that during takeoff, he rotated about 52-54 miles per hour, and about 20 feet above the ground, a strong crosswind from the left pushed the airplane to right of the runway centerline. The pilot attempted to overcome the effect of the wind with control inputs, but the airplane collided with trees on the right side of the runway. The airplane sustained substantial damage to the wings, fuselage, and empennage. An FAA inspector who went to the accident site reported that the pilot rotated approximately 400 feet and impacted trees about 621 feet from where the takeoff roll was initiated. The FAA inspector estimated there was at least an additional 2,000 feet of useable runway remaining. The field elevation was 9,300 feet MSL and density altitude was calculated as 12,600 feet. The performance charts for this airplane stop at 8000 feet and required extrapolation for the airport elevation and weather conditions. Calculations by the FAA inspector estimated a minimum takeoff roll of 425 feet before rotation under ideal conditions for weather and mixture setting. A witness reported the pilot was "hot dogging" and was trying to show off when the pilot took off in a very short distance and climbed at a steep angle. The witness reported that the airplane aerodynamically stalled, collided with trees and came to rest in a ditch. The witness also reported that the wind was calm at the time of the takeoff and accident. The airplane came to rest on private property that abutted the airport, and the witness reported that the landowner dragged the airplane onto airport property with a tractor. The airplane wreckage was not photographed by the FAA inspector before it was moved. Eight other airplanes of similar make and model departed the field about the time of the accident without incident. The pilot reported no preimpact mechanical failures or malfunctions with the airframe or engine 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 Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - C
  • C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Airspeed-Not attained/maintained - C
  • C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Climb rate-Not attained/maintained - C
  • C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Yaw control-Not attained/maintained - C
  • Environmental issues-Conditions/weather/phenomena-Wind-Crosswind-Effect on operation

Verbatim from NTSB's published report. Source file NTSB_2015_GAA15CA292.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 (stall). 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 ↗