CHI67F0582

NTSB accident investigation · Cessna 172 · Cedar Lake, MI · April 8, 1967

Accident · No injuriesClosed
Date
April 8, 1967
Place
Cedar Lake, MI · CEDAR LAKE, MI
Injuries
4 uninjured
Damage
Substantial damage
Phase of flight
Takeoff
Aircraft
N4152FCessna 172
Status
Completed · report August 31, 1967
Report
Brief approved by the director
Case key
117501

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-1111   67/4/8    CEDAR LAKE,MICH     CESSNA 172          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 18, 96 TOTAL
        TIME - 1830                    N4152F              PX-  0  0  3  PLEASURE/PERSONAL TRANSP  HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - CEDAR LAKE
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GEAR COLLAPSED                                           TAKEOFF: RUN
        PROBABLE CAUSE(S)
           AIRPORTS/AIRWAYS/FACILITIES - AIRPORT CONDITIONS: SOFT RUNWAY
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE
        REMARKS- NOSE GEAR STRUCK SOFT SPOT ON SOD RUNWAY.PILOT AWARE OF RUNWAY CONDITION.

Aircraft

Registration
N4152F
Reported as
Cessna 172
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Cedar Lake

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.