CHI66D0438

NTSB accident investigation · Taylorcraft BC12-D · Cedar Grove, IN · September 23, 1965

Accident · Minor injuriesClosed
Date
September 23, 1965
Place
Cedar Grove, IN · CEDAR GROVE, IN
Injuries
1 minor
Damage
Substantial damage
Phase of flight
Initial climb
Aircraft
N5182MTaylorcraft BC12-D
Status
Completed · report December 27, 1965
Report
Brief approved by the director
Case key
175321

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-3309  65/9/23    CEDAR GROVE IND     TAYLORCRAFT BC12-D  CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 38, 545
        TIME - 1600                    N5182M              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 50 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL: MUSH                                              TAKEOFF: INITIAL CLIMB
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - SELECTED UNSUITABLE TERRAIN
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED
        FACTOR(S)
           TERRAIN - WET,SOFT GROUND
        REMARKS- OFF AIRPORT OPERATION.

Aircraft

Registration
N5182M
Reported as
Taylorcraft BC12-D
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.