LAX67A0019

NTSB accident investigation · Luscombe 8 · Mojave, CA · August 12, 1966

Accident · FatalClosed
Date
August 12, 1966
Place
Mojave, CA · MOJAVE, CA
Injuries
1 fatal
Damage
Substantial damage
Phase of flight
Enroute
Aircraft
N1837KLuscombe 8
Status
Completed · report March 24, 1967
Report
Brief approved by the director
Case key
122435

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
----------------------------------------------------------------------------------------------------------------------------
2-0688  66/8/12  NR.MOJAVE CALIF       LUSCOMBE 8          CR-  1  0  0  NONCOMMERCIAL             PRIVATE, AGE 58, 200
        TIME - 0800                    N1837K              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, UNK/NR IN
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            TYPE, NOT INSTRUMENT
                                                                                                   RATED.
        NAME OF AIRPORT - EDWARDS AFB
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: WIRES/POLES                               IN FLIGHT: NORMAL CRUISE
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO SEE AND AVOID OBJECTS OR OBSTRUCTIONS
           MISCELLANEOUS ACTS,CONDITIONS - UNWARRANTED LOW FLYING

Aircraft

Registration
N1837K
Reported as
Luscombe 8
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Edwards Afb

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.