FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR09LA227 · Grumman G-164B

4 May 2009 · Colfax, WA, United States

Grumman G-164B · Accident: loss of engine power (total) during takeoff

From Port of Whitman Business Air Center Airport (S94) to Port of Whitman Business Air Center Airport (S94)

Report a problem

Event

NTSB case
WPR09LA227
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-164B

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
N6628Q
Operator
Darrell L Fender · private individual
Onboard fatalities
Unknown
Route
From Port of Whitman Business Air Center Airport (S94), Colfax, WATo Port of Whitman Business Air Center Airport (S94), Colfax, WA
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
Takeoff
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 pilot stated that the airplane was about 100 feet above ground level following takeoff when the engine lost power. He landed straight ahead in a muddy dirt field. During the landing roll, the airplane nosed over and the engine separated from the airframe. Postaccident examination of the engine core revealed no anomalies that would have precluded normal operation. Examination of the carburetor revealed that the bushings on the throttle shaft and pump stem were worn, which allowed excessive play. The economizer linkage was also found to be loose; there was evidence of fretting on the mating surface to the engine and around the mounting bolt holes. The carburetor fuel screen was clean. The floats exhibited hydraulic crush damage consistent with fuel in the bowl, and the accelerator pump was worn. Based on the findings of the postaccident examination, excessive wear of the carburetor likely led to the loss of engine power.

Probable cause

A total loss of engine power due to excessive wear in several carburetor components that led to a malfunction of the carburetor.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR09LA227
Event ID
20090504X02231
Case number
WPR09LA227
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: 1070d448f6d1eef81110a689d22bc4fb62e0c3476a32e08a05f025b779bbc1ac; retrieved 2026-09-15T11:00:47.001Z.