1 Jun 2023: BEECH V35A

1 Jun 2023: BEECH V35A (N8074R) — Unknown operator

No fatalities • Statesboro, GA, United States

Probable cause

Maintenance personnel’s improper installation of the pitch servo bridle cable clamp, which led to binding in the elevator control system that restricted aft yoke movement during the landing approach.

— NTSB Determination

Accident narrative

On June 1, 2023, about 1455 eastern daylight time, a Beech V35A, N8074R, was substantially damaged when it was involved in an accident near Statesboro County Airport (TBR), Statesboro, Georgia. The pilot sustained minor injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot reported that he was testing the function of newly installed servos for the Garmin GFC-500 autopilot and calibrating the fuel flow sensor. During the preflight inspection, he moved the yoke and checked all control surface movements. He programmed the flight director, setting a cruising altitude of 3,000 ft with a pitch climb between 5° and 7°. During the takeoff roll, the pilot noted the controls felt "slightly heavy" and adjusted the ruddervator trim to nose-up using the electric trim switch. After liftoff, he engaged the autopilot, and the airplane climbed and maintained 3,000 ft. Throughout the flight, the pilot issued heading change commands via the GFC-500 display. After about an hour, the pilot programmed the autopilot to descend to 2,000 ft in preparation for landing at TBR. However, the autopilot failed to intercept the waypoint he had set. He disconnected the autopilot and assumed manual control. While on approach, he noticed the airplane was descending to an altitude lower than intended. He applied power, but the nose suddenly pitched down. Despite verifying that the autopilot was disconnected, he was unable to move the yoke aft. The airplane continued descending and he struggled to regain control. On the final approach, the airplane impacted a light pole about 1,000 ft short of the runway threshold before colliding with the ground and coming to a stop. Postaccident examination of the airplane revealed an anomaly with the pitch servo bridle cable installation. The bridle cable clamp’s swaged ball fitting was positioned at the 1 o’clock position with the yoke in a full-forward position. However, installation instructions in the GFC 500 Installation Manual Addendum specified that the swaged ball should be at 1 o’clock with the yoke in the neutral position—defined as 4.5 inches aft of the instrument panel, per the Bonanza 35 Series Shop Manual, Page 3-6C (Elevator Rigging Procedure, Serials D-5726 and after). This installation resulted in the bridle cable clamp being positioned on the upper elevator cable such that it would bind against the former rib at flight station (F.S.) 179 when the yoke was pulled aft. Further examination determined that the installer did not verify the required .5- to 1-inch clearance between the bridle cable clamp and F.S. 179 when the elevator was in the full-up position, as specified in the installation manual addendum. Additionally, the installer did not follow the required procedures outlined in the GFC 500 Autopilot with ESP Part 23 AML Installation Manual, paragraph 4.2.1 (Page 45), which required: 1. Moving the flight controls through their full range of travel after servo installation and cable tensioning. 2. Ensuring that flight control surfaces move freely from stop to stop. 3. Verifying that no binding or restriction of flight controls resulted from the servo installation. 4. Confirming that servo cables, cable clamps, and main flight control cables maintained adequate clearance from adjacent structures and feed-through holes throughout the full range of motion. During an interview, the personnel from the maintenance facility who performed the installation acknowledged that the GFC-500 installation had been performed incorrectly.

Contributing factors

  • Maintenance personnel
  • Malfunction

Conditions

Weather
VMC, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.