FTW97LA316 · Piper PA-24-250
Piper PA-24-250 · Accident: total loss of engine power (non-mechanical) en route
From El Paso International Airport (ELP) to Easterwood Field (CLL)
Event
- NTSB case
- FTW97LA316
- 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-24-250
- Aircraft type
- Piper PA-24
- 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
- N6667P
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From El Paso International Airport (ELP), El Paso, TXTo Easterwood Field (CLL), College Station, 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 exhaustion
- 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 › Exhaustion
- Fluid, fuel › Siphoning
- Fuel system, cap › Leak
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During a night cross-country flight from El Paso, Texas, to College Station, Texas, the aircraft's engine lost power about 3 hours 49 minutes after takeoff. The pilot reported that the right fuel tank quantity gauge was indicating a quarter tank of fuel remaining when the engine lost power. He estimated fuel endurance for the flight would be 4.33 hours. The pilot initiated a forced landing to Highway 36, and during the approach to the highway, he flashed the aircraft's landing light to warn the traffic of his intention to land. All of the traffic moved out of the way except for a pickup truck which the aircraft's left wing struck. After landing the pilot looked into the right fuel tank with a flash light, and the bottom of the fuel tank appeared to be 'buckled or bunched' up against the fuel quantity float. Examination of the right fuel tank revealed a damp fuel stain on the wing that originated from the filler cap, and there was no 'bulging' in the bottom of the tank. It was calculated that approximately 10 gallons of fuel had siphoned out during the flight.
Probable cause
The loss of engine power due to fuel exhaustion which resulted from a leaking fuel cap. Factors were the dark night conditions, and the lack of suitable terrain for the forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW97LA316
- Event ID
- 20001208X08628
- Case number
- FTW97LA316
- 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 1997-08-18.
- API snapshot SHA-256: 996dd23c34a1094ce7a9e9e5fd13db89a16dfe9706103663cb4e0b58b2e1e358; retrieved 2026-09-21T21:13:40.196Z.