DEN68F0144

NTSB accident investigation · Cessna 140 · Crown Pt, NM · November 11, 1967

Accident · No injuriesClosed
Date
November 11, 1967
Place
Crown Pt, NM · CROWN PT, NM
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N89436Cessna 140
Status
Completed · report January 10, 1968
Report
Brief approved by the director
Case key
112722

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-3921  67/11/11   CROWN PT. N MEX     CESSNA 140          CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 19, 268
        TIME - 1130                    N89436              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 182 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - CROWN POINT
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N89436
Reported as
Cessna 140
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Crown Point

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.