OAK67D0047

NTSB accident investigation · Luscombe 8E · Vacaville, CA · July 31, 1966

Accident · Minor injuriesClosed
Date
July 31, 1966
Place
Vacaville, CA · VACAVILLE, CA
Injuries
2 minor
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N2293KLuscombe 8E
Status
Completed · report September 14, 1966
Report
Brief approved by the director
Case key
121990

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-1896  66/7/31    VACAVILLE CALIF     LUSCOMBE 8E         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 25, 86 TOTAL
        TIME - 1310                    N2293K              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  HOURS, 20 IN TYPE, UNK/NR
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - NUT TREE
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: FINAL APPROACH
           COLLIDED WITH: DIRT BANK                                 LANDING: GO-AROUND
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND ALTITUDE
           PILOT IN COMMAND - DELAYED IN INITIATING GO-AROUND

Aircraft

Registration
N2293K
Reported as
Luscombe 8E
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Nut Tree

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.