FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN20CA341 · Grumman G164 B

16 Aug 2020 · Rice, MN, United States

Grumman G164 B · Accident: loss of control on ground during landing

From Rice, MN (private airstrip) to Rice, MN (private airstrip)

Report a problem

Event

NTSB case
CEN20CA341
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 G164 B

Aircraft type
Grumman G164
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
N997QC
Operator
Unknown
Onboard fatalities
Unknown
Route
From Rice, MN (private airstrip)To Rice, MN (private airstrip)
Aircraft age
About 41 years (built 1979)
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
Substantial

Cause areas

  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot was en route to spray a field when he received a call over the company radio to return to the airport. He returned for landing with the full application load. The airstrip consisted of gravel and asphalt; grass areas bordered the runway. The main wheels touched down near the runway threshold; the initial portion of the runway was gravel. The tail wheel settled onto the runway as the airspeed dissipated, and the pilot brought the propeller into reverse. However, the tailwheel encountered a “bump” which started some pitch oscillations; this might have occurred at the transition from gravel to asphalt. The pilot reported no elevator or rudder authority, possibly due to the reduced airflow over the empennage resulting from the reverse thrust. He noted that a go-around was not an option at that point. The airplane yawed to the right and departed the paved area, proceeded into the grass area, and finally into the soft ground adjacent to the runway causing the airplane to nose over. The pilot stated that there were no mechanical anomalies with the airplane that would have precluded normal operations.

Probable cause

The pilot did not maintain control of the airplane during the landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN20CA341
Event ID
20200816X62854
Case number
CEN20CA341
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: 5a9be344c2ce55b6a52b9cc26a25c1b8e88307d8e7339fd072c76d22ec2c92ef; retrieved 2026-09-16T12:38:58.441Z.