SEA98LA140 · Grumman-Schweizer G-164A
Grumman-Schweizer G-164A · Accident: in flight collision with object while maneuvering
From Wilder, ID to an unrecorded destination
Event
- NTSB case
- SEA98LA140
- 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-Schweizer G-164A
- Aircraft type
- Grumman Schweizer 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
- N7951
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Wilder, IDTo 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
- In flight collision with object
- 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, transmission
- 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
- Pilot in command › Clearance, misjudged
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that while approaching a field for a spray run, he misjudged the height of a power line in the vicinity of the field and struck the line. The line was cut by the strike. The aircraft, while substantially damaged by the strike, was able to return to its home airstrip and land without further incident. The pilot reported that no mechanical malfunction or failure was involved in the accident. Dark night conditions existed in the accident area at the time.
Probable cause
The pilot-in-command's misjudgment of clearance with a power line, resulting in a collision with the line. Factors included a power line and dark night light conditions in the spray area.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA98LA140
- Event ID
- 20001211X10721
- Case number
- SEA98LA140
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1998-07-17.
- API snapshot SHA-256: 6a97890b9dbf0c296a160cd2b5cb3e8834db8b85d6046f21d34603f747297cc8; retrieved 2026-09-22T17:26:51.955Z.