UNK64X2928

NTSB accident investigation · Piper PA28 · Blaney Park, MI · July 19, 1964

Accident · No injuriesClosed
Date
July 19, 1964
Place
Blaney Park, MI · BLANEY PARK, MI
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N5677WPiper PA28
Status
Completed · report October 15, 1964
Report
Brief approved by the director
Case key
183129

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-2146  64/7/19    BLANEY PARK MICH    PIPER PA28          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 46, 256
        TIME - 1700                    N5677W              PX-  0  0  2  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 108 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - BLANEY PARK
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER LEVEL OFF
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N5677W
Reported as
Piper PA28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Blaney Park

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.