SEA71DWD11

NTSB accident investigation · Cessna 172 · Federal Way, WA · August 23, 1970

Accident · Serious injuriesClosed
Date
August 23, 1970
Place
Federal Way, WA · FEDERAL WAY, WA
Injuries
2 serious
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N6449BCessna 172
Status
Completed · report June 10, 1971
Report
Brief approved by the director
Case key
191033

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-3392  70/8/23    FEDERAL WAY,WASH    CESSNA 172          CR-  0  1  0  NONCOMMERCIAL             PRIVATE, AGE 25, 82 TOTAL
        TIME - 1830                    N6449B              PX-  0  1  0  PLEASURE/PERSONAL TRANSP  HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - EVERGREEN ARPT
        DEPARTURE POINT             INTENDED DESTINATION
          ROACH HARBOR,WASH           FEDERAL WAY,WASH
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: TREES                                     LANDING: GO-AROUND
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
           PILOT IN COMMAND - DELAYED IN INITIATING GO-AROUND

Aircraft

Registration
N6449B
Reported as
Cessna 172
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Evergreen Arpt

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.