FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA19CA277 · Grumman G164 B

21 May 2019 · Pearsall, TX, United States

Grumman G164 B · Accident: loss of control in flight while maneuvering

From Mc Kinley Field (T30) to Mc Kinley Field (T30)

Report a problem

Event

NTSB case
GAA19CA277
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
N7500K
Operator
Fitch, Matt Dba · private individual
Onboard fatalities
Unknown
Route
From Mc Kinley Field (T30), Pearsall, TXTo Mc Kinley Field (T30), Pearsall, TX
Aircraft age
About 33 years (built 1986)
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 · low-altitude flying
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 in flight
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
Wire
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 oper/perf/capability
  • Environmental issues › Physical environment
  • Personnel issues › Psychological

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

NTSB narrative

The pilot reported that, while conducting an agricultural application flight, he thought the airplane was above some power lines, but the landing gear got tangled in the top line, and the airplane was pulled downward. The pilot attempted to correct by pulling "hard on the stick and pushed the power forward," and the airplane became airborne, but the left wing was pulled downward again. The pilot attempted to lift the wing by using right rudder and was able to maintain flight. The airplane was again pulled downward until it impacted the ground. The airplane was destroyed by postaccident fire. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.

Probable cause

The pilot's failure to maintain clearance from power lines during low-altitude maneuvering.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA19CA277
Event ID
20190522X55614
Case number
GAA19CA277
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: 38034592740d999d12b773cda7e5f0237ab85b11313c013055fab710284deb4e; retrieved 2026-09-16T09:02:29.058Z.