DEN66F0721

NTSB accident investigation · Cessna 150 · Las Cruces, NM · March 14, 1966

Accident · Serious injuriesClosed
Date
March 14, 1966
Place
Las Cruces, NM · LAS CRUCES, NM
Injuries
1 serious, 1 minor
Damage
Destroyed
Phase of flight
Initial climb
Aircraft
N6592TCessna 150
Status
Completed · report May 9, 1966
Report
Brief approved by the director
Case key
174080

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-0050  66/3/14    LAS CRUCES N MEX    CESSNA 150          CR-  0  1  1  INSTRUCTIONAL             COMMERCIAL, FL.INSTR.,
        TIME - 1800                    N6592T              PX-  0  0  0  DUAL                      AGE 54, 13500 TOTAL
                                       DAMAGE-DESTROYED    OT-  0  0  0                            HOURS, 250 IN TYPE,
                                                                                                   INSTRUMENT RATED.
        NAME OF AIRPORT - LAS CRUCES
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL: MUSH                                              TAKEOFF: INITIAL CLIMB
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED
        REMARKS- DOWNWIND TAKE-OFF.

Aircraft

Registration
N6592T
Reported as
Cessna 150
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Las Cruces

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.