DEN68F0043

NTSB accident investigation · Piper PA-22 · Albuquerque, NM · July 8, 1967

Accident · No injuriesClosed
Date
July 8, 1967
Place
Albuquerque, NM · ALBUQUERQUE, NM
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N1603PPiper PA-22
Status
Completed · report October 10, 1967
Report
Brief approved by the director
Case key
115432

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-2295   67/7/8    ALBUQUERQUE,N MEX   PIPER PA-22         CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 32, 11 TOTAL
        TIME - 1120                    N1603P              PX-  0  0  0  SOLO                      HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - SANDIA BASE
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: LEVEL OFF/TOUCHDOWN
           COLLIDED WITH: DITCHES                                   LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
           PILOT IN COMMAND - FAILED TO INITIATE GO-AROUND

Aircraft

Registration
N1603P
Reported as
Piper PA-22
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Sandia Base

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.