RC Plane Not Responding? Bench and In-Flight Fix Guide

Disclosure: Some links in this article are affiliate links. We may earn a commission on qualifying purchases at no extra cost to you.

"My plane isn't responding" hides two very different problems. Either it never responded on the bench, or it flew normally and then went dead in the air. The first is nearly always a setup mistake: a bind that did not complete, the wrong model memory, a flat pack. The second points at power, failsafe or the radio path. Treating both as "the radio is broken" swaps good parts for nothing.

This guide is built from manufacturer manuals (Spektrum, FrSky, FlySky, Radiolink, Futaba and ESC makers) and is not based on our own flying. Menu names and procedures differ by firmware, so your own manual has the final word. Two companion guides go deeper on parts of this: our bind and arming guide and our failsafe setup guide.

Step 1: The bench check

Go through these in order before blaming hardware.

1. Transmitter battery. The HobbyZone STOL S manual and Spektrum AR637T+ tables list low transmitter or flight battery charge as a cause of binding and connection failures. It is the fastest check.
2. Receiver power. Spektrum receivers stay quiet without a transmitter signal: the AR620 and AR6610T throttle channel has no output, and the AR637T+ servo ports carry no control signal, so a silent receiver alone is normal. What matters is whether it powers up and links.
3. Model memory. On Spektrum radios with ModelMatch, the receiver only connects when the matching model memory is selected. The AR620 manual says to check this if the system fails to connect. FrSky's ETHOS has the same idea with a Model ID, which changes when a model is cloned.
4. Distance and surroundings during binding. The AR620 FAQ says a transmitter within about 4 feet of the receiver, or near metal or carbon fiber, can delay or prevent connection. Move away and try again. Radiolink's AT9S Pro manual wants the pair about 50 centimeters apart for binding.
5. Servo and wiring. If the receiver is linked but a surface does not move, look for a loose plug, a cut lead or a jammed servo. Our servo guide and wiring diagram guide help with this.

Step 2: Bind procedure, by protocol

Bind steps differ by brand, and a protocol mismatch looks like a failed bind.

After binding, the model memory check above applies again: a successful bind on the wrong model slot controls nothing. Always range check after a rebind.

Step 3: In-flight loss of control and receiver power

If the plane flew and then went dead, start with power. The Spektrum AR620 manual states that inadequate power systems that cannot supply the receiver's minimum voltage in flight "have become the number one cause of in-flight failures." The components that affect it are the receiver battery (cell count, capacity, type, state of charge), the ESC's ability to deliver current to the receiver in electric aircraft, and the switch harness, leads and regulators.

The numbers from Spektrum's manuals:

• The AR620 and AR6610T have a minimum operating voltage of 3.5 volts.
• QuickConnect with Brownout Detection means that when voltage falls below 3.5 volts, the system stops, and when power returns the receiver tries to reconnect straight away, typically in about 4/100 of a second if the transmitter is on.
• That helps you fly through brief interruptions, but the manual is blunt: "the root cause of these interruptions must be corrected before the next flight."
• The recommended test is to monitor receiver voltage with a voltmeter or telemetry while you load the control surfaces by hand. The voltage "should remain above 4.8 volts even when all servos are heavily loaded."

So the safety margin is the gap between 3.5 and 4.8 volts, and it shrinks as servo load rises. Telemetry makes the test easier: Spektrum describes the AR620 as sending receiver battery voltage to a telemetry-capable Spektrum transmitter in fly-by range. The Spektrum AR620 is an example of a sport receiver with that feature, listed at Horizon as in stock.

Fixes, in order of permanence:

1. Size the power system for the real load. Check what your ESC's BEC or regulator can supply when every servo is working, not just at rest. The ESC guide and LiPo guide cover capacity and sizing.
2. Use a dedicated receiver battery where it is appropriate. On glow, gas and larger models without a BEC, a separate receiver pack is common. Spektrum's 2200 mAh 2S 6.6V LiFe receiver battery is one example, though Horizon lists it as back-ordered. Do not combine it with an ESC BEC: the Spektrum Avian ESC manual warns not to connect a dedicated receiver battery to a receiver that the ESC already powers, because the ESC may be damaged.
3. Stop treating a stalled servo as normal. The Spektrum guidance lists servo leads and regulators among the things that affect delivery, and a binding linkage makes everything worse.

