NYC65D0210

NTSB accident investigation · Piper PA-28 · Port Allegany, PA · April 24, 1965

Accident · No injuriesClosed
Date
April 24, 1965
Place
Port Allegany, PA · PORT ALLEGANY, PA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Takeoff
Aircraft
N5329WPiper PA-28
Status
Completed · report June 24, 1965
Report
Brief approved by the director
Case key
179215

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-0995  65/4/24    PORT ALLEGANY PA    PIPER PA-28         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 41, 1000
        TIME - 0930                    N5329W              PX-  0  0  0  BUSINESS                  TOTAL HOURS, 30 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - JOHNSON STRIP
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GEAR COLLAPSED                                           TAKEOFF: ABORTED
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - SELECTED UNSUITABLE TERRAIN
           AIRPORTS/AIRWAYS/FACILITIES - AIRPORT CONDITIONS: SOFT RUNWAY
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N5329W
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Johnson Strip

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.