FTW69F0550

NTSB accident investigation · Piper PA-18 · Abilene, TX · May 31, 1969

Accident · No injuriesClosed
Date
May 31, 1969
Place
Abilene, TX · ABILENE, TX
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N2870PPiper PA-18
Status
Completed · report July 9, 1969
Report
Brief approved by the director
Case key
183779

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-1369  69/5/31    ABILENE,TEX         PIPER PA-18         CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 40, 556
        TIME - 1048                    N2870P              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 7 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - ABILENE
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER LEVEL OFF
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N2870P
Reported as
Piper PA-18
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Abilene

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.