SEA67D0117

NTSB accident investigation · Piper PA-22 · Vancouver, WA · July 4, 1966

Accident · No injuriesClosed
Date
July 4, 1966
Place
Vancouver, WA · VANCOUVER, WA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N4507APiper PA-22
Status
Completed · report January 26, 1967
Report
Brief approved by the director
Case key
122262

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-3472   66/7/4    VANCOUVER WASH      PIPER PA-22         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 53, 106
        TIME - 1630                    N4507A              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 88 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - PEARSON AIRPARK
        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
N4507A
Reported as
Piper PA-22
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Pearson Airpark

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.