NYC69D0468

NTSB accident investigation · Piper J3C-65 · New Milford, CT · May 4, 1969

Accident · Minor injuriesClosed
Date
May 4, 1969
Place
New Milford, CT · NEW MILFORD, CT
Injuries
1 minor
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N3314NPiper J3C-65
Status
Completed · report August 13, 1969
Report
Brief approved by the director
Case key
175255

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-1831   69/5/4    NEW MILFORD,CONN    PIPER J3C-65        CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 52, 3000
        TIME - 1515                    N3314N              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 4 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - DOCKTOR STRIP
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           UNDERSHOOT                                               LANDING: FINAL APPROACH
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND ALTITUDE
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N3314N
Reported as
Piper J3C-65
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Docktor Strip

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.