LAX66D0011

NTSB accident investigation · Cessna 206 · Rancho Mirage, CA · February 20, 1965

Accident · No injuriesClosed
Date
February 20, 1965
Place
Rancho Mirage, CA · RANCHO MIRAGE, CA
Injuries
7 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N5155UCessna 206
Status
Completed · report August 30, 1965
Report
Brief approved by the director
Case key
178563

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-1784  65/2/20    RANCHO MIRAGE CAL   CESSNA 206          CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 36, 850
        TIME - 1330                    N5155U              PX-  0  0  6  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 5 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - PALM DESERT
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           GEAR COLLAPSED                                           LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER LEVEL OFF
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N5155U
Reported as
Cessna 206
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Palm Desert

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.