- Date
- August 22, 1964
- Place
- Tipton, CA · TIPTON, CA
- Injuries
- 1 minor
- Damage
- Substantial damage
- Phase of flight
- Maneuvering
- Aircraft
- N58986Boeing E75
- Status
- Completed · report November 2, 1964
- Report
- Brief approved by the director
- Case key
- 181871
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-2585 64/8/22 TIPTON CALIF BOEING E75 CR- 0 0 1 COMMERCIAL COMMERCIAL, FL.INSTR., TIME - 0800 N58986 PX- 0 0 0 AERIAL APPLICATION AGE 45, 13000 TOTAL DAMAGE-SUBSTANTIAL OT- 0 0 0 HOURS, 7000 IN TYPE, NOT INSTRUMENT RATED. TYPE OF ACCIDENT PHASE OF OPERATION ENGINE FAILURE OR MALFUNCTION IN FLIGHT: SWATH RUN NOSE OVER/DOWN LANDING: ROLL PROBABLE CAUSE(S) PILOT IN COMMAND - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING MISCELLANEOUS ACTS,CONDITIONS - FUEL EXHAUSTION COMPLETE POWER LOSS - COMPLETE ENGINE FAILURE/FLAMEOUT-1 ENGINE EMERGENCY CIRCUMSTANCES - FORCED LANDING OFF AIRPORT ON LAND SPECIAL DATA TOTAL HOURS IN CROP CONTROL - 7000 KIND OF OPERATION - DUSTING CROPS KIND OF CROP - COTTON TYPE OF CHEMICAL USED - DRY CHEMICAL-NONTOXIC PILOT' S SEAT BELT -FASTENED-PROPERLY GLOVES - USED GOGGLES - USED CRASH HELMET - NOT AVAILABLE COCKPIT CRASHPAD - NOT INSTALLED CRASH BAR - NOT INSTALLED TANK/HOPPER-LOCATION - FORWARD OF PILOT TERRAIN-TYPE -LEVEL,FLAT ELEVATION-AREA BEING TREATED-FEET - 200 SWATH RUN-HOW FLOWN - WIND CALM
Aircraft
- Registration
- N58986
- Reported as
- Boeing E75
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
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.