UNK65X1407

NTSB accident investigation · Cessna 182 · Yucca Valley, CA · February 8, 1965

Accident · No injuriesClosed
Date
February 8, 1965
Place
Yucca Valley, CA · YUCCA VALLEY, CA
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N2788GCessna 182
Status
Completed · report May 19, 1965
Report
Brief approved by the director
Case key
179643

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-0651   65/2/8    YUCCA VALLEY CALI   CESSNA 182          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 35, 129
        TIME - 1630                    N2788G              PX-  0  0  2  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 10 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - YUCCA VALLEY
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: ROLL
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - SUNGLARE

Aircraft

Registration
N2788G
Reported as
Cessna 182
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Yucca Valley

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.