UNK64X2027

NTSB accident investigation · Piper PA24 · National City, CA · May 30, 1964

Accident · No injuriesClosed
Date
May 30, 1964
Place
National City, CA · NATIONAL CITY, CA
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N8194PPiper PA24
Status
Completed · report September 25, 1964
Report
Brief approved by the director
Case key
183772

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-1475  64/5/30    NATIONAL CITY CAL   PIPER PA24          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 52, 685
        TIME - 1220                    N8194P              PX-  0  0  2  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 73 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - NATIONAL CITY
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           GEAR COLLAPSED                                           LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER LEVEL OFF
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N8194P
Reported as
Piper PA24
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
National City

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.