- Date
- June 3, 1970
- Place
- Cascade, MT · CASCADE, MT
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Maneuvering
- Aircraft
- N4884APiper PA-18
- Status
- Completed · report March 17, 1971
- Report
- Brief approved by the director
- Case key
- 123644
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-2319 70/6/3 NR.CASCADE,MONT PIPER PA-18 CR- 0 0 1 COMMERCIAL COMMERCIAL, AGE 40, 5351 TIME - 0805 N4884A PX- 0 0 0 AERIAL APPLICATION TOTAL HOURS, UNK/NR IN DAMAGE-SUBSTANTIAL OT- 0 0 0 TYPE, INSTRUMENT RATED. DEPARTURE POINT INTENDED DESTINATION GREAT FALLS,MONT CASCADE,MONT TYPE OF ACCIDENT PHASE OF OPERATION COLLIDED WITH: WIRES/POLES IN FLIGHT: PULLUP FROM SWATH RUN PROBABLE CAUSE(S) PILOT IN COMMAND - FAILED TO SEE AND AVOID OBJECTS OR OBSTRUCTIONS FACTOR(S) TERRAIN - HIGH OBSTRUCTIONS SPECIAL DATA TOTAL HOURS IN CROP CONTROL - UNKNOWN/NOT REPORTED KIND OF OPERATION - SPRAYING FORESTS KIND OF CROP - MOSQUITO CONTROL TYPE OF CHEMICAL USED - LIQUID CHEMICAL-TOXIC PILOT' S SEAT BELT -FASTENED-PROPERLY GLOVES - NOT USED GOGGLES - NOT USED CRASH HELMET - AVAILABLE USED COCKPIT CRASHPAD - NOT INSTALLED CRASH BAR - NOT INSTALLED TANK/HOPPER-LOCATION - FORWARD OF PILOT TERRAIN-TYPE -HILLY ELEVATION-AREA BEING TREATED-FEET - 3396 SWATH RUN-HOW FLOWN - WIND CALM REMARKS- AFTER WIRE STRIKE,LANDED SAFELY GREAT FALLS ARPT
Aircraft
- Registration
- N4884A
- Reported as
- Piper PA-18
- 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.