FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA06LA121 · Cessna T210

15 Jul 2006 · Crestview, FL, United States

Cessna T210 · Accident: total loss of engine power (mechanical failure) en route

From Ruckel Airport (FL17) to Monroe County Aeroplex Airport (KMVC)

Report a problem

Event

NTSB case
MIA06LA121
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 T210

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
N5266Y
Operator
Unknown
Onboard fatalities
Unknown
Route
From Ruckel Airport (FL17), Niceville, FLTo Monroe County Aeroplex Airport (KMVC), Monroeville, AL
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
Total loss of engine power (mechanical 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

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot stated to the responding FAA inspector that during cruise flight the engine made a loud bang with a subsequent loss of engine power. The propeller remained windmilling and there was no response to engine controls and a restart. The pilot declared an emergency and elected to land in an open area within a timberland. The approach was normal until the landing. The main wheels touch down first and the nose wheel followed, which dug into the terrain, separating, and the airplane flipped over before coming to a stop. The pilot and passenger exited the airplane unassisted. Post recovery examination revolved there was a lost of continuity in the engine. The engine was taken to the manufacturer for a teardown examination. The crankshaft was separated at the No. 2 main bearing. The crankshaft and crankcase halves alone with associated parts were examined at the NTSB Materials Laboratory in Washington, D.C. The crankshaft was fractured through the aft cheek of the No. 2 main bearing journal. Optical examinations found features typical of fatigue propagation, smoothly textured surfaces with curved arrest lines, on the forward facture. Ratchets marks indicated that the fatigue initiated at multiple locations on the surface of the aft radius of the main journal surface with rearward propagation through the crank cheek. The fatigue initiation was located at the approximate tangent point between the aft journal radius and the face of the forward face of the cheek. The surface of the No. 2 main journal was circumferentially roughened but not deeply gouged. Heat tinting darkened was observed in the local areas. Other main and cylinder journals showed some local damage but none to the extent of the No. 2 main. The main bearing shells for the No. 2 main were fractured and broken up into several pieces. Many were not accounted for. The other bearing shells were intact showing various levels of wear, damage and debris embedment. The bearing shells were marked as FAA-PMA part numbers SA642720M10, indicating 0.010 inch oversize bearings. Engine logbooks reflect, the engine last received a major overhaul on April 22, 1998, 1,354 flight hours before the accident. On August 27, 2004, 315 flight hours before the accident; all six cylinders were replaced with new cylinders. On September 5, 2005, 141 flight hours before the accident, the airplane had an annual inspection. On July 8, 2006, about three hours before the accident, the engine had maintenance done to its turbocharger.

Probable cause

Spinning of the crankshaft No. 2 main bearing for undetermined reasons resulting in damage to the aft cheek of the No. 2 main bearing journal and fatigue failure of the crankshaft.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA06LA121
Event ID
20060724X00995
Case number
MIA06LA121
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, coordinates. 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: 54256861f7a75c81fe4052dae3450210c4991cbd229d87e472b5c059bba92c5b; retrieved 2026-09-22T04:40:25.262Z.