DEN93LA051 · Grumman G-164A
Worthington Flying Service Grumman G-164A · Accident: partial loss of engine power (non-mechanical) while maneuvering
Event
- NTSB case
- DEN93LA051
- 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-164A
- 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
- N31182
- Operator
- Worthington Flying Service
- Onboard fatalities
- Unknown
- Route
- From not recordedTo 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 (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
- 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
- Destroyed
Cause areas
- Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT WAS FLUSHING THE HOPPER WITH WATER. HE MADE A PASS OVER A FIELD WITH THE SPRAY BOOM OFF. AS HE PULLED UP TO CLEAR A WIRE, HE SWITCHED THE SPRAY BOOM ON. HE INITIATED A DESCENT INTO AN ADJOINING FIELD AND AS HE STARTED THE ROUNDOUT, THE AIRPLANE CONTINUED DESCENDING. HE ADDED FULL POWER BUT THE ENGINE DID NOT RESPOND. THE AIRPLANE TOUCHED DOWN ON THE GROUND, THEN LIFTED OFF. THE PILOT HAD INSUFFICIENT ALTITUDE TO CLEAR A KNOLL AT THE END OF THE FIELD, SO HE PULLED THE NOSE UP AND THE AIRPLANE COLLIDED WITH TREES. THREE GROUND WITNESSES REPORTED HEARING A BANG, AN EXPLOSION, OR BACKFIRE. THEN ENGINE WAS LATER FUNCTIONALLY TESTED AND IT OPERATED SATISFACTORILY.
Probable cause
A POWER LOSS FOR UNDETERMINED REASONS. A FACTOR WAS: THE LACK OF SUITABLE TERRAIN FOR THE FORCED LANDING.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN93LA051
- Event ID
- 20001211X12123
- Case number
- DEN93LA051
- 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: bcda97c3047d1a648d7419e30081e45fdf824ce638baedbefab704abdfad67a2; retrieved 2026-09-23T02:09:26.427Z.