MIA97LA146 · Grumman G-164B
Grumman G-164B · Accident: partial loss of engine power (non-mechanical) en route
From Ackerman Choctaw County Airport (9M4) to an unrecorded destination
Event
- NTSB case
- MIA97LA146
- 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
- 0
- 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
- N6601Q
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Ackerman Choctaw County Airport (9M4), MSTo 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
- En route · climb to cruise
- 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 (non-mechanical)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Fuel contamination; Tree(s)
- 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
- Airport facilities, fuel storage › Inadequate
- Fluid, fuel › Contamination, water
- Maintenance, installation › Improper
- Maintenance, service of aircraft/equipment › Inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated he was in the initial climb after takeoff, at about 400 feet, when he experienced a partial loss of engine power. He was forced to land in an area with trees, and subsequently, the airplane was damaged. Examination of the airplane fuel system revealed water contamination. Examination of the refueling source (fuel tanker trailer/auger truck), revealed contaminated fuel (water). This was the result of an improper fuel filter being installed in the tanker trailer, which had been provided by the fuel filter supplier.
Probable cause
installation of an incorrect fuel filter in the fuel tanker, which allowed water-contaminated fuel being dispensed into the aircraft, subsequent partial loss of engine power on initial takeoff climb, and a forced landing. The lack of suitable terrain for a forced landing was a related factor.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA97LA146
- Event ID
- 20001208X07797
- Case number
- MIA97LA146
- 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. 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: d918aeeeaa7b9b39da1b21a00c3a7f5cc89c21ae4fe194c97e3b2b5f12c191e3; retrieved 2026-09-22T19:55:19.035Z.