CHI65F0018

NTSB accident investigation · Cessna 310B · Freeland, MI · January 4, 1965

Accident · No injuriesClosed
Date
January 4, 1965
Place
Freeland, MI · FREELAND, MI
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N5351ACessna 310B
Status
Completed · report March 24, 1965
Report
Brief approved by the director
Case key
180133

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-0246   65/1/4    FREELAND MICH       CESSNA 310B         CR-  0  0  2  INSTRUCTIONAL             COMMERCIAL, FL.INSTR.,
        TIME - 1630                    N5351A              PX-  0  0  0  DUAL                      AGE 52, 20850 TOTAL
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            HOURS, 475 IN TYPE,
                                                                                                   INSTRUMENT RATED.
        NAME OF AIRPORT - TRI CITY
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           HARD LANDING                                             LANDING: LEVEL OFF/TOUCHDOWN
        PROBABLE CAUSE(S)
           DUAL STUDENT - IMPROPER LEVEL OFF
           PILOT IN COMMAND - INADEQUATE SUPERVISION OF FLIGHT

Aircraft

Registration
N5351A
Reported as
Cessna 310B
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Tri City

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.