CHI66F0305

NTSB accident investigation · Cessna 172B · Cheboygan, MI · September 4, 1965

Accident · No injuriesClosed
Date
September 4, 1965
Place
Cheboygan, MI · CHEBOYGAN, MI
Injuries
4 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N8056XCessna 172B
Status
Completed · report October 26, 1965
Report
Brief approved by the director
Case key
175522

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-2662   65/9/4    CHEBOYGAN MICH      CESSNA 172B         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 35, 139
        TIME - 1000                    N8056X              PX-  0  0  3  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 134 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - MARKS
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           GEAR COLLAPSED                                           LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER LEVEL OFF
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N8056X
Reported as
Cessna 172B
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Marks

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.