- Date
- October 8, 1964
- Place
- Socorro, NM · SOCORRO, NM
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Enroute
- Aircraft
- N9271DPiper PA18A
- Status
- Completed · report November 20, 1964
- Report
- Brief approved by the director
- Case key
- 181441
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-3169 64/10/8 SOCORRO N MEX PIPER PA18A CR- 0 0 1 COMMERCIAL COMMERCIAL, AGE 46, 8600 TIME - 0830 N9271D PX- 0 0 0 ASSOC CROP CTL ACTIVITY TOTAL HOURS, 3000 IN DAMAGE-SUBSTANTIAL OT- 0 0 0 TYPE, INSTRUMENT RATED. TYPE OF ACCIDENT PHASE OF OPERATION ENGINE FAILURE OR MALFUNCTION IN FLIGHT: EN ROUTE TO TREAT CROP COLLIDED WITH: DITCHES LANDING: ROLL PROBABLE CAUSE(S) PILOT IN COMMAND - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING MISCELLANEOUS ACTS,CONDITIONS - WATER IN FUEL COMPLETE POWER LOSS - COMPLETE ENGINE FAILURE/FLAMEOUT-1 ENGINE EMERGENCY CIRCUMSTANCES - FORCED LANDING OFF AIRPORT ON LAND SPECIAL DATA TOTAL HOURS IN CROP CONTROL - UNKNOWN/NOT REPORTED KIND OF OPERATION - SPRAYING CROPS KIND OF CROP - COTTON TYPE OF CHEMICAL USED - UNKNOWN/NOT REPORTED PILOT' S SEAT BELT -FASTENED-PROPERLY CRASH HELMET - NOT AVAILABLE COCKPIT CRASHPAD - NOT INSTALLED CRASH BAR - NOT INSTALLED TANK/HOPPER-LOCATION - UNKNOWN/NOT REPORTED ELEVATION-AREA BEING TREATED-FEET - 4500 REMARKS- AIRCRAFT FUELED FROM 55 GALLON DRUM
Aircraft
- Registration
- N9271D
- Reported as
- Piper PA18A
- 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.