CEN16FA095 · Cirrus Design Corp SR22T
Cirrus Design Corp SR22T · Accident: loss of control in flight on approach
From Indianapolis Executive Airport (TYQ) to Greene County/Lewis A. Jackson Regional Airport (I19)
Event
- NTSB case
- CEN16FA095
- 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 SR22T
- 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
- N1703
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Indianapolis Executive Airport (TYQ), Indianapolis, INTo Greene County/Lewis A. Jackson Regional Airport (I19), Xenia, OH
- Aircraft age
- About 2 years (built 2014)
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airline transport pilot was repositioning the airplane to its home base after maintenance was completed at a repair station. The pilot filed an instrument flight rules (IFR) flight plan with a cruise altitude of 9,000 ft mean sea level (msl). The en route portion of the flight to the destination was uneventful. Before descending to approach altitude, the pilot contacted approach control and reported that he had received weather information for the destination airport. The pilot then requested and was given clearance to fly the area navigation (RNAV) approach to runway 7. Approach control cleared the pilot to descend to 3,000 ft msl and issued pilot reports for icing. The pilot flew the RNAV approach to runway 7, tracking inbound to the airport on the published approach course. About 5.8 miles from the airport, the pilot cancelled his IFR clearance and continued inbound under visual flight rules. His recorded altitude at the time of IFR cancellation was 2,700 ft msl. Reported weather at the airport at the time of the accident included a ceiling of 1,700 ft above ground level (2,649 ft msl) and wind from 240 degrees at 9 kts, gusting to 14 kts, and variable from 240 to 330 degrees. One witness at the airport saw the airplane enter a downwind leg to land into the wind on runway 25. As the airplane began its turn from the base leg to final, several other witnesses saw it nose down and descend to impact in wooded terrain about 300 ft short of the runway threshold.
A postaccident weather study showed high icing potential within the cloud layers above the surface and a likelihood of moderate or greater icing along the airplane's route of flight until the airplane descended below the cloud ceiling. Because the surface temperature was below freezing, any structural ice that built up on the airplane while it descended through the clouds would not have melted after the airplane descended below the cloud ceiling.
An examination of the airplane revealed no preimpact mechanical malfunctions or anomalies that would have precluded normal operations. Data recovered from the airplane's Remote Data Module showed that the airplane's anti-ice tank switch was turned on about 7 minutes 30 seconds before the accident and remained on for 1 minute 50 seconds. The switch was then turned off and remained off for the remainder of the flight. The airplane's flaps were extended to the "HALF" position about 2 minutes 50 seconds before the accident. Just before the data ended, the airplane's pitch and bank increased, and the stall warning activated. In the last 3 seconds of data, the airplane's bank angle was 48 to 50 degrees, and the indicated airspeed was between 87 and 90 kts. The Pilot's Operating Handbook for the airplane showed that at 60 degrees of bank with half flaps, the airplane's stall speed was 95 kts. It is possible that, during the approach, ice accumulated on the airplane, which may have increased the airplane's stall speed. However, regardless of whether or not structural ice was present, during the turn to final, the pilot allowed the airspeed to decrease below the airplane's published stall speed. As a result, the wing's critical angle-of-attack was exceeded, and the airplane entered an aerodynamic stall and departed controlled flight.
Probable cause
The pilot's failure to maintain adequate airspeed while turning from the base leg to final, which resulted in the wing's critical angle-of-attack being exceeded and a subsequent aerodynamic stall.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN16FA095
- Event ID
- 20160201X51653
- Case number
- CEN16FA095
- 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: e3f4952eb277af81a954d3930ffa5c22da9dc3c0182621183f9003223fd80adf; retrieved 2026-09-14T21:39:58.655Z.