MKC65F0031

NTSB accident investigation · Piper PA-20 · Bemidji, MN · January 4, 1965

Accident · No injuriesClosed
Date
January 4, 1965
Place
Bemidji, MN · BEMIDJI, MN
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N7020KPiper PA-20
Status
Completed · report April 16, 1965
Report
Brief approved by the director
Case key
179581

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-0381   65/1/4    BEMIDJI MINN        PIPER PA-20         CR-  0  0  1  MISCELLANEOUS             COMMERCIAL, AGE 45, 6200
        TIME - 1615                    N7020K              PX-  0  0  1  FERRY                     TOTAL HOURS, 200 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - MOBERG
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           NOSE OVER/DOWN                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - SELECTED UNSUITABLE TERRAIN
        FACTOR(S)
           AIRPORTS/AIRWAYS/FACILITIES - AIRPORT CONDITIONS: SNOW ON RUNWAY
        REMARKS- LANDING MADE ON 6 INCH DEEP CRUSTED SNOW.

Aircraft

Registration
N7020K
Reported as
Piper PA-20
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Moberg

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.