CHI67F0089

NTSB accident investigation · Piper PA-28 · Troy, MI · July 6, 1966

Accident · No injuriesClosed
Date
July 6, 1966
Place
Troy, MI · TROY, MI
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N4689RPiper PA-28
Status
Completed · report August 26, 1966
Report
Brief approved by the director
Case key
170882

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-1797   66/7/6    TROY MICH           PIPER PA-28         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 52, 1100
        TIME - 1015                    N4689R              PX-  0  0  0  PRACTICE                  TOTAL HOURS, 7 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - BERZ
        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

Aircraft

Registration
N4689R
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Berz

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.