LAX66D0267

NTSB accident investigation · Mooney M20E · Las Vegas, NV · January 26, 1966

Accident · No injuriesClosed
Date
January 26, 1966
Place
Las Vegas, NV · LAS VEGAS, NV
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N5928QMooney M20E
Status
Completed · report May 17, 1966
Report
Brief approved by the director
Case key
173233

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-0689  66/1/26    LAS VEGAS NEV       MOONEY M20E         CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 56, 43 TOTAL
        TIME - 1100                    N5928Q              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - LAS VEGAS AIR TRM
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER OPERATION OF BRAKES AND/OR FLIGHT CONTROLS
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N5928Q
Reported as
Mooney M20E
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Las Vegas Air Trm

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.