Cubcrafters CC11-160 accident near Lake City, Colorado, September 29, 2015
On September 29, 2015 at about 10:00 pm local time, a 2015 Cubcrafters CC11-160, registered N4HW, was substantially damaged in an accident during takeoff near Lake City, Colorado (Castle Lakes airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
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.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- September 29, 2015 · about 10:00 pm local time
- Place
- Lake City, Colorado · Castle Lakes · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Cubcrafters CC11-160, built 2015
- Registration
- N4HW · no longer on the register · serial CC11-00353
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Aerodynamic stall/spin during takeoff
- Loss of control in flight during takeoff defining event
- Collision with terrain or object (not controlled flight into terrain) during takeoff
The NTSB's findings
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Not attained/maintained
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Climb rate › Not attained/maintained
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Yaw control › Not attained/maintained
- Environmental issues › Conditions/weather/phenomena › Wind › Crosswind › Effect on operation
Pilot
- Certificate: sport pilot
- Ratings: single-engine land
- Flight time: 321 hours in all; 194 in this make and model; 16 in the last 90 days; 13 in the last 30 days; 243 as pilot in command
- Last flight review: August 9, 2015
- Medical certificate: None
- Seat: frt
- Injury: no injuries
Passenger
- Seat: rear
- Injury: no injuries
The aircraft
- Airframe total time: 50 hours
- Last inspection: condition inspection, August 21, 2014
- Maximum gross weight: 1,320 lb
- Seats: 2
- Landing gear: fixed
- Engine: Titan OX-340CC-B3J3 (piston); 50 hours total
- Operator: N4Hw, LLC
The flight
- Departed from: CD32 Lake City CO at 10:00 pm
- Destination: TEX Telluride CO
- Flight plan: VFR
- Runway 04, 3,200 ft by 50 ft
Weather at the time
- Light: daylight
- Sky: scat at 12,000 ft
- Temperature: 68°F (20°C), dew point 34°F (1°C)
- Altimeter: 30.37 inHg
- Observation at 9:55 pm from KTEX, 26 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
