MKC88LA114 · Piper PA-28R-200
Piper PA-28R-200 · Accident: total loss of engine power (mechanical failure) en route
From Jefferson City Memorial Airport (JEF) to H00 · Bentonville, AR
Event
- NTSB case
- MKC88LA114
- 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
- N4490T
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Jefferson City Memorial Airport (JEF), Jefferson City, MOTo H00 · Bentonville, AR
- 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
- Lubricating system, oil line › Ruptured
- Pilot in command › Proper touchdown point, not attained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DURING A BUSINESS, CROSS-COUNTRY FLIGHT, THE PRIVATE PILOT SAID THAT HE HEARD A POPPING NOISE FOLLOWED BY OIL APPEARING ON THE WINDSHEILD. SHORTLY AFTER THE ENGINE BEGAN TO LOSE POWER, THEN QUIT. AN EMERGENCY LDG WAS ATTEMPTED ON AN AIRPORT, BUT THE ACFT LANDED SHORT OF THE RUNWAY, STRUCK A FENCE AND COLLIDED WITH THE TERRAIN. THE ACFT CAME TO REST ABOUT 25 FEET FROM THE RUNWAY. POST ACCIDENT INVESTIGATION REVEALED A BROKEN ENGINE OIL LINE WHICH RESULTED IN LOSS OF ENGINE OIL AND SUBSEQUENT TOTAL ENGINE FAILURE.
Probable cause
TOTAL FAILURE OF THE POWERPLANT DUE TO AN OIL LINE RUPTURE, AND PROPER TOUCHDOWN POINT NOT ATTAINED BY THE PILOT IN COMMAND.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MKC88LA114
- Event ID
- 20001213X26047
- Case number
- MKC88LA114
- 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: 20235244888c5383243f5183a95c3f7044b2c356deea25955a6c4b0744c7845f; retrieved 2026-09-21T16:08:49.893Z.