CHI69F0013

NTSB accident investigation · Piper PA-28 · Lapeer, MI · June 15, 1968

Accident · Serious injuriesClosed
Date
June 15, 1968
Place
Lapeer, MI · LAPEER, MI
Injuries
1 serious
Damage
Destroyed
Phase of flight
Landing
Aircraft
N3492KPiper PA-28
Status
Completed · report July 29, 1968
Report
Brief approved by the director
Case key
115011

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-1661  68/6/15    LAPEER,MICH         PIPER PA-28         CR-  0  1  0  INSTRUCTIONAL             STUDENT, AGE 43, 21 TOTAL
        TIME - 1005                    N3492K              PX-  0  0  0  SOLO                      HOURS, 18 IN TYPE, NOT
                                       DAMAGE-DESTROYED    OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - DUPONT-LAPEER
        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 RECOVERY FROM BOUNCED LANDING
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N3492K
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Destroyed
Airport
Dupont-Lapeer

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.