OAK66D0076

NTSB accident investigation · Beechcraft N-35 · Trinity Cntr, CA · August 6, 1965

Accident · No injuriesClosed
Date
August 6, 1965
Place
Trinity Cntr, CA · TRINITY CNTR, CA
Injuries
6 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N1216ZBeechcraft N-35
Status
Completed · report October 11, 1965
Report
Brief approved by the director
Case key
178644

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-2440   65/8/6    TRINITY CNTR CALI   BEECHCRAFT N-35     CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 38, 1237
        TIME - 1600                    N1216Z              PX-  0  0  5  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 84 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - TRINITY CENTER
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: ROLL
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
        REMARKS- PASSENGERS INCLUDED 3 CHILDREN

Aircraft

Registration
N1216Z
Reported as
Beechcraft N-35
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Trinity Center

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.