MKC69D0016

NTSB accident investigation · Piper PA-28 · Dundas, MN · May 30, 1968

Accident · No injuriesClosed
Date
May 30, 1968
Place
Dundas, MN · DUNDAS, MN
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Takeoff
Aircraft
N7490RPiper PA-28
Status
Completed · report July 25, 1968
Report
Brief approved by the director
Case key
110224

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-1599  68/5/30    DUNDAS,MINN         PIPER PA-28         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 21, 50 TOTAL
        TIME - 1600                    N7490R              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  HOURS, ALL IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: DITCHES                                   TAKEOFF: ABORTED
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - INADEQUATE PREFLIGHT PREPARATION AND/OR PLANNING
           PILOT IN COMMAND - SELECTED UNSUITABLE TERRAIN
        FACTOR(S)
           TERRAIN - HIGH VEGETATION
        REMARKS- TAKE OFF ATTEMPTED FROM ALFALFA FIELD. ALFALFA 2 FT HIGH.

Aircraft

Registration
N7490R
Reported as
Piper PA-28
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.