FTW99LA174 · Piper PA-34-220T
Piper PA-34-220T · Accident: total loss of engine power (non-mechanical) en route
From San Antonio International Airport (SAT) to Laredo International Airport (LRD)
Event
- NTSB case
- FTW99LA174
- 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-34-220T
- Aircraft type
- Piper PA-34
- 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
- N8329M
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From San Antonio International Airport (SAT), San Antonio, TXTo Laredo International Airport (LRD)
- 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
- 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
- Pilot in command › Refueling, not performed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During descent for landing, the twin-engine airplane lost power in both engines due to fuel exhaustion. The pilot reported that during his preflight inspection, the fuel gauges were reading a little over 30 gallons on the left and about 35 gallons on the right. When the flight neared its destination, the pilot started a descent for landing. As he 'pitched' the nose down, the left gauge went to zero. A few minutes later, the right gauge went from about 20 gallons to zero, and a few seconds later, the right engine lost power, followed by the left engine. A forced landing was initiated to a nearby road; however, after observing traffic on the road, the pilot elected to land in the grass area next to the road. After touchdown, the right wing impacted a metal fence post, and the aircraft came to rest nose down in a ditch. Examination of the fuel system by an FAA inspector revealed no usable fuel in the left fuel tank, and the right fuel tank was destroyed. There was no evidence of fuel spillage at the accident site. The pilot reported that he could have prevented this accident by adding an 'extra 10 gallons' of fuel.
Probable cause
The pilot's failure to refuel, which resulted in a total loss of engine power due to fuel exhaustion. A factor was the lack of suitable terrain for the forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW99LA174
- Event ID
- 20001212X19006
- Case number
- FTW99LA174
- 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: e1f11a0244f60aa20ad96d7afe7817246f9d3249b25395a2599ae820d91bebe0; retrieved 2026-09-22T14:44:32.532Z.