UNK64X0630

NTSB accident investigation · Piper PA12 · Ripley, TN · February 21, 1964

Accident · FatalClosed
Date
February 21, 1964
Place
Ripley, TN · RIPLEY, TN
Injuries
1 fatal
Damage
Destroyed
Phase of flight
Maneuvering
Aircraft
N3681MPiper PA12
Status
Completed · report January 8, 1965
Report
Brief approved by the director
Case key
124335

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-0106  64/2/21  NR. RIPLEY TENN       PIPER PA12          CR-  1  0  0  MISCELLANEOUS             COMMERCIAL, FL.INSTR.,
        TIME - 1400                    N3681M              PX-  0  0  0  FERRY                     AGE 47, 8000 TOTAL HOURS,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            1000 IN TYPE, NOT
                                                                                                   INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: TREES                                     IN FLIGHT: BUZZING
        PROBABLE CAUSE(S)
           MISCELLANEOUS ACTS,CONDITIONS - ALCOHOLIC IMPAIRMENT OF EFFICIENCY AND JUDGMENT
        FACTOR(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE,SPEED,ALTITUDE OR CLEARANCE

Aircraft

Registration
N3681M
Reported as
Piper PA12
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.