DEN69F0090

NTSB accident investigation · Cessna 172 · Lordsburg, NM · August 30, 1968

Accident · No injuriesClosed
Date
August 30, 1968
Place
Lordsburg, NM · LORDSBURG, NM
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N6724ACessna 172
Status
Completed · report October 30, 1968
Report
Brief approved by the director
Case key
109065

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-3016  68/8/30    LORDSBURG,NM        CESSNA 172          CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 45, 1600
        TIME - 1815                    N6724A              PX-  0  0  1  BUSINESS                  TOTAL HOURS, 700 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - LORDSBURG
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           DRAGGED WINGTIP,POD,OR FLOAT                             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
N6724A
Reported as
Cessna 172
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Lordsburg

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.