UNK65X1266

NTSB accident investigation · Piper PA22 · Yadinville, NC · January 10, 1965

Accident · No injuriesClosed
Date
January 10, 1965
Place
Yadinville, NC · YADINVILLE, NC
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N3760PPiper PA22
Status
Completed · report February 17, 1965
Report
Brief approved by the director
Case key
179953

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-0048  65/1/10    YADINVILLE NC       PIPER PA22          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 37, 167
        TIME - 1400                    N3760P              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 5 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - YADKINVILLE
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: ROLL
           NOSE OVER/DOWN                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - DOWNWIND

Aircraft

Registration
N3760P
Reported as
Piper PA22
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Yadkinville

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.