FTW92FA133 · Cessna 310K
Cessna 310K · Accident: loss of engine power en route
From Midland International Air and Space Port (MAF) to Addison Airport (ADS)
Event
- NTSB case
- FTW92FA133
- 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 310K
- Aircraft type
- Cessna 310
- 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
- N6980L
- Operator
- Sams, Charles & Linda
- Onboard fatalities
- Unknown
- Route
- From Midland International Air and Space Port (MAF), Midland, TXTo Addison Airport (ADS), Addison, TX
- 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 · descent
- 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
- Loss of engine power
- 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 › Fuel tank selector position, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE MULTIENGINE AIRPLANE WAS DESCENDED FROM 9,500 FEET MSL TO 3,500 FEET MSL WHEN THE PILOT REPORTED A LOSS OF POWER TO BOTH ENGINES AT 6,500 FEET. HE ELECTED TO TURN AND ATTEMPT A LANDING AT A MILITARY AIR FORCE BASE WHERE HE COULD SEE THE APPROACH LIGHTS. THE PILOT STATED BOTH ENGINES QUIT AT THE SAME TIME, BUT CAME BACK ON FOR 1/2 SECOND, THEN QUIT AGAIN. HE STATED THAT HE COULD NOT FEATHER THE PROPELLERS THAT WERE REPORTEDLY ROTATING AT 2,000 RPM. THE AIRPLANE DESCENDED AT A HIGH SINK RATE FOR APPROXIMATELY 1/2 STATUTE MILE. THE LANDING GEAR WERE LOWERED APPROXIMATELY 1 1/2 STATUTE MILES FROM THE END OF THE RUNWAY. THE FLAPS WERE LOWERED NEAR THE RUNWAY THRESHOLD. THE AIRPLANE STRUCK THE LOCALIZER ANTENNA ASSEMBLY WITH THE MAIN LANDING GEAR, LOWER LEFT FUSELAGE, AND LEFT ELEVATOR. IT THEN IMPACTED ONTO THE RUNWAY AND SLID APPROXIMATELY 525 FEET. THE FUEL SELECTORS WERE ON THE AUXILIARY TANKS. THEY WERE EXAMINED AND FOUND DRY. EACH MAIN FUEL TANK CONTAINED 41 GALLONS. NO MECHANICAL ANOMALIES WERE FOUND WITH THE AIRPLANE. THE THROTTLES, MIXTURES, AND PROPELLER CONTROLS WERE POSITIONED FULL FORWARD.
Probable cause
LOSS OF POWER TO BOTH ENGINES FROM FUEL STARVATION AND THE IMPROPER SELECTOR POSITIONS OF FUEL TANKS BY THE PILOT. A FACTOR WAS THE PILOT'S FAILURE TO FEATHER THE PROPELLERS.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW92FA133
- Event ID
- 20001211X14645
- Case number
- FTW92FA133
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1992-05-19.
- API snapshot SHA-256: 9d4b3a78671b0ae8275eab205b2ce97cbcca6541d34c23911892a9ac0fae3d04; retrieved 2026-09-23T03:08:37.371Z.