ANC07LA011 · Cessna T210N
Cessna T210N · Accident: total loss of engine power (mechanical failure) en route
From Winter Haven Regional Airport - Gilbert Field (KGIF) to Smyrna Airport (KMQY)
Event
- NTSB case
- ANC07LA011
- 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
- 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
- N5093A
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Winter Haven Regional Airport - Gilbert Field (KGIF), Winter Haven, FLTo Smyrna Airport (KMQY), Smyrna, TN
- 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
- Engine assembly, crankshaft › Fractured
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The commercial certificated pilot was on a cross-country personal flight in instrument meteorological conditions under Title 14, CFR Part 91. In cruise flight at 10,000 feet, the engine lost power. The pilot declared an emergency, and requested vectors to the nearest airport. The pilot said the airplane broke out of the clouds about 300 feet above ground level, and he landed gear-up in a muddy field. An inspection of the airplane revealed that the engine crankshaft had fractured. Multiple fatigue fracture initiation points were discovered along the radius of the number 2 crankshaft journal. The engine had accrued about 998 hours in service since major overhaul. The airplane sustained structural damage to the fuselage and wings.
Probable cause
The loss of engine power during cruise flight due to a fractured crankshaft, resulting in an off-airport forced landing in a muddy field.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC07LA011
- Event ID
- 20070108X00020
- Case number
- ANC07LA011
- 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: 047c603714884c73613a5ac1917b91ff24c1b52c90576fc5b209aa5ed74ebfe9; retrieved 2026-09-21T08:52:10.595Z.