LAX68D0207

NTSB accident investigation · Piper PA-24 · Carlsbad, CA · November 22, 1967

Accident · No injuriesClosed
Date
November 22, 1967
Place
Carlsbad, CA · CARLSBAD, CA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N6836PPiper PA-24
Status
Completed · report January 17, 1968
Report
Brief approved by the director
Case key
112942

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-4196  67/11/22   CARLSBAD,CALIF      PIPER PA-24         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 45, 2000
        TIME - 1200                    N6836P              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 750 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - PALOMAR
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           WHEELS-UP                                                LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO EXTEND LANDING GEAR
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - CHECKLIST-FAILED TO USE
        REMARKS- SUCCESSFUL GO AROUND AND LNDG.

Aircraft

Registration
N6836P
Reported as
Piper PA-24
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.