LAX68F0331

NTSB accident investigation · Cessna 150F · Torrance, CA · February 14, 1968

Accident · No injuriesClosed
Date
February 14, 1968
Place
Torrance, CA · TORRANCE, CA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N8497GCessna 150F
Status
Completed · report April 3, 1968
Report
Brief approved by the director
Case key
111912

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-0400  68/2/14    TORRANCE,CALIF      CESSNA 150F         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 22, 180
        TIME - 2355                    N8497G              PX-  0  0  1  PRACTICE                  TOTAL HOURS, 145 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - TORRANCE
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER OPERATION OF BRAKES AND/OR FLIGHT CONTROLS
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N8497G
Reported as
Cessna 150F
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Torrance

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.