Betaflight failsafe setup and testing: stage 1, stage 2, GPS Rescue
When the radio link drops, failsafe decides what your quad does: carry on briefly, then cut the motors and fall, land, or fly home with GPS. Here is when Betaflight detects a signal loss, how stage 1 and stage 2 work, every parameter and its default, how to set it all up in the Failsafe tab of the Betaflight App, how to test it safely and how to arm again afterwards. Checked against the source code of the firmware and App 2026.6.2 and the Betaflight docs, as of November 13, 2026.
What failsafe is and when it triggers
The failsafe docs distinguish two kinds:
- Receiver based failsafe: on signal loss the receiver sends preset channel values to the flight controller (FC). Since the data looks normal, the docs say the FC won’t notice that the link is down. Betaflight’s failsafe settings never kick in, and you see nothing in the OSD.
- Flight controller based failsafe: on signal loss the receiver stops sending channel data. Betaflight notices and responds the way you set it up in the Failsafe tab. According to the docs this also works if the wires to the receiver come loose or the receiver locks up.
The docs are clear: “We do NOT recommend using receiver based failsafe! Always ensure that the receiver is configured to 'send no data' on signal loss!” How to check that is under Receiver side.
Betaflight 2026.6.2 detects a signal loss in three ways (rx.c):
- No packets: no valid packet arrives for 150 ms. Packets the receiver itself marks as failsafe or dropped don’t count as valid. The docs still say 100 ms, the code says 150 ms (
RXLOSS_TRIGGER_INTERVAL). - Invalid pulses: a flight channel (roll, pitch, yaw or throttle) stays outside
rx_min_usectorx_max_usecfor more than 300 ms, 885 to 2115 µs by default (rx.c). According to the docs this only applies to PPM receivers. - Switch: the FAILSAFE mode is on a switch and you flip it on (see Failsafe switch).
As soon as Betaflight detects the loss, it blocks arming and shows RXLOSS (failsafe.c). Stage 2 only happens while the quad is armed, and no earlier than 5 seconds after the FC powers up; according to the docs this prevents unwanted activation with gear that takes long to bind (core.c).
Sequence: hold, stage 1, stage 2
Time counts from the last valid packet. With the defaults of 2026.6.2, a real signal loss runs like this (rx.c, failsafe.c):
| Time since last packet | What Betaflight does |
|---|---|
| 0 to 300 ms | The last valid values are held. After 150 ms without a packet RXLOSS appears and arming is blocked. |
300 ms to 1.5 s (failsafe_delay) | Stage 1: every channel gets its fallback value. By default roll, pitch and yaw go to center and throttle all the way down; the switches (AUX channels) stay where they were. The PID loop keeps running. |
| from 1.5 s | Stage 2, only when armed: the selected procedure, “Drop” by default, i.e. disarm right away and motors off. |
| Signal back | Before stage 2 you get control back immediately. After stage 2 the signal has to be valid for failsafe_recovery_delay first, 0.5 s by default. |
The docs also call stage 1 the “guard” period: if a valid packet arrives during it, the FC responds immediately and the failsafe is over. According to the docs there’s no dedicated stage 1 indicator in the OSD; the warnings field shows RXLOSS. In stage 2 the flight mode field shows “!FS!” when landing, “RESC” during GPS Rescue, “N-RESC” with the Flight Plan build option (osd_elements.c).
On stage 1 throttle the docs warn: “Because Stage 1 cuts throttle to zero by default, the craft may immediately start to fall from the sky. It may be better to set this to a throttle value where the quad descends slowly, or just hovers. It is essential to do this when GPS Rescue is enabled for Stage 2 Failsafe, or the quad may crash in Stage 1 before the Rescue has time to start.” There’s no single value for it, it depends on your quad. How the docs determine it is under GPS Rescue as stage 2.
The stage 2 procedures
- Drop (CLI
DROP, default): Betaflight disarms right away, the motors stop, the quad falls (failsafe.c). - Land (
AUTO-LAND): Betaflight switches to Angle mode if there’s an accelerometer (core.c), centers roll, pitch and yaw and holds throttle atfailsafe_throttleuntilfailsafe_landing_timeruns out; then it disarms. The switches stay at their stage 1 values. With Altitude Hold in the firmware and an altitude source, Betaflight controls the descent rate instead of the fixed throttle value (alt_hold_multirotor.c). Altitude Hold isn’t a default option on the build server, see build options. According to the App docs the quad disarms on landing by itself with Altitude Hold; in the 2026.6.2 code that depends on the impact detectionlanding_disarm_threshold, which is off by default (pid.c). - GPS Rescue (
GPS-RESCUE): the quad flies home with GPS and lands, see GPS Rescue as stage 2.
On landing throttle the docs say: “Default is set to 1000 which means throttle off, and will cause the quad to descend very rapidly”. And on Landing Mode as a whole: “We do not recommend enabling this mode, other than for testing failsafe switches and figuring out suitable hover values for GPS Rescue.”
There’s also an invisible variant, “Just Disarm” in the docs: if throttle was low for at least failsafe_throttle_low_delay before the signal loss (10 s by default), Betaflight disarms right at the end of stage 1 instead of landing. It doesn’t apply to GPS Rescue (failsafe.c). According to the docs it’s meant for the case where you switch off your radio after landing but forgot to unplug the battery.
Every failsafe parameter with its default
Each parameter with its CLI name, the field in the App, the default and the allowed range from the 2026.6.2 source code (settings.c, failsafe.c, rx.c). These are factory defaults, not recommendations. The CLI counts times in tenths of a second, only failsafe_landing_time in whole seconds; the App converts everything to seconds (FailsafeTab.vue).
| Parameter (CLI) and field in the App | Default 2026.6.2 | Range |
|---|---|---|
| Detecting signal loss | ||
rx_min_usec“Minimum length” | 885 µs | 750 to 2250 |
rx_max_usec“Maximum length” | 2115 µs | 750 to 2250 |
| Stage 1 | ||
failsafe_delay“Period of time in Stage 1 failsafe after signal loss [seconds]” | 15 = 1.5 s | 1 to 200 = 0.1 to 20 s |
rxfailbox “Stage 1 - Channel Fallback Settings” | roll, pitch, yaw, throttle: “Auto” (center 1500, throttle at rx_min_usec); AUX channels: “Hold” | “Auto” only for roll to throttle, “Hold”, “Set” with 750 to 2250 in steps of 25 |
| Stage 2 | ||
failsafe_procedureselection under “Stage 2 - Failsafe Procedure” | DROP, “Drop” in the App | AUTO-LAND (“Land”), DROP, GPS-RESCUE (“GPS Rescue”) |
failsafe_landing_time“Delay for turning off the Motors during Failsafe [seconds]” | 60 s | 0 to 250 s |
failsafe_throttle“Throttle value used while landing” | 1000 (throttle off) | 750 to 2250 |
failsafe_throttle_low_delay“Failsafe Throttle Low Delay [seconds]” | 100 = 10 s | 0 to 300 = 0 to 30 s |
| Failsafe switch | ||
failsafe_switch_mode“Failsafe Switch Action” | STAGE1, “Stage 1” in the App | STAGE1, KILL, STAGE2 |
| Getting control back | ||
failsafe_recovery_delaynot in the App, CLI only | 5 = 0.5 s (build with RACE_PRO: 1 = 0.1 s) | 1 to 200 = 0.1 to 20 s |
failsafe_stick_thresholdnot in the App, CLI only | 30% | 0 to 50% |
The docs still call the landing time failsafe_off_delay; in 2026.6.2 it’s failsafe_landing_time and counts whole seconds. What’s set on your quad is shown in the CLI:
# Target quad: <name of your quad> # only prints, changes nothing get failsafe rxfail
get failsafe lists every parameter with “failsafe” in its name, with its allowed range and default; rxfail on its own lists the fallback of every channel: a for Auto, h for Hold, s for Set with a value (cli.c, rxfail). Before you change anything, back everything up as described in Betaflight backup with diff all. After a firmware update with a full chip erase the failsafe values are back at their defaults too (Flash Betaflight firmware).
Setting it up in the App’s Failsafe tab
The App only shows the “Failsafe” tab in Expert Mode (sidebar_items.js): click the wrench in the sidebar (tooltip “Toggle expert mode”) or turn on “Enable Expert Mode” in the options. Below the info box at the top there are four boxes:
- “Valid Pulse Range Settings”: “Minimum length” and “Maximum length” are
rx_min_usecandrx_max_usec. The App docs: “For most cases, leave these settings at their default values.” - “Stage 1 - Channel Fallback Settings”: per channel “Auto” (only roll, pitch, yaw and throttle), “Hold” or “Set” with your own value. Next to each AUX channel the App shows which mode is on it. The FC stores values in steps of 25 µs, smaller changes disappear.
- “Failsafe Switch”: “Failsafe Switch Action”, see Failsafe switch.
- “Stage 2 - Settings”: “Period of time in Stage 1 failsafe after signal loss [seconds]” is
failsafe_delay, “Failsafe Throttle Low Delay [seconds]” isfailsafe_throttle_low_delay. Below, under “Stage 2 - Failsafe Procedure”, you pick the procedure. The App only shows the Land fields when “Land” is selected, and the GPS Rescue fields only with “GPS Rescue” or a switch with the GPS RESCUE mode (FailsafeTab.vue).
At the bottom click “Save and Reboot”, the FC restarts afterwards. failsafe_recovery_delay and failsafe_stick_threshold aren’t in the App: it only reads and writes the other six values (msp.c). You set these two in the CLI, with your value instead of the placeholder:
# Target quad: <name of your quad> set failsafe_recovery_delay = <value in tenths of a second> save
Failsafe switch
In the Modes tab you put the FAILSAFE mode on a switch. What it triggers depends on “Failsafe Switch Action” (failsafe_switch_mode, “Stage 1” by default):
- “Stage 1” (
STAGE1): roll, pitch, yaw and throttle jump to their fallback values immediately, the AUX channels stay active. Switch back and you have full control right away. According to the App this simulates the exact signal loss behavior. But: “If the switch is held ON for longer than the failsafe_delay period, the flight controller will enter Stage 2 (see below), and, depending on how Stage 2 is configured, may immediately drop, or disarm.” - “Stage 2” (
STAGE2): starts the stage 2 procedure right away (failsafe.c). Switching back ends it immediately according to the docs; only a Drop has already disarmed by then. - “Kill” (
KILL): “immediately disarms the quad with no delay. Your craft will crash. Note that a single glitch on the failsafe channel will immediately crash the quad.”
While the switch is on, Betaflight blocks arming with the flag BOXFAILSAFE (core.c). The GPS Rescue docs also warn: “DO NOT share the Failsafe switch aux channel activation range with any other flight mode!”
Receiver side: send nothing on signal loss
For Betaflight to detect the loss, the receiver must stop sending channel values or mark them as failsafe. What Betaflight evaluates per protocol:
- CRSF (ELRS, Crossfire): the channel packets carry no failsafe flag that Betaflight reads. It detects the loss when channel packets stop arriving (
crsf.c). - SBUS: Betaflight reads the failsafe flag in the SBUS frame (
sbus_channels.c). On ELRS receivers with SBUS output the Lua setting is called “SBUS Failsafe”: “No Pulses” stops sending, “Last Pos” keeps sending the last values with that flag (ExpressLRS docs).
Whether it works for you, the docs say to check in the Receiver tab before the test: switch off the radio or the TX module. If Betaflight detects the loss, the App 2026.6 shows a “Failsafe active” box above the channel bars and tints the bars (release notes). It appears as soon as one of the flags FAILSAFE, RXLOSS or BOXFAILSAFE is set; the values below are then the failsafe output, not your receiver’s values (stores/fc.js). If there’s no box and no RXLOSS, your receiver keeps sending values and Betaflight’s failsafe won’t kick in. How to connect an ELRS receiver to Betaflight is in Bind an ELRS receiver.
How well do your rates fit your stick? The free check measures it on your blackbox log. No account, the file stays with you.
No log yet? See a real example · Turn on logging, with pictures
For your next flying day
- Betaflight App, Blackbox tab: logging device onboard flash or SD card, logging rate 1 kHz
- RC Commands, Setpoint and Gyro on, then “Save and reboot”
- Fly 3 to 5 packs of normal acro
- Then get the log off the quad and drop it into the free check
Testing failsafe safely
The failsafe docs open with: “Always confirm that your failsafe system is working properly before flying!” Every bench test there comes with “remove the props!”, and for motor tests: “Always remove props before connecting a battery and testing motors.”
- Disconnect the App: while it’s connected, the flag MSP blocks arming (MSP). So you watch the motors and the OSD in your goggles. With the App connected the FC also doesn’t beep on signal loss (
failsafe.c). - Cause the signal loss: best by disabling the TX module in your radio. “On most radios, this immediately stops sending any data to the receiver, and is the quickest and most effective way to emulate losing the Rx signal.” The docs also list switching off the radio or cutting power to the receiver.
- Throttle up first: otherwise “Just Disarm” may kick in. “This can sometimes cause confusion when testing failsafe. Always test with throttle up at some point before the test.”
Test 1: stage 2 with Drop
- Select the “Drop” procedure (default), props off, battery on.
- Arm and throttle up briefly.
- Cause the signal loss while moving the throttle up and down.
- Expected: for 300 ms the motors respond as before, then they run on the stage 1 values. After
failsafe_delay(1.5 s from the last packet by default) they stop and the quad is disarmed. The OSD shows RXLOSS, after the disarm alternating with FAILSAFE according to the docs. - TX module back on. After 0.5 s of valid signal RXLOSS and FAILSAFE disappear. If the arm switch is still on, the OSD shows NOT_DISARMED: switch off, then arm again.
Test 2: stage 1
For this test the docs suggest setting the stage 1 time to 10 s (failsafe_delay 100), stage 2 to “Drop” and a hover value for stage 1 throttle, so you can hear what happens. Arm, throttle up briefly, move the sticks, kill the signal: the motors hold for 300 ms, then drop to the stage 1 throttle value and stay there until the quad disarms after 10 s. In a second run, restore the signal within the 10 s with some throttle and moving sticks: the motors must respond to the sticks immediately. Afterwards set failsafe_delay and the stage 1 throttle back to your values (15, i.e. 1.5 s, and “Auto” by default).
How to tell stage 2 kicked in
- Drop: the motors stop after
failsafe_delay, and the quad can only be armed again once the signal has been valid for 0.5 s. Until then it reports the flag FAILSAFE. - Land and GPS Rescue: the OSD flight mode field shows “!FS!” when landing, “RESC” or “N-RESC” during GPS Rescue. When landing the motors run at landing throttle until
failsafe_landing_timeruns out (60 s by default); in Angle mode, according to the docs, the PIDs make them spool up. - In the App: afterwards the Setup tab shows the arming flags, in the CLI the
statuscommand.
Land and GPS Rescue in the field
According to the docs you test Land and GPS Rescue only after the bench test, with the failsafe switch (action “Stage 2”), low over soft ground and well away from people and buildings. Plan beforehand how to restore the link right away if the quad flies off: you can’t disarm until the link is back. The App docs: “If a switch-induced Landing or Rescue test has a problem, or seems to float around, DO NOT DISARM IN PANIC! Undo the Rescue switch promptly and you'll get full control back immediately. Do not wait more than 15s or it may disarm and crash.”
Arming again after a failsafe
The docs are clear: “There is no way to instantly recover from Stage 2 Failsafe caused by signal loss, or from a disarm at the end of Stage 2”. Betaflight tells you what blocks arming with an arming flag:
- RXLOSS: no valid signal, or it hasn’t been valid for
failsafe_recovery_delayyet (0.5 s by default). - FAILSAFE: stage 2 has disarmed. Clears once the signal has been valid for 0.5 s (
failsafe.c). - NOT_DISARMED (BAD_RX_RECOVERY in the App): the signal came back while the arm switch was on. Switch off, then arm.
- BOXFAILSAFE: the failsafe switch is on.
Since Betaflight 4.3 you no longer have to power cycle after a failsafe, according to the docs: if you can get close enough after a crash to regain signal, you can re-arm and fly out. In flight you get control back like this: in stage 1 right away, when landing after failsafe_recovery_delay, and with GPS Rescue only once you also move a stick (see below). If a switch triggered the failsafe, switching it back is enough, except with “Kill”. Every other reason a quad won’t arm is in Quad won’t arm: all arming flags.
GPS Rescue as stage 2
With “GPS Rescue” as the procedure, according to the GPS Rescue docs the quad flies home, lands and disarms by itself. This section only covers what concerns failsafe; every setting of the rescue itself is in the docs.
- Accelerometer: with GPS Rescue as the procedure, Betaflight requires a calibrated accelerometer, otherwise NO_ACC_CAL blocks arming (
core.c). - GPS fix before arming: without a fix with at least
gps_rescue_min_satssatellites (8 by default, “Minimum satellites” in the App), GPS blocks arming. The App labels the switch that bypasses this “Allow arming without fix - WARNING: No fix = disarm on failsafe!”. The docs: “Be 100% sure you have a valid Home Point before arming or the quad will disarm and crash when a true failsafe occurs.” - Stage 1: stage 1 throttle has to keep the quad up, see the warning under Sequence. The GPS Rescue docs determine the value like this: Failsafe switch action “Stage 2”, procedure “Land”, adjust “Throttle value used while landing” until the quad descends gently. Then enter that value as the GPS Rescue “Throttle hover” and as the stage 1 fallback for throttle, and set the procedure back to “GPS Rescue”.
- No “Just Disarm”: with GPS Rescue Betaflight doesn’t disarm because of low throttle (
failsafe.c). - Getting control back: “Remember: During a real failsafe, after the link is restored, either the roll or pitch stick MUST be moved beyond the configured failsafe stick threshold (30% by default) before you can regain control over the quad.” The code also counts yaw (
core.c). According to the docs, don’t touch the sticks until your video is solid, RXLOSS has gone and the signal strength is OK. If a switch triggered the rescue, switching it back is enough.
Two sentences from the docs before you rely on it: “Test GPS Rescue very carefully before relying on it. Initial testing should be done at close range, with defaults, over soft grass.” “Even if you do everything right, GPS Rescue may not bring the craft home!” In 2026.6 GPS Rescue was rebuilt; according to the release notes some old settings are gone, a compass only counts with trust_mag = ON, and if a rescue goes wrong the firmware now attempts a controlled descent.
Faults: symptom, cause, fix
Sorted by the moment things go wrong. Causes from the 2026.6.2 source code, fixes from the docs or the code.
Detecting signal loss
Radio or TX module off, but no RXLOSS and no “Failsafe active” box in the Receiver tab; the bars stay where they are
- Cause
- The receiver keeps sending channel values on signal loss (receiver based failsafe). The docs: “the flight controller will be unaware that the link is down”, so its failsafe settings never kick in.
- Fix
- Set the receiver to send no data on signal loss (docs). On ELRS with SBUS output that’s the “SBUS Failsafe” setting in the Lua script: “No Pulses” sends nothing, “Last Pos” sends the last values with the failsafe flag, which Betaflight reads for SBUS. Then check again.
The bars in the Receiver tab don’t follow the sticks, above them it says:
App message“Failsafe active”
- Cause
- Betaflight is in failsafe, has no valid signal or the failsafe switch is on (flags FAILSAFE, RXLOSS or BOXFAILSAFE). According to the App, the values below are the failsafe output, not the live values from your receiver.
- Fix
- Get the link up (binding, port and protocol, for ELRS see Bind an ELRS receiver) or switch the failsafe switch off.
While testing
The quad won’t arm for the test, the flag is:
ShownMSP
- Cause
- The Betaflight App is connected and blocks arming.
- Fix
- Click “Disconnect” in the App, then test and watch the motors and the OSD. Details: arming flag MSP.
Test with “Land”: after stage 1 the motors stop instead of running on at landing throttle
- Cause
- Throttle was low for at least
failsafe_throttle_low_delaybefore the signal loss (10 s by default). Betaflight then disarms right at the end of stage 1 instead of landing; the docs call it “Just Disarm”. It doesn’t apply to GPS Rescue. - Fix
- The docs: “Always test with throttle up at some point before the test.”
Test with the failsafe switch: after a second or so the motors stop
- Cause
- “Failsafe Switch Action” is set to “Stage 1” (default). If the switch stays on longer than
failsafe_delay, stage 2 follows with the selected procedure, Drop by default. - Fix
- For stage 1, switch on only briefly. To test Land or GPS Rescue with the switch, pick the action “Stage 2”.
Radio switched off, the quad is on the ground, and the props suddenly spin up
- Cause
- The quad was still armed and stage 2 is set to “Land”. Betaflight then outputs the landing throttle at the end of stage 1; the docs: “the props may spin up without warning at the end of Stage 1”. “Just Disarm” only prevents this when throttle was low for 10 s.
- Fix
- The docs: “Keep the radio on, and the sticks in the disarmed position, until the quad is powered down.” Always disarm first, then switch the radio off.
After the failsafe
The signal is back but the quad won’t arm, the OSD shows:
ShownNOT_DISARMED
- Cause
- The signal came back while the arm switch was still on. The docs: “After a failsafe disarm, if the link is restored while the Arming switch is active, the quad will not automatically re-arm itself.”
- Fix
- Arm switch off, then arm as usual. More under NOT_DISARMED.
After stage 2 the quad won’t arm, the OSD alternates:
ShownFAILSAFE / RXLOSS
The quad won’t arm, the flag is:
ShownBOXFAILSAFE
- Cause
- The FAILSAFE mode is on a switch, and that switch is on.
- Fix
- Switch the failsafe switch off, see BOXFAILSAFE.
Landing and GPS Rescue
On a real signal loss the quad drops before Land or GPS Rescue even starts
- Cause
- In stage 1, throttle is on “Auto” by default, i.e. all the way down. Stage 2 only starts after
failsafe_delay(1.5 s by default). - Fix
- The docs: set the stage 1 fallback for throttle to “Set” with a value where the quad descends slowly or hovers; with GPS Rescue the docs call this essential. How to find the value is under GPS Rescue as stage 2.
When landing in failsafe the quad climbs or falls fast
- Cause
- “Throttle value used while landing” (
failsafe_throttle) doesn’t fit: too high and it climbs, too low and it falls (App docs). By default it’s 1000, i.e. throttle off. This applies without Altitude Hold in the firmware; with Altitude Hold, Betaflight controls the descent rate itself. - Fix
- The docs: work towards it with the failsafe switch, low over soft ground, and “If in doubt, start with a LOW value.”
With GPS Rescue as stage 2 the quad won’t arm, the flag is:
ShownGPS / NO_ACC_CAL
- Cause
- GPS: no fix with at least
gps_rescue_min_satssatellites yet (8 by default). NO_ACC_CAL: with GPS Rescue as the procedure Betaflight needs the accelerometer, and it isn’t calibrated. - Fix
- Wait for the fix, or calibrate the accelerometer in the Setup tab. Details: GPS and NO_ACC_CAL.
After a GPS Rescue the signal is back, but the quad keeps flying home and doesn’t respond
- Cause
- After a real signal loss Betaflight only hands back control once the signal has been valid for
failsafe_recovery_delayand you move a stick at leastfailsafe_stick_threshold(30% by default). - Fix
- Move the sticks, but according to the docs only once your video is solid, RXLOSS has gone and the signal strength is OK.
Sources
As of November 13, 2026, checked against Betaflight 2026.6.2 (firmware and App from September 16, 2026, the latest versions on that day). Nothing here was tested on hardware; sequences, defaults and App texts come from the source code and docs.
- Betaflight docs: Failsafe, Failsafe Tab, GPS Rescue, Rx, Motors Tab, 2026.6 release notes.
- Firmware source code:
failsafe.c,failsafe.h,rx.c,rx.h,settings.c,cli.c,core.c,alt_hold_multirotor.c,pid.c,msp.c,crsf.c,sbus_channels.c,common_defaults_post.h. - App source code:
FailsafeTab.vue,ReceiverTab.vue,stores/fc.js,sidebar_items.js, textslocales/en/messages.json. - ExpressLRS docs: Lua Script (SBUS Failsafe).
Last updated: Nov 14, 2026 · checked with Betaflight 2026.6.2