SEA69D0128

NTSB accident investigation · Piper PA-28 · Spanaway, WA · September 24, 1968

Accident · No injuriesClosed
Date
September 24, 1968
Place
Spanaway, WA · SPANAWAY, WA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N9265WPiper PA-28
Status
Completed · report January 6, 1969
Report
Brief approved by the director
Case key
107439

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-3922  68/9/24    SPANAWAY,WASH       PIPER PA-28         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 53, 2300
        TIME - 1930                    N9265W              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 700 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - SHADY ACRES
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           UNDERSHOOT                                               LANDING: FINAL APPROACH
           COLLIDED WITH: OBJECT                                    LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND ALTITUDE
        REMARKS- STRUCK LOG USED TO KEEP CARS OFF STRIP.

Aircraft

Registration
N9265W
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Shady Acres

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.