CHI72FET05

NTSB accident investigation · Taylorcraft BC-12D · Syracuse, IN · August 15, 1971

Accident · Minor injuriesClosed
Date
August 15, 1971
Place
Syracuse, IN · SYRACUSE, IN
Injuries
1 minor
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N5242MTaylorcraft BC-12D
Status
Completed · report March 31, 1972
Report
Brief approved by the director
Case key
162805

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-3029  71/8/15    SYRACUSE,IND        TAYLORCRAFT BC-12D  CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, FL.INSTR.,
        TIME - 1915                    N5242M              PX-  0  0  0  PRACTICE                  AGE 54, 923 TOTAL HOURS,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            2 IN TYPE, INSTRUMENT
                                                                                                   RATED.
        DEPARTURE POINT             INTENDED DESTINATION
          SYRACUSE,IND                LOCAL
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL: MUSH                                              LANDING: GO-AROUND
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED

Aircraft

Registration
N5242M
Reported as
Taylorcraft BC-12D
Category
Airplane
Engine
reciprocating
Damage
Substantial damage

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.