GAA15CA292

NTSB accident investigation · Cubcrafters CC11-160 · Lake City, CO · September 29, 2015

Accident · No injuriesData collectionFinal report
Date
September 29, 2015, 16:00 local (22:00 UTC)
Place
Lake City, CO
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Takeoff
Aircraft
N4HWCubcrafters CC11-160
Defining event
Takeoff: Loss of control in flight
Weather
Visual (VMC) · Day
Status
Completed · report December 3, 2015
Report
Approved by Office Director
NTSB office
General Aviation Accidents
Parties
Federal Aviation Admnistration
FAA report
20150929016939A
Case key
92098

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

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.

Findings · 5

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Use of equip/info: aircraft controlPersonnel issues › Task performance · PilotCubcrafters CC11-160: 13 casesAll aircraft: 9,295 casesProbable cause
Performance/control parameters: airspeedAircraft › Aircraft oper/perf/capability · Not attained/maintainedCubcrafters CC11-160: 2 casesAll aircraft: 1,681 casesProbable cause
Performance/control parameters: climb rateAircraft › Aircraft oper/perf/capability · Not attained/maintainedCubcrafters CC11-160: 1 caseAll aircraft: 265 casesProbable cause
Performance/control parameters: yaw controlAircraft › Aircraft oper/perf/capability · Not attained/maintainedCubcrafters CC11-160: 1 caseAll aircraft: 149 casesProbable cause
Wind: crosswindEnvironmental issues › Conditions/weather/phenomena · Effect on operationCubcrafters CC11-160: 4 casesAll aircraft: 1,008 cases

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

Analysis

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.

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.

Aircraft

Registration
N4HW
Reported as
Cubcrafters CC11-160
Category
Airplane
Serial number
CC11-00353
Built
2015
Airframe hours
50
Engine
Titan OX-340CC-B3J3, 180 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Operator
N4hw, LLC
Registered owner
N4hw, LLC
Airworthiness certificate
Special, Experimental light sport (Special)
Last inspection
Condition · August 21, 2014
Departed
CD32 · Lake City, CO
Destination
TEX · Telluride, CO
Flight plan
VFR
Airport
CD32 · Castle Lakes, runway 04, 3,200 × 50 ft, gravel
Equipment
Angle of attack indicator, Auto-pilot, Electronic flight bag or handheld device, Electronic multifunction display, Electronic primary flight display, Onboard weather, Stall warning system, ADS-B

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
48
Injuries
None
Certificate
Sport Pilot
Airplane ratings
Single-engine land
Last flight review
August 9, 2015
Seat
Front
Restraint
4-point
Flight hours
321 total · 194 in this make and model · 243 as pilot in command · 16 in the last 90 days · 13 in the last 30 days · 6 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
Calm
Temperature
68 °F, dew point 34 °F
Altimeter
30.37 inHg
Observed at
KTEX, 26 nm away

Docket · 3

The files NTSB released with the investigation on November 23, 2015, on NTSB’s docket system: statements, records, photos and specialists’ reports. 2.0 MB in all.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.