MKC73DTK07

NTSB accident investigation · Piper PA-22 · Mioland, SD · October 7, 1972

Accident · Minor injuriesClosed
Date
October 7, 1972
Place
Mioland, SD · MIOLAND, SD
Injuries
2 minor
Damage
Destroyed
Phase of flight
Initial climb
Aircraft
N1426APiper PA-22
Status
Completed · report March 7, 1973
Report
Brief approved by the director
Case key
168971

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-3254   72/10/7   MIOLAND,S DAK       PIPER PA-22         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 40, 550
        TIME - 0850                    N1426A              PX-  0  0  1  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 373 IN TYPE,
                                       DAMAGE-DESTROYED    OT-  0  0  0                            NOT INSTRUMENT RATED.
        DEPARTURE POINT             INTENDED DESTINATION
          MIOLAND,S DAK               PIERRE,S DAK
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           STALL: MUSH                                              TAKEOFF: INITIAL CLIMB
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO OBTAIN/MAINTAIN FLYING SPEED
        FACTOR(S)
           TERRAIN - HIGH OBSTRUCTIONS
        REMARKS- R WING HIT POLE LOCATED ON RISING TRRN.

Aircraft

Registration
N1426A
Reported as
Piper PA-22
Category
Airplane
Engine
reciprocating
Damage
Destroyed

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.