NYC67D0116

NTSB accident investigation · Piper PA-22 · Bridgeport, NJ · July 24, 1966

Accident · No injuriesClosed
Date
July 24, 1966
Place
Bridgeport, NJ · BRIDGEPORT, NJ
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N3228ZPiper PA-22
Status
Completed · report September 12, 1966
Report
Brief approved by the director
Case key
122030

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-1983  66/7/24    BRIDGEPORT NJ       PIPER PA-22         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 47, 2097
        TIME - 2100                    N3228Z              PX-  0  0  2  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 350 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - BRIDGEPORT
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: ROLL
           COLLIDED WITH: DITCHES                                   LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND SPEED
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - DOWNWIND

Aircraft

Registration
N3228Z
Reported as
Piper PA-22
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Bridgeport

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.