LAX66D0057

NTSB accident investigation · Piper J-3 · Lancaster, CA · May 9, 1965

Accident · No injuriesClosed
Date
May 9, 1965
Place
Lancaster, CA · LANCASTER, CA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N92390Piper J-3
Status
Completed · report September 8, 1965
Report
Brief approved by the director
Case key
177640

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-1927   65/5/9    LANCASTER CALIF     PIPER J-3           CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 55, 6000
        TIME - 1100                    N92390              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 1000 IN
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            TYPE, INSTRUMENT RATED.
        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
        REMARKS- OFF AIRPORT OPERATION

Aircraft

Registration
N92390
Reported as
Piper J-3
Category
Airplane
Engine
reciprocating
Damage
Substantial damage

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.