UNK65X0955

NTSB accident investigation · Cessna 310B · Hopkins, MN · December 8, 1964

Accident · No injuriesClosed
Date
December 8, 1964
Place
Hopkins, MN · HOPKINS, MN
Injuries
4 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N547MCessna 310B
Status
Completed · report January 26, 1965
Report
Brief approved by the director
Case key
180336

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-3761   64/12/8   HOPKINS MINN        CESSNA 310B         CR-  0  0  1  NONCOMMERCIAL             COMMERCIAL, AGE 45, 3543
        TIME - 1930                    N547M               PX-  0  0  3  BUSINESS                  TOTAL HOURS, 259 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            INSTRUMENT RATED.
        NAME OF AIRPORT - FLYING CLOUD
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           UNDERSHOOT                                               LANDING: FINAL APPROACH
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - MISJUDGED DISTANCE AND ALTITUDE
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - AIRFRAME ICE

Aircraft

Registration
N547M
Reported as
Cessna 310B
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Flying Cloud

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.