SEA68F0231

NTSB accident investigation · Piper PA-28 · Salem, OR · September 3, 1967

Accident · No injuriesClosed
Date
September 3, 1967
Place
Salem, OR · SALEM, OR
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N6049WPiper PA-28
Status
Completed · report February 7, 1968
Report
Brief approved by the director
Case key
113994

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-4354   67/9/3    SALEM,OREG          PIPER PA-28         CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 32, 100
        TIME - 1420                    N6049W              PX-  0  0  0  TRAINING                  TOTAL HOURS, ALL IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - MCNARY
        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
N6049W
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Mcnary

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.