FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR09LA373 · Grumman G164 A

28 Jul 2009 · Riverdale, CA, United States

Kennys Crop Dusting Grumman G164 A · Accident: powerplant system/component malfunction/failure while maneuvering

From Rasin City, CA to Riverdale, CA

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
WPR09LA373
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
N8741H
Onboard fatalities
Unknown
Route Narrative disagrees
From Rasin City, CATo Riverdale, CA
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 · low-altitude flying
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
Powerplant system/component malfunction/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

  • Aircraft › Aircraft power plant

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

NTSB narrative

During a spray pass the pilot detected a "hot smell," which prompted him to pull up out of the field to check his engine gauges. As everything appeared normal the pilot returned to the field to continue spraying operations. Upon re-entering the field the pilot reported that "…the engine changed sound." After pulling up out of the field a second time the pilot revealed that the engine began to slow down, followed by the emission of smoke from the exhaust system. The pilot made a successful forced landing in the field he was spraying; however, due to the wet field conditions it nosed over on its back, which resulted in substantial damage to the airplane. A post accident teardown examination revealed that the engine had failed as a result of a supercharger-blower failure. It also revealed that foreign object material was detected in the engine; however, it could not be determined if this was causal to the engine failure. The manufacturer recommends an overhaul time of between 600 to 1,000 hours for engines operated in aerial application operations. At the time of the accident the engine had accumulated a total of 835.27 hours since its most recent major overhaul.

Probable cause

The partial loss of engine power due to the failure of the engine's supercharger-blower.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR09LA373
Event ID
20090728X85335
Case number
WPR09LA373
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: 5b1fcbc94dc08a26ac1939b04894d2432c4e3f66737867a01265fd4fc6ecbc03; retrieved 2026-09-15T12:03:18.966Z.