UNK64X1808

NTSB accident investigation · Piper PA22 · Albany, NY · May 17, 1964

Accident · No injuriesClosed
Date
May 17, 1964
Place
Albany, NY · ALBANY, NY
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N3339BPiper PA22
Status
Completed · report September 22, 1964
Report
Brief approved by the director
Case key
183977

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-1310  64/5/17  NR.ALBANY NY          PIPER PA22          CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 24, 136
        TIME - 0800                    N3339B              PX-  0  0  0  TRAINING                  TOTAL HOURS, 11 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - SOUTH ALBANY
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           OVERSHOOT                                                LANDING: ROLL
           COLLIDED WITH: TREES                                     LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - SELECTED WRONG RUNWAY RELATIVE TO EXISTING WIND
           MISCELLANEOUS ACTS,CONDITIONS - DOWNWIND

Aircraft

Registration
N3339B
Reported as
Piper PA22
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
South Albany

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.