LAX68D0185

NTSB accident investigation · Cessna 120 · Corona, CA · September 28, 1967

Accident · No injuriesClosed
Date
September 28, 1967
Place
Corona, CA · CORONA, CA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Taxi
Aircraft
N89662Cessna 120
Status
Completed · report January 11, 1968
Report
Brief approved by the director
Case key
113954

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-3940  67/9/28    CORONA,CALIF        CESSNA 120          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 51, 175
        TIME - 0915                    N89662              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, UNK/NR IN
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            TYPE, NOT INSTRUMENT
                                                                                                   RATED.
        NAME OF AIRPORT - CORONA
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: PARKED AIRCRAFT                           TAXI: OTHER
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - STARTED ENGINE WITHOUT PROPER ASSISTANCE/EQUIPMENT
        REMARKS- HAND PROPPED ACFT. STRUCK 2 ACFT, IDENTITY AND DAMAGE NOT REPORTED.

Aircraft

Registration
N89662
Reported as
Cessna 120
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.