FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN13IA285 · Cirrus SR22

16 May 2013 · Dallas, TX, United States

Cirrus SR22 · Incident: system/component malfunction/failure (non-power) while maneuvering

From Addison Airport (ADS) to Independence Municipal Airport (IDP)

Report a problem

Event

NTSB case
CEN13IA285
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
Incident
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
0 · 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
Instrument Meteorological Cond

Cirrus 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
N715CD
Operator
Unknown
Onboard fatalities
Unknown
Route
From Addison Airport (ADS), Dallas, TXTo Independence Municipal Airport (IDP), Independence, KS
Aircraft age
About 12 years (built 2001)
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
Maneuvering
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
System/component malfunction/failure (non-power)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
None

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Aircraft › Aircraft systems

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

NTSB narrative

The pilot reported that he lost airplane control during cruise flight in instrument meteorological conditions (IMC) and turbulence. He subsequently activated the airplane's parachute system, but the parachute failed to deploy. The pilot regained control of the airplane after exiting IMC and landed the airplane without further incident.

Certification tests were performed from level flight at speeds ranging from 62 to 137 knots indicated airspeed, and one test included deployment of the parachute system after a one-turn spin. The testing showed that to minimize the chances of parachute entanglement and reduce aircraft oscillations under the parachute, the parachute system should be activated from a wings-level, upright attitude if possible.

Postincident examination of the parachute system did not reveal any system component failure. Postincident testing showed that off-axis deployment of the parachute could exceed the forces required for a successful deployment of the parachute. If the airplane has a large pitch or bank angle or angular rates (or a combination of these) as the parachute rocket leaves the airplane, the airplane will rotate and cause the rocket tether to pull at an angle other than that intended, and the parachute will fail to deploy. Radar data showed that the airplane was in a very dynamic flight pattern with extreme pitch and bank angles when the parachute system was activated. Thus, the parachute likely failed to deploy when activated due to the dynamic maneuvering of the airplane at the time of the activation, which exceeded the parachute system's certification requirements.

Probable cause

The failure of the airplane’s parachute to deploy when activated during a loss of control in cruise flight due to the dynamic maneuvering of the airplane at the time of the activation, which exceeded the parachute system’s certification requirements.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN13IA285
Event ID
20130520X84445
Case number
CEN13IA285
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, damage. 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: c919bfc20b12d65854f56ef0e715a221d134526870d673846c17fa52c7749a92; retrieved 2026-09-15T21:37:20.173Z.