CEN16FA211 · Cirrus Design Corp SR20
Safe Aviation Cirrus Design Corp SR20 · Accident: loss of control in flight on approach
From University of Oklahoma Westheimer Airport (OUN) to William P. Hobby Airport (HOU)
Event
- NTSB case
- CEN16FA211
- 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
- 3 · all aircraft and ground
- Ground fatalities
- Unknown
- 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 SR20
- Aircraft type
- Cirrus SR20
- 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
- N4252G
- Operator
- Safe Aviation
- Onboard fatalities
- Unknown
- Route
- From University of Oklahoma Westheimer Airport (OUN), Norman, OKTo William P. Hobby Airport (HOU), Houston, TX
- Aircraft age
- About 4 years (built 2012)
- 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 go-around
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN16FA211
- Event ID
- 20160609X50758
- Case number
- CEN16FA211
- 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: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 02dc62210675db3c16b309220c4b80556e888f2304d74dcf21deb241d94269ab; retrieved 2026-09-14T21:49:21.488Z.