FTW67F0133

NTSB accident investigation · Piper PA-28 · Pine Bluff, AR · August 28, 1966

Accident · No injuriesClosed
Date
August 28, 1966
Place
Pine Bluff, AR · PINE BLUFF, AR
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N6990WPiper PA-28
Status
Completed · report October 3, 1966
Report
Brief approved by the director
Case key
122123

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-2072  66/8/28    PINE BLUFF ARK      PIPER PA-28         CR-  0  0  1  NONCOMMERCIAL             STUDENT, AGE 31, 36 TOTAL
        TIME - 1123                    N6990W              PX-  0  0  0  PRACTICE                  HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - GRIDER FIELD
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER RECOVERY FROM BOUNCED LANDING
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N6990W
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Grider Field

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.