FTW66D0109

NTSB accident investigation · Mooney M20C · Arlington, TX · June 22, 1965

Accident · No injuriesClosed
Date
June 22, 1965
Place
Arlington, TX · ARLINGTON, TX
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N6897UMooney M20C
Status
Completed · report August 17, 1965
Report
Brief approved by the director
Case key
177503

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-1614  65/6/22    ARLINGTON TEX       MOONEY M20C         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 42, 2000
        TIME - 1130                    N6897U              PX-  0  0  1  BUSINESS                  TOTAL HOURS, 900 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - ARLINGTON
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           WHEELS-UP                                                LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO EXTEND LANDING GEAR
        FACTOR(S)
           AIRFRAME - LANDING GEAR: LANDING GEAR WARNING AND INDICATING COMPONENTS
        REMARKS- GEAR WARNING HORN INOPERATIVE

Aircraft

Registration
N6897U
Reported as
Mooney M20C
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Arlington

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.