LAX67F0262

NTSB accident investigation · Luscombe 8A · Huntington, CA · January 7, 1967

Accident · No injuriesClosed
Date
January 7, 1967
Place
Huntington, CA · HUNTINGTON, CA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N71148Luscombe 8A
Status
Completed · report November 22, 1967
Report
Brief approved by the director
Case key
119654

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-3023   67/1/7    HUNTINGTON,CALIF    LUSCOMBE 8A         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 45, 184
        TIME - 1615                    N71148              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 90 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - MEADOWLARK
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL                                                    LANDING: FINAL APPROACH
           COLLIDED WITH: PARKED AIRCRAFT                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED
        REMARKS- PKD ACFT N2736N, DAMAGES UNKNOWN.

Aircraft

Registration
N71148
Reported as
Luscombe 8A
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Meadowlark

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.