- Date
- September 11, 1969
- Place
- Hughes, AR · HUGHES, AR
- Injuries
- 1 fatal
- Damage
- Destroyed
- Phase of flight
- Maneuvering
- Aircraft
- N4538YPiper PA-25
- Status
- Completed · report May 6, 1970
- Report
- Brief approved by the director
- Case key
- 156211
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-3906 69/9/11 HUGHES,ARK PIPER PA-25 CR- 1 0 0 COMMERCIAL COMMERCIAL, AGE 50, 12000 TIME - 1600 N4538Y PX- 0 0 0 AERIAL APPLICATION TOTAL HOURS, 200 IN TYPE, DAMAGE-DESTROYED OT- 0 0 0 INSTRUMENT RATED. NAME OF AIRPORT - HUGHES DEPARTURE POINT INTENDED DESTINATION HUGHES,ARK LOCAL TYPE OF ACCIDENT PHASE OF OPERATION COLLIDED WITH: WIRES/POLES IN FLIGHT: SWATH RUN NOSE OVER/DOWN IN FLIGHT: SWATH RUN PROBABLE CAUSE(S) PILOT IN COMMAND - MISJUDGED CLEARANCE TERRAIN - HIGH OBSTRUCTIONS SPECIAL DATA TOTAL HOURS IN CROP CONTROL - UNKNOWN/NOT REPORTED 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 TANK/HOPPER-LOCATION - FORWARD OF PILOT TERRAIN-TYPE -ROLLING ELEVATION-AREA BEING TREATED-FEET - 210 SWATH RUN-HOW FLOWN - CROSSWIND REMARKS- TAILWHEEL CAUGHT TWO WIRES OF SECOND ROW OF WIRES.
Aircraft
- Registration
- N4538Y
- Reported as
- Piper PA-25
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
- Airport
- Hughes
N4538YRegistered now · Piper PA-25-235Airframe modelPiper PA-25-235Engine modelLycoming 0-540 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.