CHI66F0757

NTSB accident investigation · Cessna 150 · Lansing, MI · May 22, 1966

Accident · No injuriesClosed
Date
May 22, 1966
Place
Lansing, MI · LANSING, MI
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N2506JCessna 150
Status
Completed · report July 1, 1966
Report
Brief approved by the director
Case key
172253

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-1117  66/5/22    LANSING MICH        CESSNA 150          CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 26, 27 TOTAL
        TIME - 1337                    N2506J              PX-  0  0  0  SOLO                      HOURS, 13 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - CAPITOL CITY
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER OPERATION OF BRAKES AND/OR FLIGHT CONTROLS
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N2506J
Reported as
Cessna 150
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Capitol City

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.