UNK69X0113

NTSB accident investigation · Piper PA-28 · Rio Salado, Mexico · March 25, 1969

Accident · No injuriesClosed
Date
March 25, 1969
Place
Rio Salado, Mexico · RIO SALADO, Mexico
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Enroute
Aircraft
N4295JPiper PA-28
Status
Completed · report June 9, 1969
Report
Brief approved by the director
Case key
186014

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
----------------------------------------------------------------------------------------------------------------------------
6-0012  69/3/25    RIO SALADO,MEX      PIPER PA-28         CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 46, 1400
        TIME - 1050                    N4295J              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, ALL IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           ENGINE FAILURE OR MALFUNCTION                            IN FLIGHT: NORMAL CRUISE
           COLLIDED WITH: TREES                                     LANDING: ROLL
        PARTIAL POWER LOSS - PARTIAL LOSS OF POWER - 1 ENGINE
        EMERGENCY CIRCUMSTANCES - FORCED LANDING OFF AIRPORT ON LAND
        REMARKS- INVESTIGATION UNDER JURISDICTION OF GOVT OF MEX.

Aircraft

Registration
N4295J
Reported as
Piper PA-28
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.