NYC67D0033

NTSB accident investigation · Piper PA-24 · Poestenkill, NY · June 3, 1966

Accident · No injuriesClosed
Date
June 3, 1966
Place
Poestenkill, NY · POESTENKILL, NY
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N8190PPiper PA-24
Status
Completed · report August 10, 1966
Report
Brief approved by the director
Case key
171317

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-1476   66/6/3    POESTENKILL NY      PIPER PA-24         CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 35, 278
        TIME - 1700                    N8190P              PX-  0  0  2  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 4 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - SICHO
        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
N8190P
Reported as
Piper PA-24
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Sicho

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.