MIA97LA066 · Cessna 172P
Cessna 172P · Accident: total loss of engine power (mechanical failure) en route
From North Perry Airport (HWO) to an unrecorded destination
Event
- NTSB case
- MIA97LA066
- 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
Cessna 172P
- Aircraft type
- Cessna 172
- 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
- N136FR
- 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 bolt › Undertorqued
- Other maintenance personnel › Maintenance, installation, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The engine lost partial power and engine oil leaked out, covering the windshield. About 3 miles from the airport the engine quit completely. While making a forced landing downwind, the aircraft overran the runway, collided with 2 fences, and nosed over. Postcrash examination of the engine showed the No. 3 connecting rod had disconnected from the crankshaft. One of the No. 3 connecting rod nuts was found in the oil pan with no thread damage and the threaded portion of the respective rod bolt for this nut was found protruding through the engine case with no thread damage. All other engine damage was consistent with secondary damage following connecting rod separation. The engine had accumulated 47 flight hours since major overhaul, at which time the connecting rod bolts were replaced.
Probable cause
Failure of other maintenance personnel to properly torque a connecting rod bolt and nut for the No. 3 cylinder during engine overhaul.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA97LA066
- Event ID
- 20001208X07334
- Case number
- MIA97LA066
- 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: c247c13b1b98aaa3e9e005d0f7eb4d009c2b1835aa2e6971eb366c49263a614d; retrieved 2026-09-21T21:31:03.332Z.