LAX68D0229

NTSB accident investigation · Cessna 172A · Corona, CA · December 2, 1967

Accident · No injuriesClosed
Date
December 2, 1967
Place
Corona, CA · CORONA, CA
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N7217TCessna 172A
Status
Completed · report January 25, 1968
Report
Brief approved by the director
Case key
112997

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-4254   67/12/2   CORONA,CALIF        CESSNA 172A         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 45, 101
        TIME - 1415                    N7217T              PX-  0  0  2  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 29 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - CORONA
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           GEAR COLLAPSED                                           LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER LEVEL OFF
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N7217T
Reported as
Cessna 172A
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Corona

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.