SEA67D0070

NTSB accident investigation · Luscombe 8E · Puyallup, WA · July 10, 1966

Accident · No injuriesClosed
Date
July 10, 1966
Place
Puyallup, WA · PUYALLUP, WA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N2282KLuscombe 8E
Status
Completed · report December 30, 1966
Report
Brief approved by the director
Case key
122862

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-3222  66/7/10    PUYALLUP WASH       LUSCOMBE 8E         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 32, 182
        TIME - 1100                    N2282K              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 71 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT 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 RECOVERY FROM BOUNCED LANDING
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N2282K
Reported as
Luscombe 8E
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.