FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN16LA223 · Cirrus Design Corp SR22

18 Jun 2016 · Colorado Springs, CO, United States

Cirrus Design Corp SR22 · Accident: loss of engine power (partial) en route

From City of Colorado Springs Municipal Airport (COS) to City of Colorado Springs Municipal Airport (COS)

Report a problem

Event

NTSB case
CEN16LA223
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
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
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
N678Z
Operator
Unknown
Onboard fatalities
Unknown
Route
From City of Colorado Springs Municipal Airport (COS), Colorado Springs, COTo City of Colorado Springs Municipal Airport (COS), Colorado Springs, CO
Aircraft age
About 14 years (built 2002)
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
En route
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 engine power (partial)
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

  • Not determined › Not determined

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

NTSB narrative

The commercial pilot was conducting a local flight when he noted a lower-than-normal oil pressure indication and engine roughness. The engine subsequently experienced a partial loss of power and the airplane could not maintain altitude. The pilot deployed the Cirrus Airframe Parachute System (CAPS) at an estimated 472 ft above ground level, and the airplane impacted rough terrain under canopy in a nose-low, upright attitude. A test run of the engine and review of recorded data did not reveal the reason for the partial loss of engine power.

Examination of the airframe parachute system revealed that, during deployment of the CAPS, the rocket separated from its lanyard in overstress. Fracture testing of the lanyard revealed that it did not exceed the minimum value in several tests, and the examined lanyard sections did not fully conform to specification; however, it is unlikely that these anomalies resulted in the overstress fracture.

Features observed on the CAPS retaining harness suggested that some resistance was encountered when pulling the incremental bridle from the sleeve during the deployment. The cover flap from the retaining harness had discoloration and heat damage consistent with abnormal exposure to the rocket exhaust, and pulled stitches were noted in the vicinity of the sleeve where the incremental bridle was stowed. It is likely that the incremental bridle was not released immediately from the sleeve, which kept the rocket closer to the retaining harness and placed abnormal loads on the lanyards. At some point, the incremental bridle was released from the sleeve and loaded to separate the stitches in the incremental bridle as designed.

During a nominal CAPS deployment, the airplane enters a nose-low attitude before leveling off, a stage of deployment referred to as "tail drop." For tail drop to occur, the deployment must be initiated to allow adequate time and/or altitude. During the accident, the parachute inflated fully; however, the abnormal CAPS deployment, as well as low deployment altitude resulted in the airplane touching down in a nose-low attitude before tail drop occurred.

Based on static pull tests in the lab, the orientation of the incremental bridle within the sleeve can significantly affect the force required to release the incremental bridle from its stowed position. A review of parachute packing procedures revealed that the orientation of the incremental bridle as it was inserted in its sleeve was not specified. In the absence of any specific procedure for orienting the incremental bridle in the sleeve, it would be possible for the incremental bridle to be inserted in either orientation. The investigation could not determine whether the incremental bridle had been inserted in an unfavorable orientation or if such an orientation would have resulted in the lanyard fracture. Based on review of the parachute deployment and subsequent testing, an exact cause for the abnormal CAPS deployment could not be determined.

Probable cause

A hard landing on rough terrain due to a faulty deployment of the airplane’s airframe parachute system following a partial loss of engine power for reasons that could not be determined, because postaccident examination revealed no malfunctions or anomalies that would have precluded normal operation. Contributing to the accident was the low altitude deployment of the parachute system.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN16LA223
Event ID
20160620X94648
Case number
CEN16LA223
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: 2391b1b016c34f5ed59e88a0f15d30e9107e00b3fbc326c4717120770d3fdbda; retrieved 2026-09-16T03:31:52.024Z.