MIA67F0134

NTSB accident investigation · Beech G17S · Atlanta, GA · June 23, 1966

Accident · No injuriesClosed
Date
June 23, 1966
Place
Atlanta, GA · ATLANTA, GA
Injuries
4 uninjured
Damage
Substantial damage
Phase of flight
Takeoff
Aircraft
N291YBeech G17S
Status
Completed · report October 4, 1966
Report
Brief approved by the director
Case key
170999

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-2080  66/6/23    ATLANTA GA          BEECH G17S          CR-  0  0  1  NONCOMMERCIAL             PRIVATE, AGE 37, 226
        TIME - 0730                    N291Y               PX-  0  0  3  PLEASURE/PERSONAL TRANSP  TOTAL HOURS, 120 IN TYPE,
                                       DAMAGE-SUBSTANTIAL  OT-  0  0  0                            NOT INSTRUMENT RATED.
        NAME OF AIRPORT - FULTON COUNTY
        TYPE OF ACCIDENT                                         PHASE OF OPERATION
           GROUND-WATER LOOP-SWERVE                                 TAKEOFF: RUN
           GEAR COLLAPSED                                           TAKEOFF: RUN
        PROBABLE CAUSE(S)
           PILOT IN COMMAND - FAILED TO MAINTAIN DIRECTIONAL CONTROL
        FACTOR(S)
           MISCELLANEOUS ACTS,CONDITIONS - OVERLOAD FAILURE

Aircraft

Registration
N291Y
Reported as
Beech G17S
Category
Airplane
Engine
reciprocating
Damage
Substantial damage
Airport
Fulton County

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.