SEA72AS039

NTSB accident investigation · Piper PA-23 · Salem, OR · March 14, 1972

Accident · FatalClosed
Date
March 14, 1972
Place
Salem, OR · SALEM, OR
Injuries
1 fatal
Damage
Destroyed
Phase of flight
Uncontrolled descent
Aircraft
N5600YPiper PA-23
Status
Completed · report September 14, 1972
Report
Brief approved by the director
Case key
165367

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-0109  72/3/14    SALEM,OREG          PIPER PA-23         CR-  1  0  0  NONCOMMERCIAL             PRIVATE, AGE 46, 1276
        TIME - 1410                    N5600Y              PX-  0  0  0  BUSINESS                  TOTAL HOURS, 661 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            INSTRUMENT RATED.
        DEPARTURE POINT             INTENDED DESTINATION
          PORTLAND,OREG               GRANTS PASS,OREG
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLISION WITH GROUND/WATER: UNCONTROLLED                IN FLIGHT: UNCONTROLLED DESCENT
        PROBABLE CAUSE(S)
           MISCELLANEOUS - UNDETERMINED
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - SEPARATION IN FLIGHT
         FIRE AFTER IMPACT
        REMARKS- WING TIPS SEPD PRIOR TO IMPACT.

Aircraft

Registration
N5600Y
Reported as
Piper PA-23
Category
Airplane
Engine
reciprocating
Damage
Destroyed

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.