FTW83LA146 · Piper PA-20
Piper PA-20 · Accident: total loss of engine power (non-mechanical) en route
From T02 · Houston, TX to Ambia Farm Airport (21TX)
Event
- NTSB case
- FTW83LA146
- 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
Piper PA-20
- Aircraft type
- Piper PA-20
- 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
- N4944M
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From T02 · Houston, TXTo Ambia Farm Airport (21TX), Texarkana, 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 contamination; Fuel starvation; Tree(s)
- 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
- Fluid, fuel › Starvation
- Fuel system, strainer › Blocked(total)
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
REPORTEDLY, THE PLT TOOK OFF WITH 36 GALLONS OF FUEL ON BOARD, OF WHICH, 10 GALS WAS AUTOMOBILE LOW LEAD FUEL. THE AUTOMOBILE FUEL HAD BEEN PURCHASED FROM AN OFF AIRPORT GASOLINE STATION, WAS TRANSPORTED TO THE ACFT IN 5 GAL CANS, THEN ADDED TO THE FUEL TANKS WITH A FILTERED SPOUT. THE PLT REPORTED THAT HE BURNED FUEL FROM THE RIGHT TANK UNTIL THE ENGINE QUIT WHILE THE RIGHT GAGE INDICATED APRX 1/4 FULL. HE RESTARTED THE ENGINE & CONTINUED, USING THE LEFT TANK. THE ENGINE LOST POWER AGAIN WHEN THE LEFT FUEL GAGE INDICATE APRX 1/2 FULL. THE ACFT WAS OVER A HILLY & WOODED AREA AT 4500 FT MSL. THE PLT FOUND A SUITABLE AREA FOR AN EMERGENCY LANDING, BUT THE RIGHT WING OF THE ACFT HIT A TREE SHORT OF THE AREA. AN EXAM REVEALED THAT THE GASCOLATOR WAS CLOGGED WITH UNIDENTIFIED CONTAMINANTS. THE GASCOLATOR WAS DRAINED & CHECKED DURING AN ANNUAL INSPECTION, 13 FLT HRS PRIOR TO THE ACCIDENT. BEFORE THE ANNUAL INSPECTION, THE ACFT HAD BEEN IN STORAGE FOR 10 YRS.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record FTW83LA146
- Event ID
- 20001214X42433
- Case number
- FTW83LA146
- 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: 46b15d01eb3ba160003e3b6d9fafdc19fdcabd14f38c00e53e975bcba7184846; retrieved 2026-09-22T02:45:48.065Z.