NYC65F0043

NTSB accident investigation · Piper PA22 · Seneca Falls, NY · February 6, 1965

Accident · No injuriesClosed
Date
February 6, 1965
Place
Seneca Falls, NY · SENECA FALLS, NY
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N6154DPiper PA22
Status
Completed · report March 25, 1965
Report
Brief approved by the director
Case key
180158

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-0273   65/2/6    SENECA FALLS NY     PIPER PA22          CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 26, 47 TOTAL
        TIME - 1400                    N6154D              PX-  0  0  0  PRACTICE                  HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - SENECA FALLS
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: SNOWBANK                                  LANDING: LEVEL OFF/TOUCHDOWN
           NOSE OVER/DOWN                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           MISCELLANEOUS ACTS,CONDITIONS - NOT ALIGNED WITH RUNWAY/INTENDED LANDING AREA

Aircraft

Registration
N6154D
Reported as
Piper PA22
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Seneca Falls

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.