DEN66D0347

NTSB accident investigation · Cessna 150 · Trinidad, CO · May 1, 1966

Accident · No injuriesClosed
Date
May 1, 1966
Place
Trinidad, CO · TRINIDAD, CO
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N7729FCessna 150
Status
Completed · report July 27, 1966
Report
Brief approved by the director
Case key
172345

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-1270   66/5/1    TRINIDAD COLO       CESSNA 150          CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 28, 16 TOTAL
        TIME - 1000                    N7729F              PX-  0  0  0  SOLO                      HOURS, 1 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - LOS ANIMAS COUNTY
        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
N7729F
Reported as
Cessna 150
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Los Animas County

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.