DEN67D0043

NTSB accident investigation · Cessna 170 · Moab, UT · July 16, 1966

Accident · No injuriesClosed
Date
July 16, 1966
Place
Moab, UT · MOAB, UT
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N3455CCessna 170
Status
Completed · report September 9, 1966
Report
Brief approved by the director
Case key
121960

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-1852  66/7/16    MOAB UT             CESSNA 170          CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 38, 58 TOTAL
        TIME - 1030                    N3455C              PX-  0  0  0  PRACTICE                  HOURS, 27 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - CANYONLANDS
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER OPERATION OF BRAKES AND/OR FLIGHT CONTROLS
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N3455C
Reported as
Cessna 170
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Canyonlands

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.