UNK65X0297

NTSB accident investigation · Beechcraft G-35 · Columbus, TX · October 16, 1964

Accident · FatalClosed
Date
October 16, 1964
Place
Columbus, TX · COLUMBUS, TX
Injuries
3 fatal
Damage
Destroyed
Phase of flight
Enroute
Aircraft
N4449DBeechcraft G-35
Status
Completed · report January 22, 1965
Report
Brief approved by the director
Case key
181753

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-0730  64/10/16 NR.COLUMBUS TEXAS     BEECHCRAFT G-35     CR-  1  0  0  COMMERCIAL                COMMERCIAL, FL.INSTR.,
        TIME - 1421                    N4449D              PX-  2  0  0  OTHER                     AGE 19, 900 TOTAL HOURS,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            400 IN TYPE, INSTRUMENT
                                                                                                   RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL                                                    IN FLIGHT: NORMAL CRUISE
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED
         FIRE AFTER IMPACT
        REMARKS- CHARTER FLIGHT TO AIR-DROP SUPPLIES AT OILWELL DRILLING SITE.

Aircraft

Registration
N4449D
Reported as
Beechcraft G-35
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.