ANC67A0004

NTSB accident investigation · Piper PA-22 · Fairbanks, AK · July 11, 1966

Accident · FatalClosed
Date
July 11, 1966
Place
Fairbanks, AK · FAIRBANKS, AK
Injuries
2 fatal, 1 serious
Damage
Destroyed
Phase of flight
Approach
Aircraft
N2913ZPiper PA-22
Status
Completed · report February 13, 1967
Report
Brief approved by the director
Case key
171125

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
----------------------------------------------------------------------------------------------------------------------------
2-0595  66/7/11    FAIRBANKS ALAS      PIPER PA-22         CR-  1  0  0  NONCOMMERCIAL             PRIVATE, AGE 43, 3000
        TIME - 1800                    N2913Z              PX-  1  1  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, UNK/NR IN
                                       DAMAGE-DESTROYED    OT-  0  0  0                            TYPE, NOT INSTRUMENT
                                                                                                   RATED.
        NAME OF AIRPORT - PHILLIPS
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL: SPIRAL                                            LANDING: TRAFFIC PATTERN-CIRCLING
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED
        REMARKS- SURVIVOR DOES NOT RECALL ACCIDENT CIRCUMSTANCES.

Aircraft

Registration
N2913Z
Reported as
Piper PA-22
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Phillips

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.