LAX66F0072

NTSB accident investigation · Piper PA-20 · Van Nuys, CA · August 4, 1965

Accident · No injuriesClosed
Date
August 4, 1965
Place
Van Nuys, CA · VAN NUYS, CA
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N7325KPiper PA-20
Status
Completed · report November 3, 1965
Report
Brief approved by the director
Case key
176133

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-2739   65/8/4    VAN NUYS CALIF      PIPER PA-20         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 62, 623
        TIME - 1407                    N7325K              PX-  0  0  2  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 302 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT -  BAN NUYS
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N7325K
Reported as
Piper PA-20
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Ban Nuys

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.