OAK68F0090

NTSB accident investigation · Cessna 172 · Columbia, CA · August 14, 1967

Accident · Minor injuriesClosed
Date
August 14, 1967
Place
Columbia, CA · COLUMBIA, CA
Injuries
1 minor, 3 uninjured
Damage
Destroyed
Phase of flight
Landing
Aircraft
N4689LCessna 172
Status
Completed · report December 27, 1967
Report
Brief approved by the director
Case key
114783

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-3981  67/8/14    COLUMBIA,CALIF      CESSNA 172          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 30, 102
        TIME - 0800                    N4689L              PX-  0  0  3  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, ALL IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - COLUMBIA
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: LEVEL OFF/TOUCHDOWN
           COLLIDED WITH: OBJECT                                    LANDING: GO-AROUND
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
           PILOT IN COMMAND - DELAYED IN INITIATING GO-AROUND
        REMARKS- STRUCK ROCKS.

Aircraft

Registration
N4689L
Reported as
Cessna 172
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Columbia

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.