NYC66F0030

NTSB accident investigation · Mooney M20 · Milford, DE · May 30, 1965

Accident · No injuriesClosed
Date
May 30, 1965
Place
Milford, DE · MILFORD, DE
Injuries
4 uninjured
Damage
Substantial damage
Phase of flight
Takeoff
Aircraft
N5283BMooney M20
Status
Completed · report July 30, 1965
Report
Brief approved by the director
Case key
177928

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-1350  65/5/30    MILFORD DEL         MOONEY M20          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 39, 280
        TIME - 1930                    N5283B              PX-  0  0  3  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 100 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - MILFORD
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 TAKEOFF: RUN
           GEAR COLLAPSED                                           TAKEOFF: RUN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED
           PILOT IN COMMAND - FAILED TO ABORT TAKEOFF
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N5283B
Reported as
Mooney M20
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Milford

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.