Failsafe: How to Set It on Every Brand, and Why Binding Wipes It
What failsafe does when the link drops, the brake-versus-neutral argument with both sides, the actual procedure for Spektrum, FrSky, Futaba and budget receivers, the 30-second test almost nobody does — and the warning that every re-bind resets it.
Updated Jul 22, 2026 · RC Crash Crew
Your transmitter and receiver are talking to each other hundreds of times a second. Failsafe is what the receiver does the moment that conversation stops.
Set correctly, a car that loses signal brakes and centers its steering, and stops within a few meters. Set carelessly — or never set at all — it carries on at whatever throttle it last had until it hits something, runs out of battery, or reaches a road.
This is the one setting that costs nothing, takes two minutes, and is skipped by almost everyone.
When failsafe actually fires
It is not only for dramatic failures. The link drops for ordinary reasons:
- Out of range — further than you thought, or with something between you and the model
- Transmitter battery dies mid-run — the most common cause by a distance
- You switch the transmitter off first by mistake, before the model
- Interference or a saturated 2.4GHz environment — a busy race meeting, a crowded park
- A damaged or badly placed receiver aerial — the model still works at 20 meters and fails at 60
- Loose receiver power wiring, or a BEC browning out under a hard steering load
That last one deserves emphasis: a brown-out looks exactly like a signal loss and is far more common than people think. If the receiver loses power momentarily it reboots, and whatever your failsafe does happens then too.
The setting that matters: brake, or neutral?
Most hobby advice says "set failsafe to full brake." There is a real counter-argument, and both sides have a point. This is worth understanding rather than copying.
The case for full brake. The model stops in the shortest possible distance. On a big open field, near a car park, or anywhere near a road, distance travelled after signal loss is the thing that matters and braking wins.
The case for neutral. Two practical problems with brake, raised by experienced racers (RCTech):
- If you switch the transmitter off and leave the car on, a brake failsafe holds the ESC in braking indefinitely. On some setups that means the servo is also being held hard over, and you can cook a servo or drain a pack without noticing.
- On a race track, a car that locks up at full brake mid-straight becomes a stationary obstacle for everyone behind it. A car set to neutral coasts and slides off the racing line.
Our position: *where* you run should decide it.
- Bashing in open ground, near roads, water, or people → full brake. Stopping distance is the priority.
- Club racing on a marshalled track → neutral is defensible, and is what many racers use, for the reasons above.
- Aircraft and drones are a different problem entirely — see below.
Whichever you choose, steering to center is not controversial. A model that loses signal mid-corner should not keep turning.
How to set it — by brand
The procedures genuinely differ. Yours is in your manual; these are the common patterns so you know what you are looking for.
Spektrum — set during binding. Failsafe positions are captured *as part of the bind process*. Start the bind as the manual describes, and hold the controls where you want the failsafe to be while binding completes. Holding full brake during bind sets failsafe to full brake (RCTech). This is why re-binding a Spektrum system silently changes your failsafe — see the warning below.
FrSky — the F/S button, after binding. Bind first, disable transmitter-side failsafe, set every control where you want it, then briefly press the F/S button on the receiver. This "no signal" method is how most modern FrSky receivers work (FrSky manual, PDF).
Futaba — via a temporary throttle position. On some Futaba systems the transmitter is temporarily set to output a throttle value *below* normal low idle, that value is stored as the failsafe, and low stick is then returned to normal.
Generic / budget receivers (FlySky and many others) — a bind or set button. Usually: hold the controls where you want them, press and hold the receiver's button until the LED confirms.
⚠️ Some very cheap receivers have no configurable failsafe at all. They either hold the last received position — the worst possible behavior — or cut all output. If you cannot find failsafe in the manual, assume it does not have one and treat the model accordingly.
⚠️ Binding resets failsafe. Every time.
This is the single most important line on this page.
Any time you re-bind — new receiver, new transmitter, a fix for a glitch, a firmware update — your failsafe settings are reset to factory defaults or lost entirely. On Spektrum it is captured *during* the bind, so a careless re-bind with the throttle wherever your hand happened to be sets that as your failsafe.
Re-set and re-test failsafe after every single bind. Put it on the checklist with wheel nuts and gear mesh.
Testing it — the part nobody does
An untested failsafe is an assumption.
Ground test, surface models:
- Put the model on a stand with all wheels clear of the ground. Not on the floor.
- Switch on the model. Confirm normal control.
- Apply a little throttle, and while it is running, switch the transmitter off.
- Watch what happens. The wheels should stop (or coast, if you chose neutral) and the steering should center — within about a second.
- Switch the transmitter back on and confirm control returns.
If the wheels keep spinning at the throttle you left, your failsafe is not set. That is the whole test, and it takes thirty seconds.
Do the same after any crash, along with a range check — aerial damage is invisible and both symptoms show up together.
Aircraft, drones and boats
Fixed-wing aircraft: cutting the motor and holding a gentle turn is the common approach, so the model spirals down in a small area rather than flying away under power. Check your national model-flying body's guidance — several publish specific recommendations.
Multirotors: flight controllers handle this rather than the receiver. Betaflight and similar firmware have their own failsafe stage settings — typically a brief hold, then a drop or a return-to-home if GPS is fitted. Configure it in the flight controller, and confirm the receiver is set to output no signal on link loss rather than holding last position, or the flight controller never realises anything is wrong. That combination — receiver holding last position, flight controller therefore not triggering — is a classic fly-away cause.
Boats: a boat that loses signal at speed keeps going, and there is no braking. Cutting throttle is standard, and it is a good argument for not running further out than you could reach with a recovery.
What failsafe does not protect you from
Worth being clear, because people over-trust it:
- It does not prevent signal loss. It only limits the consequences.
- It cannot help if the receiver loses power entirely — a disconnected battery, a severed wire, a dead BEC. There is nothing running to execute the failsafe.
- It does not fix a bad installation. Aerials against carbon fiber or metal, or wrapped around power wires, will keep causing dropouts.
- On a model that has already gone out of range and is driving away, it will fire the moment the link drops — which is why range and aerial placement matter more than failsafe does.
The two-minute checklist
- Read your receiver's manual section on failsafe. They genuinely differ.
- Decide brake or neutral based on where you run.
- Set it, with steering centered.
- Test it with the wheels off the ground by switching the transmitter off.
- Re-set and re-test after every re-bind, every receiver swap, and every crash.
- Do a range check at the same time.
What we could not confirm
Exact procedures vary not only by brand but by receiver model and firmware version within a brand, and manufacturers revise them. We have described the common patterns so you know what to look for — your own receiver's manual is the authority, and it is worth reading before the first run rather than after the incident.