- Date
- March 27, 1972
- Place
- Watsonville, CA · WATSONVILLE, CA
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Maneuvering
- Aircraft
- N3961BBoeing E75N1
- Status
- Completed · report October 10, 1972
- Report
- Brief approved by the director
- Case key
- 165911
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-0380 72/3/27 WATSONVILLE,CALIF BOEING E75N1 CR- 0 0 1 COMMERCIAL COMMERCIAL, AGE 44, 12400 TIME - 0900 N3961B PX- 0 0 0 AERIAL APPLICATION TOTAL HOURS, 9000 IN DAMAGE-SUBSTANTIAL OT- 0 0 0 TYPE, INSTRUMENT RATED. NAME OF AIRPORT - WATSONVILLE DEPARTURE POINT INTENDED DESTINATION WATSONVILLE,CALIF LOCAL TYPE OF ACCIDENT PHASE OF OPERATION COLLIDED WITH: WIRES/POLES IN FLIGHT: STARTING SWATH RUN PROBABLE CAUSE(S) PILOT IN COMMAND - FAILED TO SEE AND AVOID OBJECTS OR OBSTRUCTIONS FACTOR(S) MISCELLANEOUS ACTS,CONDITIONS - SUNGLARE SPECIAL DATA TOTAL HOURS IN CROP CONTROL - 8000 KIND OF OPERATION - SPRAYING CROPS KIND OF CROP - STRAWBERRIES TYPE OF CHEMICAL USED - LIQUID CHEMICAL-TOXIC PILOT' S SEAT BELT -UNKNOWN/NOT REPORTED GLOVES - USED GOGGLES - USED CRASH HELMET - AVAILABLE USED COCKPIT CRASHPAD - INSTALLED CRASH BAR - NOT INSTALLED TANK/HOPPER-LOCATION - FORWARD OF PILOT TERRAIN-TYPE -MOUNTAINOUS ELEVATION-AREA BEING TREATED-FEET - 300 SWATH RUN-HOW FLOWN - WIND CALM REMARKS- HIT PWR LINES
Aircraft
- Registration
- N3961B
- Reported as
- Boeing E75N1
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Watsonville
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.