FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA99LA166 · Cessna 182E

6 Jun 1999 · Rolling Fork, MS, United States

Cessna 182E · Accident: partial loss of engine power (mechanical failure) en route

From Wade Airport (MS35) to an unrecorded destination

Report a problem

Event

NTSB case
MIA99LA166
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 182E

Aircraft type
Cessna 182
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
N9267X
Operator
Robert V. Cummings · private individual
Onboard fatalities
Unknown
Route
From Wade Airport (MS35)To 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 · 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
Partial 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, installation, improper

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

NTSB narrative

While climbing through 600 feet after takeoff, a loud bang was heard and a hole appeared in the top of the engine cowling. Oil leaked from the engine and covered the windshield. The engine did not stop running, but did loose power. A forced landing was landing was made in a field and the nose landing gear collapsed during rollout. Post crash examination of the engine showed the number 3 connecting rod had separated from the crankshaft. Examination of the number three connecting rod bolts showed one bolt had failed due to fatigue which emanated from the edge of the bolt in the dowel area. The other bolt separated due to bending overstress. Examination of connecting rod bolts from the numbers 1 and 2 connecting rods showed slight rubbing in the dowel area of the bolts. Breakaway torque on the numbers 1,2,5, and 6 connecting rod bolts showed torque values below the manufacturers requirements.

Probable cause

Improper torqueing of the connecting rod bolts which resulted in the bolts being loose and rubbing in the dowel area which resulted in fatigue emanation and cracking and separation of the number 3 connecting rod after bolt failure.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA99LA166
Event ID
20001212X19058
Case number
MIA99LA166
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: 64478528090de3a4326f8980529a332835a513b30b249aa94e5599ea0e9c6a24; retrieved 2026-09-22T14:58:13.393Z.