LAX68D0346

NTSB accident investigation · Mooney M20D · Riverside, CA · March 11, 1968

Accident · No injuriesClosed
Date
March 11, 1968
Place
Riverside, CA · RIVERSIDE, CA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N6791UMooney M20D
Status
Completed · report April 23, 1968
Report
Brief approved by the director
Case key
118606

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-0599  68/3/11    RIVERSIDE,CALIF     MOONEY M20D         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 18, 80 TOTAL
        TIME - 1523                    N6791U              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  HOURS, 10 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - RIVERSIDE
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: LEVEL OFF/TOUCHDOWN
           COLLIDED WITH: DITCHES                                   LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
           PILOT IN COMMAND - FAILED TO INITIATE GO-AROUND

Aircraft

Registration
N6791U
Reported as
Mooney M20D
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Riverside

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.