DEN66D0177

NTSB accident investigation · Cessna 150 · Tucson, AZ · November 26, 1965

Accident · No injuriesClosed
Date
November 26, 1965
Place
Tucson, AZ · TUCSON, AZ
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N4138UCessna 150
Status
Completed · report March 9, 1966
Report
Brief approved by the director
Case key
174329

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-3822  65/11/26   TUCSON ARIZ         CESSNA 150          CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 21, 17 TOTAL
        TIME - 1203                    N4138U              PX-  0  0  0  SOLO                      HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - TUCSON
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           GEAR COLLAPSED                                           LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           MISCELLANEOUS - VORTEX TURBULENCE
          PILOT-LACK OF EXPERIENCE.
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N4138U
Reported as
Cessna 150
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Tucson

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.