UNK65X1111

NTSB accident investigation · Mooney MC20 · Asheboro, NC · December 24, 1964

Accident · No injuriesClosed
Date
December 24, 1964
Place
Asheboro, NC · ASHEBORO, NC
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N1376WMooney MC20
Status
Completed · report January 27, 1965
Report
Brief approved by the director
Case key
180340

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-3764  64/12/24   ASHEBORO NC         MOONEY MC20         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 41, 1022
        TIME - 1140                    N1376W              PX-  0  0  0  BUSINESS                  TOTAL HOURS, 325 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - PUGH FIELD
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: ROLL
           COLLIDED WITH: TREES                                     LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
           PILOT IN COMMAND - DELAYED IN INITIATING GO-AROUND

Aircraft

Registration
N1376W
Reported as
Mooney MC20
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Pugh Field

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.