UNK65X1353

NTSB accident investigation · Cessna 210 · Silver City, NM · January 26, 1965

Accident · No injuriesClosed
Date
January 26, 1965
Place
Silver City, NM · SILVER CITY, NM
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N6665XCessna 210
Status
Completed · report February 19, 1965
Report
Brief approved by the director
Case key
180036

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-0123  65/1/26    SILVER CITY NM      CESSNA 210          CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, FL.INSTR.,
        TIME - 1000                    N6665X              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  AGE 50, 4000 TOTAL HOURS,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            300 IN TYPE, INSTRUMENT
                                                                                                   RATED.
        NAME OF AIRPORT - TURNER STRIP
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           WHEELS-UP                                                LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO EXTEND LANDING GEAR

Aircraft

Registration
N6665X
Reported as
Cessna 210
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Turner Strip

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.