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.

You switch the transmitter off on the bench, braced for the throttle to drop, and the servos just sit there like nothing happened. Before you decide the receiver is broken, consider the duller explanation: it was never told what to do, so it is doing the one thing every receiver does without instructions. It holds the last command it heard.

Failsafe is not one standard. It is a family of behaviors that each radio maker implemented its own way, with different defaults, different menus and different traps. This page is built from the manufacturers' own manuals and documentation, not from our own flying, so every procedure below points back to what the maker printed. Menu names change between firmware versions, so treat the paths as a map and your own manual as the territory.

Two housekeeping notes. First, the whole subject lives in the transmitter and receiver half of the hobby, so if you are still choosing a radio, start there. Second, if your plane carries a flight controller, part of this changes, and that is covered further down.

Where failsafe lives and what it does by default

On a plain fixed-wing setup with no flight controller, failsafe is stored in the receiver. When the link drops, the receiver drives the servo and ESC outputs to the stored positions. The transmitter is gone, so it cannot help.

That is why the bench test matters: whatever the receiver outputs on signal loss is exactly what your servos and motor will do in the air. The table summarizes what the manuals say for the models covered here.

Fixed-wing failsafe is not quad failsafe

Most of the failsafe advice floating around the internet was written for FPV multirotors, where "cut everything and let the flight controller sort it out" is a reasonable convention. Copying that onto a plain RC plane gives you a motor that stops and surfaces that freeze in whatever position they had. Sometimes that is fine. Sometimes it is a plane holding a hard bank straight into the ground.

The manuals are surprisingly consistent about what to aim for instead:

• Throttle to idle or off. The Radiolink AT9S Pro manual suggests setting the throttle channel so the engine idles on interference in an aerobatic model, which gives time to fly away from the interference and recover. Spektrum's receivers move the throttle to the low position by default.
• Surfaces to a position that keeps the plane gliding. Spektrum's AR637T+ manual recommends setting bank and pitch for "a gentle gliding turn, preventing a flyaway" in its SAFE Failsafe mode. A club failsafe guideline from WRCS suggests neutral ailerons, neutral or slightly up elevator and a slight rudder deflection.
• Not a promise. The same club guideline closes with the honest line that failsafe does not guarantee a perfect landing; it only reduces risk.

Treat the gentle-turn recipe as common club practice rather than a law of physics. A glider, a trainer and a fast pylon racer will not agree about what "safe" looks like, so decide per airframe and verify on the bench.

Spektrum: failsafe is captured, and bind-time stick positions matter

Spektrum receivers store failsafe in two broad ways depending on the model.

AR620 and similar: set at binding

The AR620 manual states that failsafe position is set during binding. There are two modes:

• SmartSafe + Hold Last. If the signal is lost, the throttle channel moves to the low-throttle position set at binding and every other channel holds its last position. Bind with the throttle stick lowered.
• Preset Failsafe. Every channel goes to the position it had when you bound. The manual describes this as ideal for sailplanes that should dethermalize on signal loss.

For SmartSafe, the manual's recipe is: lower the throttle on the transmitter, push and hold the receiver's bind button, power on the receiver, release the button when the receiver flashes in bind mode, then put the transmitter in bind mode and finish. For Preset Failsafe, first move all sticks and switches to the positions you want, run the same sequence, and push and hold the bind button a second time before the transmitter enters bind mode.

The AR620 manual also says that after you set up a model you should rebind the transmitter and receiver to set the failsafe positions you want. Read that as a standing rule: any rebind is a failsafe event, so retest afterward.

AR6610T and AR637T+: Forward Programming

On the AR6610T and AR637T+, SmartSafe + Hold Last is the default, and Preset Failsafe is available only through Forward Programming on a compatible Spektrum transmitter. The AR637T+ adds SAFE Failsafe, which tries to level the aircraft; per Spektrum you must complete the First Time SAFE Setup before that option appears.

The menu paths differ slightly between the two manuals:

In both, you pick each channel and assign it Preset or Hold Last, then use Capture Failsafe Positions: hold the sticks where you want them and select Apply. The manuals add a trap worth underlining. Channels must be set individually, or each one defaults to Hold Last. Capture your positions and forget to assign Preset to the throttle channel, and you have configured nothing for it.

One more Spektrum detail that explains many "my failsafe isn't working" moments on the bench: with no transmitter signal at power-up, the AR637T+ servo ports have no control signal at all, and the AR620 and AR6610T throttle channel has no output, specifically so a receiver powered up alone does not arm the ESC. So a receiver that is quiet before the transmitter connects is by design, not failure.

