FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN18LA031 · Cessna T210N

12 Nov 2017 · Grayslake, IL, United States

Runzel Brothers Aviation Cessna T210N · Accident: loss of engine power (total) on approach

From Pierre Regional Airport (PIR) to Chicago Executive Airport (PWK)

Report a problem

Event

NTSB case
CEN18LA031
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
Instrument Meteorological Cond

Cessna T210N

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
N5300A
Onboard fatalities
Unknown
Route
From Pierre Regional Airport (PIR), Pierre, SDTo Chicago Executive Airport (PWK), CHICAGO/PROSPECT HEIGHTS/WHEELING, IL
Aircraft age
About 38 years (built 1979)
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
Approach
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 › Fluids/miscellaneous hardware

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

While en route on an instrument flight rules cross-country flight, the pilot noticed that the engine oil pressure had decreased; the oil pressure gauge was indicating in the yellow range, but the other engine instruments were showing normal indications. During the descent to landing, when the airplane was about 2,500 ft mean sea level, the pilot heard a "loud bang" from the engine, and smoke filled the cockpit. After declaring an emergency and requesting vectors from air traffic control to the nearest airport, the pilot executed an emergency landing just short of the runway in a wet, grassy area; the airplane slid, came to rest upright on the runway, and sustained substantial damage.

A postaccident examination of the engine revealed two large holes in the crankcase and mechanical damage on the inside of both crankcase halves. The No. 4 connecting rod, which exhibited thermal damage signatures, had separated from the crankshaft and thus punctured the holes in the crankcase. The No. 4 connecting rod bearings were significantly damaged consistent with lack of lubrication, and all of the connecting rod bearings displayed smear-type signatures consistent with lubrication distress. Gouging was found inside the oil pump consistent with the passage of hard particles during engine operation; it is likely that the metal pieces from the damaged engine passed through the oil pump and created the gouges.

The turbocharger's oil scavenge check valve spring was found broken, which resulted in the check valve not closing automatically; it would not restrict oil traveling from the turbo to the scavenge pump. The pilot reported a normal oil level before the flight and no signs of oil leaking. Further, according to the engine manufacturer, an open check valve would not have any effect on oil consumption during engine operation; thus, it was not a factor in this accident. The reason for the lack of lubrication could not be determined.

Probable cause

The failure of the No. 4 connecting rod due to inadequate oil lubrication for reasons that could not be determined because the postaccident engine examination did not reveal any anomalies that would have caused a lack of lubrication.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN18LA031
Event ID
20171114X52018
Case number
CEN18LA031
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: 85a37740723c443820a6ddde51e2a98ddcdb522275c3c92f07a17a768f18e413; retrieved 2026-09-16T06:00:15.993Z.