NTSB CAROL · Event
Event ERA22FA001
Registry · N876T
FAA Aircraft Registry record.
Make / Model
BEECH S35
Year of manufacture
1965 · 56 years old at event
Engine
CONT MOTOR IO 520 SERIES (285 hp)
Seats / Engines
6 seats · 1 engine
ADS-B equipped
Yes — Mode-S AC0E49
Registrant of record
HIGHRIDER LLC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot’s decision to fly toward rapidly rising, obscured mountainous terrain after departing under visual flight rules at night.
Factual 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. The pilot was conducting a personal, cross-country flight. As he approached a planned stop en route to his destination, he diverted to a nearby airport due to deteriorating weather conditions. A witness at the diversion airport reported that the pilot’s first approach was too fast, and he landed on his second attempt. Also, he flew visual traffic patterns contrary to what was published for the runway and toward rising terrain. Before departing again to resume the flight to the final destination, the pilot obtained a weather briefing by telephone. Based on the preflight weather briefing, the pilot was likely aware of the weather conditions along his route of flight, which included mountain obscuration. The pilot also seemed to be concerned with deteriorating weather conditions approaching the departure airport, which may have rushed him during his departure preparations. The weather at the time of his departure from the diversion airport included visual meteorological conditions; however, the mountainous terrain near the diversion airport was likely obscured with low clouds, rain, and drizzle. He subsequently departed about 4 minutes after the end of civil twilight. He took off and made a slight left turn toward rapidly rising terrain. While climbing, the airplane collided with trees, near the top of a mountain, about 5 miles from the airport. Postaccident examination of the wreckage found the landing gear extended and the cockpit landing gear switch in the “gear down” position, indicating that the pilot may have forgotten to raise the landing gear after takeoff. Leaving the landing gear extended after takeoff would have reduced the airplane’s climb rate. The pilot had recently purchased the accident airplane and his previous airplane was equipped with fixed landing gear. Examination of the remaining wreckage revealed no evidence of a preexisting mechanical failure or anomaly with the airplane. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- — Personnel issues-Action/decision-Info processing/decision-Decision making/judgment-Pilot
- — Environmental issues-Conditions/weather/phenomena-Light condition-Dark-Effect on operation
- — Environmental issues-Conditions/weather/phenomena-Ceiling/visibility/precip-Obscuration-Effect on operation
- — Environmental issues-Physical environment-Terrain-Mountainous/hilly terrain-Decision related to condition
Verbatim from NTSB's published report. Source file
NTSB_2021_ERA22FA001.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (go-around). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- NASA NTRS 2025 · Conference Paper
A Training Study to Improve Monitoring During A Go-Around
As part of an FAA program to improve go-around (GA) safety, we were asked to determine if we could improve the performance of the Pilot Monitoring (PM) during a GA maneuver.
- Flight Safety Foundation 2024 · FSF / AeroSafety World
Go-Around Safety Forum Findings
Foundation Go-Around Safety Forum technical findings — examines why pilots fail to execute go-arounds when criteria are met (stabilized approach gate not met, energy state out of envelope, traffic con…
- Semantic Scholar 2022 · Article (Journal of Safety Research)
Go-around accidents and general aviation safety.
INTRODUCTION Changes in General Aviation (GA) accident rates, specifically in the go-around phase, are examined by comparing the number of accidents, the proportion of fatal accidents, and the proport…
- Semantic Scholar 2021 · Article (Aerospace)
Classification and Analysis of Go-Arounds in Commercial Aviation Using ADS-B Data
Go-arounds are a necessary aspect of commercial aviation and are conducted after a landing attempt has been aborted. It is necessary to conduct go-arounds in the safest possible manner, as go-arounds …
- NASA NTRS 2021 · Accepted Manuscript (Version with final changes)
Go-Around Criteria Refinement for Transport Category Aircraft
Presently, airline pilots are trained to go around if, when lower than 500 ft above the ground, they are outside of a handful of parameters such as airspeed, position, and rate of descent.
- NASA NTRS 2019 · Conference Paper
Validation of Proposed Go-Around Criteria Under Various Environmental Conditions
This paper evaluates the effects of environmental conditions on touchdown performance under varying approach states and validates proposed go-around criteria developed using data from a previously con…
Browse the full corpus — academia portal ↗