MKC73AK004

NTSB accident investigation · Cessna 172 · Tunica, MS · July 6, 1972

Accident · FatalClosed
Date
July 6, 1972
Place
Tunica, MS · TUNICA, MS
Injuries
1 fatal
Damage
Destroyed
Phase of flight
Enroute
Aircraft
N3965LCessna 172
Status
Completed
Report
Brief approved by the director
Case key
167010

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-1966   72/7/6  NR.TUNICA,MISS        CESSNA 172          CR-  1  0  0  NONCOMMERCIAL             PRIVATE, AGE 35, 1850
        TIME - UNK/NR                  N3965L              PX-  0  0  0  OTHER                     TOTAL HOURS, UNK/NR IN
                                       DAMAGE-DESTROYED    OT-  0  0  0                            TYPE, INSTRUMENT RATED.
        DEPARTURE POINT             INTENDED DESTINATION
          MEMPHIS,TENN               UNKNOWN/NOT REPORTED
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: TREES                                     IN FLIGHT: OTHER
        PROBABLE CAUSE(S)
          PLT-PSBL DISORIENTN DUE INJESTN LRG AMT TRANQ DRUG
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - AIRCRAFT CAME TO REST IN WATER
        MISSING AIRCRAFT - LATER RECOVERED
        REMARKS- DARK NIGHT,NO MOON.

Aircraft

Registration
N3965L
Reported as
Cessna 172
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.