SEA68D0083

NTSB accident investigation · Cessna 172 · Vashon Is., WA · July 29, 1967

Accident · No injuriesClosed
Date
July 29, 1967
Place
Vashon Is., WA · VASHON IS., WA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N4618LCessna 172
Status
Completed · report December 8, 1967
Report
Brief approved by the director
Case key
115357

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-3236  67/7/29    VASHON IS.,WASH     CESSNA 172          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 38, 413
        TIME - 1915                    N4618L              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 401 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - VASHON
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: LEVEL OFF/TOUCHDOWN
           COLLIDED WITH: DITCHES                                   LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
           PILOT IN COMMAND - FAILED TO INITIATE GO-AROUND

Aircraft

Registration
N4618L
Reported as
Cessna 172
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Vashon

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.