LAX66D0071

NTSB accident investigation · Piper PA-23 · Lancaster, CA · July 20, 1965

Accident · No injuriesClosed
Date
July 20, 1965
Place
Lancaster, CA · LANCASTER, CA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N5487YPiper PA-23
Status
Completed · report November 2, 1965
Report
Brief approved by the director
Case key
176120

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-2725  65/7/20    LANCASTER CALIF     PIPER PA-23         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 48, 3200
        TIME - 1500                    N5487Y              PX-  0  0  1  BUSINESS                  TOTAL HOURS, 300 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - FOX
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           WHEELS-UP                                                LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO ASSURE THE GEAR WAS DOWN AND LOCKED
        FACTOR(S)
           AIRFRAME - LANDING GEAR: LANDING GEAR WARNING AND INDICATING COMPONENTS
        REMARKS- GEAR WARNING HORN INOPERATIVE

Aircraft

Registration
N5487Y
Reported as
Piper PA-23
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Fox

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.