OAK67F0001

NTSB accident investigation · Piper PA-30 · Oakland, CA · May 17, 1966

Accident · No injuriesClosed
Date
May 17, 1966
Place
Oakland, CA · OAKLAND, CA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N7561YPiper PA-30
Status
Completed · report August 4, 1966
Report
Brief approved by the director
Case key
171763

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-1377  66/5/17    OAKLAND CALIF       PIPER PA-30         CR-  0  0  1  COMMERCIAL                COMMERCIAL, AGE 30, 3300
        TIME - 1110                    N7561Y              PX-  0  0  0  AIR TAXI-PASSG            TOTAL HOURS, 32 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - OAKLAND INTERNAT
        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)
           PILOT IN COMMAND - DIVERTED ATTENTION FROM OPERATION OF AIRCRAFT
        REMARKS- CONCENTRATING ON LANDING SHORT

Aircraft

Registration
N7561Y
Reported as
Piper PA-30
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Oakland Internat

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.