DEN66D0068

NTSB accident investigation · Piper PA-22 · Shiprock, NM · August 3, 1965

Accident · No injuriesClosed
Date
August 3, 1965
Place
Shiprock, NM · SHIPROCK, NM
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N3233BPiper PA-22
Status
Completed · report September 9, 1965
Report
Brief approved by the director
Case key
177009

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-2013   65/8/3    SHIPROCK N MEX      PIPER PA-22         CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 33, 20 TOTAL
        TIME - 1730                    N3233B              PX-  0  0  0  PRACTICE                  HOURS, 18 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - SHIPROCK
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           COLLIDED WITH: FENCE,FENCEPOSTS                          LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER LEVEL OFF
           PILOT IN COMMAND - IMPROPER RECOVERY FROM BOUNCED LANDING

Aircraft

Registration
N3233B
Reported as
Piper PA-22
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Shiprock

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.