LAX70FUG04

NTSB accident investigation · Luscombe 8A · Upland, CA · January 7, 1970

Accident · No injuriesClosed
Date
January 7, 1970
Place
Upland, CA · UPLAND, CA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N77904Luscombe 8A
Status
Completed · report June 23, 1970
Report
Brief approved by the director
Case key
142364

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-0251   70/1/7    UPLAND,CALF         LUSCOMBE 8A         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 20, 160
        TIME - 1100                    N77904              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 30 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - CABLE
        DEPARTURE POINT             INTENDED DESTINATION
          TORRANCE,CALIF              UPLAND,CALF
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           COLLIDED WITH: DITCHES                                   LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER OPERATION OF BRAKES AND/OR FLIGHT CONTROLS

Aircraft

Registration
N77904
Reported as
Luscombe 8A
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Cable

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.