UNK64X3708

NTSB accident investigation · Piper PA28 · Pine Ridge, SD · August 31, 1964

Accident · No injuriesClosed
Date
August 31, 1964
Place
Pine Ridge, SD · PINE RIDGE, SD
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N8699WPiper PA28
Status
Completed · report November 4, 1964
Report
Brief approved by the director
Case key
185955

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-2710  64/8/31    PINE RIDGE S DAK    PIPER PA28          CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 52, 118
        TIME - 1330                    N8699W              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 99 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: DIRT BANK                                 LANDING: ROLL
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - SELECTED UNSUITABLE TERRAIN
           TERRAIN - ROUGH/UNEVEN
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N8699W
Reported as
Piper PA28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage

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.