ANC67D0048

NTSB accident investigation · Piper J-3 · Dillingham, AK · July 17, 1966

Accident · No injuriesClosed
Date
July 17, 1966
Place
Dillingham, AK · DILLINGHAM, AK
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N35525Piper J-3
Status
Completed · report January 26, 1967
Report
Brief approved by the director
Case key
121896

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-3477  66/7/17  NR.DILLINGHAM ALAS    PIPER J-3           CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 29, 34 TOTAL
        TIME - 2030                    N35525              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL: MUSH                                              LANDING: FINAL APPROACH
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - PILOT FATIGUE
        REMARKS- STUDENT WAS IN STEEP TURN TO FINAL APPROACH FOR LANDING ON BEACH.NO SLEEP DURING PREVIOUS 24 HRS.

Aircraft

Registration
N35525
Reported as
Piper J-3
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.