- Date
- July 21, 1964
- Place
- El Campo, TX · EL CAMPO, TX
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Enroute
- Aircraft
- N63916Boeing A75
- Status
- Completed · report October 30, 1964
- Report
- Brief approved by the director
- Case key
- 182772
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-2169 64/7/21 EL CAMPO TEX BOEING A75 CR- 0 0 1 COMMERCIAL COMMERCIAL, AGE 42, 6500 TIME - 1115 N63916 PX- 0 0 0 ASSOC CROP CTL ACTIVITY TOTAL HOURS, 5000 IN DAMAGE-SUBSTANTIAL OT- 0 0 0 TYPE, NOT INSTRUMENT RATED. TYPE OF ACCIDENT PHASE OF OPERATION ENGINE FAILURE OR MALFUNCTION IN FLIGHT: EN ROUTE TO TREAT CROP NOSE OVER/DOWN LANDING: ROLL PROBABLE CAUSE(S) POWERPLANT - FUEL SYSTEM: FILTERS,STRAINERS,SCREENS MISCELLANEOUS ACTS,CONDITIONS - MATERIAL FAILURE FACTOR(S) TERRAIN - WET,SOFT GROUND PARTIAL POWER LOSS - PARTIAL LOSS OF POWER - 1 ENGINE EMERGENCY CIRCUMSTANCES - FORCED LANDING OFF AIRPORT ON LAND SPECIAL DATA TOTAL HOURS IN CROP CONTROL - 5000 KIND OF OPERATION - FERTILIZING (DUST) KIND OF CROP - RICE TYPE OF CHEMICAL USED - LIQUID CHEMICAL-NONTOXIC PILOT' S SEAT BELT -FASTENED-PROPERLY GLOVES - NOT USED GOGGLES - NOT USED CRASH HELMET - AVAILABLE-NOT USED COCKPIT CRASHPAD - NOT INSTALLED CRASH BAR - NOT INSTALLED TANK/HOPPER-LOCATION - FORWARD OF PILOT REMARKS- CARBURETOR AIR FILTER RETAINING STUD FAILED.
Aircraft
- Registration
- N63916
- Reported as
- Boeing A75
- 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.