CIRRUS DESIGN CORP SR22 near Anderson, SC — 2012-04-27
- Date
- 2012-04-27
- Location
- Anderson, SC, USA
- Airport
- KAND
- Aircraft
- CIRRUS DESIGN CORP SR22
- Registration
- N154CK
- Category
- Airplane
- Highest injury
- Fatal
- Fatalities
- 1
- Phase of flight
- Takeoff roll
Probable cause
The pilot's failure to maintain control of the airplane during the aborted landing, which resulted in an aerodynamic stall and impact with terrain.
NTSB narrative
The pilot receiving instruction performed several takeoffs and landings with a flight instructor aboard. The flight instructor then disembarked and told the pilot to perform three additional solo takeoffs and landings (to a full stop), which the instructor observed from the ground. According to the flight instructor, the pilot's first flight around the airport traffic pattern appeared normal and terminated in a full stop landing and taxi back to the runway for the next takeoff. The instructor stated that the airplane appeared to touch down normally during the second landing; however, shortly thereafter the engine power increased and the airplane began to ascend. The airplane then climbed at a steep angle, entered an aerodynamic stall, and impacted terrain to the left of the runway. Review of data recorded by an onboard recoverable data module showed that as the airplane approached the runway during the landing, the stall warning activated and 1 second later the pilot increased engine power. As the engine power increased, the airplane began an unarrested turn to the left and the pilot retracted the airplane's flaps from the fully extended to the fully retracted position, which was contrary to the airframe manufacturer's published procedure for a balked landing. The data showed that after it reached an altitude of about 75 feet above ground level, the airplane entered an aerodynamic stall, and then rolled left while pitching down. The data recording ended before the airplane impacted terrain. Examination of the wreckage revealed no evidence of preimpact mechanical malfunctions or failures that would have precluded normal operation. The installed whole airframe parachute system likely deployed during the postimpact fire; however, given the low altitude at which the aerodynamic stall occurred, it is unlikely that preimpact deployment of the system would have positively affected the outcome of the accident. Review of the pilot's flight logs showed that he had accumulated more than 330 total hours of flight experience, including more than 220 hours in the accident airplane; however, he had not previously flown the accident airplane solo before the accident flight. Review of autopsy and toxicology test results showed no evidence of any preexisting condition that would have been expected to result in the pilot's incapacitation.
Analysis
- Primary failure mode
- Loss of control
- First missed decision gate
- Pilot could have aborted the takeoff after the initial climb began to stall.
NTSB coding
Evidence available
- Photos
- 14 docket documents
Docket documents14
- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1form
- Release of Aircraft Wreckage, NTSB Form 6120.15form
- Interview Summary, Flight Instructor (Courtesy of FAA)interview
- Memorandum for Record - Telephone Interview, Flight Instructorinterview
- Statement of Party Representatives to NTSB Investigationinterview
- Witness Statementinterview
- Pilot Operating Handbook Excerptsother
- RDM Tabular Dataother
- Photo 1 - Overview of Wreckage from Runway Elevationphotos
- Photo 2 - Initial Impact Point (Foreground) and Main Wreckage (Background)photos
- Photo 3 - Main Wreckage from Aft Rightphotos
- Photo 4 - Main Wreckage from Leftphotos
- Recoverable Data Module Factual Reportreport
- Toxicological Reportreport
Related mishaps
- Moose SR 2500
2026-05-27 · Sonoma, CA
- CESSNA 172
2025-12-07 · Pensacola, FL
- TORRES RUBEN AVENTURA II
2025-11-15 · Culebrita Beach, PR
- PIPER PA-32R-301
2025-09-18 · Oxford, MS
- PIPER PA-18-150
2024-09-15 · Fairbanks, AK
- CESSNA 207A
2024-06-03 · Bethel, AK