MKC69D0173

NTSB accident investigation · Taylorcraft BC12-D · Lacygne, KS · July 13, 1968

Accident · Minor injuriesClosed
Date
July 13, 1968
Place
Lacygne, KS · LACYGNE, KS
Injuries
1 minor
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N96438Taylorcraft BC12-D
Status
Completed · report November 7, 1968
Report
Brief approved by the director
Case key
109541

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-3193  68/7/13    LACYGNE,KANS        TAYLORCRAFT BC12-D  CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 52, 648
        TIME - 2020                    N96438              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 620 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - PIOLIT STRIP
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: FENCE,FENCEPOSTS                          LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - SELECTED UNSUITABLE TERRAIN
           MISCELLANEOUS ACTS,CONDITIONS - NOT ALIGNED WITH RUNWAY/INTENDED LANDING AREA
        REMARKS- LANDED ON ROAD NEXT TO UNLIGHTED STRIP.

Aircraft

Registration
N96438
Reported as
Taylorcraft BC12-D
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Piolit Strip

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.