ATL82DA252 · Grumman G-164C
Grumman G-164C · Accident: total loss of engine power (mechanical failure) while maneuvering
From GUNNISON, MS to GUNNISON, MS
Event
- NTSB case
- ATL82DA252
- 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
Grumman G-164C
- Aircraft type
- Grumman G-164
- 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
- N6787K
- Operator
- Darryc E. Mccreary · private individual
- Onboard fatalities
- Unknown
- Route
- From GUNNISON, MSTo GUNNISON, 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 137: Agricultural
- 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
- Maneuvering · aerial application
- 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 › Overtemperature
- Engine assembly, master rod › Binding(mechanical)
- Lubricating system, oil seal › Leaded
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT REPORTED THAT HE SMELLED SOMETHING HOT WHILE SPRAYING. HE CHECKED THE INSTRUMENTS AND NOTED THAT THE OIL TEMPERATURE GAUGE WAS INDICATING OFF THE HIGH SIDE OF THE SCALE. HE STARTED TO MAKE A PRECAUTIONARY LANDING BUT THE ENGINE SEIZED DURING FINAL APPROACH. A FORCED LANDING WAS MADE IN A FRESHLY PLOWED FIELD WHERE THE PLANE NOSED OVER. A TEARDOWN OF THE ENGINE REVEALED THAT A MASTER ROD SPACER, PN 117547, HAD FAILED. WITHOUT THIS SPACER THE MASTER ROD WOULD NOT BE PROPERLY LUBRICATED, AND REPORTEDLY, THE ENGINE COULD SEIZE. FURTHER INVESTIGATION REVEALED THAT THE ENGINE HAD BEEN OVERHAULED 93 HRS PRIOR TO THE ACCIDENT. FOLLOWING THE OVERHAUL, THE ENGINE HAD A PROBLEM LEAKING OIL PAST THE VALVES, SO IT WAS TAKEN BACK TO THE OVERHAUL FACILITY. SEVEN CYLINDERS WERE REMOVED AND REWORKED. THE ACCIDENT OCCURRED FOLLOWING A BRIEF BREAK-IN PERIOD AFTER THAT.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL82DA252
- Event ID
- 20020917X02822
- Case number
- ATL82DA252
- 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: 80e723306558f00bf345deb29ff22fa35e040ce026c80d74fda9733fd2476ecf; retrieved 2026-09-24T01:16:58.474Z.