MIA67D0544

NTSB accident investigation · Beech A23 · Batesburg, SC · February 23, 1967

Accident · No injuriesClosed
Date
February 23, 1967
Place
Batesburg, SC · BATESBURG, SC
Injuries
2 uninjured
Damage
Destroyed
Phase of flight
Approach
Aircraft
N8863MBeech A23
Status
Completed · report August 8, 1967
Report
Brief approved by the director
Case key
118394

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-0588  67/2/23    BATESBURG,SC        BEECH A23           CR-  0  0  2  INSTRUCTIONAL             COMMERCIAL, FL.INSTR.,
        TIME - 1610                    N8863M              PX-  0  0  0  DUAL                      AGE 29, 400 TOTAL HOURS,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            40 IN TYPE, INSTRUMENT
                                                                                                   RATED.
        NAME OF AIRPORT - TWIN CITY
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL: MUSH                                              LANDING: FINAL APPROACH
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED
           PILOT IN COMMAND - INADEQUATE SUPERVISION OF FLIGHT

Aircraft

Registration
N8863M
Reported as
Beech A23
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Twin City

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.