CHI69F0136

NTSB accident investigation · Beech 35 · Byron, MI · July 25, 1968

Accident · No injuriesClosed
Date
July 25, 1968
Place
Byron, MI · BYRON, MI
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Takeoff
Aircraft
N89WBeech 35
Status
Completed · report September 23, 1968
Report
Brief approved by the director
Case key
109187

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-2359  68/7/25    BYRON,MICH          BEECH 35            CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 36, 209
        TIME - 1915                    N89W                PX-  0  0  0  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 66 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           COLLIDED WITH: CROP                                      TAKEOFF: RUN
           GEAR COLLAPSED                                           TAKEOFF: RUN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - SELECTED UNSUITABLE TERRAIN
           PILOT IN COMMAND - MISJUDGED CLEARANCE
           TERRAIN - WET,SOFT GROUND
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE
        REMARKS- STRUCK CORN.

Aircraft

Registration
N89W
Reported as
Beech 35
Category
Airplane
Engine
reciprocating
Damage
Substantial damage

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.