SEA68F0251

NTSB accident investigation · Cessna 150 · Anacortes, WA · February 4, 1968

Accident · No injuriesClosed
Date
February 4, 1968
Place
Anacortes, WA · ANACORTES, WA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N6035TCessna 150
Status
Completed · report October 8, 1968
Report
Brief approved by the director
Case key
111531

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-2535   68/2/4    ANACORTES,WASH      CESSNA 150          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 29, 78 TOTAL
        TIME - 1530                    N6035T              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  HOURS, 63 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - SKYLINE
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL: MUSH                                              LANDING: GO-AROUND
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED
           PILOT IN COMMAND - DELAYED IN INITIATING GO-AROUND
        FACTOR(S)
           TERRAIN - HIGH OBSTRUCTIONS
        REMARKS- DRAGGED FLD INTO RISING TERRAIN.

Aircraft

Registration
N6035T
Reported as
Cessna 150
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Skyline

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.