- Date
- September 3, 1980
- Place
- Lemoore, CA · LEMOORE, CA
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Enroute
- Aircraft
- N5632XSnow 600S2R
- Status
- Completed · report October 7, 1980
- Report
- Brief approved by the director
- FAA report
- 19800903064009A
- Case key
- 128794
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-2142 80/9/3 NR.LEMOORE,CA SNOW 600S2R CR- 0 0 1 COMMERCIAL COMMERCIAL, FL.INSTR., TIME - 2120 N5632X PX- 0 0 0 ASSOC CROP CTL ACTIVITY AGE 42, 8368 TOTAL HOURS, DAMAGE-SUBSTANTIAL OT- 0 0 0 330 IN TYPE, INSTRUMENT RATED. NAME OF AIRPORT - BOSTON RANCH DEPARTURE POINT INTENDED DESTINATION LEMOORE,CA LOCAL TYPE OF ACCIDENT PHASE OF OPERATION COLLIDED WITH: TREES IN FLIGHT: EN ROUTE TO TREAT CROP PROBABLE CAUSE(S) PILOT IN COMMAND - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING PILOT IN COMMAND - MISJUDGED ALTITUDE SPECIAL DATA TOTAL HOURS IN CROP CONTROL - 2000 KIND OF OPERATION - SPRAYING CROPS KIND OF CROP - COTTON TYPE OF CHEMICAL USED - LIQUID CHEMICAL-TOXIC PILOT' S SEAT BELT -FASTENED-PROPERLY GLOVES - USED GOGGLES - NOT USED CRASH HELMET - AVAILABLE USED COCKPIT CRASHPAD - INSTALLED CRASH BAR - INSTALLED TANK/HOPPER-LOCATION - FORWARD OF PILOT TERRAIN-TYPE -LEVEL,FLAT ELEVATION-AREA BEING TREATED-FEET - 250 REMARKS- WITNESSES RPRTD-PLT UNFAMILIAR W AREA.
Aircraft
- Registration
- N5632X
- Reported as
- Snow 600S2R
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Boston Ranch
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.