CHI89LA087 · Piper PA-24-250
Piper PA-24-250 · Accident: total loss of engine power (mechanical failure) en route
From WI06 · WAUNAKEE, IL to Morris Municipal Airport James R. Washburn field (C09)
Event
- NTSB case
- CHI89LA087
- 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-24-250
- Aircraft type
- Piper PA-24
- 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
- N7465P
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From WI06 · WAUNAKEE, ILTo Morris Municipal Airport James R. Washburn field (C09), Morris, IL
- 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 · climb to 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
- Engine assembly, bearing › Slipped
- Lubricating system, oil port/passage, internal › Blocked(total)
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
AS THE AIRCRAFT WAS CLIMBING FROM TAKEOFF, THE PILOT NOTICED AN UNUSUAL ENGINE NOISE & OIL PRESSURE FLUCTUATIONS. WHEN HE REALIZED THE AIRCRAFT WOULD NOT REACH THE AIRPORT, HE SHUT DOWN THE ENGINE & MADE A WHEELS UP LANDING IN A NEWLY PLANTED CORN FIELD. EXAMINATION OF THE ENGINE REVEALED EVIDENCE OF OIL STARVATION OF THE #4 ROD BEARING, THE #5 ROD BEARING & THE MAIN BEARING, THEN SUBSEQUENT FAILURE OF THE #5 ROD. THERE WAS EVIDENCE THAT THE OCCURRENCE WAS INITIATED BY SLIPPAGE OF A BEARING.
Probable cause
SLIPPAGE OF A BEARING, WHICH RESULTED IN BLOCKAGE OF THE LUBRICATION SYSTEM, AND SUBSEQUENT FAILURE OF A CONNECTING ROD.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI89LA087
- Event ID
- 20001213X28268
- Case number
- CHI89LA087
- 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: c91c881fe794558d17429ae5c684fd96e8d393660ba556cf4599ba71e986a27b; retrieved 2026-09-23T07:37:24.048Z.