SEA79DUK03

NTSB accident investigation · Piper PA-28 · Riley, OR · June 16, 1979

Accident · No injuriesClosed
Date
June 16, 1979
Place
Riley, OR · RILEY, OR
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N1716JPiper PA-28
Status
Completed · report December 19, 1979
Report
Brief approved by the director
FAA report
19790616031699A
Case key
135535

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-2631  79/6/16    RILEY,OR            PIPER PA-28         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 30, 373
        TIME - 1600                    N1716J              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 237 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        DEPARTURE POINT             INTENDED DESTINATION
          CHICO,CA                    SPOKANE,WA
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: FENCE,FENCEPOSTS                          LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED CLEARANCE
        FACTOR(S)
           TERRAIN - OTHER
        REMARKS- LNDD ON GRASS FLD,R WG HIT FENCEPOSTS.

Aircraft

Registration
N1716J
Reported as
Piper PA-28
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.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.