LAX66D0101

NTSB accident investigation · Luscombe 8F · Torrance, CA · August 10, 1965

Accident · No injuriesClosed
Date
August 10, 1965
Place
Torrance, CA · TORRANCE, CA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N1453BLuscombe 8F
Status
Completed · report November 3, 1965
Report
Brief approved by the director
Case key
176137

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-2743  65/8/10    TORRANCE CALIF      LUSCOMBE 8F         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 42, 121
        TIME - 1915                    N1453B              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 25 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - TORRANCE
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           COLLIDED WITH: RUNWAY OR APPROACH LIGHTS                 LANDING: GO-AROUND
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER LEVEL OFF
           PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL

Aircraft

Registration
N1453B
Reported as
Luscombe 8F
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Torrance

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.