CHI67D0216

NTSB accident investigation · Piper PA-22 · Midlothain, IL · July 30, 1966

Accident · No injuriesClosed
Date
July 30, 1966
Place
Midlothain, IL · MIDLOTHAIN, IL
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N5857ZPiper PA-22
Status
Completed · report November 4, 1966
Report
Brief approved by the director
Case key
121679

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-2478  66/7/30    MIDLOTHAIN ILL      PIPER PA-22         CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 20, 45 TOTAL
        TIME - 1430                    N5857Z              PX-  0  0  0  SOLO                      HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - HOWELL
        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 RECOVERY FROM BOUNCED LANDING
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N5857Z
Reported as
Piper PA-22
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Howell

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.