SEA80DYE16

NTSB accident investigation · Cessna 172 · Spanaway, WA · February 10, 1980

Accident · No injuriesClosed
Date
February 10, 1980
Place
Spanaway, WA · SPANAWAY, WA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Taxi
Aircraft
N64266Cessna 172
Status
Completed · report March 6, 1980
Report
Brief approved by the director
FAA report
19800210002589A
Case key
132169

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-0017  80/2/10    SPANAWAY,WA         CESSNA 172          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 46, 226
        TIME - 1430                    N64266              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 104 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - SHADY ACRES
        DEPARTURE POINT             INTENDED DESTINATION
          SPANAWAY,WA                 BELLEVUE,WA
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: FENCE,FENCEPOSTS                          TAXI: TO TAKEOFF
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED CLEARANCE
        REMARKS- WING TIP STRUCK FENCE POST.

Aircraft

Registration
N64266
Reported as
Cessna 172
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.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.