Betaflight Failsafe and arming: CLI settings

What the quad does when the RC link drops (stage 1 delay, stage 2 procedure, throttle), arming angle limits, auto-disarm and runaway-takeoff protection.

14 settings in Betaflight 2026.6, plus 1 that earlier releases had. Each range and value list is read from the firmware's settings.c, each default from the CLI get of the release built for the simulator (no board config applied), so a board's own config can still change it. Set one with set name = value, then save. Paste a diff all into the CLI checker to test it against any release.

SettingTypeRange or valuesDefault 4.44.52025.122026.6Notes
auto_disarm_delay # uint8
global
0 to 60 5 ✓✓✓✓
failsafe_delay # uint8
global
1 to 200 15 ✓Δ✓✓ 4.5: min 2 → 1
failsafe_landing_time # uint8
global
0 to 250 60 ——✓✓
failsafe_off_delay # uint8
global
0 to 200 10 ✓✓—— Removed in 2025.12.
failsafe_procedure # uint8
global
AUTO-LAND, DROP, GPS-RESCUE DROP ✓✓✓✓
failsafe_recovery_delay # uint16
global
1 to 200 set by the target ✓Δ✓✓ 4.5: min 0 → 1
failsafe_stick_threshold # uint8
global
0 to 50 30 ✓✓✓✓
failsafe_switch_mode # uint8
global
STAGE1, KILL, STAGE2 STAGE1 ✓✓✓✓
failsafe_throttle # uint16
global
750 to 2250 1000 ✓✓✓✓
failsafe_throttle_low_delay # uint16
global
0 to 300 100 ✓✓✓✓
gyro_cal_on_first_arm # uint8
global
OFF, ON OFF ✓✓✓✓
prearm_allow_rearm # uint8
global
OFF, ON OFF ——✓✓
runaway_takeoff_deactivate_delay # uint16
global
100 to 1000 500
needs USE_RUNAWAY_TAKEOFF
✓✓✓✓
runaway_takeoff_deactivate_throttle_percent # uint8
global
0 to 100 20
needs USE_RUNAWAY_TAKEOFF
✓✓✓✓
runaway_takeoff_prevention # uint8
global
OFF, ON ON
needs USE_RUNAWAY_TAKEOFF
✓✓✓✓

✓ present, Δ changed in that release (hover for what changed), — not in that release. “needs USE_…” is the build option the setting is compiled with: a cloud build without it has no such setting.

Other sections

What changed between releases: 4.4 → 4.5 · 4.5 → 2025.12 · 2025.12 → 2026.6. Machine-readable: params.json (2026.6.2), GPL-3.0 like the firmware it comes from.