A "glitch" capacitor is sometimes suggested as a fix. No maker document read for this guide recommends one for a brownout, and it cannot enlarge an undersized supply, so the sourced fix is to correct the power system.

Step 4: Failsafe

A badly set failsafe can make a short glitch look like total unresponsiveness, and it decides what happens in a real loss. Spektrum's AR620 defaults to SmartSafe with Hold Last: the throttle goes to the low position captured at binding and other channels hold their last positions. The AR6610T and AR637T+ define a hold as 45 consecutive frame losses, about one second, after which outputs move to the failsafe settings, and they say it is normal to see a hold logged when you turn the transmitter off and on.

By brand, from the manuals:

• FrSky ETHOS: Hold, Custom, No Pulses or Receiver, with failsafe data sent about every 10 seconds, and a startup checklist item that warns if failsafe is unset.
• FlySky FS-i6X: a channel showing [Off] holds its last position.
• Radiolink AT9S Pro: NOR holds, F/S moves to a preset, with data sent about every two minutes, and the throttle F/S also sets the battery F/S.
• Futaba S-FHSS: throttle channel only, with a one second hold before moving.

The test is the same everywhere: restrain the model, remove the propeller, power up, then turn off the transmitter and watch what the throttle and surfaces do. Our failsafe guide walks through each brand in more detail.

Step 5: Antenna placement and range

On modern 2.4GHz systems, true interference is less common than installation mistakes. The manuals agree on several points:

• Keep antennas straight and clear of conductors. Radiolink says to keep receiver antennas as straight as possible, at least half an inch from metal and carbon fiber, and away from motor, ESC and other interference sources. Futaba's S-FHSS manual says the same half inch for its antennas. FlySky's FS-iA6B manual asks for at least 1 centimeter from carbon or metal.
• Use both sides on big models. Radiolink suggests placing antennas on both sides of a model with metal parts. Futaba's dual antenna diversity receiver has its antennas exit both sides of the model.
• Do not bend or crush the antenna. Futaba warns against tight bends, particularly of the coax.
• Point the transmitter antenna correctly. Radiolink says never to point the transmitter antenna directly at the model, and Futaba says not to grasp its module antenna in flight.
• Do a real range test. Spektrum's range check has you stand 30 paces (about 90 feet, or 28 meters) from the restrained model with the transmitter in range check mode, and for models with a lot of conductive material it describes an advanced test using telemetry fade and hold values while someone positions the model in different orientations.

For ready-made spare receivers to isolate a suspect unit, the FrSky Archer Plus R6 is listed on Amazon with 6 PWM channels, 24 SBUS channels, signal redundancy and telemetry. Those are listing claims. Any spare must match your transmitter's protocol.

Step 6: Gas and nitro notes

On gas and nitro models the same checks apply, with two extras. First, follow your engine maker's manual for how far to keep receiver, battery and servo leads from the ignition system; this guide did not find a maker figure it could verify. Second, consider an electronic kill switch with a failsafe: one Amazon listing for an opto kill switch describes fiber-optic coupling that separates the ignition circuit from the receiver circuit, remote kill through an auxiliary channel, and an engine that shuts off when the receiver signal is lost. The Radiolink AT9S Pro manual also recommends setting a gasoline engine's electronic kill switch to OFF in its failsafe. Our gas engine guide covers the engines themselves.

If your plane uses stabilization or autopilot, the flight controller guide covers how those systems interact with the radio link, and the transmitter and receiver guide covers choosing the radio in the first place.

Mistakes that waste time

• Assuming the battery without checking whether the plane ever worked today. Bench and in-flight failures rarely share a cause.
• Ignoring a logged brownout. Spektrum says the cause must be found and fixed before the next flight.
• Leaving failsafe at default. Verify it on the bench, every model.
• Binding at arm's length from a plane full of carbon. Move away.
• Mixing protocols. ACCESS and ACCST differ, and FlySky AFHDS and AFHDS 2A receivers need matching RF standards.
• Burying antennas against carbon or metal. Follow your radio's spacing guidance.

FAQ