FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA92FA099 · Piper PA-32-300

16 Mar 1992 · Aberdeen, MS, United States

S and S Construction Piper PA-32-300 · Accident: partial loss of engine power (mechanical failure) during initial climb

From an unrecorded airport to Macon Municipal Airport (20M)

Report a problem

Event

NTSB case
MIA92FA099
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
1 · 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-32-300

Aircraft type
Piper PA-32
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
N16388
Onboard fatalities
Unknown
Route
From not recordedTo Macon Municipal Airport (20M), Macon, MS
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
Initial climb
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)
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Tree(s)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command › Emergency procedure, improper

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

NTSB narrative

AT APPROXIMATELY 100-FOOT ALTITUDE, AFTER TAKEOFF, WITNESSES HEARD ENGINE SPUTTER AND LOSE POWER. AIRCRAFT WAS THEN OBSERVED TO BANK STEEPLY TO THE LEFT AND DESCEND INTO TREES. A POSTCRASH FIRE ERUPTED. THE NO. 3 CONNECTING ROD HAD FAILED DUE TO FATIGUE. THE FATIGUE ORIGINATED IN GALLING MARKS IN THE BEARING AREA ON THE CRANKSHAFT END. ACCORDING TO LYCOMING ENGINES, GALLING IS CAUSED BY ENGINE OVERSPEED OR OVERBOOST. NO RECORDS OF THESE EVENTS HAVING OCCURRED WERE FOUND. AFTER NO. 3 ROD SEPARATED, IT JAMMED INTO THE ENGINE CASE AND DID NOT HINDER ROTATION OF THE ENGINE. THE PROPELLER WAS FOUND TO HAVE ROTATIONAL DAMAGE, AND BLADE ANGLE AT IMPACT WAS IN THE 2100 RPM RANGE. SEVERAL LARGE TREE LIMBS WERE FOUND CUT BY THE PROPELLER AT THE CRASH SITE.

Probable cause

THE PILOT-IN-COMMAND'S DECISION TO INITIATE A TURN BACK TO THE AIRPORT AT A LOW ALTITUDE FOLLOWING LOSS OF ENGINE POWER.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA92FA099
Event ID
20001211X14331
Case number
MIA92FA099
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: bfe526263786e2a4c820fa3aaa968ad9793cd33d3ab7e24b57c1a8a076b061c0; retrieved 2026-09-21T01:18:53.666Z.