DIA68F0011

NTSB accident investigation · Mooney M20E · Greensboro, NC · June 5, 1967

Accident · No injuriesClosed
Date
June 5, 1967
Place
Greensboro, NC · GREENSBORO, NC
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N5976QMooney M20E
Status
Completed · report September 22, 1967
Report
Brief approved by the director
Case key
116668

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-1905   67/6/5    GREENSBORO,NC       MOONEY M20E         CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 29, 600
        TIME - 1404                    N5976Q              PX-  0  0  2  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 85 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - GREENSBORO
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           UNDERSHOOT                                               LANDING: LEVEL OFF/TOUCHDOWN
           GEAR COLLAPSED                                           LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND ALTITUDE
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N5976Q
Reported as
Mooney M20E
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Greensboro

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.