- Date
- September 10, 1967
- Place
- Silver City, MS · SILVER CITY, MS
- Injuries
- 1 uninjured
- Damage
- Destroyed
- Phase of flight
- Maneuvering
- Aircraft
- N6717ZPiper PA-25
- Status
- Completed · report December 6, 1967
- Report
- Brief approved by the director
- Case key
- 114268
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-3307 67/9/10 NR.SILVER CITY,MISS PIPER PA-25 CR- 0 0 1 COMMERCIAL COMMERCIAL, AGE 27, 1020 TIME - 1530 N6717Z PX- 0 0 0 AERIAL APPLICATION TOTAL HOURS, 285 IN TYPE, DAMAGE-DESTROYED OT- 0 0 0 NOT INSTRUMENT RATED. NAME OF AIRPORT - BELZONI TYPE OF ACCIDENT PHASE OF OPERATION COLLISION WITH GROUND/WATER: CONTROLLED IN FLIGHT: FLAREOUT FOR SWATH RUN PROBABLE CAUSE(S) PILOT IN COMMAND - MISJUDGED SPEED AND ALTITUDE SPECIAL DATA TOTAL HOURS IN CROP CONTROL - 721 KIND OF OPERATION - SPRAYING CROPS KIND OF CROP - BEANS TYPE OF CHEMICAL USED - LIQUID CHEMICAL-TOXIC PILOT' S SEAT BELT -UNKNOWN/NOT REPORTED GLOVES - NOT USED GOGGLES - NOT USED CRASH HELMET - AVAILABLE USED COCKPIT CRASHPAD - INSTALLED CRASH BAR - INSTALLED TANK/HOPPER-LOCATION - FORWARD OF PILOT TERRAIN-TYPE -LEVEL,FLAT ELEVATION-AREA BEING TREATED-FEET - 110 SWATH RUN-HOW FLOWN - UPWIND REMARKS- PLT OPERATING CLOSE TO CROP,NO MARGIN FOR ERROR.
Aircraft
- Registration
- N6717Z
- Reported as
- Piper PA-25
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
- Airport
- Belzoni
N6717ZRegistered 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.