OAK67D0311

NTSB accident investigation · Cessna 172 · Antioch, CA · March 11, 1967

Accident · No injuriesClosed
Date
March 11, 1967
Place
Antioch, CA · ANTIOCH, CA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N4344LCessna 172
Status
Completed · report August 15, 1967
Report
Brief approved by the director
Case key
118094

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-0766  67/3/11    ANTIOCH,CALIF       CESSNA 172          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 24, 100
        TIME - 1300                    N4344L              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 12 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - ANTIOCH
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: WIRES/POLES                               LANDING: FINAL APPROACH
           GEAR COLLAPSED                                           LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO SEE AND AVOID OBJECTS OR OBSTRUCTIONS
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N4344L
Reported as
Cessna 172
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Antioch

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.