FTW68D0608

NTSB accident investigation · Beech C35 · Hamilton, TX · May 5, 1968

Accident · No injuriesClosed
Date
May 5, 1968
Place
Hamilton, TX · HAMILTON, TX
Injuries
4 uninjured
Damage
Substantial damage
Phase of flight
Takeoff
Aircraft
N1954DBeech C35
Status
Completed · report July 2, 1968
Report
Brief approved by the director
Case key
111003

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-1368   68/5/5    HAMILTON,TEX        BEECH C35           CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 36, 438
        TIME - 1700                    N1954D              PX-  0  0  3  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 2 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - HAMILTON
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 TAKEOFF: RUN
           COLLIDED WITH: RUNWAY OR APPROACH LIGHTS                 TAKEOFF: RUN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL
        REMARKS- PLT DID NOT REALIZE THE WINGS WERE DAMAGED,CONTINUED FLIGHT TO PLAINVIEW.

Aircraft

Registration
N1954D
Reported as
Beech C35
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Hamilton

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.