MKC68F0232

NTSB accident investigation · Cessna 172 · Mercer, ND · September 10, 1967

Accident · Minor injuriesClosed
Date
September 10, 1967
Place
Mercer, ND · MERCER, ND
Injuries
1 minor
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N8165BCessna 172
Status
Completed · report December 20, 1967
Report
Brief approved by the director
Case key
113898

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-3740  67/9/10  NR.MERCER,N DAK       CESSNA 172          CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 51, 48 TOTAL
        TIME - 1800                    N8165B              PX-  0  0  0  TRAINING                  HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - MERCER
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - SELECTED UNSUITABLE TERRAIN
           AIRPORTS/AIRWAYS/FACILITIES - AIRPORT CONDITIONS: SOFT RUNWAY
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE
        REMARKS- LANDED ON PVT AIRSTRIP.

Aircraft

Registration
N8165B
Reported as
Cessna 172
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Mercer

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.