- Date
- May 19, 1979
- Place
- Gaylord, MN · GAYLORD, MN
- Injuries
- 1 fatal
- Damage
- Destroyed
- Phase of flight
- Maneuvering
- Aircraft
- N70152Piper PA-25
- Status
- Completed · report July 30, 1979
- Report
- Brief approved by the director
- Case key
- 135837
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-1656 79/5/19 GAYLORD,MN PIPER PA-25 CR- 1 0 0 COMMERCIAL COMMERCIAL, AGE 24, 522 TIME - 0630 N70152 PX- 0 0 0 AERIAL APPLICATION TOTAL HOURS, 37 IN TYPE, DAMAGE-DESTROYED OT- 0 0 0 NOT INSTRUMENT RATED. DEPARTURE POINT INTENDED DESTINATION GAYLORD,MN LOCAL TYPE OF ACCIDENT PHASE OF OPERATION COLLIDED WITH: TREES IN FLIGHT: PULLUP FROM SWATH RUN PROBABLE CAUSE(S) PILOT IN COMMAND - MISJUDGED CLEARANCE FACTOR(S) TERRAIN - HIGH OBSTRUCTIONS SPECIAL DATA TOTAL HOURS IN CROP CONTROL - 65 KIND OF OPERATION - FERTILIZING (LIQUID) KIND OF CROP - CORN TYPE OF CHEMICAL USED - LIQUID CHEMICAL-TOXIC PILOT' S SEAT BELT -FASTENED-PROPERLY GLOVES - 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 - 1060 SWATH RUN-HOW FLOWN - UNKNOWN/NOT REPORTED FIRE AFTER IMPACT
Aircraft
- Registration
- N70152
- Reported as
- Piper PA-25
- Category
- Airplane
- Engine
- reciprocating
- Damage
- Destroyed
N70152Registration cancelled Sep 16, 2013 · Piper J3C-65Airframe modelPiper J3C-65Engine modelContinental A&C65 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.