3 Oct 2021: BEECH S35

3 Oct 2021: BEECH S35 (N876T) — Unknown operator

2 fatalities • Andrews, NC, United States

Probable cause

The pilot’s decision to fly toward rapidly rising, obscured mountainous terrain after departing under visual flight rules at night.

— NTSB Determination

Accident narrative

HISTORY OF FLIGHTOn October 3, 2021, about 1949 eastern daylight time, a Beech S35, N876T, was destroyed when it was involved in an accident near Andrews, North Carolina. The private pilot and one passenger were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

The pilot was performing the first leg of a cross-country flight to Pennsylvania that originated at Liberty Municipal Airport (T78), Liberty, Texas, about 1134 central daylight time with an intended destination of Macon County Airport (1A5), Franklin, North Carolina. Due to weather conditions, the pilot diverted to Western Carolina Regional Airport (RHP) in Andrews. A witness on the ramp, who was also a pilot, reported that the accident pilot entered the left downwind of the airport traffic pattern for runway 8 from the east and flew north of the runway; however, the published traffic pattern for runway 8 was right traffic (due to rising terrain north of the runway). The witness further reported that the pilot’s first approach was too fast, and he performed a go-around. The pilot continued to fly a left traffic pattern and landed on his second attempt.   While on the ground at RHP, the pilot purchased 60 gallons of 100 low lead aviation fuel, received a weather briefing through Leidos Flight Service, and filed an instrument flight rules flight plan to Lancaster Airport (LNS), Lancaster, Pennsylvania.   The airplane was equipped with a handheld GPS receiver that was found inside the wreckage. The recovered data revealed that the airplane departed runway 8 at 1945 and made a slight left turn toward the northeast and mountainous terrain (figure 1). The airplane continued to climb at a rate of about 700 fpm, and at a groundspeed of about 95-100 knots for about 3 minutes and 20 seconds. The altitude peaked at 4,011 ft GPS altitude at 1948:57, and the last GPS position was recorded at 1949:00. At that time, the airplane suddenly turned to the right 11°, descended about 31 ft, and slowed by 25 knots of groundspeed. The last GPS position was located about 518 ft southwest of the accident site at an elevation of about 3,880 ft. The elevation at RHP was 1,698 ft.

Figure 1 - Airplane's GPS-derived departure track (magenta overlay) from runway 8 toward the rising terrain northeast of the airport. PERSONNEL INFORMATIONAccording to a witness, the pilot recently transitioned from a Piper PA-28 equipped with fixed landing gear to the accident airplane, which he purchased in June 2021.

The pilot’s logbook was not located. The flight instructor who administered the pilot’s most recent flight review reported that the pilot had logged about 2,100 hours of flight time. A review of ADS-B data revealed that, after its purchase, the pilot flew the airplane about 51 hours. METEOROLOGICAL INFORMATIONThe RHP weather at 1945 included scattered clouds at 1,400 ft, broken clouds at 3,200 ft, and 7 miles visibility in rain. Sunset at Andrews was about 1916 and the end of civil twilight was about 1941.

According to the National Weather Service Surface Analysis Chart, a stationary front stretched from Michigan southwestward through the Ohio Valley and into Mississippi at the time of the accident. A low pressure system was located in southern Michigan, along the front. The accident site was located to the east of the stationary front in an area of southerly and calm surface winds. The accident site was located east of a low- and mid-level trough. Troughs can act as lifting mechanisms to help produce clouds and precipitation if sufficient moisture is present.

The station models around the accident site depicted air temperatures in the mid-60s degrees F with temperature-dewpoint spreads of 1°F or less. Cloudy skies and light rain were reported at airports to the east of the accident site.

The Leidos Flight Service specialist provided weather information to the pilot, including convective SIGMETs, AIRMETs, and TAFs valid at 1839. When asked by the specialist if the pilot would be filing instrument flight rules (IFR) or visual flight rules (VFR), the pilot responded, “IFR, if we have to. I don’t think, I don’t think VFR is going to be possible.” The specialist also informed the pilot, “…mountain tops obscured in the higher terrain pretty much for your entire route of flight.” The specialist, when briefing the SIGMETs and approaching convective weather from the south of the departure airport, stated, “Looks like the sooner you can get out of there the better.” WRECKAGE AND IMPACT INFORMATIONThe highly fragmented wreckage was found on steep, mountainous, wooded terrain. An examination of the accident site and wreckage revealed that all major structural components of the airplane were accounted for. The airplane collided with a tall pine tree and continued 600 ft before colliding with another tree. The main wreckage impacted the terrain in a steep, nose low attitude and came to rest, inverted. Both wings and the ruddervator separated during the impact sequence. The wing flaps were found in the retracted positions. The landing gear drive system was observed in the “gear extended” position, and the cockpit gear switch was found in the “gear down” position. Numerous tree branches were observed along the wreckage patch that exhibited smooth, 45° cuts and black paint transfer, consistent with propeller blade contact.

The wreckage was recovered to a salvage facility where additional examination was performed. Flight control continuity was confirmed from the cockpit controls to each flight control surface bellcrank. Examination of the engine did not reveal any evidence of a preexisting anomaly or malfunction. The propeller blades exhibited s-bending and blade twisting; two blade tips were separated.

The landing gear switch was tested and performed in a normal manner. The landing gear position light bulbs were examined: the “up” bulb filament was broken from its leads. The “down” bulb filament remained attached it its leads and appeared stretched. MEDICAL AND PATHOLOGICAL INFORMATIONAccording to autopsy report from the Wake Forest Baptist Medical Center, Winston-Salem, North Carolina, the cause of death of the pilot was multiple blunt force injuries and the manner of death was accident. Testing for ethanol and drugs was negative.

Contributing factors

  • Pilot
  • Decision related to condition
  • Effect on operation
  • Effect on operation

Conditions

Weather
IMC, vis 7sm

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.