FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA24LA095 · Cessna 210D

21 Jan 2024 · Paris, TN, United States

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

From Murray-Calloway County Airport Kyle-Oakley Field (CEY) to McKellar-Sipes Regional Airport (MKL)

Report a problem

Event

NTSB case
ERA24LA095
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 210D

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
N3857Y
Operator
Unknown
Onboard fatalities
Unknown
Route
From Murray-Calloway County Airport Kyle-Oakley Field (CEY), Murray, KYTo McKellar-Sipes Regional Airport (MKL), Jackson, TN
Aircraft age
About 60 years (built 1964)
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
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 from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilots reported the airplane started to shake violently during cruise flight, and oil then covered the windscreen. The engine subsequently lost all power. The flight instructor took control of the airplane and performed a forced landing to a nearby airport. During the forced landing, the airplane’s main landing gear contacted the airport perimeter fence, resulting in the airplane nosing over. The airplane sustained substantial damage to both wings and the engine firewall. Postaccident examination of the engine revealed that the No. 4 cylinder crankshaft connecting rod journals showed evidence of lubrication distress and metal transfer between the bearing and the journal. Review of the airplane’s maintenance logbooks revealed that three of the engine’s six cylinders were replaced about 3 years before the accident, with the remaining three having been replaced about 2 years before the accident. Given this information, and the condition of the No. 4 connecting rod journals, it is likely that the torque on the journals was disrupted during the cylinder replacement(s) which resulted in a spun bearing.

Probable cause

The disruption of torque to the No 4 connecting rod journals, which resulted in a spun bearing and the subsequent total loss of engine power.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA24LA095
Event ID
20240122193696
Case number
ERA24LA095
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, coordinates, cause areas. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2024-01-22.
  • API snapshot SHA-256: 766be8d4296401b893722f957de2f0fb491193399362a6e5b3181a7ec89931aa; retrieved 2026-09-16T18:27:36.150Z.