ANC71FAG01

NTSB accident investigation · Piper J3C-65 · Palmer, AK · July 5, 1970

Accident · FatalClosed
Date
July 5, 1970
Place
Palmer, AK · PALMER, AK
Injuries
1 fatal, 1 serious
Damage
Substantial damage
Phase of flight
Enroute
Aircraft
N88174Piper J3C-65
Status
Completed · report April 29, 1971
Report
Brief approved by the director
Case key
114559

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-2898   70/7/5    PALMER,ALAS         PIPER J3C-65        CR-  1  0  0  NONCOMMERCIAL             PRIVATE, AGE 38, 146
        TIME - 1330                    N88174              PX-  0  1  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 80 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - SHEEP MOUNTAIN
        DEPARTURE POINT             INTENDED DESTINATION
          EUREKA,ALAS                UNKNOWN/NOT REPORTED
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLISION WITH GROUND/WATER: CONTROLLED                  IN FLIGHT: OTHER
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED CLEARANCE
        REMARKS- FLYING LOW IN VALLEY,STEEP MTNS BOTH SIDES.

Aircraft

Registration
N88174
Reported as
Piper J3C-65
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Sheep Mountain

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.