LAX66F0384

NTSB accident investigation · Cessna 170B · Bakersfield, CA · June 13, 1966

Accident · No injuriesClosed
Date
June 13, 1966
Place
Bakersfield, CA · BAKERSFIELD, CA
Injuries
4 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N4595CCessna 170B
Status
Completed · report November 28, 1966
Report
Brief approved by the director
Case key
171095

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-2759  66/6/13    BAKERSFIELD CALIF   CESSNA 170B         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 33, 95 TOTAL
        TIME - 0742                    N4595C              PX-  0  0  3  PLEASURE/PERSONAL TRANSP  HOURS, 3 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - MEADOWS FIELD
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER OPERATION OF BRAKES AND/OR FLIGHT CONTROLS
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N4595C
Reported as
Cessna 170B
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Meadows Field

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.