WPR18LA018 · Cirrus Design Corp SR22
Cirrus Design Corp SR22 · Accident: powerplant system/component malfunction/failure en route
From Camarillo International Airport (CMA) to Safford Regional Airport (SAD)
Event
- NTSB case
- WPR18LA018
- 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
- N418CP
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Camarillo International Airport (CMA), Camarillo, CATo Safford Regional Airport (SAD), Safford, AZ
- Aircraft age
- About 9 years (built 2008)
- 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
- Powerplant system/component malfunction/failure
- 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 › Fluids/miscellaneous hardware
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The flight instructor reported that he and the pilot receiving instruction were conducting an instructional, cross-country flight. About 1.3 hours into the flight, the oil pressure started to decrease, and the pilots decided to divert to a nearby airport. The oil pressure continued to decrease, and the engine subsequently lost all power. The airplane was unable to reach the runway, so the pilots chose to activate the parachute system. Upon ground impact, the parachute dragged the airplane for about 20 ft. The pilots then egressed the airplane, and the parachute then dragged it another 200 ft. The nose landing gear and left main landing gear collapsed, and the fuselage and engine firewall sustained substantial damage. During postaccident examination of the airframe, an oil streak was observed covering the airplane’s belly. During engine examination, a b-nut fitting that attached the oil supply line to the turbocharger inlet check valve was found loose. A significant amount of fresh oil was observed in the area around the b-nut fitting and on the engine’s right side near the turbocharger next to the b-nut. The cowling bottom’s right side exhibited significantly more oil staining than the bottom’s left side. The b-nut and its threads were not damaged. A small hole was found on the top of the engine crankcase, consistent with an internal engine failure. A review of the airplane’s maintenance records revealed that an annual inspection was completed earlier on the day of the accident flight and that actions were taken to comply with a turbocharger manufacturer's safety bulletin that recommended that the turbocharger oil supply inlet screen be inspected and cleaned on a regular basis. To inspect and clean the inlet screen, the oil line to the turbocharger bearing housing inlet and cap has to be removed, followed by the removal of the valve assembly from the turbocharger oil inlet fitting. The valve assembly must then be reassembled, during which the check valve should be torqued to 85-inch lbs. The valve assembly should then be reinstalled on the turbo oil adapter and torqued to 85-inch lbs. It is likely that, during the maintenance, maintenance personnel failed to properly torque the b-nut fitting that attached to the turbocharger inlet check valve oil line supply line to the turbocharger inlet check valve, which resulted in oil starvation and a subsequent engine failure.
Probable cause
Maintenance personnel's failure to properly torque an oil supply line fitting, which resulted in oil starvation, a subsequent engine failure, and an off-airport landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR18LA018
- Event ID
- 20171003X01002
- Case number
- WPR18LA018
- 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, coordinates. 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: 981b82dadfeac03c3bb2c0d9ccd47a49e40aaf33eedf76a0eb297b90cbb57845; retrieved 2026-09-16T05:54:30.017Z.