- Date
- July 13, 1970
- Place
- Pitts, GA · PITTS, GA
- Injuries
- 1 fatal
- Damage
- Destroyed
- Phase of flight
- Maneuvering
- Aircraft
- N4356YPiper PA-25
- Status
- Completed · report May 17, 1971
- Report
- Brief approved by the director
- Case key
- 108469
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-2991 70/7/13 PITTS,GA PIPER PA-25 CR- 1 0 0 COMMERCIAL COMMERCIAL, AGE 22, 550 TIME - 1447 N4356Y PX- 0 0 0 AERIAL APPLICATION TOTAL HOURS, 200 IN TYPE, DAMAGE-DESTROYED OT- 0 0 0 NOT INSTRUMENT RATED. DEPARTURE POINT INTENDED DESTINATION PITTS,GA LOCAL TYPE OF ACCIDENT PHASE OF OPERATION STALL IN FLIGHT: PROCEDURE TURNAROUND PROBABLE CAUSE(S) PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED MISCELLANEOUS - EVASIVE MANEUVER TO AVOID COLLISION SPECIAL DATA TOTAL HOURS IN CROP CONTROL - 300 KIND OF OPERATION - SPRAYING CROPS KIND OF CROP - OTHER 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 - 325 SWATH RUN-HOW FLOWN - CROSSWIND PROCEDURE TURNAROUND - THIRD 1/3 TURN FIRE AFTER IMPACT REMARKS- PLT APPARENTLY SAW OTR AG ACFT APCHG,PULLED UP,ENTERED L WING OVER,CONTD TURN HIT GRND NOSE DOWN.
Aircraft
- Registration
- N4356Y
- Reported as
- Piper PA-25
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
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.