CHI69D0305

NTSB accident investigation · Piper PA-18 · Lansing, IL · September 28, 1968

Accident · No injuriesClosed
Date
September 28, 1968
Place
Lansing, IL · LANSING, IL
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N1232APiper PA-18
Status
Completed · report December 24, 1968
Report
Brief approved by the director
Case key
107917

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-3677  68/9/28    LANSING,ILL         PIPER PA-18         CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 16, 23 TOTAL
        TIME - 1230                    N1232A              PX-  0  0  0  TRAINING                  HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - CHICAGO-HAMMOND
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER LEVEL OFF
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N1232A
Reported as
Piper PA-18
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Chicago-Hammond

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.