NYC69D0409

NTSB accident investigation · Piper PA-22 · Bridgeport, CT · April 6, 1969

Accident · No injuriesClosed
Date
April 6, 1969
Place
Bridgeport, CT · BRIDGEPORT, CT
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Taxi
Aircraft
N4672ZPiper PA-22
Status
Completed · report June 9, 1969
Report
Brief approved by the director
Case key
191083

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-0806   69/4/6    BRIDGEPORT,CONN     PIPER PA-22         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 28, 172
        TIME - 1300                    N4672Z              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 89 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - BRIDGEPORT
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           NOSE OVER/DOWN                                           TAXI: TO TAKEOFF
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - EXERCISED POOR JUDGMENT
           MISCELLANEOUS - PROP/JET/ROTOR BLAST
        REMARKS- N4672Z TAXIED BEHIND B26 ACFT RUNNING BOTH ENGINES AT 1800 RPM.SURFACE WIND 20K.

Aircraft

Registration
N4672Z
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.