UNK64X3296

NTSB accident investigation · Piper PA18 · Anchorage, AK · August 9, 1964

Accident · No injuriesClosed
Date
August 9, 1964
Place
Anchorage, AK · ANCHORAGE, AK
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N7579KPiper PA18
Status
Completed · report October 22, 1964
Report
Brief approved by the director
Case key
182378

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-2410   64/8/9  NR.ANCHORAGE ALAS     PIPER PA18          CR-  0  0  1  MISCELLANEOUS             COMMERCIAL, AGE 50, 1100
        TIME - 0730                    N7579K              PX-  0  0  1  HUNTING                   TOTAL HOURS, 150 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: OBJECT                                    LANDING: ROLL
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - SELECTED UNSUITABLE TERRAIN
        FACTOR(S)
           TERRAIN - ROUGH/UNEVEN
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE
        REMARKS- AIRCRAFT COLLIDED WITH ROCKS.

Aircraft

Registration
N7579K
Reported as
Piper PA18
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.