CHI68F0303

NTSB accident investigation · Piper PA-22 · Plymouth, MI · October 11, 1967

Accident · No injuriesClosed
Date
October 11, 1967
Place
Plymouth, MI · PLYMOUTH, MI
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N5100ZPiper PA-22
Status
Completed · report December 26, 1967
Report
Brief approved by the director
Case key
113182

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-3643  67/10/11   PLYMOUTH,MICH       PIPER PA-22         CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 32, 13 TOTAL
        TIME - 1130                    N5100Z              PX-  0  0  0  TRAINING                  HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - METTETAL
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           COLLIDED WITH: PARKED AIRCRAFT                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER OPERATION OF BRAKES AND/OR FLIGHT CONTROLS
        REMARKS- PARKED ACFT-CESSNA 150 N6569S,SUBSTANTIAL DAMAGE

Aircraft

Registration
N5100Z
Reported as
Piper PA-22
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Mettetal

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.