SEA67D0302

NTSB accident investigation · Cessna 170B · Puyallup, WA · March 21, 1967

Accident · No injuriesClosed
Date
March 21, 1967
Place
Puyallup, WA · PUYALLUP, WA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N3509CCessna 170B
Status
Completed · report August 28, 1967
Report
Brief approved by the director
Case key
117962

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-0928  67/3/21    PUYALLUP, WASH      CESSNA 170B         CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 30, 17 TOTAL
        TIME - 1430                    N3509C              PX-  0  0  0  TRAINING                  HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - THUN FIELD
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           GEAR COLLAPSED                                           LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER LEVEL OFF
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N3509C
Reported as
Cessna 170B
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Thun Field

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.