FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN18LA357 · Grumman G164 A

29 Aug 2018 · Opelousas, LA, United States

Grumman G164 A · Accident: loss of engine power (total) while maneuvering

From Church Point Flyers Airport (6LA5) to Church Point Flyers Airport (6LA5)

Report a problem

Event

NTSB case
CEN18LA357
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
Unknown
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 G164 A

Aircraft type
Grumman G164
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
N956X
Operator
Unknown
Onboard fatalities
Unknown
Route
From Church Point Flyers Airport (6LA5), Church Point, LATo Church Point Flyers Airport (6LA5), Church Point, LA
Aircraft age
About 50 years (built 1968)
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
Maneuvering
Defining eventThe 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
Loss of engine power (total)
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

  • Aircraft › Aircraft power plant

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

NTSB narrative

The private pilot was practicing crop-dusting maneuvers when the engine lost total power; he performed a forced landing in an open, muddy field. The airplane nosed over and sustained substantial damage. Postaccident examination of the engine revealed that two of three bolts that secured the left magneto had come loose and were missing. The safety wire was broken, and the Sims coupling was heavily damaged. The magneto could easily be moved around, which disrupted the spark timing and resulted in a total loss of power.

Probable cause

The loss of two securing bolts that allowed the left magneto to move around, which disrupted the spark timing and resulted in the engine losing total power.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN18LA357
Event ID
20180829X81542
Case number
CEN18LA357
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 252ea3ffeb38cb4bc63f42bc75cb32ea443a97419acf9e5b2c546f88374f6efe; retrieved 2026-09-16T08:10:38.776Z.