Disclosure: Some links in this article are affiliate links. We may earn a commission on qualifying purchases at no extra cost to you.
A plane that won't respond splits into two completely different problems, and mixing them up wastes hours. Either it's sitting on the bench refusing to bind or move a servo, or it flew fine for a few minutes and then went unresponsive in the air. The first is almost always a setup mistake — wrong bind procedure, dead pack, wrong model memory. The second is usually an electronic failure mode: a receiver brownout, a bad failsafe configuration, or occasionally interference. Treating both as "the radio is broken" leads to swapped-out good parts and a problem that comes right back.
This guide splits the diagnosis the way it actually happens in the field: bench failures first, then in-flight loss of control, then the two causes pilots blame first and are usually wrong about — interference and "a bad radio." Each transmitter and receiver protocol family binds and fails differently, so the binding and failsafe sections are broken out by brand rather than given as one universal sequence.
The goal is an ordered checklist, not a wall of theory: what to check first, what to check only if the first thing didn't fix it, and which fixes are permanent versus which are band-aids that will fail you again at the worst moment.
Quick Reference — Symptom to Likely Cause
| Symptom | Most likely cause | Section |
|---|---|---|
| No servo movement, RX LED not solid | Bind failure or dead RX battery | Bench Check |
| Binds, LED solid, still no control | Protocol/firmware mismatch (e.g. ACCST vs ACCESS) | Binding by Protocol |
| Flew fine, then went dead mid-flight | Receiver brownout (BEC voltage sag) | In-Flight Loss of Control |
| Plane did something unexpected then recovered | Failsafe triggered and released | Failsafe |
| Loses control only at distance or behind obstacles | Antenna orientation or range | Interference and Antenna Placement |
| Erratic controls only with engine running | Ignition noise or vibration-loosened connector | Gas and Nitro |
Before You Start — Bench Failure or In-Flight Failure?
Before touching a screwdriver, answer one question: did the plane ever respond correctly today, even for a moment? If it never worked on the bench, the cause is almost certainly binding, power, or wiring — nothing aerodynamic or electronic-failure related has happened yet. If it flew normally and then lost control, the fault is happening under load, in the air, which points straight at brownouts, failsafe, or interference rather than a dead component.
Also separate "not responding" from "flies badly." Wing warps, bad CG, or incorrect control-surface throws are flight-quality problems, not communication failures — if the plane answers your stick inputs at all, even wrong, this isn't a radio-link guide. This one is strictly about the plane ignoring the transmitter.
Step 1 — Bench Check: Won't Bind or No Servo Movement
Work through this order before assuming anything is damaged:
- Transmitter battery. A low TX pack can prevent binding entirely on some radios. Charge or swap it first — it's the fastest check to eliminate.
- Receiver power. Confirm the RX is actually getting voltage: plug a servo tester or a known-good servo directly into a spare channel and power the system. No twitch on power-up means the receiver isn't getting power, not that it's unbound.
- Model memory / model match. Most radios store multiple aircraft profiles. If the transmitter is in the wrong model slot, it can appear completely dead to that airframe even though the radio itself works fine.
- Bind procedure for your specific protocol. This is the single most common bench failure — see the binding table below before replacing anything.
- Servo and wiring integrity. If the receiver LED goes solid (bound) but nothing moves, check for a loose servo plug, a cut lead, or a servo that failed independently of the radio. A servo that's mechanically jammed will read as "not responding" even with a perfectly good link.
If the receiver LED never goes solid no matter what you try, move to the protocol-specific binding steps below rather than guessing.
Step 2 — Binding by Protocol
Binding procedures are not interchangeable between radio brands, and a mismatch between firmware branches within the same brand can look identical to a failed bind — the LED goes solid, but nothing actually links. Confirm which protocol your gear uses before troubleshooting further.
| Protocol family | Typical bind procedure | Known gotcha |
|---|---|---|
| Spektrum DSM2/DSMX | Power the receiver first with the bind plug installed (or press the AR620's integrated bind button), then power the transmitter in bind mode; LED solid = bound | None major — Spektrum's newer receivers (like the AR620) use a physical bind button instead of a plug, simplifying the step |
| FrSky ACCST D16 / ACCESS | Hold the F/S button while powering the receiver, then put the transmitter in bind mode | ACCESS requires registration ("Smart Match") before the receiver will bind at all; a receiver on ACCST V1 firmware will not link with a transmitter expecting V2.1 — it binds but outputs no signal |
| Futaba FASST / FASSTest / S-FHSS / T-FHSS | Protocol and model-specific; always follow the exact steps in your transmitter's manual | Power the transmitter before the receiver; many Futaba systems restrict programmable failsafe to the throttle channel only |
| Flysky AFHDS / AFHDS 2A | Hold the RX bind button (or plug) at power-up, put the TX in bind mode; solid LED = bound | AFHDS, AFHDS 2A, and AFHDS 3 are not cross-compatible with each other — a receiver and transmitter on different generations will never bind, however many times you try |
If binding succeeds but you still get no control response, recheck the model-memory setting from Step 1 before assuming the bind itself failed — a successful bind on the wrong model slot still won't move the correct servo outputs.
Once bound, do a proper range check by walking away from the model with the transmitter in its range-test mode rather than trusting a bench-distance test — some manufacturer guidance calls for separations well beyond arm's length before you trust the link outdoors.
Step 3 — In-Flight Loss of Control: Diagnosing Brownouts
If the plane flew normally and then went unresponsive, the receiver most likely browned out — its voltage dropped below the minimum needed to keep operating, and it rebooted mid-flight.
The mechanism: a servo that stalls (hits a mechanical limit, binds against linkage, or is simply undersized for the load) draws a current spike far above normal. If that spike pulls the shared power bus below the receiver's floor, the receiver resets. According to Spektrum's AR12000 documentation, "brownouts occur when the receiver voltage drops below 3.5 volts thus interrupting control as the servos and receiver require a minimum of 3.5 volts to operate." A stalled digital servo can hold that current draw and prevent the receiver from rebooting cleanly, extending the loss of control.
Specific numbers to know if you're running Spektrum gear: the AR620 receiver operates from 3.5–9V, with a hard minimum of 3.5V, but Spektrum's own guidance states voltage "should remain above 4.8 volts even when all servos are heavily loaded" — that gap between 3.5V and 4.8V is your real safety margin, and it shrinks fast with more or larger servos on the same BEC.
Fixes, in order of permanence:
- Confirm your ESC's BEC or your standalone regulator can actually supply the combined current of every servo at full deflection, not just at rest. Undersized power delivery is the root cause, not a symptom to patch around.
- On gas, nitro, or large electric models, move to a dedicated receiver battery instead of relying on an ESC's BEC. A 2S LiFe pack like Spektrum's 6.6V 2200mAh receiver battery drives the RX and servo bus directly, with a stated minimum discharge of 5.0V — well clear of the receiver's brownout floor — and LiFe chemistry is safe to run straight into standard servos without a separate regulator.
- Avoid treating a "glitch-buster" capacitor as a fix. These smooth brief voltage sag and ripple, but they do nothing for RF interference and cannot compensate for a genuinely undersized power system — pilots who rely on one after a brownout are usually setting up a repeat failure.
- If your receiver has voltage telemetry, use it. The Spektrum AR620 logs receiver voltage during flight, so you can confirm after landing whether a fade or hold actually happened and how low the bus dropped — rather than guessing at the cause after the fact.
For a deeper look at matching power delivery to your servo load, see the ESC guide and the LiPo battery guide.
Step 4 — Failsafe: Configure It Before You Ever Fly
A poorly configured failsafe doesn't just fail to protect the plane in a real signal loss — it can make an unrelated glitch look exactly like total unresponsiveness. If a receiver browns out and reboots mid-flight while set to hold-last on every channel, the plane can appear frozen or unresponsive for the split second it takes to reacquire, and on some systems a receiver can even re-enter bind mode on a bad restart if failsafe wasn't set correctly.
The instructor's rule holds regardless of brand: set failsafe first, on every new model, before checking anything else. Specifics by protocol:
- Spektrum: The AR620 defaults to SmartSafe combined with Hold Last — throttle drops to the position set during binding, while every other channel holds its last commanded position. Confirm this is actually set to a safe throttle-low position during your bind, not left at whatever the stick happened to be at.
- FrSky: Failsafe is set through the transmitter menu with No Pulse, Hold, or Custom options on ACCESS systems. FrSky's own manual instructs pilots to select the mode in the menu and then wait roughly 9 seconds for the setting to actually take effect before assuming it's saved.
- Futaba: Many Futaba receivers restrict programmable failsafe to the throttle channel only, cutting power to a preset low position after roughly a second of lost signal, while other channels simply hold. Don't assume full-channel failsafe unless your specific receiver's manual confirms it.
- Flysky: Failsafe is configured through the transmitter's model menu on both AFHDS and AFHDS 2A systems; confirm the setting per model rather than assuming it carried over from a previous airframe.
Whatever your protocol, the test is the same: power up, bind, then power off the transmitter only and watch what the plane's control surfaces and throttle do. If you don't like what you see, fix it on the bench — not after a real loss of signal in the air.
Step 5 — Interference and Antenna Placement
On modern 2.4GHz spread-spectrum gear, true RF interference is far less common than pilots assume, but antenna placement mistakes still cause real range and reliability problems.
The rule of thumb from experienced RC pilots: "parallel strong, perpendicular weak, tip-to-tip very weak." A transmitter antenna radiates least energy straight out of its tip, so never point the antenna tip directly at the model — hold it so the antenna's length, not its end, faces the aircraft.
On the receiver side, dual antennas should be mounted roughly 90 degrees apart from each other, with the tips left exposed rather than buried in carbon fiber or wrapped against metal, and separated from each other by around 12cm or more — roughly a full wavelength at 2.4GHz. Cutting or shortening a receiver's antenna element reduces range and should never be done to tidy up wiring.
One under-discussed cause worth checking on older transmitters, especially in humid climates: corrosion or residue on the stick gimbal contacts can cause erratic or uncommanded control inputs that look exactly like an interference problem. A basic contact cleaning has resolved this on radios that otherwise tested electronically fine.
If you've ruled out binding, brownout, failsafe, and antenna placement and still see intermittent loss of control, the receiver or transmitter hardware itself may have failed — this is the least common cause on modern gear, but it does happen, and swapping in a known-good receiver like the FrSky Archer Plus R6 (rated for full range beyond 2km and built with enhanced anti-RF-interference performance) is a reasonable way to isolate a suspect unit rather than repeatedly re-testing the original.
Step 6 — Gas and Nitro: Ignition Noise and Related Checks
On gas and nitro models specifically, "not responding" sometimes gets blamed on the engine's ignition system. With today's 2.4GHz spread-spectrum radios this is a far smaller risk than it was in the AM/crystal era, but it isn't zero: engine manufacturers still recommend keeping receiver, battery, and servo leads at least 8 inches from ignition components, and twisting or routing throttle-servo wiring away from the ignition module and spark leads reduces the chance of noise-induced glitches.
Don't confuse a radio problem with an engine-starting problem. A glow-plug igniter like the Dynamite metered glow driver — with its built-in meter and Sure-Lock hands-free clip — helps you rule out a bad or unheated glow plug when the engine itself won't run, but that's a separate failure mode from the control link ignoring your transmitter. If the engine starts and runs fine but the plane won't answer the sticks, look at Steps 1–5 above, not the ignition system.
If you're set up on a receiver whose spec sheet specifically calls out interference resistance during spark ignition — the Archer Plus R6 does — that's a genuine advantage for gas/nitro flyers over a generic receiver, but it addresses noise rejection, not power delivery; a dedicated receiver battery still matters more for avoiding brownouts on these larger, harder-working airframes.
Common Mistakes to Avoid
- Assuming it's "the battery" without checking whether the plane ever worked at all today — bench failures and in-flight failures have almost no cause overlap.
- Buying a glitch-buster capacitor as a fix for a brownout instead of correcting the actual power-delivery shortfall.
- Leaving failsafe at factory defaults without verifying throttle-low behavior on the bench, every time you bind a new model.
- Treating AFHDS, AFHDS 2A, and AFHDS 3 gear as interchangeable — they are not, no matter how many times you retry the bind.
- Cutting or shortening a receiver antenna to "clean up" wiring, which directly reduces range.
- Blaming interference before ruling out brownout — power-side sag is the more common real-world cause on modern 2.4GHz systems.
- Wiring receiver, battery, or servo leads directly against ignition components on gas models instead of maintaining the recommended separation.
Frequently Asked Questions
Q: Is a dead or weak battery always the cause of a "not responding" plane?
No. It's a common cause of bench failures, but in-flight loss of control is more often a receiver brownout under servo load, a bad failsafe configuration, or occasionally an antenna or hardware issue — not simply a discharged pack.
Q: My receiver LED is solid but the plane still won't respond. What's wrong?
Check the transmitter's model memory first — a successful bind on the wrong model slot looks identical to a failed bind. If that's correct, suspect a protocol/firmware mismatch, which is common on FrSky ACCST versus ACCESS systems, or a wiring/servo fault downstream of the receiver.
Q: What actually causes a receiver brownout?
A servo or group of servos drawing more current than the power system can supply — often because one servo has stalled against a mechanical limit — pulls the shared voltage bus below the receiver's minimum operating voltage, forcing it to reset mid-flight.
Q: Do glitch-buster capacitors fix radio interference?
No. They smooth brief voltage sag and ripple on the power bus, which can help with marginal brownout margins, but they do nothing to address actual RF interference and won't fix an undersized power system.
Q: Are AFHDS, AFHDS 2A, and AFHDS 3 receivers and transmitters interchangeable?
No. These are distinct protocol generations from Flysky and are not cross-compatible — a transmitter and receiver on different generations will never successfully bind regardless of how the procedure is followed.
Q: Should I always set up a separate receiver battery instead of relying on the ESC's BEC?
On gas, nitro, and larger electric models carrying multiple or high-torque servos, yes — a dedicated receiver pack removes the risk of a stalled servo browning out the flight electronics, which a shared BEC can't always protect against under heavy load.
Conclusion
Most "RC plane not responding" cases resolve once you correctly identify which of the two problems you actually have. Bench failures are almost always binding, model-memory, or wiring mistakes — work the checklist in order rather than jumping straight to replacing the receiver. In-flight failures point toward brownouts and failsafe misconfiguration far more often than interference, and the fix for a brownout is always proper power delivery, never a capacitor band-aid.
Set failsafe correctly on every new model before you ever fly it, verify your receiver's voltage margin under real servo load rather than at rest, and match your binding procedure to your specific radio protocol rather than a generic universal sequence. For the broader picture on choosing and setting up your radio system, see the transmitter and receiver guide; if stabilization or autopilot features are part of your setup, the flight controller guide covers how those systems interact with your radio link; and for full electronics installation from scratch, the wiring diagram guide walks through keeping power and signal wiring clean from day one.
A plane that ignores its transmitter is telling you something specific about a real electrical or configuration fault — not that the hobby's electronics are inherently unreliable. Work the diagnostic tree in order, and most failures resolve on the bench before they ever cost you a model in the air.
