Loss of control Accident Cirrus SR20 N4252G,
ASN logo
ASN Wikibase Occurrence # 188000
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 9 June 2016
Type:Silhouette image of generic SR20 model; specific model in this crash may look slightly different    
Cirrus SR20
Owner/operator:Safe Aviation LLC
Registration: N4252G
MSN: 2217
Year of manufacture:2012
Total airframe hrs:429 hours
Fatalities:Fatalities: 3 / Occupants: 3
Aircraft damage: Substantial
Location:N of Hobby Airport, Houston, TX -   United States of America
Phase: Initial climb
Departure airport:Norman, OK (OUN)
Destination airport:Houston, TX (HOU)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
The pilot was attempting to land the airplane at a busy airport with high volume airline traffic. While attempting to sequence the airplane between airplanes, the air traffic controller issued numerous instructions to the pilot, which included changing runways multiple times. The pilot was instructed to go around twice by the local controller; the first time because an air carrier airplane was overtaking the accident airplane and the second time because the airplane was too high to make a safe landing. During the airplane's third approach, a new local controller came on duty. On this approach, the pilot again had difficulty descending fast enough to make a safe landing, and she elected to perform another go-around. The new local controller then issued the pilot a lengthy clearance as the pilot was performing the go-around procedure. Data retrieved from the airplane revealed that, during the go-around, the pilot did not follow the recommended go-around procedure; specifically, the pilot did not attain a speed between 81 to 83 knots indicated airspeed (KIAS) before raising the flaps. Rather, the airplane's airspeed was 58 KIAS when the pilot raised the airplane's flaps while in a left turn, which resulted in exceedance of the critical angle of attack and a subsequent aerodynamic stall and spin into terrain.

Postaccident examination of the airframe and engine did not reveal any anomalies that would have precluded normal operation. The air traffic control instructions given to the pilot during the three approaches were complex and potentially distracting. The initial local controller elected to keep the airplane in the traffic pattern rather than transferring the airplane to an approach controller for resequencing when airline traffic interrupted the pilot's first landing attempt and when the pilot displayed difficulty landing the airplane on her second landing attempt. The complex instructions from the second local controller during the pilot's go-around following her third landing attempt, were unnecessary at that time and likely distracted the pilot from monitoring critical flight parameters.

The pilot was attempting to comply with ATC instructions throughout the flight and the pilot's actions are understandable as the instructions were largely consistent with the pilot's goal to land at the busy airport. However, compliance with ATC instructions greatly increased the pilot's workload as it led to an extended period of close-in maneuvering at a Class B airport due to the larger and faster airplanes converging on the airport. During this extended period of maneuvering the pilot did not assert the responsibilities that accompany being a pilot-in-command and did not offload the workload by either requesting to be re-sequenced, telling the controller to standby, or stating "unable." This allowed for an increased likelihood of operational distractions associated with air traffic communications and affected the pilot's ability to focus on aircraft control.

Probable Cause: The pilot's improper go-around procedure that did not ensure that the airplane was at a safe airspeed before raising the flaps, which resulted in exceedance of the critical angle of attack and resulted in an accelerated aerodynamic stall and spin into terrain. Contributing to the accident were the initial local controller's decision to keep the pilot in the traffic pattern, the second local controller's issuance of an unnecessarily complex clearance during a critical phase of flight. Also contributing was the pilot's lack of assertiveness.


FAA register: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=4252G


Accident investigation:
Investigating agency: NTSB
Report number: CEN16FA211
Status: Investigation completed
Duration: 1 year and 6 months
Download report: Final report


. .


Revision history:

09-Jun-2016 18:54 dmorrelljrtx Added
09-Jun-2016 18:54 harro Updated [Aircraft type, Cn, Operator, Embed code]
09-Jun-2016 19:21 Geno Updated [Operator, Total fatalities, Total occupants, Other fatalities, Location, Source, Embed code, Narrative]
09-Jun-2016 20:20 Iceman 29 Updated [Embed code]
09-Jun-2016 20:38 bovine Updated [Time, Phase, Departure airport, Destination airport, Source]
09-Jun-2016 20:51 Iceman 29 Updated [Embed code]
10-Jun-2016 08:21 dfix1 Updated [Departure airport, Destination airport, Narrative]
10-Jun-2016 10:06 Iceman 29 Updated [Photo, ]
12-Jun-2016 10:17 Iceman 29 Updated [Embed code]
16-Jun-2016 14:43 Aerossurance Updated [Time, Location, Phase, Nature, Departure airport, Destination airport, Source, Narrative]
16-Jun-2016 14:43 Aerossurance Updated [Departure airport, Destination airport]
22-Aug-2016 18:24 flytefan Updated [Embed code]
21-Dec-2016 19:30 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
16-Dec-2017 14:54 ASN Update Bot Updated [Operator, Nature, Departure airport, Destination airport, Source, Embed code, Narrative]
16-Dec-2017 17:07 harro Updated [Operator, Source, Embed code, Narrative]
16-Dec-2017 17:08 harro Updated [Phase]
24-Sep-2018 19:08 harro Updated [Embed code]
19-Apr-2020 07:54 Anon. Updated [Embed code]

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

©2023 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314