MIA72IM144

NTSB incident investigation · Beech 65-A80 · Columbia, SC · June 27, 1972

Incident · No injuriesClosed
Date
June 27, 1972
Place
Columbia, SC · COLUMBIA, SC
Injuries
1 uninjured
Damage
Minor damage
Phase of flight
Approach
Aircraft
N32TMBeech 65-A80
Status
Completed · report March 19, 1973
Report
Brief approved by the director
Case key
118149

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the incident.

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
----------------------------------------------------------------------------------------------------------------------------
5-0033  72/6/27    COLUMBIA,SC         BEECH 65-A80        CR-  0  0  1  MISCELLANEOUS             COMMERCIAL, AGE 37, 1200
        TIME - 1043                    N32TM               PX-  0  0  0  FERRY                     TOTAL HOURS, 30 IN TYPE,
                                       DAMAGE-MINOR        OT-  0  0  0                            INSTRUMENT RATED.
        CLASSIFIED AS INCIDENT
        NAME OF AIRPORT - COLUMBIA METRO
        DEPARTURE POINT             INTENDED DESTINATION
          AUGUSTA,GA                  COLUMBIA,SC
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           FIRE OR EXPLOSION: IN FLIGHT                             LANDING: FINAL APPROACH
        PROBABLE CAUSE(S)
           MISCELLANEOUS - UNDETERMINED
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - FIRE IN ENGINE

Aircraft

Registration
N32TM
Reported as
Beech 65-A80
Category
Airplane
Engine
reciprocating
Damage
Minor damage
Airport
Columbia Metro

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.