OAK73FVA20

NTSB accident investigation · Taylorcraft BC12-D · Porterville, CA · September 14, 1972

Accident · Serious injuriesClosed
Date
September 14, 1972
Place
Porterville, CA · PORTERVILLE, CA
Injuries
2 serious
Damage
Destroyed
Phase of flight
Enroute
Aircraft
N43850Taylorcraft BC12-D
Status
Completed · report March 27, 1973
Report
Brief approved by the director
Case key
168265

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-3572  72/9/14    PORTERVILLE,CALIF   TAYLORCRAFT BC12-D  CR-  0  1  0  NONCOMMERCIAL             PRIVATE, AGE 43, 500
        TIME - 1530                    N43850              PX-  0  1  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 175 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        DEPARTURE POINT             INTENDED DESTINATION
          STRATHMORE,CALIF            LOCAL
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL                                                    IN FLIGHT: NORMAL CRUISE
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - DIVERTED ATTENTION FROM OPERATION OF AIRCRAFT
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED

Aircraft

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