LAX70D0228

NTSB accident investigation · Cessna 150 · Phoenix, AZ · December 25, 1969

Accident · Serious injuriesClosed
Date
December 25, 1969
Place
Phoenix, AZ · PHOENIX, AZ
Injuries
1 serious, 1 minor
Damage
Substantial damage
Phase of flight
Enroute
Aircraft
N3783JCessna 150
Status
Completed · report June 2, 1970
Report
Brief approved by the director
Case key
145531

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-4554  69/12/25 NR.PHOENIX,ARIZ       CESSNA 150          CR-  0  1  0  NONCOMMERCIAL             STUDENT, AGE 20, 49 TOTAL
        TIME - 1700                    N3783J              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        DEPARTURE POINT             INTENDED DESTINATION
         PHOENIX,ARIZ                 LOCAL
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLISION WITH GROUND/WATER: CONTROLLED                  IN FLIGHT: OTHER
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - ATTEMPTED OPERATION BEYOND EXPERIENCE/ABILITY LEVEL
           PILOT IN COMMAND - IMPROPER IN-FLIGHT DECISIONS OR PLANNING
        REMARKS- TRIED TO OUTCLIMB MTN RIDGE.

Aircraft

Registration
N3783J
Reported as
Cessna 150
Category
Airplane
Engine
reciprocating
Damage
Substantial damage

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.