RC Plane Failsafe Not Working: How to Set It Up Correctly

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

If you just switched your transmitter off on the bench, expecting the throttle to cut and nothing happened, you haven't found a broken feature — you've found a receiver that was never actually told what to do. On almost every fixed-wing setup, failsafe lives in the receiver, not the transmitter, and its default out-of-the-box behavior on most brands is to simply hold the last command it received. A bench test against that default looks identical to a failsafe that's "on" and doing nothing, which is exactly what sends people down the wrong troubleshooting path.

The fix isn't universal, because failsafe isn't a single standard — it's five different implementations wearing the same name. Spektrum, FrSky, FlySky, Radiolink and Futaba each store it differently, default to different behavior when unset, and use different menus to configure it. Get the wrong one and you can end up with a plane that holds full throttle on signal loss instead of cutting it.

This guide goes brand by brand: what your receiver does out of the box, the exact menu path to set failsafe correctly, and the specific mistakes that make a properly-configured failsafe look broken during testing. It also covers something most failsafe guides skip entirely: fixed-wing failsafe logic is not the same as multirotor failsafe logic, and copying one onto the other is a real cause of avoidable crashes.

If your setup includes a flight controller for FPV or autopilot work, some of this changes — that's covered separately in our flight controller guide.

Fixed-Wing Failsafe vs. Multirotor Failsafe — Know Which One You're Setting

Most online guides for "failsafe setup" are written for FPV quads, and their default advice — cut power immediately, let the flight controller sort out the fall — is wrong for a plane with no FC and no props to catch a fall. A fixed-wing without a flight controller needs a different outcome on signal loss: throttle to idle, plus a slight, deliberate turn (rudder held over, a touch of up elevator) to induce a slow descending spiral near the point where signal was lost. That's the opposite of "drop" and different from "No Pulse and let the FC handle it."

If your setup is a flight controller-based plane (INAV/Betaflight/ArduPilot), the receiver's job is usually just to signal loss-of-link cleanly (No Pulse or a distinct failsafe flag) — the FC decides what happens next. Plain PWM planes with no FC don't have that luxury: whatever the receiver outputs on signal loss is exactly what your servos and ESC will do.

What You'll Need

