LAX68D0005

NTSB accident investigation · Piper PA-23 · El Monte, CA · May 17, 1967

Accident · No injuriesClosed
Date
May 17, 1967
Place
El Monte, CA · EL MONTE, CA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N3116PPiper PA-23
Status
Completed · report September 13, 1967
Report
Brief approved by the director
Case key
116995

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-1571  67/5/17    EL MONTE,CALIF      PIPER PA-23         CR-  0  0  2  INSTRUCTIONAL             COMMERCIAL, FL.INSTR.,
        TIME - 1200                    N3116P              PX-  0  0  0  DUAL                      AGE 58, 17000 TOTAL
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            HOURS, 800 IN TYPE,
                                                                                                   INSTRUMENT RATED.
        NAME OF AIRPORT - EL MONTE
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           WHEELS-UP                                                LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           DUAL STUDENT - FAILED TO EXTEND LANDING GEAR
           PILOT IN COMMAND - INADEQUATE SUPERVISION OF FLIGHT

Aircraft

Registration
N3116P
Reported as
Piper PA-23
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
El Monte

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.