SEA66D0187

NTSB accident investigation · Piper PA-22 · Eugene, OR · December 11, 1965

Accident · No injuriesClosed
Date
December 11, 1965
Place
Eugene, OR · EUGENE, OR
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N6956DPiper PA-22
Status
Completed · report February 8, 1966
Report
Brief approved by the director
Case key
174259

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-3703  65/12/11   EUGENE OREG         PIPER PA-22         CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 42, 146
        TIME - 0930                    N6956D              PX-  0  0  0  BUSINESS                  TOTAL HOURS, ALL IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GEAR COLLAPSED                                           LANDING: ROLL
           NOSE OVER/DOWN                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - SELECTED UNSUITABLE TERRAIN
           TERRAIN - WET,SOFT GROUND
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE
        REMARKS- OFF AIRPORT OPERATION

Aircraft

Registration
N6956D
Reported as
Piper PA-22
Category
Airplane
Engine
reciprocating
Damage
Substantial damage

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.