CHI67D0675

NTSB accident investigation · Cessna 180 · Eaton Rapids, MI · April 29, 1967

Accident · No injuriesClosed
Date
April 29, 1967
Place
Eaton Rapids, MI · EATON RAPIDS, MI
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N2284CCessna 180
Status
Completed · report September 7, 1967
Report
Brief approved by the director
Case key
117064

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-1356  67/4/29    EATON RAPIDS,MICH   CESSNA 180          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 40, 799
        TIME - 1115                    N2284C              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 186 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - RIGGLES FIELD
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           NOSE OVER/DOWN                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - SELECTED UNSUITABLE TERRAIN
           PILOT IN COMMAND - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING
           AIRPORTS/AIRWAYS/FACILITIES - AIRPORT CONDITIONS: SOFT RUNWAY

Aircraft

Registration
N2284C
Reported as
Cessna 180
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Riggles Field

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.