MIA68A0062

NTSB accident investigation · Cessna 170B · Tarpon Sprngs, FL · January 8, 1968

Accident · FatalClosed
Date
January 8, 1968
Place
Tarpon Sprngs, FL · TARPON SPRNGS, FL
Injuries
4 fatal
Damage
Destroyed
Phase of flight
Uncontrolled descent
Aircraft
N3156BCessna 170B
Status
Completed · report May 15, 1968
Report
Brief approved by the director
Case key
111443

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-0753   68/1/8  NR.TARPON SPRNGS,FLA  CESSNA 170B         CR-  1  0  0  NONCOMMERCIAL             STUDENT, AGE 23, 70 TOTAL
        TIME - UNK/NR                  N3156B              PX-  3  0  0  PLEASURE/PERSONAL TRANSP  HOURS, 50 IN TYPE, NOT
                                       DAMAGE-DESTROYED    OT-  0  0  0                            INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLISION WITH GROUND/WATER: UNCONTROLLED                IN FLIGHT: UNCONTROLLED DESCENT
        PROBABLE CAUSE(S)
           MISCELLANEOUS - UNDETERMINED
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - AIRCRAFT CAME TO REST IN WATER
        MISSING AIRCRAFT - LATER RECOVERED
        REMARKS- RECOVERY DATE.1/12/68.1 PAX MISSING,INJURY PRESUMED.CRASHED IN GULF OF MEX.

Aircraft

Registration
N3156B
Reported as
Cessna 170B
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.