DEN67A0001

NTSB accident investigation · Cessna T210F · Cisco, UT · July 6, 1966

Accident · FatalClosed
Date
July 6, 1966
Place
Cisco, UT · CISCO, UT
Injuries
2 fatal
Damage
Destroyed
Phase of flight
Enroute
Aircraft
N6790RCessna T210F
Status
Completed · report February 2, 1967
Report
Brief approved by the director
Case key
171698

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
----------------------------------------------------------------------------------------------------------------------------
2-0552   66/7/6    CISCO UTAH          CESSNA T210F        CR-  2  0  0  MISCELLANEOUS             PRIVATE, AGE 34, 850
        TIME - 0550                    N6790R              PX-  0  0  0  FERRY                     TOTAL HOURS, UNK/NR IN
                                       DAMAGE-DESTROYED    OT-  0  0  0                            TYPE, NOT INSTRUMENT
                                                                                                   RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLISION WITH GROUND/WATER: CONTROLLED                  IN FLIGHT: NORMAL CRUISE
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED ALTITUDE AND CLEARANCE
         FIRE AFTER IMPACT
        REMARKS- STRUCK TOP OF SHEER CLIFF THAT JUTTED-UP FROM RELATIVELY FLAT TERRAIN.WX CLEAR-NO WIND-UNLIMIT VIS

Aircraft

Registration
N6790R
Reported as
Cessna T210F
Category
Airplane
Engine
reciprocating
Damage
Destroyed

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.