20 Oct 2022: BEECH V35B

20 Oct 2022: BEECH V35B (N50JM) — Unknown operator

No fatalities • Nogales, AZ, United States

Probable cause

The pilot’s failure to establish a positive rate of climb before retracting the landing gear when he executed an aborted landing, which resulted in a propeller strike, diminished climb performance, and the inadvertent contact with terrain.

— NTSB Determination

Accident narrative

On October 20, 2022, about 1258 mountain standard time, a Beechcraft V35B airplane, N50JM, was substantially damaged when it was involved in an accident near Nogales, Arizona. The pilot sustained minor injuries and the passenger was hospitalized with serious injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot reported that he was returning from Tarkio, Missouri (K57) on a visual flight rules (VFR) flight plan. At 1252, the pilot canceled VFR flight following, announced his intentions on the common traffic advisory frequency for Nogales International Airport (OLS), Nogales, Arizona, and entered the left downwind for runway 21. He lowered the landing gear and confirmed 3 green landing gear lights with his passenger after he turned to the base leg of the airport traffic pattern. At this time, the aural landing gear warning system confirmed the landing gear was down for landing. The pilot reported that during touchdown the airplane immediately “flopped down” and veered to the left. The pilot applied right brake and rudder to try regain the runway centerline, but he decided to perform an aborted landing. He applied full power and raised the landing gear. Striations on the runway, which were consistent with propeller strike marks, were observed about 150 ft beyond the 1,000-foot markers of runway 21. The pilot reported that the airplane was unable to gain airspeed and decided to land off the airport. After he circled around to the north via the east side of the airport, he was still unable to gain airspeed and executed a forced landing to an open field about 0.5 nm north of the approach end of runway 21. The airplane came to rest on its belly and was oriented on a northeast heading. A postcrash fire ensued and the airplane subsequently exploded. One witness reported that he watched the airplane make what was apparently a normal landing, but then he heard the engine rev up and saw the landing gear retracted. He stated that he saw the right side of the airplane on fire after the aborted landing. Another witness observed the airplane flying in a nose-high attitude at a very low altitude during the balked landing. He reported that the airplane was “on the edge of a stall, his gear was up, barely hanging on at about 10-30 feet above the ground.” He did not observe the airplane on fire until after the impact with terrain. Postaccident examination of the airplane did not reveal any preimpact anomalies with the flight control system. The rudder control system cables were traced from the cockpit to the rudder through cable cuts made by recovery personnel. Although fire damaged, the right main landing gear linkages were continuous from the landing gear actuator to the landing gear. The left main landing gear linkages were continuous from the actuator to the left main landing gear through an overload separation at the drive tube near the left-wing root. The landing gear and brake systems were destroyed by fire and could not be examined due to lack of available evidence. Postaccident examination of the engine did not reveal any preimpact mechanical anomalies. In addition, the pilot and witnesses who observed the aborted landing said the engine sounded like it was developing full power.

Each propeller blade displayed deformation about 20 inches from its blade root. Bending, curling, and chordwise scratching was consistent with that of damage to a propeller with an engine developing full power. There were no tire marks associated with the accident airplane found on the runway; however, the runway had propeller strike markings consistent with that of an engine developing full power while traveling down, and in contact with, the runway.

Figure 1. Flight path after go-around is initiated.

Contributing factors

  • Pilot
  • Pilot
  • Attain/maintain not possible
  • Incorrect use/operation

Conditions

Weather
VMC, wind 120/08kt, 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.