NYC67F0094

NTSB accident investigation · Piper PA-28 · Poestenkill, NY · July 24, 1966

Accident · No injuriesClosed
Date
July 24, 1966
Place
Poestenkill, NY · POESTENKILL, NY
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N6350RPiper PA-28
Status
Completed · report August 17, 1966
Report
Brief approved by the director
Case key
121941

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-1769  66/7/24    POESTENKILL NY      PIPER PA-28         CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 32, 25 TOTAL
        TIME - 1810                    N6350R              PX-  0  0  0  SOLO                      HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - POESTEN SICHO
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: LEVEL OFF/TOUCHDOWN
           NOSE OVER/DOWN                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER OPERATION OF FLIGHT CONTROLS
        REMARKS- AIRCRAFT LANDED IN CRAB.

Aircraft

Registration
N6350R
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Poesten 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.