DIA68F0072

NTSB accident investigation · Mooney M20E · Friendship Int., MD · August 28, 1967

Accident · No injuriesClosed
Date
August 28, 1967
Place
Friendship Int., MD · FRIENDSHIP INT., MD
Injuries
4 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N9348MMooney M20E
Status
Completed · report November 21, 1967
Report
Brief approved by the director
Case key
114108

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-3013  67/8/28    FRIENDSHIP INT.MD   MOONEY M20E         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 50, 748
        TIME - 1818                    N9348M              PX-  0  0  3  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 419 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - FRIENDSHIP
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           WHEELS-UP                                                LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO ASSURE THE GEAR WAS DOWN AND LOCKED
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - CHECKLIST-FAILED TO USE

Aircraft

Registration
N9348M
Reported as
Mooney M20E
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Friendship

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.