FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW89LA098 · Piper PA-28R-200

23 May 1989 · Edmond, OK, United States

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

From OKC Will Rogers World Airport (OKC) to Stillwater Regional Airport (SWO)

Report a problem

Event

NTSB case
FTW89LA098
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-200

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
N3940X
Operator
James, Rodney C. · private individual
Onboard fatalities
Unknown
Route
From OKC Will Rogers World Airport (OKC), Oklahoma City, OKTo Stillwater Regional Airport (SWO), Stillwater, OK
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 (mechanical failure)
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

  • Company maintenance personnel › Maintenance, improper

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

NTSB narrative

THE AIRPLANE WAS ON A PERSONAL NIGHT CROSS-COUNTRY FLIGHT WHEN THE PILOT NOTICED A RAPID LOSS OF OIL PRESSURE AND A FULL INCREASE OF PROPELLER RPM. HE HEADED TOWARD THE NEAREST AIRPORT BUT THE ENGINE FAILED COMPLETELY. DURING THE FORCED LANDING, THE AIRPLANE TOUCHED DOWN SHORT OF A IRON PIPE FENCE. THE PILOT TRIED TO PULL THE AIRPLANE UP OVER THE FENCE BUT THE LANDING GEAR SHEARED OFF WHEN IT HIT THE TOP OF THE FENCE. INSPECTION REVEALED THERE WAS NO OIL IN THE ENGINE, NO SUMP PLUG IN THE ENGINE, AND NO EVIDENCE OF THE SUMP PLUG HAVING EVER BEEN SAFETIED. THE NUMBER TWO CYLINDER ALSO HAD A HOLE IN IT.

Probable cause

IMPROPER MAINTENANCE PERFORMED BY THE COMPANY MECHANIC WHO FAILED TO TIGHTEN THE OIL SUMP PLUG, AND ALSO FAILED TO SAFETY IT.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW89LA098
Event ID
20001213X28322
Case number
FTW89LA098
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 1989-05-24.
  • API snapshot SHA-256: fde12b741adabbe31d18afec2800a1bea3bed02fe4389d5a415a2b7c48bfbc37; retrieved 2026-09-23T07:35:20.881Z.