SEA69F0240

NTSB accident investigation · Piper PA-28 · Enumclaw, WA · April 21, 1969

Accident · No injuriesClosed
Date
April 21, 1969
Place
Enumclaw, WA · ENUMCLAW, WA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Takeoff
Aircraft
N4910JPiper PA-28
Status
Completed · report June 20, 1969
Report
Brief approved by the director
Case key
188797

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-1029  69/4/21    ENUMCLAW,WASH       PIPER PA-28         CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 32, 984
        TIME - 1015                    N4910J              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 10 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - ENUMCLAW
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 TAKEOFF: RUN
           COLLIDED WITH: FENCE,FENCEPOSTS                          TAKEOFF: INITIAL CLIMB
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL
           PILOT IN COMMAND - FAILED TO ABORT TAKEOFF

Aircraft

Registration
N4910J
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Enumclaw

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.