MKC68D0198

NTSB accident investigation · Cessna 182H · Hammond, KS · August 19, 1967

Accident · No injuriesClosed
Date
August 19, 1967
Place
Hammond, KS · HAMMOND, KS
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N2434XCessna 182H
Status
Completed · report December 18, 1967
Report
Brief approved by the director
Case key
113732

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-3451  67/8/19    HAMMOND,KANS        CESSNA 182H         CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 37, 200
        TIME - 1400                    N2434X              PX-  0  0  0  SOLO                      TOTAL HOURS, 6 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - SELECTED UNSUITABLE TERRAIN
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE
           TERRAIN - WET,SOFT GROUND
           TERRAIN - HIGH VEGETATION
        REMARKS- UNAUTHORIZED LNDG ON FARM FIELD,16 INCH THICK GRASS.

Aircraft

Registration
N2434X
Reported as
Cessna 182H
Category
Airplane
Engine
reciprocating
Damage
Substantial damage

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.