MKC67F0034

NTSB accident investigation · Piper J3C · New England, ND · June 19, 1966

Accident · Serious injuriesClosed
Date
June 19, 1966
Place
New England, ND · NEW ENGLAND, ND
Injuries
2 serious
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N37916Piper J3C
Status
Completed · report December 14, 1966
Report
Brief approved by the director
Case key
171546

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
----------------------------------------------------------------------------------------------------------------------------
2-0459  66/6/19    NEW ENGLAND N DAK   PIPER J3C           CR-  0  1  0  NONCOMMERCIAL             PRIVATE, AGE 42, 300
        TIME - 1930                    N37916              PX-  0  1  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, ALL IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - NEW ENGLAND
        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
N37916
Reported as
Piper J3C
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
New England

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.