FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA90LA181 · Piper J3C-65

1 Sept 1990 · Opa-locka, FL, United States

Piper J3C-65 · Accident: total loss of engine power (mechanical failure) en route

From North Perry Airport (HWO) to an unrecorded destination

Report a problem

Event

NTSB case
MIA90LA181
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 J3C-65

Aircraft type
Piper J3
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
N70659
Operator
Unknown
Onboard fatalities
Unknown
Route
From North Perry Airport (HWO), Hollywood, FLTo 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
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

  • Engine assembly, connecting rod cap › Separation

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

NTSB narrative

DURING NORMAL CRUISE FLT, THE PLT REPORTED THAT THE RPM WAS DECREASING & THE OIL TEMPERATURE WAS INCREASING. THE ENG THEN SEIZED. WITH POOR FWD VISIBILITY DUE TO OIL COVERING THE WINDSCREEN, HE OVERSHOT THE FIELD HE WAS ATTEMPTING TO LAND IN. THE ACFT COLLIDED WITH A FENCE THEN NOSED OVER. EXAM OF THE ENG REVEALED THAT THE NUMBER 3 CYLINDER CONNECTING ROD END CAP SEPARATED, EXISTED THE CASE & CAME TO REST IN THE OIL SUMP. LYCOMING ENG PERSONNEL STATED THAT THE SEPARATION OF THE ROD CAP WAS DUE TO A LACK OF LUBRICATION WHICH CAUSED THE ROD BOLTS TO STRETCH, LOSING THEIR TORQUE, & ONE OF THE TWO NUTS VIBRATED OFF. THE OTHER ROD BOLT FAILED DUE TO OVERLOAD. THE ENG RECEIVED A TOP OVERHAUL 136 HRS EARLIER & A MAJOR OVERHAUL WAS PERFORMED 2,122 HRS EARLIER. NO DETERMINATION COULD BE MADE AS TO THE REASON FOR THE LACK OF LUBRICATION.

Probable cause

ENGINE FAILURE DUE TO LACK OF OIL SUPPLY TO THE NUMBER 3 CYLINDER CONNECTING ROD FOR UNDETERMINED REASONS. THIS ALLOWED THE CONNECTING ROD END CAP TO SEPARATE THROUGH THE CASE RESULTING IN OIL EXHAUSTION.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA90LA181
Event ID
20001212X24327
Case number
MIA90LA181
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: 663bc432c9092c70857c2a5bb453afb2b4523f4812846fdf9a8c9a1012915d60; retrieved 2026-09-21T23:44:59.828Z.