FTW04CA246 · Grumman G-164A
The Airport Grumman G-164A · Accident: total loss of engine power (mechanical failure) during initial climb
From Gilbert, LA to an unrecorded destination
Event
- NTSB case
- FTW04CA246
- 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 G-164A
- 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
- N8661H
- Operator
- The Airport
- Onboard fatalities
- Unknown
- Route
- From Gilbert, LATo 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 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
- 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
- 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 › Failure
- Reason for occurrence undetermined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The 11,000-hour pilot reported that during an aerial application flight, the "engine began running rough." The pilot initiated a turn back toward the airport and "attempted to gain altitude." At an altitude of approximately 200 feet above ground level and approximately 1/2 mile from the runway when the engine "shuttered violently and quit." The pilot initiated a forced landing to a nearby pasture. The pilot stated that during the landing roll, the airplane impacted a wire fence, crossed two ditches, one road, impacted a second fence, crossed another pasture, and impacted a third fence before coming to rest upright in a plowed field. Examination of the radial engine revealed a piston connecting rod was separated the piston. The operator reported that at the time of the accident, the engine had accumulated 462 hours since major overhaul and 300 hours since the last annual inspection.
Probable cause
The failure of a piston connecting rod for undetermined reasons resulting in the loss of engine power. A contributing factor was the lack of suitable terrain for the forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW04CA246
- Event ID
- 20041013X01614
- Case number
- FTW04CA246
- 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, coordinates. 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: a49384152c215d68efc9a1d2956c57bce5308fb01e2d169ca8513967f5a4de92; retrieved 2026-09-22T06:40:32.368Z.