DEN67D0117

NTSB accident investigation · Cessna 150 · Salt Lake City, UT · September 18, 1966

Accident · No injuriesClosed
Date
September 18, 1966
Place
Salt Lake City, UT · SALT LAKE CITY, UT
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N4411UCessna 150
Status
Completed · report November 15, 1966
Report
Brief approved by the director
Case key
121190

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-2632  66/9/18    SALT LAKE CITY UT   CESSNA 150          CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 28, 37 TOTAL
        TIME - 1400                    N4411U              PX-  0  0  0  PRACTICE                  HOURS, 25 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - SALT LAKE CITY
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER LEVEL OFF
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N4411U
Reported as
Cessna 150
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Salt Lake City

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.