MIA65A0116

NTSB accident investigation · Beechcraft 65 · Greenville, MS · May 30, 1965

Accident · FatalClosed
Date
May 30, 1965
Place
Greenville, MS · GREENVILLE, MS
Injuries
1 fatal
Damage
Destroyed
Phase of flight
Enroute
Aircraft
N196BGBeechcraft 65
Status
Completed · report September 8, 1965
Report
Brief approved by the director
Case key
178174

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-0423  65/5/30  NR.GREENVILLE MISS    BEECHCRAFT 65       CR-  1  0  0  NONCOMMERCIAL             COMMERCIAL, AGE 40, 2600
        TIME - 0520                    N196BG              PX-  0  0  0  BUSINESS                  TOTAL HOURS, 45 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: TREES                                     IN FLIGHT: NORMAL CRUISE
           COLLISION WITH GROUND/WATER: UNCONTROLLED                IN FLIGHT: UNCONTROLLED DESCENT
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - INCAPACITATION
           MISCELLANEOUS ACTS,CONDITIONS - PILOT FATIGUE
         FIRE AFTER IMPACT
        REMARKS- INCAPICATION INDUCED BY SLEEP

Aircraft

Registration
N196BG
Reported as
Beechcraft 65
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.