The U.S. aircraft register, updated daily
Accidents · NTSB CEN17FA084 · Final report

Cirrus Design CORP SR22 accident near San Antonio, Texas, January 25, 2017

On January 25, 2017 at about 9:39 pm local time, a 2004 Cirrus Design CORP SR22, registered N401SC, was destroyed in an accident during approach (VFR pattern final) near San Antonio, Texas (Stinson Municipal airport). It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
January 25, 2017 · about 9:39 pm local time
Place
San Antonio, Texas · Stinson Municipal · map
Type
Accident
Injuries
1 person was killed.
Weather
visual conditions (good weather)
Aircraft
Cirrus Design CORP SR22, built 2004
Registration
N401SC · no longer on the register · serial 0951
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Aerodynamic stall/spin during approach (VFR pattern final) defining event
  2. Loss of control in flight during approach (VFR pattern final)
  3. Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent

The NTSB's findings

  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Yaw control › Incorrect use/operation
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Angle of attack › Capability exceeded
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot

Pilot

  • Certificate: commercial pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 2,556 hours in all
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: left
  • Injury: fatal

The aircraft

  • Airframe total time: 1,124.6 hours
  • Last inspection: annual inspection, January 24, 2017; 1 hours since
  • Maximum gross weight: 3,400 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Cont Motor IO-550-N-27 (piston); 1,125 hours total

The flight

  • Departed from: SAT San Antonio TX at 9:32 pm
  • Destination: SSF San Antonio TX
  • Flight plan: none
  • Runway 32, 4,128 ft by 100 ft

Weather at the time

  • Light: daylight
  • Wind: from 010° at 12 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 70°F (21°C), dew point 21°F (-6°C)
  • Altimeter: 29.92 inHg
  • Observation at 9:53 pm from SSF, 1 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

20 documents, released by the NTSB on October 4, 2018. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.