NYC67F0441

NTSB accident investigation · Piper PA-23 · Waterford, CT · December 15, 1966

Accident · No injuriesClosed
Date
December 15, 1966
Place
Waterford, CT · WATERFORD, CT
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N4249PPiper PA-23
Status
Completed · report April 6, 1967
Report
Brief approved by the director
Case key
119915

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-4114  66/12/15   WATERFORD CONN      PIPER PA-23         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 41, 190
        TIME - 1500                    N4249P              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, ALL IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - WATERFORD
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           WHEELS-UP                                                LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO ASSURE THE GEAR WAS DOWN AND LOCKED
        FACTOR(S)
           AIRFRAME - LANDING GEAR: LANDING GEAR WARNING AND INDICATING COMPONENTS
        REMARKS- GEAR WARNING HORN POINTS STICKING.

Aircraft

Registration
N4249P
Reported as
Piper PA-23
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Waterford

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.