LAX67D0325

NTSB accident investigation · Cessna 120 · Torrance, CA · March 9, 1967

Accident · No injuriesClosed
Date
March 9, 1967
Place
Torrance, CA · TORRANCE, CA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N77294Cessna 120
Status
Completed · report August 10, 1967
Report
Brief approved by the director
Case key
118048

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-0695   67/3/9    TORRANCE, CALIF     CESSNA 120          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 40, 1200
        TIME - 1730                    N77294              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 15 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - TORRANCE MUNI
        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
N77294
Reported as
Cessna 120
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Torrance Muni

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.