FTW69A0074

NTSB accident investigation · Cessna 310N · Huntsville, TX · April 15, 1969

Accident · FatalClosed
Date
April 15, 1969
Place
Huntsville, TX · HUNTSVILLE, TX
Injuries
6 fatal
Damage
Destroyed
Phase of flight
Initial climb
Aircraft
N5072QCessna 310N
Status
Completed · report May 28, 1969
Report
Brief approved by the director
Case key
118580

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-0679  69/4/15    HUNTSVILLE,TEX      CESSNA 310N         CR-  1  0  0  NONCOMMERCIAL             COMMERCIAL, AGE 46, 13000
        TIME - 2330                    N5072Q              PX-  5  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 2007 IN
                                       DAMAGE-DESTROYED    OT-  0  0  0                            TYPE, INSTRUMENT RATED.
        NAME OF AIRPORT - HUNTSVILLE
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL                                                    TAKEOFF: INITIAL CLIMB
        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- PLT BLOOD ALCOHOL LEVEL 0.158 PCT.

Aircraft

Registration
N5072Q
Reported as
Cessna 310N
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Huntsville

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.