- Date
- August 25, 1966
- Place
- Sylvester, GA · SYLVESTER, GA
- Injuries
- 1 serious
- Damage
- Destroyed
- Phase of flight
- Maneuvering
- Aircraft
- N7683ZPiper PA-25
- Status
- Completed · report December 12, 1966
- Report
- Brief approved by the director
- Case key
- 122488
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-0749 66/8/25 SYLVESTER GA PIPER PA-25 CR- 0 1 0 COMMERCIAL COMMERCIAL, AGE 37, 6000 TIME - 1645 N7683Z PX- 0 0 0 AERIAL APPLICATION TOTAL HOURS, 5000 IN DAMAGE-DESTROYED OT- 0 0 0 TYPE, NOT INSTRUMENT RATED. NAME OF AIRPORT - SYLVESTER-CROWE TYPE OF ACCIDENT PHASE OF OPERATION COLLIDED WITH: TREES IN FLIGHT: PULLUP FROM SWATH RUN PROBABLE CAUSE(S) PILOT IN COMMAND - MISJUDGED CLEARANCE SPECIAL DATA TOTAL HOURS IN CROP CONTROL - 5000 KIND OF OPERATION - DEFOLIATION (LIQUID) KIND OF CROP - COTTON TYPE OF CHEMICAL USED - LIQUID CHEMICAL-TOXIC PILOT' S SEAT BELT -FASTENED-PROPERLY GLOVES - NOT USED GOGGLES - USED CRASH HELMET - AVAILABLE USED COCKPIT CRASHPAD - NOT INSTALLED CRASH BAR - INSTALLED TANK/HOPPER-LOCATION - FORWARD OF PILOT TERRAIN-TYPE -LEVEL,FLAT ELEVATION-AREA BEING TREATED-FEET - 400 SWATH RUN-HOW FLOWN - UNKNOWN/NOT REPORTED PROCEDURE TURNAROUND - ENTRY TO PROCEDURE TURN FIRE AFTER IMPACT
Aircraft
- Registration
- N7683Z
- Reported as
- Piper PA-25
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
- Airport
- Sylvester-Crowe
N7683ZRegistration cancelled Nov 21, 2017 · 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.