ATL07CA018 · Grumman G-164B
Grumman G-164B · Accident: total loss of engine power (non-mechanical) en route
From Pine Hill Municipal Airport (71A) to an unrecorded destination
Event
- NTSB case
- ATL07CA018
- 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
- N962QC
- Operator
- Robert D. Merrill · private individual
- Onboard fatalities
- Unknown
- Route
- From Pine Hill Municipal Airport (71A), Pine Hill, ALTo 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 · 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
- Total 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 exhaustion
- 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
- Pilot in command › Fuel management, improper
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 stated that he completed five aerial application sorties before returning for fuel and fertilizer. The fuel and fertilizer was added to the airplane, and the pilot assumed the airplane had been topped off with fuel. The pilot did not visually check the fuel tanks. The airplane holds 82 gallons of fuel of which 2 gallons are unusable. The airplane burns 44 gallons of fuel per hour and it burns 15 gallons of fuel while at flight idle when the airplane is being loaded with fuel or fertilizer. The pilot stated that he was not sure how much fuel the airplane uses for taxi, takeoff, and climb to his cruise altitude. The pilot departed and flew five additional sorties before returning 1 hour 27 minutes later. The airplane remained at flight idle while fertilizer was loaded onto the airplane and no fuel was added. The pilot departed, climbed to 700 feet, and was in cruise flight when the engine lost power. The pilot turned to the left and made a forced landing to a field where trees had been harvested. The landing gear collided with the tree stumps on landing roll out, separated the landing gear, and the airframe received structural damage. Examination of the airplane by recovery personnel revealed that the fuel tank was not ruptured and no fuel was present in the fuel tank. No fuel spill was observed nor was there a presence of the smell of fuel at the crash site. The fuel line from the fuel tank to the airframe filters was severed. The main fuel line from the airframe filters was removed from the main engine fuel pump inlet fitting and residual fuel was present. The opposite end of the fuel line was removed from the exit side of the airframe filters and no fuel was present. The main fuel line to the engine was disconnected and no fuel was present. The fuel line from the inlet side of the airframe filters was disconnected and no fuel was present. The engine assembly was transported to an authorized repair facility. The engine assembly was installed in a test cell. The engine started in 22 seconds on the first attempt. The engine vibrated which was attributed to a suspected bent propeller shaft. All ground idle operations were normal. The fuel control unit and propeller governor were damaged. When power was applied, the fuel control unit and propeller governor would not govern the engine rpm. The engine was shut down, started three additional times, and ran for about 30 minutes.
Probable cause
The pilot's improper fuel management resulting in a total loss of engine power in cruise flight due to fuel exhaustion, subsequent forced landing to non suitable terrain, and an on-ground collision with tree stumps on the landing roll out.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL07CA018
- Event ID
- 20061207X01751
- Case number
- ATL07CA018
- 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: 388852c0bbe7f45845f496461efb50d537b34ac9ac1d4d079444938b7f87e69a; retrieved 2026-09-22T04:14:54.269Z.