CHI66F0660

NTSB accident investigation · Piper PA-28 · Grand Rapids, MI · March 28, 1966

Accident · No injuriesClosed
Date
March 28, 1966
Place
Grand Rapids, MI · GRAND RAPIDS, MI
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N5719WPiper PA-28
Status
Completed · report May 16, 1966
Report
Brief approved by the director
Case key
172588

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-0731  66/3/28    GRAND RAPIDS MICH   PIPER PA-28         CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 20, 12 TOTAL
        TIME - 1100                    N5719W              PX-  0  0  0  PRACTICE                  HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - KENT COUNTY
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           GEAR COLLAPSED                                           LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER LEVEL OFF
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N5719W
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Kent 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.