OAK69D0056

NTSB accident investigation · Cessna 172 · San Jose, CA · July 19, 1968

Accident · No injuriesClosed
Date
July 19, 1968
Place
San Jose, CA · SAN JOSE, CA
Injuries
4 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N8190LCessna 172
Status
Completed · report October 4, 1968
Report
Brief approved by the director
Case key
109269

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-2485  68/7/19    SAN JOSE,CALIF      CESSNA 172          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 38, 119
        TIME - 2230                    N8190L              PX-  0  0  3  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 55 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - SAN JOSE
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER RECOVERY FROM BOUNCED LANDING
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N8190L
Reported as
Cessna 172
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
San Jose

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.