OAK67D0097

NTSB accident investigation · Piper PA-28 · Mulege, Mexico · October 1, 1966

Accident · No injuriesClosed
Date
October 1, 1966
Place
Mulege, Mexico · MULEGE,BAJA, Mexico
Injuries
4 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N9283JPiper PA-28
Status
Completed · report November 16, 1966
Report
Brief approved by the director
Case key
120538

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-0071   66/10/1   MULEGE,BAJA MEX     PIPER PA-28         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 23, 85 TOTAL
        TIME - 1530                    N9283J              PX-  0  0  3  PLEASURE/PERSONAL TRANSP  HOURS, 35 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - SERENIDAD
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: OBJECT                                    LANDING: ROLL
        EMERGENCY CIRCUMSTANCES - PRECAUTIONARY LANDING ON AIRPORT
                                  SUSPECTED OR KNOWN AIRCRAFT DAMAGE
        REMARKS- INVESTIGATION UNDER THE JURISDICTION OF THE GOVERNMENT OF MEXICO.

Aircraft

Registration
N9283J
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Serenidad

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.