ANC67D0036

NTSB accident investigation · Piper PA-20 · Dillingham, AK · June 27, 1966

Accident · No injuriesClosed
Date
June 27, 1966
Place
Dillingham, AK · DILLINGHAM, AK
Injuries
6 uninjured
Damage
Substantial damage
Phase of flight
Takeoff
Aircraft
N7625KPiper PA-20
Status
Completed · report December 30, 1966
Report
Brief approved by the director
Case key
122855

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-3205  66/6/27    DILLINGHAM ALAS     PIPER PA-20         CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 27, 700
        TIME - 0830                    N7625K              PX-  0  0  5  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 30 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: OBJECT                                    TAKEOFF: RUN
           GEAR COLLAPSED                                           TAKEOFF: RUN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - SELECTED UNSUITABLE TERRAIN
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE
        REMARKS- LEFT GEAR STRUCK A LOG ON NARROW BEACH. PX INCLUDED 2 SMALL CHILDREN.

Aircraft

Registration
N7625K
Reported as
Piper PA-20
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.