LAX68F0417

NTSB accident investigation · Cessna 172 · Huntingtn Bch, CA · March 31, 1968

Accident · Minor injuriesClosed
Date
March 31, 1968
Place
Huntingtn Bch, CA · HUNTINGTN BCH, CA
Injuries
1 minor, 3 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N5916RCessna 172
Status
Completed · report July 2, 1968
Report
Brief approved by the director
Case key
110943

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-1314  68/3/31    HUNTINGTN BCH,CAL   CESSNA 172          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 26, 103
        TIME - 0850                    N5916R              PX-  0  0  3  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 8 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - MEADOWLARK
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: LEVEL OFF/TOUCHDOWN
           COLLIDED WITH: WIRES/POLES                               LANDING: GO-AROUND
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
           PILOT IN COMMAND - DELAYED IN INITIATING GO-AROUND

Aircraft

Registration
N5916R
Reported as
Cessna 172
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Meadowlark

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.