LAX67D0135

NTSB accident investigation · Piper PA-30 · Carlsbad, CA · September 28, 1966

Accident · No injuriesClosed
Date
September 28, 1966
Place
Carlsbad, CA · CARLSBAD, CA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N7762YPiper PA-30
Status
Completed · report January 10, 1967
Report
Brief approved by the director
Case key
120843

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-3305  66/9/28    CARLSBAD CALIF      PIPER PA-30         CR-  0  0  2  INSTRUCTIONAL             COMMERCIAL, FL.INSTR.,
        TIME - 0800                    N7762Y              PX-  0  0  0  DUAL                      AGE 44, 6000 TOTAL HOURS,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            190 IN TYPE, INSTRUMENT
                                                                                                   RATED.
        NAME OF AIRPORT - PALOMAR
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GEAR RETRACTED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           DUAL STUDENT - INADVERTENTLY RETRACTED GEAR
           DUAL STUDENT - SPONTANEOUS-IMPROPER ACTION

Aircraft

Registration
N7762Y
Reported as
Piper PA-30
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Palomar

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.