LAX66D0142

NTSB accident investigation · Piper PA-28 · Ridgecrest, CA · September 5, 1965

Accident · No injuriesClosed
Date
September 5, 1965
Place
Ridgecrest, CA · RIDGECREST, CA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N5333WPiper PA-28
Status
Completed · report February 2, 1966
Report
Brief approved by the director
Case key
175388

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-3636   65/9/5    RIDGECREST CALIF    PIPER PA-28         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 29, 187
        TIME - 1630                    N5333W              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 81 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - VALLEY VIEW
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER OPERATION OF BRAKES AND/OR FLIGHT CONTROLS
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N5333W
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Valley View

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.