FTW66F0018

NTSB accident investigation · Luscombe 8A · Baytown, TX · April 3, 1965

Accident · No injuriesClosed
Date
April 3, 1965
Place
Baytown, TX · BAYTOWN, TX
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N2915KLuscombe 8A
Status
Completed · report July 26, 1965
Report
Brief approved by the director
Case key
178478

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-1226   65/4/3    BAYTOWN TEX         LUSCOMBE 8A         CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 30, 11 TOTAL
        TIME - 1035                    N2915K              PX-  0  0  0  SOLO                      HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - BAYTEX
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: GO-AROUND
           COLLIDED WITH: PARKED AIRCRAFT                           LANDING: GO-AROUND
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER COMPENSATION FOR WIND CONDITIONS
        REMARKS- PARKED AIRCRAFT TAYLORCRAFT BC-12D N43092 SUBSTANTIAL DAMAGE.

Aircraft

Registration
N2915K
Reported as
Luscombe 8A
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Baytex

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.