OAK66D0155

NTSB accident investigation · Beechcraft 23 · Santa Cruz, CA · November 6, 1965

Accident · No injuriesClosed
Date
November 6, 1965
Place
Santa Cruz, CA · SANTA CRUZ, CA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N2377LBeechcraft 23
Status
Completed · report January 6, 1966
Report
Brief approved by the director
Case key
174635

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-3407   65/11/6   SANTA CRUZ CALIF    BEECHCRAFT 23       CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 44, 243
        TIME - 1645                    N2377L              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 106 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - SKYPARK
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: ROLL
           COLLIDED WITH: FENCE,FENCEPOSTS                          LANDING: GO-AROUND
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
           PILOT IN COMMAND - DELAYED IN INITIATING GO-AROUND

Aircraft

Registration
N2377L
Reported as
Beechcraft 23
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Skypark

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.