OAK68D0339

NTSB accident investigation · Piper PA-18 · Palo Alto, CA · March 29, 1968

Accident · Minor injuriesClosed
Date
March 29, 1968
Place
Palo Alto, CA · PALO ALTO, CA
Injuries
1 minor, 1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N4337ZPiper PA-18
Status
Completed · report May 7, 1968
Report
Brief approved by the director
Case key
111086

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-0708  68/3/29    PALO ALTO,CALIF     PIPER PA-18         CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 25, 203
        TIME - 1215                    N4337Z              PX-  0  0  1  PRACTICE                  TOTAL HOURS, 10 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - PALO ALTO
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: LEVEL OFF/TOUCHDOWN
           COLLIDED WITH: DIRT BANK                                 LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER OPERATION OF BRAKES AND/OR FLIGHT CONTROLS
           PILOT IN COMMAND - IMPROPER RECOVERY FROM BOUNCED LANDING

Aircraft

Registration
N4337Z
Reported as
Piper PA-18
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.