- Date
- June 5, 1979
- Place
- Norborne, MO · NORBORNE, MO
- Injuries
- 1 serious
- Damage
- Destroyed
- Phase of flight
- Maneuvering
- Aircraft
- N6942KGrumman G-164B
- Status
- Completed · report July 10, 1979
- Report
- Brief approved by the director
- FAA report
- 19790605011839A
- Case key
- 136208
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
NTSB brief
NTSB’s brief of the accident, as it was printed: the coded facts, with the probable cause and factors.
---------------------------------------------------------------------------------------------------------------------------- FILE DATE LOCATION AIRCRAFT DATA INJURIES FLIGHT PILOT DATA F S M/N PURPOSE ---------------------------------------------------------------------------------------------------------------------------- 3-1117 79/6/5 NORBORNE,MO GRUMMAN G-164B CR- 0 1 0 COMMERCIAL COMMERCIAL, AGE 42, 4150 TIME - 0830 N6942K PX- 0 0 0 AERIAL APPLICATION TOTAL HOURS, 545 IN TYPE, DAMAGE-DESTROYED OT- 0 0 0 INSTRUMENT RATED. DEPARTURE POINT INTENDED DESTINATION NORBORNE,MO LOCAL TYPE OF ACCIDENT PHASE OF OPERATION COLLIDED WITH: WIRES/POLES IN FLIGHT: SWATH RUN PROBABLE CAUSE(S) PILOT IN COMMAND - FAILED TO SEE AND AVOID OBJECTS OR OBSTRUCTIONS SPECIAL DATA TOTAL HOURS IN CROP CONTROL - 545 KIND OF OPERATION - SPRAYING CROPS KIND OF CROP - BEANS TYPE OF CHEMICAL USED - LIQUID CHEMICAL-TOXIC PILOT' S SEAT BELT -FASTENED-PROPERLY GLOVES - NOT USED GOGGLES - NOT USED CRASH HELMET - AVAILABLE USED COCKPIT CRASHPAD - INSTALLED CRASH BAR - INSTALLED TANK/HOPPER-LOCATION - FORWARD OF PILOT TERRAIN-TYPE -ROLLING ELEVATION-AREA BEING TREATED-FEET - 700 SWATH RUN-HOW FLOWN - WIND CALM FIRE AFTER IMPACT REMARKS- COLLIDED WITH WIRES
Aircraft
- Registration
- N6942K
- Reported as
- Grumman G-164B
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
N6942KRegistration cancelled Aug 3, 1979 · Grumman Acft ENG Cor-Schweizer G-164BAirframe modelGrumman Acft ENG Cor-Schweizer G-164B
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.