MKC69D0361

NTSB accident investigation · Piper PA-28 · Fort Dodge, IA · March 7, 1969

Accident · No injuriesClosed
Date
March 7, 1969
Place
Fort Dodge, IA · FORT DODGE, IA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N7591RPiper PA-28
Status
Completed · report May 19, 1969
Report
Brief approved by the director
Case key
190850

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-0474   69/3/7    FORT DODGE,IOWA     PIPER PA-28         CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 44, 11 TOTAL
        TIME - 1130                    N7591R              PX-  0  0  0  SOLO                      HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - FORT DODGE
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           UNDERSHOOT                                               LANDING: FINAL APPROACH
           COLLIDED WITH: SNOWBANK                                  LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE,SPEED,AND ALTITUDE
        REMARKS- 3RD LNDG OF 1ST SOLO FLT.

Aircraft

Registration
N7591R
Reported as
Piper PA-28
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Fort Dodge

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.