DEN70D0152

NTSB accident investigation · Cessna 172 · Moriarty, NM · December 12, 1969

Accident · No injuriesClosed
Date
December 12, 1969
Place
Moriarty, NM · MORIARTY, NM
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Takeoff
Aircraft
N8292XCessna 172
Status
Completed · report May 26, 1970
Report
Brief approved by the director
Case key
144893

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-4494  69/12/12   MORIARTY,N MEX      CESSNA 172          CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 39, 101
        TIME - 1700                    N8292X              PX-  0  0  0  TRAINING                  TOTAL HOURS, 53 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - MORIARTY
        DEPARTURE POINT             INTENDED DESTINATION
          MORIARTY,N MEX              ALBUQUERQUE,N MEX
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 TAKEOFF: RUN
           COLLIDED WITH: DIRT BANK                                 TAKEOFF: RUN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL

Aircraft

Registration
N8292X
Reported as
Cessna 172
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Moriarty

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.