CHI69F0518

NTSB accident investigation · Beech B35 · Gladwin, MI · March 2, 1969

Accident · No injuriesClosed
Date
March 2, 1969
Place
Gladwin, MI · GLADWIN, MI
Injuries
4 uninjured
Damage
Substantial damage
Phase of flight
Takeoff
Aircraft
N5197CBeech B35
Status
Completed · report June 2, 1969
Report
Brief approved by the director
Case key
190992

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-0649   69/3/2    GLADWIN,MICH        BEECH B35           CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 60, 815
        TIME - 1705                    N5197C              PX-  0  0  3  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 147 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - GLADWIN
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 TAKEOFF: RUN
           COLLIDED WITH: SNOWBANK                                  TAKEOFF: RUN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL
        FACTOR(S)
           AIRPORTS/AIRWAYS/FACILITIES - AIRPORT CONDITIONS: WET RUNWAY

Aircraft

Registration
N5197C
Reported as
Beech B35
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Gladwin

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.