MIA68F0531

NTSB accident investigation · Piper PA-28 · Gadsden, AL · May 31, 1968

Accident · No injuriesClosed
Date
May 31, 1968
Place
Gadsden, AL · GADSDEN, AL
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N5828WPiper PA-28
Status
Completed · report June 26, 1968
Report
Brief approved by the director
Case key
110060

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-1277  68/5/31    GADSDEN,ALA         PIPER PA-28         CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 24, 24 TOTAL
        TIME - 1115                    N5828W              PX-  0  0  0  TRAINING                  HOURS, 15 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - GADSDEN
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: LEVEL OFF/TOUCHDOWN
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - IMPROPER OPERATION OF BRAKES AND/OR FLIGHT CONTROLS
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N5828W
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Gadsden

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.