DEN80DTK22

NTSB accident investigation · Piper PA-11 · Olsonville, SD · September 14, 1980

Accident · No injuriesClosed
Date
September 14, 1980
Place
Olsonville, SD · OLSONVILLE, SD
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N4818MPiper PA-11
Status
Completed · report November 4, 1980
Report
Brief approved by the director
FAA report
19800914041549A
Case key
128967

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-2548  80/9/14    OLSONVILLE,SD       PIPER PA-11         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 25, 298
        TIME - 1800                    N4818M              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 295 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - PRIVATE
        DEPARTURE POINT             INTENDED DESTINATION
          VALENTINE,NE                OLSONVILLE,SD
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: OBJECT                                    LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED CLEARANCE
        REMARKS- COLLIDED WITH FARM MACHINERY.

Aircraft

Registration
N4818M
Reported as
Piper PA-11
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Private

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.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.