LAX66D0149

NTSB accident investigation · Cessna 182 · Furnace Creek, CA · November 4, 1965

Accident · No injuriesClosed
Date
November 4, 1965
Place
Furnace Creek, CA · FURNACE CREEK, CA
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N2382GCessna 182
Status
Completed · report February 8, 1966
Report
Brief approved by the director
Case key
174272

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-3717   65/11/4   FURNACE CREEK CAL   CESSNA 182          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 40, 499
        TIME - 1230                    N2382G              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 122 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - FURNACE CREEK
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           UNDERSHOOT                                               LANDING: FINAL APPROACH
           NOSE OVER/DOWN                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND ALTITUDE
        REMARKS- LANDING WAS MADE ON SOFT OVERUN AREA

Aircraft

Registration
N2382G
Reported as
Cessna 182
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Furnace Creek

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.