FTW93LA097 · Beech A36
Centerline Aviation Beech A36 · Accident: total loss of engine power (non-mechanical) en route
From MSA · MT. PLEASANT, TX to Addison Airport (ADS)
Event
- NTSB case
- FTW93LA097
- 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
Beech A36
- Aircraft type
- Beechcraft 36
- 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
- N6088S
- Operator
- Centerline Aviation
- Onboard fatalities
- Unknown
- Route
- From MSA · MT. PLEASANT, 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 · 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 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 use of
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT HAD FLOWN APPROXIMATELY 2.65 HOURS AND WAS RETURNING TO THE AIRPORT WHERE HE HAD RENTED THE AIRPLANE WHEN A POWER LOSS OCCURRED. HE STATED THAT HE SWITCHED FUEL TANKS AND THE ENGINE MOMENTARILY RESTARTED THEN QUIT AGAIN. THE AIRPLANE'S RECORDED ALTITUDE WAS 2,500 FEET MEAN SEA LEVEL WHEN THE ENGINE STOPPED. DURING THE EMERGENCY DESCENT HE MANEUVERED OVER POWERLINES THEN LANDED IN AN OPEN FIELD. THE AIRPLANE STRUCK A DIRT MOUND AND A CEMENT CULVERT. THE LEFT FUEL TANK WAS FOUND EMPTY. THE RIGHT FUEL TANK WAS FULL, BUT LEAKED DURING THE NIGHT UNTIL THE RECOVERY TEAM ARRIVED. ELEVEN GALLONS OF FUEL WAS DRAINED FROM THE RIGHT TANK. THE ENGINE WAS TEST RUN USING THE FUEL FROM THE RIGHT TANK. NO ANOMALIES WERE NOTED TO THE ENGINE. DARK NIGHT CONDITIONS PREVAILED
Probable cause
FUEL STARVATION INDUCED POWER LOSS RESULTANT FROM FAILURE OF THE PILOT TO SWITCH THE FUEL SELECTOR TO THE PROPER FUEL TANK. FACTORS WERE THE DARK NIGHT CONDITIONS AND LACK OF SUITABLE TERRAIN FOR A FORCED LANDING
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW93LA097
- Event ID
- 20001211X11979
- Case number
- FTW93LA097
- 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 1993-03-07.
- API snapshot SHA-256: 935f2877794f2ab9e8ec5e9eb3a7922a30beb7bf51fb5a8454dfb596b7ada529; retrieved 2026-09-21T23:01:22.388Z.