MKC70D0123

NTSB accident investigation · Piper PA-28 · Sac City, IA · August 5, 1969

Accident · No injuriesClosed
Date
August 5, 1969
Place
Sac City, IA · SAC CITY, IA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N5497WPiper PA-28
Status
Completed · report September 22, 1969
Report
Brief approved by the director
Case key
170256

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-2383   69/8/5    SAC CITY,IOWA       PIPER PA-28         CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 44, 20 TOTAL
        TIME - 0530                    N5497W              PX-  0  0  0  SOLO                      HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - SAC CITY
        DEPARTURE POINT             INTENDED DESTINATION
          SAC CITY,IOWA               SAC CITY,IOWA
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           COLLIDED WITH: FENCE,FENCEPOSTS                          LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL

Aircraft

Registration
N5497W
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Sac City

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.