FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR17LA172 · Cessna T210F

31 Jul 2017 · Llano, CA, United States

Cessna T210F · Accident: loss of engine power (total) en route

From Modesto City Co-Harry Sham Field (MOD) to Hemet Ryan Airport (HMT)

Report a problem

Event

NTSB case
WPR17LA172
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

Cessna T210F

Aircraft type
Cessna 210
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
N6109R
Operator
Unknown
Onboard fatalities
Unknown
Route
From Modesto City Co-Harry Sham Field (MOD), Modesto, CATo Hemet Ryan Airport (HMT), Hemet, CA
Aircraft age
About 52 years (built 1965)
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)
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 had flown the airplane uneventfully on the outbound leg of a cross-country flight. On the return leg, the pilot noticed that he was unable to achieve full manifold pressure and that the engine was "running roughly." He stopped at an interim airport, where an aircraft mechanic examined the airplane but was unable to find any problems with the airplane or engine. The pilot subsequently departed to continue the trip home. While in cruise flight, he noticed that the oil pressure had dropped to 0 psi. The pilot retarded the throttle, declared an emergency with air traffic control, and diverted toward a nearby airport. The engine then lost total power. The airplane was unable to reach the diversion airport and sustained substantial damage to the fuselage during the forced landing.

Preliminary examination of the wreckage revealed that the engine was devoid of oil; no obvious leaks or other failures were apparent. Further examination of the engine revealed that the No. 1 connecting rod bearing and cap assembly had failed catastrophically due to oil starvation and that the liberated or partially liberated components caused significant internal damage to the engine. In addition, many internal engine components exhibited thermal distress signatures due to oil starvation. Detailed examination of the turbocharger revealed significant damage to the compressor and turbine blades, grossly excessive axial and radial freeplay of the compressor and turbine rotors, and fracture separation of the two rotors from one another. In addition, the turbocharger bearing housing, turbine outlet case, and turbine blades displayed coked oily/dirty residue. This evidence indicated that the engine oil was depleted by leaking and/or burning via the turbocharger.

The turbocharger manufacturer guidance specified certain inspections and that the turbocharger overhaul interval should coincide with, but not exceed, the time between overhaul (TBO) (hours in service) published by the engine manufacturer. The engine manufacturer's published TBO was 1,400 hours. However, the engine manufacturer guidance explicitly excluded engines with parts not supplied by the engine manufacturer, which was the case for this engine. The airplane maintenance records showed that the turbocharger was overhauled 13 years before the accident and had accumulated about 1,974 hours since that overhaul. The records did not document any relevant maintenance actions or inspections of the turbocharger since its overhaul. Given this information, it is likely that the turbocharger failure was the result of improper and/or incomplete maintenance and inspection. The turbocharger failure completely depleted the engine oil during the accident flight, and the oil depletion resulted in a catastrophic internal failure of the engine and a complete loss of engine power. There was insufficient evidence to determine when the oil depletion began or how long that process took.

Probable cause

A failure of the turbocharger that resulted in complete depletion of the engine oil and catastrophic internal failure of the engine. Contributing to the accident was improper and/or incomplete maintenance and inspection of the turbocharger.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR17LA172
Event ID
20170731X30722
Case number
WPR17LA172
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2017-08-01.
  • API snapshot SHA-256: 9660d6866aa8fee02174f31d32e9cb8cb97d2c55dda4ba1da7e474baeacad6ef; retrieved 2026-09-16T05:37:36.373Z.