FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX05LA165 · Grumman G-164C

8 May 2005 · Willows, CA, United States

Grumman G-164C · Accident: partial loss of engine power (mechanical failure) while maneuvering

From Willows, CA to an unrecorded destination

Report a problem

Event

NTSB case
LAX05LA165
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-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
N6535K
Operator
Unknown
Onboard fatalities
Unknown
Route
From Willows, CATo 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
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
Partial 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, piston › Fractured

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot force landed the airplane in a rice field following a loss of engine power and the main landing gear was sheared off after contacting a berm. While the pilot was seeding rice over a field, the engine lost partial power. The pilot force landed the airplane in a field. During the landing roll, the landing gear impacted a berm and were sheared from their structural attachment points on the airplane. Until the ground impact, the engine was producing partial power, but not enough to sustain flight. Post accident inspection of the engine by the Federal Aviation Administration accident coordinator revealed that the number 5 cylinder piston had fractured at the piston pin boss. The piston pin, which is mounted in the piston pin boss and holds the piston to the connecting rod, fell from the boss and the connecting rod was free to rotate. The engine was overhauled about 1,154 hours prior to the accident. The maintenance history on the piston could not be determined based on available records.

Probable cause

the loss of engine power due to the fractured piston pin boss on the number 5 cylinder.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX05LA165
Event ID
20050513X00612
Case number
LAX05LA165
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: f5aa6eea6794c3ce8613ad8acb6b00a3030df8d6928c59e2d67c382c6459a64b; retrieved 2026-09-22T05:57:34.087Z.