SEA66D0113

NTSB accident investigation · Piper PA-28 · Aurora, OR · August 6, 1965

Accident · No injuriesClosed
Date
August 6, 1965
Place
Aurora, OR · AURORA, OR
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N5805WPiper PA-28
Status
Completed · report October 19, 1965
Report
Brief approved by the director
Case key
176702

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-2543   65/8/6    AURORA OREG         PIPER PA-28         CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 40, 117
        TIME - 1730                    N5805W              PX-  0  0  0  PRACTICE                  TOTAL HOURS, 25 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - SHERMAN
        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
N5805W
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Sherman

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.