LAX68A0092

NTSB accident investigation · Mooney M20E · Borego Sprngs, CA · March 24, 1968

Accident · FatalClosed
Date
March 24, 1968
Place
Borego Sprngs, CA · BOREGO SPRNGS, CA
Injuries
3 fatal
Damage
Destroyed
Phase of flight
Initial climb
Aircraft
N3387XMooney M20E
Status
Completed · report May 6, 1968
Report
Brief approved by the director
Case key
111072

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-0695  68/3/24    BOREGO SPRNGS,CAL   MOONEY M20E         CR-  1  0  0  NONCOMMERCIAL             PRIVATE, AGE 40, 500
        TIME - 2059                    N3387X              PX-  2  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 31 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - BORREGO SPRINGS
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLISION WITH GROUND/WATER: UNCONTROLLED                TAKEOFF: INITIAL CLIMB
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - ATTEMPTED OPERATION BEYOND EXPERIENCE/ABILITY LEVEL
           PILOT IN COMMAND - SPATIAL DISORIENTATION
        REMARKS- NON-INST RATED PLT.ATTEMPTED FLT ON DARK NITE,HAD NO VISIBLE HORIZON.

Aircraft

Registration
N3387X
Reported as
Mooney M20E
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Borrego Springs

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.