LAX81DUG18

NTSB accident investigation · Cessna 150 · Corona, CA · March 2, 1981

Accident · No injuriesClosed
Date
March 2, 1981
Place
Corona, CA · CORONA, CA
Injuries
1 uninjured
Damage
Destroyed
Phase of flight
Landing
Aircraft
N9375UCessna 150
Status
Completed · report May 5, 1981
Report
Brief approved by the director
Case key
126967

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-0632   81/3/2    CORONA,CA           CESSNA 150          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 51, 370
        TIME - 1805                    N9375U              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, UNK/NR IN
                                       DAMAGE-DESTROYED    OT-  0  0  0                            TYPE, NOT INSTRUMENT
                                                                                                   RATED.
        DEPARTURE POINT             INTENDED DESTINATION
          CORONA,CA                   LOCAL
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: FENCE,FENCEPOSTS                          LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - SELECTED UNSUITABLE TERRAIN
        FACTOR(S)
           TERRAIN - HIGH OBSTRUCTIONS

Aircraft

Registration
N9375U
Reported as
Cessna 150
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Open Field

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.