UNK64X1937

NTSB accident investigation · Piper PA22 · Selinsgrove, PA · May 24, 1964

Accident · No injuriesClosed
Date
May 24, 1964
Place
Selinsgrove, PA · SELINSGROVE, PA
Injuries
4 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N3048ZPiper PA22
Status
Completed · report September 24, 1964
Report
Brief approved by the director
Case key
184094

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-1415  64/5/24    SELINSGROVE PA      PIPER PA22          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 27, 53 TOTAL
        TIME - 1000                    N3048Z              PX-  0  0  3  PLEASURE/PERSONAL TRANSP  HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - PENN VALLEY
        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
N3048Z
Reported as
Piper PA22
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Penn Valley

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.