SEA71DXM25

NTSB accident investigation · Piper PA-32 · Preston, ID · February 12, 1971

Accident · No injuriesClosed
Date
February 12, 1971
Place
Preston, ID · PRESTON, ID
Injuries
4 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N3213WPiper PA-32
Status
Completed · report December 10, 1971
Report
Brief approved by the director
Case key
160102

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-0746  71/2/12    PRESTON,ID          PIPER PA-32         CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 34, 261
        TIME - 1945                    N3213W              PX-  0  0  3  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 64 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - PRESTON
        DEPARTURE POINT             INTENDED DESTINATION
          SALT LAKE CITY,UT           PRESTON,ID
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 LANDING: ROLL
           COLLIDED WITH: SNOWBANK                                  LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL

Aircraft

Registration
N3213W
Reported as
Piper PA-32
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Preston

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.