FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA18CA383 · Grumman Acft ENG COR-Schweizer G 164 B

27 Jun 2018 · Malin, OR, United States

Macy's Flying Service Grumman Acft ENG COR-Schweizer G 164 B · Accident: aerodynamic stall/spin while maneuvering

From Tulelake Municipal Airport (O81) to Tulelake Municipal Airport (O81)

Report a problem

Event

NTSB case
GAA18CA383
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 Acft ENG COR-Schweizer G 164 B

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
N151QC
Onboard fatalities
Unknown
Route
From Tulelake Municipal Airport (O81), Tulelake, CATo Tulelake Municipal Airport (O81), Tulelake, CA
Aircraft age
About 40 years (built 1978)
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
Aerodynamic stall/spin
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
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Psychological
  • Personnel issues › Task performance

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 reported that, during an agricultural application flight, he misjudged the approach and did not have enough clearance to avoid power lines. The airplane began to sink, and he pulled back on the flight control stick. Subsequently, the airplane aerodynamically stalled and then struck power lines.

The airplane sustained substantial damage to the fuselage, empennage, and both wings.

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 misjudgment of the approach and his subsequent exceedance of the airplane’s critical angle of attack during an agricultural application flight, which resulted in an aerodynamic stall and collision with power lines.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA18CA383
Event ID
20180627X21629
Case number
GAA18CA383
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, 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: 221916c3ef460106f0ea690d0b8aa30b297a76d6159b9d44910ae639154fd18c; retrieved 2026-09-16T07:41:12.674Z.