DEN00LA099 · Cessna TR182
Cessna TR182 · Accident: airframe, component or system failure en route
From Cedar City Regional Airport (CDC) to Provo Municipal Airport (PVU)
Event
- NTSB case
- DEN00LA099
- 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
- 0
- 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 TR182
- 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
- N738FN
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Cedar City Regional Airport (CDC), Cedar City, UTTo Provo Municipal Airport (PVU), Provo, UT
- Aircraft age
- Not recorded
- 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
- First occurrenceThe 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
- Airframe, component or system 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
- Lubricating system, oil scavenge pump › Failure, total
- Pilot in command › Compensation for wind conditions, inadequate
- Powerplant › Failure, total
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot said that the engine began to run rough, and he could smell smoke in the cockpit. He said that the smoke got worse, and he shut off the master switch. He saw the airport, headed for it, and his engine power began to fail. He attempted to land on runway 16, with a 22 knot gusting to 26 knot tailwind, but was too high. The pilot said he turned right, to approximately 180 degrees, to miss some buildings. He landed approximately 1,000 feet from the departure end of the runway in scrub-covered terrain. The airplane impacted a berm, and nosed over. The airplane's vertical stabilizer, left wing, and fuselage were damaged. Postaccident examination of the engine by a mechanic revealed that the turbocharger's oil scavenger pump had failed. The mechanic said that the scavenger pump's failure would cause the engine's oil to pass overboard.
Probable cause
The failure of the turbocharger scavenging pump resulting in the total failure of the engine, and the pilot's failure to compensate for wind conditions that led him to over fly the runway during his forced landing. Factors were the pilot's diverted attention due to smoke in the cockpit, and the tailwind weather condition.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN00LA099
- Event ID
- 20001212X20986
- Case number
- DEN00LA099
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 95e9d35381221e529227fe7b7e179fc733ad57e7829887e833531f067fcbcc86; retrieved 2026-09-21T20:12:51.889Z.