- Date
- June 20, 1970
- Place
- Casselton, ND · CASSELTON, ND
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Approach
- Aircraft
- N6265ZPiper PA-25
- Status
- Completed · report April 12, 1971
- Report
- Brief approved by the director
- Case key
- 119153
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-2620 70/6/20 NR.CASSELTON,N DAK PIPER PA-25 CR- 0 0 1 COMMERCIAL COMMERCIAL, AGE 48, 11900 TIME - 1800 N6265Z PX- 0 0 0 ASSOC CROP CTL ACTIVITY TOTAL HOURS, 752 IN TYPE, DAMAGE-SUBSTANTIAL OT- 0 0 0 NOT INSTRUMENT RATED. DEPARTURE POINT INTENDED DESTINATION CASSELTON,N DAK LOCAL TYPE OF ACCIDENT PHASE OF OPERATION COLLIDED WITH: WIRES/POLES LANDING: GO-AROUND PROBABLE CAUSE(S) PILOT IN COMMAND - EXERCISED POOR JUDGMENT PILOT IN COMMAND - SELECTED UNSUITABLE TERRAIN PILOT IN COMMAND - FAILED TO SEE AND AVOID OBJECTS OR OBSTRUCTIONS TERRAIN - HIGH OBSTRUCTIONS FACTOR(S) MISCELLANEOUS - EVASIVE MANEUVER TO AVOID COLLISION MISCELLANEOUS ACTS,CONDITIONS - SUNGLARE SPECIAL DATA TOTAL HOURS IN CROP CONTROL - 9999 KIND OF OPERATION - SPRAYING CROPS KIND OF CROP - GRAIN FIELDS TYPE OF CHEMICAL USED - LIQUID CHEMICAL-NONTOXIC PILOT' S SEAT BELT -FASTENED-PROPERLY GLOVES - NOT USED GOGGLES - NOT USED CRASH HELMET - AVAILABLE USED TANK/HOPPER-LOCATION - FORWARD OF PILOT REMARKS- USING PUBLIC RD FOR OPERATING BASE,NO FLAGMEN TO CHECK TRAFFIC.SAW TRUCK ON RD,ABORTED,HIT WIRES.
Aircraft
- Registration
- N6265Z
- 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.