- Date
- April 15, 1966
- Place
- Exeter, CA · EXETER, CA
- Injuries
- 1 uninjured
- Damage
- Destroyed
- Phase of flight
- Enroute
- Aircraft
- N67870Boeing A75
- Status
- Completed · report June 3, 1966
- Report
- Brief approved by the director
- Case key
- 172661
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-0837 66/4/15 NR.EXETER CALIF BOEING A75 CR- 0 0 1 COMMERCIAL COMMERCIAL, FL.INSTR., TIME - 0700 N67870 PX- 0 0 0 ASSOC CROP CTL ACTIVITY AGE 26, 2300 TOTAL HOURS, DAMAGE-DESTROYED OT- 0 0 0 750 IN TYPE, NOT INSTRUMENT RATED. TYPE OF ACCIDENT PHASE OF OPERATION ENGINE FAILURE OR MALFUNCTION IN FLIGHT: EN ROUTE TO RELOADING AREA GEAR COLLAPSED LANDING: ROLL PROBABLE CAUSE(S) MISCELLANEOUS ACTS,CONDITIONS - FUEL EXHAUSTION PILOT IN COMMAND - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING FACTOR(S) MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE COMPLETE POWER LOSS - COMPLETE ENGINE FAILURE/FLAMEOUT-1 ENGINE EMERGENCY CIRCUMSTANCES - FORCED LANDING OFF AIRPORT ON LAND SPECIAL DATA TOTAL HOURS IN CROP CONTROL - 1000 KIND OF OPERATION - DUSTING CROPS KIND OF CROP - GRAPES TYPE OF CHEMICAL USED - DRY CHEMICAL-NONTOXIC PILOT' S SEAT BELT -FASTENED-PROPERLY GLOVES - NOT USED GOGGLES - USED CRASH HELMET - AVAILABLE USED COCKPIT CRASHPAD - NOT INSTALLED CRASH BAR - INSTALLED TANK/HOPPER-LOCATION - FORWARD OF PILOT TERRAIN-TYPE -LEVEL,FLAT ELEVATION-AREA BEING TREATED-FEET - 320
Aircraft
- Registration
- N67870
- Reported as
- Boeing A75
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
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.