OAK72DVM11

NTSB accident investigation · Luscombe 8A · Palo Alto, CA · November 6, 1971

Accident · No injuriesClosed
Date
November 6, 1971
Place
Palo Alto, CA · PALO ALTO, CA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N2833KLuscombe 8A
Status
Completed · report June 29, 1972
Report
Brief approved by the director
Case key
164068

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-4133   71/11/6   PALO ALTO,CALIF     LUSCOMBE 8A         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 43, 159
        TIME - 1709                    N2833K              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 16 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - PALO ALTO
        DEPARTURE POINT             INTENDED DESTINATION
          PALO ALTO,CALIF             LOCAL
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           COLLIDED WITH: FENCE,FENCEPOSTS                          LANDING: GO-AROUND
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL

Aircraft

Registration
N2833K
Reported as
Luscombe 8A
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Palo Alto

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.