MKC65F0101

NTSB accident investigation · Beechcraft B-35 · Big Fork, MN · January 21, 1965

Accident · No injuriesClosed
Date
January 21, 1965
Place
Big Fork, MN · BIG FORK, MN
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N5079CBeechcraft B-35
Status
Completed · report June 15, 1965
Report
Brief approved by the director
Case key
179657

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-0849  65/1/21    BIG FORK MINN       BEECHCRAFT B-35     CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 44, 638
        TIME - 1040                    N5079C              PX-  0  0  0  BUSINESS                  TOTAL HOURS, 306 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - BIG FORK
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GEAR COLLAPSED                                           LANDING: ROLL
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - SELECTED UNSUITABLE TERRAIN
        FACTOR(S)
           AIRPORTS/AIRWAYS/FACILITIES - AIRPORT CONDITIONS: SNOW ON RUNWAY
        REMARKS- 12 INCHES LOOSE SNOW ON RUNWAY

Aircraft

Registration
N5079C
Reported as
Beechcraft B-35
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Big Fork

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.