WPR19FA126 · Cessna 182 P
Air Carriage Cessna 182 P · Accident: loss of engine power (total) en route
From Chico Regional Airport (CIC) to Chico Regional Airport (CIC)
Event
- NTSB case
- WPR19FA126
- 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
- 1 · 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
Cessna 182 P
- Aircraft type
- Cessna 182
- 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
- N7302S
- Operator
- Air Carriage
- Onboard fatalities
- Unknown
- Route
- From Chico Regional Airport (CIC), Chico, CATo Chico Regional Airport (CIC), Chico, CA
- Aircraft age
- About 43 years (built 1976)
- 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 (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
- Wire
- 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 power plant
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot and two passengers departed on a sightseeing flight over mountainous terrain. About 30 minutes into the flight, the engine lost partial power and smoke began to enter the cockpit. The pilot turned the airplane toward a grassy meadow for a forced landing. While approaching the field, the pilot suddenly saw power lines immediately ahead and attempted to maneuver the airplane below them. The airplane contacted the wires and came to rest inverted. Postaccident examination revealed several holes in the engine crankcase. The oil filter adapter was found loose and the fiber gasket was protruding beyond the castings. Removal of the oil filter adapter revealed that the fiber gasket was split. The failure of the gasket allowed oil to exit the engine, resulting in oil starvation and the subsequent catastrophic failure. During postaccident testing, the gasket failure seen in the accident adapter could not be replicated, and the reason for the failure could not be determined. The testing did reveal that the adapters were difficult to install properly, and on some occasions, when the proper torque was achieved, the adapter housing could still be rotated about the hub when hand pressure was applied. In response to the accident and testing, the supplemental type certificate (STC) holder issued a service bulletin (SB) that stated that the adapter should be inspected for oil leakage and gasket damage. The SB also provided detailed instructions to eliminate and identify rotation of the housing during and after installation. The purpose of the oil filter adapter was to enable use of a conventional spin-on oil filter. The adapter was installed on the engine about 2 years before the accident; the engine had accrued about 340 hours since that time. There were no documents regarding the installation of the oil filter adapter, and it is unknown how it was installed or if new gaskets were used at the time of installation. Maintenance records indicated that the oil filter was changed 7 times between the engine installation and the accident. The last maintenance performed on the airplane was an annual inspection completed 5 days and about 9.4 flight hours before the accident. During this maintenance, the oil filter and the vacuum pump accessory driveshaft seal were replaced. It is possible that the vacuum pump seal was replaced because the mechanics thought it was leaking due to the presence of oil in the engine compartment. This may have been the first indication that the oil filter adapter was beginning to leak.
Probable cause
A total loss of engine power due to oil starvation as a result of the failure of a gasket on the oil filter adapter and the pilot’s inability to clear power lines during the emergency landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR19FA126
- Event ID
- 20190501X62455
- Case number
- WPR19FA126
- 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: 4123475a4a64dcf5bb741d5917ed7f839a9acc22d9b13ebd90e4a7cffca54dc8; retrieved 2026-09-15T06:57:20.620Z.