ATL93LA043 · Cessna 210
Cessna 210 · Accident: total loss of engine power (non-mechanical) on approach
From Tompkinsville Monroe County Airport (TZV) to an unrecorded destination
Event
- NTSB case
- ATL93LA043
- 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
- 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
- N7479E
- Operator
- Love, Carl C. · private individual
- Onboard fatalities
- Unknown
- Route
- From Tompkinsville Monroe County Airport (TZV), Tompkinsville, KYTo not recorded
- 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
- Approach · VFR go-around
- 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 starvation
- 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 › Starvation
- Pilot in command › Procedures/directives, not followed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PRIVATE PILOT LANDED AT AN AIRPORT 45 MILES SHORT OF HIS DESTINATION TO REFUEL. NO FUEL WAS AVAILABLE, SO HE ELECTED TO CONTINUE TO HIS DESTINATION. HE ESTIMATED 12 GALLONS OF FUEL ON BOARD AT THE TIME. ENROUTE TO THE AIRPORT, HE RAN THE RIGHT TANK DRY, AND SWITCHED TO THE LEFT TANK. HE DECIDED TO FLY A NO FLAP LANDING DUE TO LOW FUEL. HE WAS HIGH AND FAST ON FINAL, SO HE SLIPPED THE AIRCRAFT, LEFT WING LOW. HE COULD NOT LAND SAFELY, SO HE EXECUTED A GO AROUND, AND THE ENGINE DID NOT RESPOND. HE ATTEMPTED A TURN BACK TO THE AIRPORT FOR A FORCED LANDING. WHILE IN THE TURN, THE AIRCRAFT STRUCK A FENCE, THEN COLLIDED WITH THE GROUND. THE CESSNA 210 PILOT'S MANUAL STATES THAT PROLONGED SIDESLIPS CAN RESULT IN UNPORTING OF THE FUEL SYSTEM, AND FUEL STARVATION. THERE CAN BE UP TO 10 GALLONS OF UNUSABLE FUEL IN THE SYSTEM WHEN LEVEL FLIGHT IS NOT MAINTAINED. THE ENGINE POWER LOSS OCCURRED ABOUT 35 MINUTES INTO THE ACCIDENT FLIGHT.
Probable cause
THE FAILURE OF THE PILOT TO FOLLOW PILOT MANUAL PROCEDURES BY SLIPPING THE AIRCRAFT WITH INADEQUATE FUEL AVAILABLE, WHICH RESULTED IN FUEL STARVATION. FACTORS WERE THE INADEQUATE FUEL SUPPLY ON THE AIRCRAFT AND THE FAILURE OF THE PILOT TO REFUEL.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL93LA043
- Event ID
- 20001211X16126
- Case number
- ATL93LA043
- 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: b6e41c32883cac049f2427b263aef91232126cfdbbd279a3915a09134cbf879a; retrieved 2026-09-21T14:36:10.856Z.