MKC71DCD42

NTSB accident investigation · Piper PA-22 · Sibley, IA · December 27, 1970

Accident · No injuriesClosed
Date
December 27, 1970
Place
Sibley, IA · SIBLEY, IA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N6836BPiper PA-22
Status
Completed · report October 4, 1971
Report
Brief approved by the director
Case key
159594

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-4510  70/12/27   SIBLEY,IOWA         PIPER PA-22         CR-  0  0  1  INSTRUCTIONAL             STUDENT, AGE 59, 39 TOTAL
        TIME - 1030                    N6836B              PX-  0  0  0  TRAINING                  HOURS, 18 IN TYPE, NOT
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - SIBLEY
        DEPARTURE POINT             INTENDED DESTINATION
          SIBLEY,IOWA                 LOCAL
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           COLLIDED WITH: SNOWBANK                                  LANDING: ROLL
        PROBABLE CAUSE(S)
          PILOT-SHOE HEEL WEDGED L RUDDER AND SCUFF PLATE.

Aircraft

Registration
N6836B
Reported as
Piper PA-22
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Sibley

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.