FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW00LA237 · Piper PA-28-140

20 Aug 2000 · Ennis, TX, United States

Aviation Training Center Piper PA-28-140 · Accident: total loss of engine power (non-mechanical) while maneuvering

From Lancaster Airport (LNC) to an unrecorded destination

Report a problem

Event

NTSB case
FTW00LA237
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-28-140

Aircraft type
Piper PA-28
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
N41375
Onboard fatalities
Unknown
Route
From Lancaster Airport (LNC), Lancaster, TXTo not recorded
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
Maneuvering
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

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The flight instructor was maneuvering the aircraft when the engine cowling blew open. The pilot then heard a loud bang and the engine experienced a loss of engine power. The pilot subsequently performed a forced landing to a field, and during the landing roll, the nose landing gear collapsed. The FAA inspector found the fuel selector positioned on the left fuel tank. The flight instructor stated that she moved the fuel selector to that position after the accident. The salvage personnel, who recovered the airplane, stated that they drained approximately 15 gallons of fuel from the right fuel tank and the left fuel tank was empty. Examination of the airplane revealed no anomalies that would have prevented engine operation. No fuel was found in the electric fuel pump, the fuel line to the fuel sump, the sump, the fuel line to the carburetor, or the carburetor bowl.

Probable cause

The loss of engine power due to fuel starvation, which resulted from the pilot's improper fuel selector positioning.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW00LA237
Event ID
20001212X21733
Case number
FTW00LA237
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: a1f8e58d21a83968a2ccf5d17ee4ee72318450996bc966e5bc063183e2fe3f0a; retrieved 2026-09-21T20:06:31.716Z.