- Date
- May 22, 1966
- Place
- Taft, TX · TAFT, TX
- Injuries
- 1 serious
- Damage
- Substantial damage
- Phase of flight
- Maneuvering
- Aircraft
- N9390DPiper PA-18
- Status
- Completed · report August 24, 1966
- Report
- Brief approved by the director
- Case key
- 172384
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 ---------------------------------------------------------------------------------------------------------------------------- 2-0246 66/5/22 TAFT TEX PIPER PA-18 CR- 0 1 0 COMMERCIAL COMMERCIAL, FL.INSTR., TIME - 0745 N9390D PX- 0 0 0 AERIAL APPLICATION AGE 55, 11080 TOTAL DAMAGE-SUBSTANTIAL OT- 0 0 0 HOURS, 4000 IN TYPE, NOT INSTRUMENT RATED. NAME OF AIRPORT - WORSHAM TYPE OF ACCIDENT PHASE OF OPERATION STALL: SPIN IN FLIGHT: SURVEY FIELD/AREA PROBABLE CAUSE(S) PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED FACTOR(S) PILOT IN COMMAND - DIVERTED ATTENTION FROM OPERATION OF AIRCRAFT SPECIAL DATA TOTAL HOURS IN CROP CONTROL - 8000 KIND OF OPERATION - SPRAYING CROPS KIND OF CROP - COTTON TYPE OF CHEMICAL USED - LIQUID CHEMICAL-TOXIC 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 - BELLY TERRAIN-TYPE -LEVEL,FLAT ELEVATION-AREA BEING TREATED-FEET - 54 SWATH RUN-HOW FLOWN - DOWNWIND
Aircraft
- Registration
- N9390D
- Reported as
- Piper PA-18
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
- Airport
- Worsham
N9390DRegistered now · Piper PA-18-150Airframe modelPiper PA-18-150Engine modelLycoming 0-320 series
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.