CHI69F0048

NTSB accident investigation · Piper J4E · Edinburg, IN · July 5, 1968

Accident · No injuriesClosed
Date
July 5, 1968
Place
Edinburg, IN · EDINBURG, IN
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N35906Piper J4E
Status
Completed · report August 6, 1968
Report
Brief approved by the director
Case key
110330

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-1765   68/7/5    EDINBURG,IND        PIPER J4E           CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 30, 54 TOTAL
        TIME - 1730                    N35906              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  HOURS, 33 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        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
           TERRAIN - HIGH VEGETATION
        REMARKS- PLT LANDED IN HAY FLD.

Aircraft

Registration
N35906
Reported as
Piper J4E
Category
Airplane
Engine
reciprocating
Damage
Substantial damage

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.