FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR24LA282 · Grumman Acft ENG COR-Schweizer G-164B

13 Aug 2024 · Durham, CA, United States

Grumman Acft ENG COR-Schweizer G-164B · Accident: low altitude operation/event while maneuvering

Report a problem

Event

NTSB case
WPR24LA282
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
Event fatalities
Unknown
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-164B

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
N6633K
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
About 46 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
Low altitude operation/event
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

  • Environmental issues › Physical environment
  • Personnel issues › Psychological

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

According to the operator, the pilot was flying near high tension powerline wires during an aerial application flight. During the application of a rice field while flying north, the airplane’s right wing struck one of the powerlines. The airplane subsequently impacted the ground north of the powerline wires and sustained substantial damage to all four wings the empennage and the fuselage. The pilot exited the airplane, called the operator and reported that the accident was caused by pilot error. The Investigator-in-charge made several attempts to contact the pilot in command (PIC) via email and cell phone, but an email reply was not received from the PIC and the voicemail box was full. The pilot reported there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.

Probable cause

The pilot’s failure to maintain clearance from powerlines, which resulted in a wire strike.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR24LA282
Event ID
20240820194957
Case number
WPR24LA282
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, 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: 56b63f8c2630ce9a925603fd35968d7b2eb558807a757c3d75d195336c978445; retrieved 2026-09-16T19:11:04.692Z.