For reference, Spektrum defines a "hold" as 45 consecutive frame losses, which takes about one second, after which the receiver moves the outputs to the failsafe settings. The manual notes it is normal to see a hold logged when you turn the transmitter off and on again.

If you need a receiver with Forward Programming and telemetry, the Spektrum AR637T is the listing this guide previously pointed to. Note that the manual quoted above is for the AR637T+, which Horizon's own page currently shows as back-ordered. Failsafe behavior was confirmed here only in the AR637T+ manual, so owners of the earlier AR637T should read the manual that shipped with theirs rather than assume the two match.

FrSky: pick the mode on purpose

FrSky's ETHOS manual describes the failsafe screen as determining "what happens at the receiver when the transmitter signal is lost." The options:

• Hold: keeps the last received positions.
• Custom: each channel gets its own setting, either Not Set, Hold, Custom or No Pulses. For a Custom channel you can capture the current channel value with the set icon or type a fixed value.
• No Pulses: turns off the pulses entirely. FrSky describes it as meant for flight controllers that handle return-to-home on loss of signal.
• Receiver: on X-series and later receivers, failsafe is set in the receiver itself.

For a plain plane with no flight controller, No Pulses is the one to treat with suspicion. It is a signal to a flight controller, not an instruction to a servo.

The ten-second rule

ETHOS states that failsafe data is sent from the transmitter approximately every 10 seconds. That has a practical consequence: change a value, then wait before you run the signal-loss test. Otherwise you are testing the old setting and wondering why the screen and the plane disagree.

The manual also notes that for TD, TW, AP and AP Plus receivers the failsafe data is now saved on the receiver, so settings are available immediately if the receiver reboots. The flip side: failsafe must be reset and checked after upgrading receivers that gain this feature. And if you change RF mode between ACCST D16 and ACCESS, FrSky tells you to check the model carefully, "especially Failsafe."

Let the radio nag you

ETHOS has a startup checklist with a failsafe check. When enabled it warns you if failsafe has not been set for the current model, and the manual calls it highly advisable to leave this enabled. It is a free reminder for a mistake that is easy to make on a new model slot.

A current FrSky receiver example is the FrSky Archer Plus R6, whose Amazon listing describes 6 PWM channels, 24 SBUS channels, signal redundancy and telemetry (listing claims, not tested here). This guide did not find failsafe details specific to that receiver, so use FrSky's documentation for it and the ETHOS screen above.

FlySky: read the [Off]

The FS-i6X manual is clear about what its failsafe screen means. Every channel is listed. If a channel displays [Off], then on signal loss that servo keeps its last received position. If it shows a percentage, the servo instead moves to that position.

To set it:

1. Press and hold OK until the main menu opens, then choose System Setup and RX setup.
2. Open the Failsafe item.
3. Use UP and DOWN to select a channel and press OK to enter its failsafe setting.
4. Use UP and DOWN to turn failsafe on for that channel.
5. Move the control for that channel to the position you want and hold CANCEL to confirm and exit.

The FS-iA6B receiver manual covers AFHDS 2A, binds with a binding cable on the B/VCC port (a solid LED means success, then unplug the cable), and carries a plain warning that an unreasonable failsafe setting may cause accidents. The manuals read for this guide do not say whether failsafe ships off, only what [Off] means, so look at the screen: [Off] holds, a percentage moves.

Radiolink: NOR versus F/S

On the AT9S Pro, failsafe sits in section 2.11 of the manual and is reached from the BASIC menu. Each channel is set independently and has two states:

• NOR (normal): holds the servo at its last commanded position.
• F/S: moves the servo to a predetermined position.

Three details from the manual that are easy to miss:

1. Throttle F/S also sets Battery F/S. The setting you choose for throttle applies to the low-receiver-battery response too.
2. Failsafe data goes out about every two minutes. Once you specify an F/S setting, the data is transmitted automatically once each two minutes. After changing it, wait at least two minutes with the receiver powered before turning the transmitter off to test.
3. Some channels need confirmation. The manual's example is a gasoline engine kill switch on channel 8: set it to the OFF position in F/S, and note the radio asks for confirmation before making that change.

The same page of the manual warns about governors. A governor controls the throttle while it is active, so the throttle will not obey the transmitter's throttle failsafe; set the failsafe of the governor's on/off channel to OFF so the governor shuts down and the throttle follows the failsafe.

