# Incident 20130516010199I: Cirrus Design Corp SR22, Sherman, TX, May 16, 2013

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: May 16, 2013, 10:30 local time
- Place: Sherman, TX
- Damage: No damage
- Phase of flight: Climb
- Operating rules: General operating rules (Part 91)
- Location: 32.9605° N, 96.8292° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=32.9605&lon=-96.8292&mi=10
- Aircraft: N715CD, registered now (https://openairdocs.org/aircraft/N715CD) (OpenAirDocs)
- Registry model: Cirrus Design SR22 (registry code 2130001, https://openairdocs.org/model/cirrus-design-sr22) (OpenAirDocs)
- Registry engine: Continental IO-550 series (registry code 17042, https://openairdocs.org/engine/continental-io-550-series) (OpenAirDocs)
- Reported make and model: CIRRUS DESIGN CORP SR22
- Reported engine: CONT MOTOR IO-550N-7
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 2,513 total, 1,700 in this make and model, 17 in the last 90 days
- NTSB investigation: [NTSB CEN13IA285](https://openairdocs.org/ntsb/CEN13IA285) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20130516010199I

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

DEPARTED ADS APPROX. 1045 FOR DESTINATION IDP ON AN IFR FLIGHT PLAN. WEATHER BRIEFING OBTAINED FROM 1-800-WX-BRIEF

DEPARTED AIRPORT AND PROCEEDED ON DIRECTED HEADING TOWARDS SHERMAN. CLEARED TO ?7000, AIRCRAFT ON AUTOPILOT AT APPROX. 169 KNOTS INDICATED AIRSPEED. AS THE AIRCRAFT NEARED ?7000 FT ALTITUDE IN MODERATE TURBULENCE THE HORIZONTAL SITUATIONAL INDICATOR (HSI) (SANDEL SN3308) DISPLAYED A ?FLUXGATE EXCITATION FAILURE? MESSAGE. THE PILOT STATED THE ?HSI WENT RED AND STARTED TUMBLING?. OTHER INSTRUMENTS IN THE AIRCRAFT SEEMED INOPERATIVE OR UNUSEABLE. THE PILOT UNCOUPLED THE AUTO-PILOT, REDUCED SPEED TO APPROX. 120 KNOTS, DECLARED AN EMERGENCY THEN WENT THROUGH THE CHUTE DEPLOYMENT PROCEDURE. THE CHUTE DID NOT PROPERLY DEPLOY. WHEN THE PILOT REALIZED THE CHUTE HAD NOT DEPLOYED PROPERLY HE NOSED THE AIRCRAFT OVER AND CLEARED THE CLOUD BASE AT APPROX. 1000 FEET AGL. HE WAS ABLE TO FLY THE AIRCRAFT BACK TO ADS. THE PILOT WAS ASKED TO CLARIFY WHY HE HAD MADE THE DECISION TO DEPLOY THE CAPS CHUTE TO WHICH HE REPLIED ?BECAUSE I WAS IN HARD IFR AND MY HSI MALFUNCTIONED?.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB CEN13IA285](https://openairdocs.org/ntsb/CEN13IA285), May 16, 2013: Cirrus SR22 (N715CD), Dallas, TX, incident, no damage. 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…

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.