CHI65F0013

NTSB accident investigation · Beechraft H35 · Fraser, MI · January 3, 1965

Accident · No injuriesClosed
Date
January 3, 1965
Place
Fraser, MI · FRASER, MI
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Initial climb
Aircraft
N5556DBeechraft H35
Status
Completed · report March 24, 1965
Report
Brief approved by the director
Case key
180132

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-0245   65/1/3    FRASER MICH         BEECHRAFT H35       CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 39, 300
        TIME - 1430                    N5556D              PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 250 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - MCKINLEY
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           ENGINE FAILURE OR MALFUNCTION                            TAKEOFF: INITIAL CLIMB
           WHEELS-UP                                                TAKEOFF: ABORTED
        PROBABLE CAUSE(S)
           POWERPLANT - MISCELLANEOUS: POWERPLANT FAILURE FOR UNDETERMINED REASONS
        PARTIAL POWER LOSS - PARTIAL LOSS OF POWER - 1 ENGINE

Aircraft

Registration
N5556D
Reported as
Beechraft H35
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Mckinley

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.