MKC67A0023

NTSB accident investigation · Piper J3C-65 · Faith, SD · September 14, 1966

Accident · FatalClosed
Date
September 14, 1966
Place
Faith, SD · FAITH, SD
Injuries
1 fatal
Damage
Destroyed
Phase of flight
Enroute
Aircraft
N87964Piper J3C-65
Status
Completed · report August 28, 1967
Report
Brief approved by the director
Case key
121021

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-1185  66/9/14  NR.FAITH,S DAK        PIPER J3C-65        CR-  1  0  0  NONCOMMERCIAL             STUDENT, AGE 29, 121
        TIME - 0745                    N87964              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 119 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL: SPIN                                              IN FLIGHT: OTHER
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED
           PILOT IN COMMAND - PHYSICAL IMPAIRMENT
           MISCELLANEOUS ACTS,CONDITIONS - ALCOHOLIC IMPAIRMENT OF EFFICIENCY AND JUDGMENT
        REMARKS- PILOT WAS SEARCHING FOR LOST SHEEP.PILOT BLOOD ALCOHOL LEVEL 0.059 PERCENT.

Aircraft

Registration
N87964
Reported as
Piper J3C-65
Category
Airplane
Engine
reciprocating
Damage
Destroyed

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.