• Your transmitter and receiver model numbers (failsafe menus differ even within the same brand's generation)
• The plane with the propeller removed — you're about to intentionally cut signal
• A fully charged flight battery and, ideally, a spare
• Access to your radio's manual or its official wiki page (menu wording varies by firmware version)
• 10–15 minutes of uninterrupted bench time — some systems (FrSky) enforce a write delay before settings take effect

Step 1 — Confirm Failsafe Was Actually Stored, Not Just Set On-Screen

Before touching any menu, understand the most common root cause: the setting was configured on-screen but never actually saved to the receiver. On Spektrum, this happens when the bind plug is pulled after power-off instead of before, or when the transmitter is powered down mid-process. On FrSky, it happens when a value is changed and tested before the ~9-second write delay elapses. Neither system gives you an error message — it just silently keeps the previous (often default) behavior.

Rule of thumb across every brand here: after changing a failsafe value, wait, then power-cycle the receiver on its own (transmitter off) and check what the servos and throttle actually do — not what the transmitter screen says you set.

Step 2 — Spektrum: Fix SmartSafe by Binding With Throttle at Idle

Spektrum's default scheme, SmartSafe, drives only the throttle channel to whatever position the stick was in at the moment of binding; every other channel holds its last command. If you bound with the throttle stick even slightly above idle, that's the position failsafe will jump to on signal loss — full power included, in rare but documented cases.

Fix on classic AR receivers (AR6210, AR8000, AR9000, etc.):

1. Put the throttle stick at idle and all other sticks/switches in the positions you want on signal loss.
2. Insert the bind plug into the BATT/BIND port and power on the receiver.
3. Power on the transmitter in bind mode; hold stick positions steady until the receiver connects.
4. Remove the bind plug before powering anything off — this is the step people miss, and skipping it means the failsafe setting never actually saves.

On telemetry/stabilized receivers (AR637T, AR631, AR6610T), you get more control via Forward Programming: Forward Programming > Port Settings > Failsafe, then choose Hold Last, Preset (with a stored position), or SAFE Failsafe on stabilized units, which levels the model automatically rather than just holding a stick position. The AR637T is a reasonable step-up pick specifically because Forward Programming gives you per-channel control that basic AR receivers don't.

One more trap: rebinding wipes Custom Failsafe and Position values every time (SAFE Failsafe on stabilized receivers survives a rebind, everything else doesn't). If you rebind after a crash repair or a servo swap, your failsafe reverts to whatever throttle position you bind at — re-check it before the next flight.

Step 3 — FrSky: Transmitter-Set Failsafe Beats Receiver-Set, and It Isn't Instant

FrSky gives you three options — No Pulse, Hold, or Custom — configurable either from the radio menu (EdgeTX/OpenTX: Model Setup > Internal RF > Failsafe) or via the receiver's physical F/S button. In D16/ACCESS mode, transmitter-set failsafe overrides receiver-set failsafe, so if you've configured both and they disagree, the transmitter wins.

If you've never touched either, the receiver defaults to Hold — last command, indefinitely, no cut. For a fixed-wing that means the throttle keeps running at whatever setting it was at when the link dropped, which is the opposite of what you want.

To set Custom failsafe correctly:

1. Enter the failsafe menu and select Custom.
2. For each channel, move the cursor to it, set the desired value (throttle to idle, rudder/elevator to your spiral setting), and confirm.
3. Wait 9 seconds after each change before assuming it's applied — this is a documented write delay, not a UI glitch.
4. Power-cycle the receiver alone and verify servo positions before trusting it in the air.

If you're on older ACCST firmware, be aware FrSky documented a genuine bug — "uncontrolled servo movements" under certain RF conditions — fixed in ACCST D16 v2.1.0. Updating requires flashing both the transmitter/module and every receiver you fly with it, and it breaks compatibility with older ACCST v1 gear and third-party clones, so don't do it mid-season without a plan. A current, in-stock option that sidesteps the older-firmware ambiguity entirely is the FrSky Archer Plus R6.

Step 4 — FlySky: Failsafe Is Off by Default, Per Channel

FlySky's AFHDS 2A receivers (FS-iA6B and similar) ship with failsafe off, which means the channel locks to whatever value it held right before signal loss — not idle, not neutral, whatever it happened to be doing. This is arguably the riskiest default of the five, because "off" looks identical to "working as intended" on a casual bench check if the plane happened to be sitting at idle when you tested.

To enable it correctly on an FS-i6/i6X-class transmitter:

1. System Setup > RX Setup > Failsafe.
2. Select the throttle channel (typically Channel 3).
3. Move the throttle stick fully down and trim it down as well.
4. Toggle failsafe ON for that channel; confirm it reads -100%.
5. Long-press Cancel to save.

Only channels you explicitly enable will act on signal loss — everything else keeps holding last command regardless. If you're running a flight controller off an FS-iA6B, know that stock firmware doesn't reliably send a distinct failsafe flag; some FC setups need the throttle value driven below the normal minimum threshold to register loss-of-link at all. That's a firmware limitation, not a wiring issue — worth knowing before you spend an afternoon re-checking connections.

Step 5 — Radiolink: Set It From the Basic Menu, Confirm on Power-Down

Radiolink transmitters (AT9, AT9S Pro, AT10II) only bind to Radiolink receivers, which simplifies compatibility but means you're relying on Radiolink's documentation alone — and their official English manuals are notably thin on what the unset default actually does. Treat it as hold/unpredictable until you've explicitly configured it.

1. Bind the receiver: hold the ID SET button on the receiver (R9DS, R6DS, etc.) for more than a second until the LED goes solid, then power-cycle the transmitter.
2. Open the Basic Menu on the transmitter and find the F/S parameter.
3. Move each stick to its desired failsafe position — throttle low, control surfaces to your preferred spiral trim — and store it.
4. Confirm the receiver's channel count matches your transmitter setting (AT10II defaults to 12 channels; drop it to 10 under SYSTEM > CH-SELECT if you're running an R9DS).
5. Switch the transmitter off and physically watch the servos move to the stored F/S positions — this is the only reliable confirmation with this system.

Also check the LED color on the receiver: red typically indicates PWM/9-channel mode, blue or purple indicates SBUS/10-channel. Setting failsafe on the wrong signal path from what's actually feeding your servos or flight controller is an easy, invisible mistake.

Step 6 — Futaba: Two Separate Failsafes, Don't Confuse Them

Futaba systems (14SG, 16SZ, 18MZ and similar) run two independent safety features that get conflated constantly: Fail Safe (F/S), which reacts to lost signal, and Battery Fail Safe (B.F/S), which reacts to low receiver-battery voltage by moving the throttle to a preset slow position. They're set in different places and solve different problems — a plane can have one configured and not the other.

Setting F/S:

1. Linkage Menu > Fail Safe (or the Function screen, depending on model).
2. Select the throttle channel, hold the stick at the slow/idle position, and confirm F/S position.
3. Repeat for rudder/elevator if you want a spiral rather than a straight hold.
4. Settings transmit to the receiver roughly every two minutes — give it time before testing.

Setting B.F/S is a separate step in the same general menu area, and it's worth doing even if F/S is already configured: it's what protects you against a receiver battery sagging mid-flight, which F/S alone won't catch. Only FASSTest, FASST, T-FHSS and S-FHSS modes support full per-channel failsafe; older 3-channel FASST and 7-channel S-FHSS have limited channel coverage, so check which protocol your receiver is actually running before assuming full control. A dedicated telemetry receiver like the R7008SB is the common pairing for pilots running the full F/S + B.F/S setup — check current listings on Amazon since availability runs mostly through specialist retailers rather than Amazon proper.

Step 7 — The Ground Test That Actually Proves It Works

Every brand above gets verified the same way, and skipping this step is how "I set it" becomes "it didn't work" mid-flight.

1. Remove the propeller. Non-negotiable — you're about to intentionally trigger a throttle response.
2. Power on the receiver and transmitter normally, arm as you would before flight, and note current servo positions.
3. Switch the transmitter off (or put it to sleep, if that's how your system disconnects).
4. Watch — don't assume — what the throttle and control surfaces actually do. Throttle should go to idle or off; surfaces should move to whatever spiral positions you configured, not just freeze in place.
5. Power the transmitter back on and confirm normal control returns before considering the test complete.

One caveat that trips people up: your ESC has its own signal-loss and low-voltage cutoff behavior, independent of the receiver's failsafe. A receiver correctly outputting zero throttle doesn't guarantee the motor stops the way you expect — test the actual motor response, not just the servo tester or a visual check on the throttle channel. If you're not sure which layer is misbehaving, our ESC guide covers how to isolate ESC-side cutoffs from receiver-side failsafe.

Common Mistakes to Avoid

• Binding Spektrum with the throttle stick above idle. SmartSafe locks in whatever position you bind at — this is the single most common cause of a failsafe that raises throttle instead of cutting it.
• Testing FrSky failsafe before the 9-second write delay elapses. The change hasn't applied yet; you're testing the old value.
• Assuming FlySky failsafe is on by default. It isn't — it has to be enabled per channel, and unset channels just hold last command indefinitely.
• Treating multirotor failsafe advice as universal. "Cut power and let it drop" is a quad convention; a fixed-wing without a flight controller needs throttle-to-idle plus a controlled turn, not a dead-stick free-fall from altitude.
• Rebinding a Spektrum receiver after a repair and not re-checking failsafe. Rebinding wipes Custom Failsafe and Position values every time.
• Confusing Futaba's Fail Safe with Battery Fail Safe. They're independent settings; having one configured says nothing about the other.
• Skipping the prop-off ground test. A menu that says "Custom" or "Preset" doesn't confirm the receiver actually stored it — only a real power-cycle test does.

Frequently Asked Questions

Conclusion

"Failsafe not working" is almost never a hardware fault — it's a mismatch between what you assumed your receiver does on signal loss and what it's actually configured to do. Spektrum locks in your bind-time throttle position, FrSky and FlySky both quietly default to holding last command until you explicitly change it, and Futaba splits the job across two separate settings that are easy to configure only one of. None of that shows up as an error message; it shows up as a plane that doesn't behave the way you expected, usually at the worst possible moment.

The fix is the same across every brand: know your system's actual default, set failsafe deliberately for a fixed-wing outcome — throttle to idle, a controlled turn, not a multirotor-style drop — and confirm it with a real prop-off ground test rather than trusting the transmitter's on-screen confirmation. Do that once per model and re-check it after any rebind or receiver swap.

For the broader radio-system decision this all sits inside, see our transmitter and receiver guide and servo guide for how these settings interact with your control linkages. If you're setting up a battery-monitoring layer on top of failsafe, our LiPo battery guide covers voltage cutoffs that work alongside — not instead of — your receiver's failsafe. And if you're still building fundamental stick skills, start with our beginner's flight guide before pushing into advanced radio configuration.