CHI67D0014

NTSB accident investigation · Piper PA22 · Janesville, WI · May 30, 1966

Accident · No injuriesClosed
Date
May 30, 1966
Place
Janesville, WI · JANESVILLE, WI
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N5156ZPiper PA22
Status
Completed · report August 5, 1966
Report
Brief approved by the director
Case key
171268

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-1428  66/5/30    JANESVILLE WIS      PIPER PA22          CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 46, 18 TOTAL
        TIME - 1843                    N5156Z              PX-  0  0  0  SOLO                      HOURS, 8 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - ROCK COUNTY
        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
N5156Z
Reported as
Piper PA22
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Rock County

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.