UNK65X1272

NTSB accident investigation · Piper PA22 · Defiance, OH · January 11, 1965

Accident · No injuriesClosed
Date
January 11, 1965
Place
Defiance, OH · DEFIANCE, OH
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N5950ZPiper PA22
Status
Completed · report February 17, 1965
Report
Brief approved by the director
Case key
179955

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-0050  65/1/11    DEFIANCE OHIO       PIPER PA22          CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 21, 29 TOTAL
        TIME - 1710                    N5950Z              PX-  0  0  0  SOLO                      HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - DEFIANCE OHIO
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: ROLL
           COLLIDED WITH: DITCHES                                   LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - DOWNWIND

Aircraft

Registration
N5950Z
Reported as
Piper PA22
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Defiance Ohio

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.