GAA15CA292 · Cubcrafters CC11-160
N4HW Cubcrafters CC11-160 · Accident: loss of control in flight during takeoff
From Castle Lakes Airport (CD32) to Telluride Regional Airport (TEX)
Event
- NTSB case
- GAA15CA292
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cubcrafters CC11-160
- Aircraft type
- Cubcrafters CC11
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N4HW
- Operator
- N4HW
- Onboard fatalities
- Unknown
- Route
- From Castle Lakes Airport (CD32), Lake City, COTo Telluride Regional Airport (TEX), Telluride, CO
- Aircraft age
- Built the same year (2015)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Takeoff
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Loss of control in flight
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB 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 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.
Probable cause
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA15CA292
- Event ID
- 20151002X22156
- Case number
- GAA15CA292
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: dfccd89c3d3e36be355ca7c074f1a5b15961caba92ed1abb230604ac27a4a454; retrieved 2026-09-16T02:51:05.139Z.