OAK69D0209

NTSB accident investigation · Piper PA-30 · Turlock, CA · December 28, 1968

Accident · No injuriesClosed
Date
December 28, 1968
Place
Turlock, CA · TURLOCK, CA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Takeoff
Aircraft
N8377YPiper PA-30
Status
Completed · report February 24, 1969
Report
Brief approved by the director
Case key
191885

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-4514  68/12/28   TURLOCK,CALIF       PIPER PA-30         CR-  0  0  2  INSTRUCTIONAL             COMMERCIAL, FL.INSTR.,
        TIME - 1600                    N8377Y              PX-  0  0  0  DUAL                      AGE 44, 2215 TOTAL HOURS,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            30 IN TYPE, INSTRUMENT
                                                                                                   RATED.
        NAME OF AIRPORT - TURLOCK
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GEAR RETRACTED                                           TAKEOFF: RUN
        PROBABLE CAUSE(S)
           DUAL STUDENT - INADVERTENTLY RETRACTED GEAR
           PILOT IN COMMAND - INADEQUATE SUPERVISION OF FLIGHT

Aircraft

Registration
N8377Y
Reported as
Piper PA-30
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Turlock

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.