FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW95LA139 · Piper PA-28R-201

18 Mar 1995 · Devine, TX, United States

Piper PA-28R-201 · Accident: total loss of engine power (non-mechanical) en route

From Pleasanton Municipal Airport (PEZ) to 23R

Report a problem

Event

NTSB case
FTW95LA139
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-28R-201

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
N47839
Operator
Unknown
Onboard fatalities
Unknown
Route
From Pleasanton Municipal Airport (PEZ), Pleasanton, TXTo 23R
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)
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

  • Lubricating system, oil quickdrain/drain plug › Open
  • Lubricating system, oil quickdrain/drain plug › Unapproved part
  • Other maintenance personnel › Maintenance, modification, improper

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

NTSB narrative

THE ENGINE OIL ANNUNCIATOR LIGHT ILLUMINATED 10 MINUTES INTO THE FLIGHT FOLLOWING AN ENGINE INSTALLATION AND COMPLETION OF AN ANNUAL INSPECTION. THE ENGINE OIL PRESSURE DROPPED TO ZERO AFTER THE ENGINE OIL DRAINED FROM AN UNAPPROVED QUICK DRAIN PLUG WHICH WAS INSTALLED ON THE ENGINE OIL PAN BY THE MECHANIC. THIS RESULTED IN A TOTAL POWER LOSS. INVESTIGATION REVEALED THAT THE NOSE LANDING GEAR DRAG LINK MADE CONTACT WITH THE QUICK OIL DRAIN DURING THE GEAR RETRACTION CYCLE RESULTING IN THE LOSS OF OIL. WHILE ATTEMPTING A FORCED LANDING IN A SOFT FRESHLY PLOWED FIELD, THE AIRPLANE WAS SUBSTANTIALLY DAMAGED.

Probable cause

A POWER LOSS DUE TO THE INADVERTENT OPENING OF AN UNAPPROVED QUICK OIL DRAIN INSTALLED BY MAINTENANCE PERSONNEL. 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 FTW95LA139
Event ID
20001207X03120
Case number
FTW95LA139
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: d9fa08137375d1e0cdac03f71a9958e83f267ee20f1f05ea82252b1c8bb6ffe9; retrieved 2026-09-23T00:08:30.650Z.