CHI66F0096

NTSB accident investigation · Mooney M20B · Dunkirk, IN · July 25, 1965

Accident · No injuriesClosed
Date
July 25, 1965
Place
Dunkirk, IN · DUNKIRK, IN
Injuries
4 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N74582Mooney M20B
Status
Completed · report September 9, 1965
Report
Brief approved by the director
Case key
176968

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-1969  65/7/25    DUNKIRK IND         MOONEY M20B         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 40, 1150
        TIME - 1355                    N74582              PX-  0  0  3  BUSINESS                  TOTAL HOURS, 22 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - LUDWIG LAND CORP
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           GEAR COLLAPSED                                           LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER LEVEL OFF
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N74582
Reported as
Mooney M20B
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Ludwig Land Corp

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.