CEN17LA030 · Cirrus Design Corp SR22
Cirrus Design Corp SR22 · Accident: loss of engine power (total) en route
From Albuquerque International Sunport (ABQ) to Stevens Field (PSO)
Event
- NTSB case
- CEN17LA030
- 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
- N234PJ
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Albuquerque International Sunport (ABQ), Albuquerque, NMTo Stevens Field (PSO), Pagosa Springs, CO
- Aircraft age
- About 11 years (built 2005)
- 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 · cruise
- 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 (total)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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 systems
- Aircraft › Fluids/miscellaneous hardware
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The private pilot was conducting a cross-country personal flight. He reported that, during cruise flight, the engine starting "missing" and that, within 2 minutes, lost all power. His attempts to restore engine power were not successful. He was unable to locate a suitable forced landing site within the airplane's glide range, so he chose to activate the ballistic parachute system. The aft fuselage separated from the airframe during the accident sequence. The airplane came to rest in an area of low brush and small trees.
Postaccident engine examination revealed that the fuel port cap was not installed on the throttle body metering unit. The cap was subsequently found in the cylinder baffling immediately below the metering unit. Both the fitting and the cap appeared to be undamaged. The cap was subsequently reinstalled, and an engine test run was conducted with no anomalies noted.
Data downloaded from the airplane's onboard avionics indicated that the engine speed and fuel flow were stable for the initial portion of the flight. However, about 45 minutes into the flight, the engine speed and fuel flow decayed abruptly, and the airplane entered a gradual descent. The engine speed did not recover during the rest of the flight. Before the loss of engine power, the fuel flow initially decreased from about 18.0 gallons per hour (gph) to 9.9 gph, before increasing to about 30.0 gph after the loss of power.
Examination of the fuel system revealed that the fuel flow transducer was installed between the fuel pump/mixture control and the throttle body metering unit, which was upstream in the fuel flow relative to the fuel port fitting. The loss of the fuel port cap would have allowed unrestricted fuel flow into the engine compartment. The transducer would have continued to measure fuel flow passing through the unit even though that fuel was ultimately not reaching the engine because it was installed upstream to the fuel port fitting. Further, the increased fuel flow measured after the loss of engine speed was consistent with an availability of fuel, a functioning fuel pump, and the mixture control being at or near the full-rich position.
Maintenance records revealed that, about 3 weeks before the accident, the engine's fuel nozzles were replaced, followed by an operational flight check and a ground run, to verify that the fuel system setting was in accordance with the Engine Maintenance and Overhaul Manual. The manual specified that the fuel port cap needed to be removed to connect external fuel pressure gauges and then reinstalled once testing and necessary fuel system adjustments were completed. The airplane had been operated 9.2 hours since the fuel nozzles were installed.
Based on the available information, it is likely that maintenance personnel did not fully torque the fuel port cap before the airplane was returned to service, which allowed the cap to loosen due to engine vibration during normal operation and then back off. At that point, the fuel supply to the engine would have been interrupted, and the engine would have lost all power due to fuel starvation. Restoring fuel flow to the engine in-flight in this situation would not have been possible.
Probable cause
Maintenance personnel’s failure to fully torque the fuel port cap, which allowed the cap to back off in flight and interrupted fuel flow to the engine, which resulted in a total loss of engine power.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN17LA030
- Event ID
- 20161031X53717
- Case number
- CEN17LA030
- 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: a0a71090472018aa0f5eca2da8fdd577a063cd5121988c30bfcc3966b6791a62; retrieved 2026-09-16T04:47:54.570Z.