FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN17FA084 · Cirrus Design Corp SR22

25 Jan 2017 · San Antonio, TX, United States

Cirrus Design Corp SR22 · Accident: aerodynamic stall/spin on approach

From San Antonio International Airport (SAT) to Stinson Municipal Airport (SSF)

Report a problem

Event

NTSB case
CEN17FA084
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
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 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
N401SC
Operator
Unknown
Onboard fatalities
Unknown
Route
From San Antonio International Airport (SAT), San Antonio, TXTo Stinson Municipal Airport (SSF), San Antonio, TX
Aircraft age
About 13 years (built 2004)
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
Aerodynamic stall/spin
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot was maneuvering in the airport traffic pattern at the time of the accident. The pilot entered a continuous right turn from downwind toward the final approach course when he abruptly lost control. A witness stated that the airplane wings were "totally vertical" before it nosed over and descended toward the ground. A second witness also reported that the airplane wings were nearly vertical before it descended below the tree line. He added that the engine sounded "fine."

An NTSB performance study revealed that after the airplane entered the airport traffic pattern, it began a continuous right turn from downwind toward the final approach course suggesting that the pilot did not fly a traditional rectangular traffic pattern, but instead flew a circling base to final pattern. The airplane approached the extended runway centerline in a 48° right bank, at 103 kts and about 220 ft agl. Lateral accelerations began to increase shortly before the accident and varied between 0.37g and 0.62g for the final portion of the flight. The lateral accelerations were consistent with sideslip angles of 15° to 20° during the final turn. The calculated angle-of-attack (AOA) of the wing subsequently exceeded the critical AOA and the airplane entered a descent which ultimately reached 1,800 fpm. Although the pilot's control inputs were not directly recorded, the large lateral accelerations are consistent with left rudder input and an uncoordinated flight condition for the airplane.

The accident site was located in a wooded area about 1/2 mile southeast from the landing runway threshold. Airframe and engine examinations did not reveal evidence of any anomalies consistent with a preimpact failure or malfunction.

The Pilot's Operating Handbook noted that extreme care must be taken to avoid uncoordinated or accelerated control inputs when close to the stall, especially when close to the ground. If, at the stall, the flight controls are misapplied and accelerated inputs are made to the elevator, rudder, and/or ailerons, an abrupt wing drop may be felt and a spiral or spin may be entered.

The FAA Airplane Flying Handbook (FAA-H-8083-3B) noted that coordinated flight is important to maintaining control of the airplane. Situations can develop when a pilot is flying in uncoordinated flight and depending on the flight control deflections, may support pro-spin flight control inputs. This is especially hazardous when operating at low altitudes, such as in the airport traffic pattern. A cross-control stall occurs when the critical AOA is exceeded with aileron pressure applied in one direction and rudder pressure in the opposite direction, causing uncoordinated flight. The aerodynamic effects of an uncoordinated, cross-control stall can occur with very little warning and can be deadly if it occurs close to the ground. The nose may pitch down, the bank angle may suddenly change, and the airplane may continue to roll to an inverted position, which is usually the beginning of a spin.

Probable cause

The pilot's uncoordinated flight control inputs and subsequent inadvertent cross-control aerodynamic stall in the airport traffic pattern that resulted in a loss of control and uncontrolled descent with insufficient altitude for recovery.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN17FA084
Event ID
20170125X83045
Case number
CEN17FA084
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: ab7ead2aa819643b06aa2ed3ed5d807f7ee5f1ebaa6db1e876c040b297389b2e; retrieved 2026-09-15T05:58:11.630Z.