LAX70DUJ08

NTSB accident investigation · Piper PA-32 · Pima, AZ · February 2, 1970

Accident · No injuriesClosed
Date
February 2, 1970
Place
Pima, AZ · PIMA, AZ
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N4293RPiper PA-32
Status
Completed · report August 10, 1970
Report
Brief approved by the director
Case key
144018

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-0648   70/2/2    PIMA,ARIZ           PIPER PA-32         CR-  0  0  1  MISCELLANEOUS             PRIVATE, AGE 33, 300
        TIME - 1800                    N4293R              PX-  0  0  1  UNKNOWN/NOT REPORTED      TOTAL HOURS, 30 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - SKYLINE RANCH
        DEPARTURE POINT             INTENDED DESTINATION
          PIMA,ARIZ                  UNKNOWN/NOT REPORTED
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           MISCELLANEOUS - UNDETERMINED
        REMARKS- PLT DID NOT SUBMIT ACCIDENT REPORT,SUBSEQUENTLY INVOLVED IN FATAL ACFT ACDNT ON 3/13/70.

Aircraft

Registration
N4293R
Reported as
Piper PA-32
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Skyline Ranch

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.