FTW96LA345 · Cessna 210-5
Cessna 210-5 · Accident: total loss of engine power (non-mechanical) en route
From Lonoke, AR to GTR · Guthrie, OK
Event
- NTSB case
- FTW96LA345
- 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 210-5
- 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
- N8139Z
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Lonoke, ARTo GTR · Guthrie, OK
- 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 (non-mechanical)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Fuel contamination
- 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
- Fluid, fuel › Contamination
Approximate · Estimated position: the centre of Muskogee, OK, the place the record names. Not the accident site.
NTSB narrative
According to the pilot, the engine started to run rough, and then lost power, while in cruise flight at 6,500 feet MSL. The pilot attempted to land at a nearby airport; however, he subsequently landed short of the airport in a field approximately one mile southeast of the airport. During the landing roll, the airplane impacted a fence and fence posts, which resulted in leading edge damage to one wing and structural damage to both wing struts. The engine was examined by an FAA inspector, the aircraft owner, and a representative from the engine manufacturer at an local FBO. The contents of the fuel system were examined, and evidence of fuel contamination was found. The fuel in the tanks was yellow/straw in color and lacked the appearance of 100LL fuel; however, no diesel or jet fuel was detected. New spark plugs were installed, and the airplane was defueled and serviced with fresh 100LL fuel. The engine was started, and it operated normally through the normal operating range.
Probable cause
loss of engine power due to fuel contamination. The lack of suitable terrain for a forced landing was a related factor.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW96LA345
- Event ID
- 20001208X06498
- Case number
- FTW96LA345
- 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. 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: ae925c25f9de9104caad2efa58db62b957541a36dd6d076bb8be29d3a6848ee6; retrieved 2026-09-22T21:33:40.380Z.