CHI69F0627

NTSB accident investigation · Piper PA-12 · Milan, MI · May 3, 1969

Accident · No injuriesClosed
Date
May 3, 1969
Place
Milan, MI · MILAN, MI
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N7532HPiper PA-12
Status
Completed · report July 2, 1969
Report
Brief approved by the director
Case key
183264

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-1319   69/5/3    MILAN,MICH          PIPER PA-12         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 42, 735
        TIME - 1140                    N7532H              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 52 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - MILAN
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           UNDERSHOOT                                               LANDING: FINAL APPROACH
           GEAR COLLAPSED                                           LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND ALTITUDE
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE
        REMARKS- RT GR BENT.

Aircraft

Registration
N7532H
Reported as
Piper PA-12
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Milan

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.