- Date
- May 8, 1971
- Place
- Lake Providnce, LA · LAKE PROVIDNCE, LA
- Injuries
- 1 minor
- Damage
- Substantial damage
- Phase of flight
- Maneuvering
- Aircraft
- N7082ZPiper PA-25
- Status
- Completed · report January 7, 1972
- Report
- Brief approved by the director
- Case key
- 161661
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-1531 71/5/8 LAKE PROVIDNCE,LA PIPER PA-25 CR- 0 0 1 COMMERCIAL COMMERCIAL, AGE 33, 5100 TIME - 1315 N7082Z PX- 0 0 0 AERIAL APPLICATION TOTAL HOURS, 1720 IN DAMAGE-SUBSTANTIAL OT- 0 0 0 TYPE, NOT INSTRUMENT RATED. DEPARTURE POINT INTENDED DESTINATION LAKE PROVIDNCE,LA LOCAL TYPE OF ACCIDENT PHASE OF OPERATION COLLIDED WITH: WIRES/POLES IN FLIGHT: SWATH RUN PROBABLE CAUSE(S) PILOT IN COMMAND - EXERCISED POOR JUDGMENT PILOT IN COMMAND - FAILED TO SEE AND AVOID OBJECTS OR OBSTRUCTIONS FACTOR(S) TERRAIN - HIGH OBSTRUCTIONS SPECIAL DATA TOTAL HOURS IN CROP CONTROL - 3500 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-NOT USED COCKPIT CRASHPAD - INSTALLED CRASH BAR - INSTALLED TANK/HOPPER-LOCATION - FORWARD OF PILOT TERRAIN-TYPE -LEVEL,FLAT ELEVATION-AREA BEING TREATED-FEET - 75 SWATH RUN-HOW FLOWN - WIND CALM REMARKS- HAD NOT TREATED AREA IN RECENT YEARS,NOT MADE PRE-APPLICATION SURVEY.
Aircraft
- Registration
- N7082Z
- Reported as
- Piper PA-25
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Substantial damage
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.