Loss of control Accident Cirrus SR22 N1116C,
ASN logo
ASN Wikibase Occurrence # 179064
 
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Thursday 27 August 2015
Time:19:05
Type:Silhouette image of generic SR22 model; specific model in this crash may look slightly different    
Cirrus SR22
Owner/operator:Hard Times Llc
Registration: N1116C
MSN: 0471
Year of manufacture:2003
Total airframe hrs:2289 hours
Engine model:Continental IO-550-N
Fatalities:Fatalities: 1 / Occupants: 1
Aircraft damage: Substantial
Category:Accident
Location:Shelby County Airport (KEET), Alabaster, AL -   United States of America
Phase: Approach
Nature:Private
Departure airport:Alabaster, AL (EET)
Destination airport:Alabaster, AL (EET)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
The private pilot was performing traffic pattern work at the airport before the accident, had completed four touch-and-go landings, and was flying the traffic pattern again to attempt a fifth landing. According to witnesses and the recorded flight data, the airplane was on the final leg of the traffic pattern when it pitched down in a near vertical attitude and impacted trees and the ground about 1,700 ft from the approach end of the runway. A postimpact fire ensued, which partially consumed the wreckage.

Although one witness reported that it sounded like the airplane was having "throttle issues" and another witness reported that the engine "cut out" three times before the airplane descended "straight down," examination of the wreckage revealed that there were no preimpact anomalies with the airframe or engine that would have precluded normal operation. The airplane's last recorded airspeed of 67 knots before it pitched down was well above its 50% flap extension stall speed of about 55 knots. The last two valid data points showed a pitch angle of about -40°. The reason for the abrupt, near vertical pitch down could not be determined.

According to a witness, the parachute deployed after the airplane impacted the ground, indicating that the pilot likely did not attempt to activate it during the accident sequence.

A review of the pilot's medical records indicated that he had a history of depression with a recent recurrence. The pilot stopped taking his antidepressant medication primarily so he could obtain a medical certificate and begin flying again. Subsequently, his physician reported that his depression had improved and that he was no longer using any antidepressants, and he was issued a medical certificate about 5 weeks before the accident.

The pilot's wife reported that he continued to be very stressed and anxious and that he had returned to his physician about 1 week before the accident. Toxicology testing indicated that the pilot was using two antidepressants, citalopram and trazodone. Exactly what symptoms or cognitive impairments the pilot might have been experiencing from his depression could not be determined. However, it was likely that he had been having sufficient symptoms for his physician to start him on two new antidepressants. Antidepressants typically take several weeks to begin relieving the symptoms of depression. Although citalopram has not been shown to degrade performance in psychological testing experiments using healthy volunteers, at least 40% of outpatient users reported drowsiness or fatigue when using trazodone. It is likely that the pilot was cognitively impaired by a combination of significant recurrent depression and sedation from trazodone. This impairment may have contributed to the pilot's inability to control the airplane.
Probable Cause: An in-flight loss of airplane control for reasons that could not be determined because postaccident examination of the airframe and engine revealed no preimpact mechanical malfunctions or failures that would have precluded normal operation.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: ERA15FA330
Status: Investigation completed
Duration:
Download report: Final report

Sources:

NTSB
https://flightaware.com/live/flight/N1116C

FAA register: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=1116C

History of this aircraft

Other occurrences involving this aircraft
24 January 2011 N1116C 0 Jasper, Alabama sub
Runway excursion

Location

Revision history:

Date/timeContributorUpdates
28-Aug-2015 05:51 Geno Added
28-Aug-2015 06:06 Geno Updated [Time, Registration, Cn, Operator, Departure airport, Source]
21-Dec-2016 19:30 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
19-Aug-2017 14:59 ASN Update Bot Updated [Time, Operator, Nature, Departure airport, Destination airport, Source, Narrative]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org