FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA15FA330 · Cirrus Design Corp SR22

27 Aug 2015 · Alabaster, AL, United States

Hard Times Cirrus Design Corp SR22 · Accident: loss of control in flight on approach

From Shelby County Airport (EET) to Shelby County Airport (EET)

Report a problem

Event

NTSB case
ERA15FA330
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
1 · all aircraft and ground
Ground fatalities
0
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

Cirrus Design Corp SR22

Aircraft type
Cirrus SR22
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
N1116C
Operator
Hard Times
Onboard fatalities
Unknown
Route
From Shelby County Airport (EET), Alabaster, ALTo Shelby County Airport (EET), Alabaster, AL
Aircraft age
About 12 years (built 2003)
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
Approach · VFR pattern final
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

  • Not determined › Not determined

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB 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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA15FA330
Event ID
20150827X13623
Case number
ERA15FA330
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2015-08-28.
  • API snapshot SHA-256: adf309bc880f717149118befde0790e76cf5cf921e5b4b7652da183fcf6ad248; retrieved 2026-09-14T21:29:27.784Z.