If you run a 10-channel Radiolink receiver, the SYSTEM menu has a CH-SELECT item defaulting to 10CH. The manual says to set 12CH only for receivers such as the R12DS or R12DSM. The Radiolink R9DS is listed on Amazon as a 10-channel SBUS/PWM receiver for the AT9, AT9S, AT9S Pro, AT10II and AT10 transmitters (listing claims). Not every detail of a given Radiolink receiver is covered in the AT9S Pro manual, so verify your receiver's behavior on the bench rather than from a table.

Futaba: throttle only on S-FHSS, plus a battery failsafe

The Futaba TM-FH module and R2006GS receiver manual describes an S-FHSS system where failsafe works on the throttle channel only (channel 3). Its modes:

• HOLD: on signal loss the throttle servo stays at its last commanded position.
• F/S: on signal loss the receiver holds the throttle for one second, then moves it to a predetermined position.
• B.F/S (Battery Fail Safe): when the airborne battery voltage drops to approximately 3.8 V, the throttle moves to a predetermined position.

The manual is blunt about B.F/S: if it triggers, land immediately. You can temporarily reset it by moving the throttle stick to the predetermined position, after which you have about 30 seconds of throttle control before it reactivates. It suggests a 4-cell NiCd or NiMH receiver pack for effective use of the battery F/S, and advises against dry cells.

Setting is done with the "F/S, Range" switch on the back of the module, with a warning not to hold that switch while powering up because it alters the F/S status.

That is a good example of why "Futaba failsafe" is not one thing. Futaba's R7008SB receiver manual, for instance, lists a Battery F/S voltage that is set up from the transmitter, which is a different arrangement from the module-switch method above. For a Futaba transmitter family not covered here, use its own manual for the menu path.

For R7008SB shoppers, check the current Amazon listing for the Futaba R7008SB since this guide could not confirm an exact live listing.

Why failsafe can look broken when it is not

Most "failsafe isn't working" reports trace back to a short list of causes. Check these before you start swapping hardware.

That last row deserves emphasis. FrSky tells you to reset and check failsafe after upgrading receivers with failsafe saved on the receiver, Spektrum tells you to rebind to set failsafe on the AR620, and Futaba's S-FHSS setup uses a physical switch that behaves differently depending on when you press it. Every one of those is an easy way to end up with stale settings.

The ESC has an opinion too

The receiver is not the only device that reacts to signal loss. Many speed controllers include their own protection. As an example, Spektrum's Avian ESC manual lists throttle signal loss protection: if the ESC detects loss of signal for more than 0.25 second it cuts power to the motor immediately, and it resumes normal operation when throttle signals return.

Other ESCs behave differently, and some may do nothing special. That is why the ground test below watches the motor, not just the throttle servo output on a tester. If you are chasing a motor that cuts off or restarts oddly, the ESC guide explains how to separate ESC-side protections from receiver-side failsafe.

Two neighbors of failsafe are worth a read: the LiPo battery guide for voltage cutoffs, and the servo guide for how servos behave when the signal changes. If you are still building basic flying habits, the beginner's flying guide puts failsafe in the context of the pre-flight routine, where it belongs.

The ground test that proves it

This is the one step you should never skip, and every maker manual in this research agrees on its shape.

1. Remove the propeller. Spektrum's manuals say to secure the aircraft and remove the propeller before testing. For a nitro or gas model, disable the engine and restrain the airframe.
2. Power up normally. Turn on the transmitter, then the receiver, link, and note the servo and throttle positions.
3. Move the controls away from the failsafe positions. Throttle up a little, surfaces deflected. You want to see them move, not merely sit where they started.
4. Turn the transmitter off, or turn its RF output off. Spektrum's manuals phrase it as turning the transmitter RF output off.
5. Watch what happens. The throttle should go where you set it and the surfaces should go to their positions. If the outcome is "nothing", you have found a Hold.
6. Turn the transmitter back on and confirm normal control returns before putting the propeller back on.
7. Repeat after changes. Do it again after any rebind, firmware update, receiver swap or model-memory copy, and at the field before the first flight of the day, which is what the WRCS guideline recommends.

If your plane has a flight controller, the receiver's job is often just to report signal loss cleanly (No Pulses on FrSky, for example) and the flight controller decides what to do. That is a different kind of setup, covered in the flight controller guide. A flight controller does not remove the need for a ground test; it moves what you are testing.

FAQ