ANC66D0043

NTSB accident investigation · Piper PA-22 · Fairbanks, AK · September 25, 1965

Accident · Minor injuriesClosed
Date
September 25, 1965
Place
Fairbanks, AK · FAIRBANKS, AK
Injuries
1 minor
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N9167DPiper PA-22
Status
Completed · report October 27, 1965
Report
Brief approved by the director
Case key
175557

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-2692  65/9/25    FAIRBANKS ALAS      PIPER PA-22         CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, FL.INSTR.,
        TIME - 0920                    N9167D              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  AGE 54, 3300 TOTAL HOURS,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            1100 IN TYPE, NOT
                                                                                                   INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           UNDERSHOOT                                               LANDING: FINAL APPROACH
           NOSE OVER/DOWN                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND ALTITUDE

Aircraft

Registration
N9167D
Reported as
Piper PA-22
Category
Airplane
Engine
reciprocating
Damage
Substantial damage

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.