CEN22FA215 · Grumman American AVN. Corp G-164 B
Hackberry Flying Service Grumman American AVN. Corp G-164 B · Accident: loss of control on ground during landing
From Beech Grove, AR to an unrecorded destination
Event
- NTSB case
- CEN22FA215
- 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
- 1 · 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 American AVN. Corp G-164 B
- Aircraft type
- Grumman American 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
- N178LB
- Operator
- Hackberry Flying Service
- Onboard fatalities
- Unknown
- Route
- From Beech Grove, ARTo not recorded
- Aircraft age
- About 45 years (built 1977)
- 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
- Landing
- 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 control on ground
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Aircraft › Aircraft systems
- Environmental issues › Physical environment
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot departed in the aerial application airplane to apply dry chemical to a rice field. Shortly after takeoff, the operator who was training the pilot heard the pilot announce over the company radio frequency that, “I’ve got to land this airplane.” There were no further radio transmissions from the pilot. A postimpact fire ensued and the wreckage was destroyed. Shortly after, the wreckage was discovered upright next to ditch. Due to the absence of any flight track data, the airplane’s flight path, altitude, and airspeed were unknown for the accident flight. Postaccident examination of the airframe and the engine revealed no mechanical anomalies that would have precluded normal operation. The pilot did not extricate herself from the airplane and died from inhaling products of combustion, which also caused an elevated carboxyhemoglobin level. There is no evidence to suggest the pilot was exposed to significant levels of carbon monoxide before the accident. Two sedating medications were found in the pilot’s blood postmortem, diphenhydramine, an antihistamine, and zolpidem, a sleep aid. The postmortem level of diphenhydramine for this pilot was 79 ng/ml in central blood; dividing by 3 to account for postmortem redistribution places the likely antemortem level just at or above the level where any effects might be expected. In addition, she had safely flown the airplane on a flight earlier that day. Therefore, it is unlikely any effects from the pilot’s use of diphenhydramine contributed to the accident circumstances. In this case, the pilot’s very low postmortem level of 3 ng/ml of zolpidem is unlikely to have caused any effects or contributed to the accident circumstances. Finally, the detected but not quantified quinine in heart blood most likely indicates the pilot drank some tonic water at some point in the night or hours before the accident, but it is unlikely that any effects from her use contributed to the accident circumstances. Overall, it is unlikely that any effects from the identified substances contributed to the accident circumstances. The airplane’s fuel system ruptured during the accident sequence and a fire ensued, consuming the airplane. The airplane was not equipped with, nor was it required to be equipped with, a crash-resistant fuel system. According to sources, a postimpact fire presents a significant risk of fire-related injuries to airplane occupants, and crash-resistant fuel systems reduce the risk of postimpact fire and can provide occupants with more time to escape or be rescued. The pilot’s last radio transmission indicated that she likely intended to land the airplane; however, it could not be determined what the reason was for her wanting to land the airplane. There was no evidence that the pilot performed an emergency hopper dump procedure. Based on the available evidence, it is likely the pilot was attempting to perform an emergency landing to a rice field, but because of the full chemical load, she misjudged the approach to landing and impacted a ditch immediately after touchdown, which resulted in the substantial damage to the airplane and postimpact fire.
Probable cause
The pilot misjudged the approach during the emergency landing, likely due to the full chemical load, and impacted a ditch, resulting in substantial damage and postimpact fire. Contributing to the pilot’s injuries was the lack of a crash-resistant fuel system in the airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN22FA215
- Event ID
- 20220528105142
- Case number
- CEN22FA215
- 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, cause areas. 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: 34848a47d09a6054200f4e93e47596910a6ea6452bbc0ce1eda79a8860307e47; retrieved 2026-09-15T07:44:59.899Z.