Betaflight won’t arm? All arming disable flags explained

When your quad won’t arm, Betaflight tells you why: as short names like RXLOSS, THROTTLE or MSP, the arming disable flags. Here are all 30 of Betaflight 2026.6.2 with cause and fix, plus where to see them and what the Betaflight App calls them. Backed by the source code of the firmware and the App and by the Betaflight docs.

Quick: how to find the reason

  1. With goggles: props off (if nothing blocks, the quad arms), battery in, radio on, flip the arm switch. The OSD shows the reason as a warning, but only while the arm switch is on.
  2. On a computer: connect the quad to the Betaflight App over USB. In the Setup tab, the “System info” box has the line “Arming Disable Flags:” with every active reason. Or type status in the CLI tab.
  3. Look it up: find the name in the list of all flags. Without goggles or a computer, the beep code helps.

The Betaflight troubleshooting page lists THROTTLE (throttle not all the way down), ANGLE (quad not level), NOPREARM, CALIB and DSHOT_TELEM (there still under its old name RPMFILTER) among “the more common arm prevention flags”. MSP, CLI and CMS, according to the same page, “should only appear when using some sort of configuration interface (ie. connected to the Betaflight App)”.

Where Betaflight shows you the reason

In the goggles (OSD)

According to the source code (osd_warnings.c), the OSD shows an arming block only while the arm switch is on, using exactly the short name from the list below. ARM_SWITCH only shows up there when nothing else is blocking. The warning is on by default. In the App it belongs to the OSD element “Warnings”, whose description includes “warnings (e.g. reasons for not arming, critically low battery)”; in the OSD tab the single warning is called “Arming disabled”. If several reasons are active, the App or status gives you the full list.

In the Betaflight App

Setup tab, “System info” box, line “Arming Disable Flags:”. Every active reason is listed there, and a tooltip explains it when you hover over it (SetupTab.vue). The App uses some names that differ from the OSD and CLI, such as BAD_RX_RECOVERY instead of NOT_DISARMED or ACC_CALIBRATION instead of NO_ACC_CAL; the list below has both. When nothing but ARM_SWITCH is set, the App shows “Arming Allowed”.

In the CLI

Type status in the CLI tab. The output contains the line “Arming disable flags:” followed by the short names of all active reasons, separated by spaces, ARM_SWITCH included (cli.c). New in Betaflight 2026.6 is the env command: env ARMING shows only the line ARMING_DISABLE_FLAGS= with the same names.

By beeps

With a buzzer on the flight controller, Betaflight beeps the most important reason after a failed arm attempt: the flag with the lowest number (core.c). A few short attention beeps are followed by long and short beeps. The docs: “The arming prevention condition that is active can be calculated as (5 * <number of long beeps>) + <number of short beeps>.” Two long and three short beeps are beep code 13, which is CALIB. The table below maps every code to its flag. According to the source code, the DShot motor beacon does not play this code (beeper.h); you need a real buzzer for it.

Other signs

  • Status LED: it flashes as long as arming is blocked (core.c).
  • Radio with CRSF telemetry: the telemetry docs: “While disarmed (and not in failsafe), one of the following characters is appended to the flight mode string” (sensor FM): “!” means arming disabled, “*” ready to arm, “?” GPS rescue configured but not enough satellites or no fix.

CLI and MSP: blocks set by the connection

When you check on a computer, CLI and MSP can show up in the list. Both come from the connection itself: the Betaflight App blocks arming over MSP when it connects (serial_backend.js) and releases it when it disconnects, and Betaflight sets CLI as soon as the command line is opened (cli.c). The troubleshooting page puts both among the flags that only appear with a configuration interface connected.

For troubleshooting this means: if you are connected to the App or in the CLI right now, these two come from there; what matters are the other names. To fly, click “Disconnect” in the App, because according to the docs, “unplugging USB does not clear this flag”. You leave the CLI with exit or save; both reboot the flight controller.

All 30 arming flags with cause and fix

The flags are grouped by topic. Each box gives the name in the OSD and CLI, the beep code, the name and tooltip in the Betaflight App, when Betaflight sets the flag and what helps according to the docs or the source code. The basis is the Betaflight 2026.6.2 source code (runtime_config.c, core.c) and the docs page Arming Sequence & Safety.

Radio link and failsafe

RXLOSS

Beep code 3: 3 short

In the App
RXLOSS, tooltip: “No valid receiver signal is detected”
Cause
The flight controller gets no valid signal from the receiver: right after power-on until the signal has been stable for a while, when no valid data arrives for more than 150 ms, or when the link is gone for longer than failsafe_delay. The flag clears once the signal has been valid for failsafe_recovery_delay (default 500 ms).
Fix
The docs: “Your receiver is either faulty or has no link to the transmitter.” Switch on the radio and get the link up. In the Receiver tab the App then shows a box “Failsafe active”: the channel values below it are the failsafe output, not the live values from your receiver.

NOT_DISARMED

Beep code 4: 4 short

In the App
BAD_RX_RECOVERY, tooltip: “Your receiver has just recovered from receiver failsafe but the arm switch is on”
Cause
The radio signal came back, or was just detected, while the arm switch was on. This only exists when you arm with a switch. The Failsafe 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
The docs: “Switch the arm switch off.” Then arm as usual.

FAILSAFE

Beep code 2: 2 short

In the App
FAILSAFE, tooltip: “Failsafe is active”
Cause
Failsafe stage 2 has run and disarmed the quad, whether by drop, landing or kill switch. The lock clears once the radio signal has been valid again for failsafe_recovery_delay (default 500 ms).
Fix
The docs: “Rectify the failure condition and try again.” And: “The pilot cannot re-arm until after the failsafe_recovery_delay period expires.”

BOXFAILSAFE

Beep code 5: 1 long

In the App
BOXFAILSAFE, tooltip: “The 'FAILSAFE' switch was activated”
Cause
The FAILSAFE mode is on a switch, and that switch is on.
Fix
Switch the FAILSAFE switch off.

Throttle and attitude

THROTTLE

Beep code 8: 1 long, 3 short

In the App
THROTTLE, tooltip: “Throttle channel is too high”
Cause
The throttle channel is not below min_check (default 1050). In 3D mode a range around stick center applies instead.
Fix
Throttle all the way down. The docs: “Lower throttle below min_check.” The Receiver tab of the App shows the value your throttle channel has with the stick down.

ANGLE

Beep code 9: 1 long, 4 short

In the App
ANGLE, tooltip: “Aircraft is not level (enough)”
Cause
Only with an accelerometer (ACC): the quad is tilted more than small_angle (default 25 degrees), or Betaflight has not established its attitude yet. Without ACC this flag never appears.
Fix
The docs: “Level craft to within small_angle degrees (default 25).” In the App the setting is “Maximum ARM Angle [degrees]” in the Configuration tab; with 180 degrees, according to the docs, “you can arm the craft in any position”.

Switches and modes

ARM_SWITCH

Beep code 30: 6 long

In the App
ARM_SWITCH, tooltip: “One of the others disarm flags is active when arming”
Cause
The arm switch was on while another reason was blocking arming. Betaflight also sets it after an automatic disarm on landing and after a disarm by GPS rescue.
Fix
Fix the other reasons first, then flip the arm switch off and on again (the docs: “Toggle the arm switch to arm.”). The App already shows “Arming Allowed” when nothing but ARM_SWITCH is set.

NOPREARM

Beep code 11: 2 long, 1 short

In the App
NOPREARM, tooltip: “Prearm switch is not activated or prearm has not been toggled after disarm”
Cause
Only when the PREARM mode is on a switch: PREARM is off, or it has not been switched off and on again since the last arm (unless prearm_allow_rearm = ON).
Fix
The docs: “Toggle the prearm switch.”

RESCUE_SW

Beep code 20: 4 long

In the App
RESC, tooltip: “The 'GPS Rescue' switch was activated”
Cause
The GPS RESCUE switch is on (only when GPS rescue is configured).
Fix
The docs: “Turn off the GPS Rescue switch to arm.”

ALT_HOLD_SW

Beep code 27: 5 long, 2 short

In the App
ALTHOLD, tooltip: “Altitude Hold is active”
Cause
The ALTHOLD (altitude hold) switch is on while the quad is disarmed.
Fix
Switch ALTHOLD off, then arm.

POS_HOLD_SW

Beep code 28: 5 long, 3 short

In the App
POSHOLD, tooltip: “Position Hold is active”
Cause
The POSHOLD (position hold) switch is on.
Fix
Switch POSHOLD off, then arm.

AUTOPILOT_SW

Beep code 29: 5 long, 4 short

In the App
AUTOPILOT, tooltip: “Autopilot mode switch is active”
Cause
The AUTOPILOT switch is on. The flag only exists in firmware builds with the autopilot (ENABLE_FLIGHT_PLAN), not for wings.
Fix
Switch it off. The 2026.6 release notes: “Autopilot is experimental and only tested in simulation (SITL). It is not flight-ready and must not be armed on a real aircraft.”

FLIP_SWITCH

Beep code 26: 5 long, 1 short

In the App
CRASHFLIP, tooltip: “Crash Flip Switch is active”
Cause
In crashflip (turtle mode) the switch was turned back while the quad was armed. With crashflip_auto_rearm OFF (default), Betaflight then disarms and blocks arming.
Fix
Disarm once by hand (arm switch off), then arm again. Or switch on crashflip_auto_rearm.

PARALYZE

Beep code 18: 3 long, 3 short

In the App
PARALYZE, tooltip: “Paralyze mode has been activated”
Cause
The PARALYZE mode was switched on. It latches and stays active even when you turn the switch back.
Fix
The docs: “Power cycle/reset FC board.”

App, CLI and OSD menu

MSP

Beep code 17: 3 long, 2 short

In the App
MSP, tooltip: “MSP connection is active, likely with the Betaflight App”
Cause
An MSP connection has blocked arming, usually the Betaflight App: it blocks when it connects and releases when it disconnects. Arming is free only once every MSP connection has released it.
Fix
The docs: “Use the disconnect button in the Betaflight App (unplugging USB does not clear this flag).”

CLI

Beep code 14: 2 long, 4 short

In the App
CLI, tooltip: “CLI is active”
Cause
The command line (CLI) was opened, for example in the CLI tab of the App.
Fix
The docs: “Exit the CLI.” The commands exit and save both reboot the flight controller.

CMS

Beep code 15: 3 long

In the App
CMS_MENU, tooltip: “CMS (config menu) is Active - over OSD or other display -”
Cause
The configuration menu (CMS) is open, for example the OSD menu in your goggles.
Fix
The docs: “Exit the CMS (or OSD menu).”

REBOOT_REQD

Beep code 22: 4 long, 2 short

In the App
REBOOT_REQUIRED, tooltip: “A configuration change requires a reboot”
Cause
A setting was changed that only takes effect after a reboot, for example certain items in the OSD menu or RC smoothing via the App.
Fix
The docs: “Reboot the flight controller for settings changes to take effect.”

Startup, sensors and GPS

BOOTGRACE

Beep code 10: 2 long

In the App
BOOT_GRACE_TIME, tooltip: “Arming too soon after power on”
Cause
After power-on Betaflight blocks arming for pwr_on_arm_grace seconds (default 5), with DShot also until DShot is ready.
Fix
The docs: “Wait until pwr_on_arm_grace seconds (default 5) have elapsed.”

CALIB

Beep code 13: 2 long, 3 short

In the App
CALIBRATING, tooltip: “The aircraft is currently calibrating”
Cause
The gyro, accelerometer, barometer or magnetometer is being calibrated.
Fix
The docs: “Wait for sensor calibration to complete.” The troubleshooting page: “Wait a little bit after powering on the drone”.

NO_ACC_CAL

Beep code 24: 4 long, 4 short

In the App
ACC_CALIBRATION, tooltip: “Accelerometer calibration is still ongoing”. The App tooltip is misleading here: according to the source code the flag does not mean “still ongoing” but “never calibrated, but needed”.
Cause
The accelerometer was never calibrated, but a feature needs it: for example a configured ANGLE, HORIZON, ALTHOLD, POSHOLD or GPS RESCUE mode, an OSD element that needs it, or GPS rescue as the failsafe procedure.
Fix
The docs: “Calibrate the accelerometer or disable features that use it”.

NOGYRO

Beep code 1: 1 short

In the App
NO_GYRO, tooltip: “A gyro was not detected”
Cause
No gyro was found at startup. The flag stays until the next start.
Fix
The docs: “You may have a hardware failure, if a previous firmware version works then it may be a firmware issue. Or you might have flashed a wrong target.”

GPS

Beep code 19: 3 long, 4 short

In the App
GPS, tooltip: “GPS rescue mode is configured but required number of satellites has not been fixed”
Cause
Only when GPS rescue is configured (as the failsafe procedure or as a mode on a switch): the GPS has no fix with at least gps_rescue_min_sats satellites yet (default 8). After the first arm since power-on Betaflight no longer checks this.
Fix
The docs: “Wait for GPS fix, enable arming without GPS fix, or disable GPS rescue mode.” The setting in the Failsafe tab is “Allow arming without fix”; the GPS Rescue docs say: “Using GPS_RESCUE_ALLOW_ARMING_WITHOUT_FIX is NOT recommended!”

Motors and ESCs

MOTOR_PROTO

Beep code 25: 5 long

In the App
MOTOR_PROTOCOL, tooltip: “There is no motor output protocol selected”
Cause
No valid motor protocol is set, for example DISABLED.
Fix
In the Motors tab of the App, pick your ESCs’ protocol under “ESC/Motor protocol” and save. The flag only clears after the reboot.

DSHOT_TELEM

Beep code 21: 4 long, 1 short

In the App
DSHOT_TELEM, tooltip: “Dshot telemetry is enabled but one or more ESC's are not supplying valid DSHOT telemetry. Check that the ESC's are capable of and have the required firmware installed to support bidirectional DSHOT telemetry.”
Cause
Bidirectional DShot is on (dshot_bidir = ON), but not every motor delivers RPM telemetry.
Fix
The docs: “Check that the ESC’s are capable of and have the required firmware installed to support bidirectional DSHOT telemetry.” The CLI docs name “ESC firmware that supports it (BLHeli_32, AM32, BlueJay)”.

DSHOT_BBANG

Beep code 23: 4 long, 3 short

In the App
DSHOT_BITBANG, tooltip: “Bitbanged DSHOT is not working properly and the motors can't be controlled. Likely caused by a timer conflict with other features enabled on the flight controller.”
Cause
Bitbang DShot is active but not running (status MOTOR_PIN_CONFLICT, NO_PACER or TOO_MANY_PORTS).
Fix
The docs: “Likely caused by a timer conflict with other features enabled on the flight controller.” Check those features.

Runaway and crash protection

RUNAWAY

Beep code 6: 1 long, 1 short

In the App
RUNAWAY_TAKEOFF, tooltip: “Runway Takeoff Prevention has been triggered”. The App writes “Runway” here; the feature is called runaway takeoff prevention.
Cause
Runaway takeoff prevention (on by default) has disarmed the armed quad: the PID output on one axis was at 60 % or more while the quad rotated faster than 15 °/s (roll, pitch) or 50 °/s (yaw), for longer than 75 ms.
Fix
The docs: “Disarm to clear this condition.” With switch arming that means arm switch off. As causes the docs name “Props on incorrectly”, “Motor order wrong”, “Motors spinning the wrong direction” and “Flight controller (gyro) orientation incorrect”.

CRASH

Beep code 7: 1 long, 2 short

In the App
CRASH_DETECTED, tooltip: “Crash detection is active”
Cause
Only with crash_recovery set to DISARM: Betaflight detected a crash and disarmed.
Fix
The docs: “Disarm to clear this condition.” With switch arming that means arm switch off.

System

LOAD

Beep code 12: 2 long, 2 short

In the App
LOAD, tooltip: “System load is too high for safe flight”
Cause
The processor cannot keep up: in the last second more than cpu_late_limit_permille of the tasks ran late (default 10, i.e. 1.0 %). With the arm switch off, the OSD also shows “CPU OVERLOAD”.
Fix
The docs: “Revisit configuration and disable features.”

BST

Beep code 16: 3 long, 1 short

In the App
BST, tooltip: “A Black Sheep Telemetry device (TBS Core Pro for example) disarmed and is preventing arming”
Cause
Meant for Black Sheep Telemetry devices (such as the TBS Core Pro). In Betaflight 2026.6.2 the code never sets this flag.
Fix
The docs: “Refer to the manual for your hardware.”

How well do your rates fit your stick? The free check measures it on your blackbox log. No account, the file stays with you.

Check my log for free

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

No flag shown, but still no arming?

The troubleshooting docs: “You need to have an ARM mode set up, which can be done in the Modes tab.” If there is none and stick arming is off (enable_stick_arming, OFF by default), Betaflight never makes an arm attempt: no beep code, no OSD warning (rc_controls.c). About stick arming the docs say it “is pretty dangerous and not recommended”.

An arm attempt only starts once the ARM mode becomes active, and the OSD only shows blocks then too. Which channel and range the ARM mode uses is set in the Modes tab.

Beep codes and names in the App, OSD and CLI

In bit order, the way Betaflight beeps: beep code equals bit number plus 1. OSD and CLI use the same names, the App calls some of them differently. Click a name to jump to its box with cause and fix.

Beep codeOSD and CLIBetaflight App
1
1 short
NOGYRONO_GYRO
2
2 short
FAILSAFEFAILSAFE
3
3 short
RXLOSSRXLOSS
4
4 short
NOT_DISARMEDBAD_RX_RECOVERY
5
1 long
BOXFAILSAFEBOXFAILSAFE
6
1 long, 1 short
RUNAWAYRUNAWAY_TAKEOFF
7
1 long, 2 short
CRASHCRASH_DETECTED
8
1 long, 3 short
THROTTLETHROTTLE
9
1 long, 4 short
ANGLEANGLE
10
2 long
BOOTGRACEBOOT_GRACE_TIME
11
2 long, 1 short
NOPREARMNOPREARM
12
2 long, 2 short
LOADLOAD
13
2 long, 3 short
CALIBCALIBRATING
14
2 long, 4 short
CLICLI
15
3 long
CMSCMS_MENU
16
3 long, 1 short
BSTBST
17
3 long, 2 short
MSPMSP
18
3 long, 3 short
PARALYZEPARALYZE
19
3 long, 4 short
GPSGPS
20
4 long
RESCUE_SWRESC
21
4 long, 1 short
DSHOT_TELEMDSHOT_TELEM
22
4 long, 2 short
REBOOT_REQDREBOOT_REQUIRED
23
4 long, 3 short
DSHOT_BBANGDSHOT_BITBANG
24
4 long, 4 short
NO_ACC_CALACC_CALIBRATION
25
5 long
MOTOR_PROTOMOTOR_PROTOCOL
26
5 long, 1 short
FLIP_SWITCHCRASHFLIP
27
5 long, 2 short
ALT_HOLD_SWALTHOLD
28
5 long, 3 short
POS_HOLD_SWPOSHOLD
29
5 long, 4 short
AUTOPILOT_SWAUTOPILOT
30
6 long
ARM_SWITCHARM_SWITCH

Older firmware: other names and beep codes

The list applies to Betaflight 2026.6. Older versions have fewer flags, and from code 26 on the beep codes no longer match. This is what a comparison of the name lists in runtime_config.c at versions 4.4.3, 4.5.5, 2025.12.5 and 2026.6.2 shows:

  • 4.4: 26 flags. NOT_DISARMED was called BADRX, DSHOT_TELEM was RPMFILTER, the arm switch was ARMSWITCH with beep code 26.
  • 4.5: 26 flags with today’s names NOT_DISARMED and DSHOT_TELEM; ARMSWITCH still with beep code 26.
  • 2025.12: 29 flags. New are FLIP_SWITCH (code 26), ALT_HOLD_SW (27) and POS_HOLD_SW (28); the arm switch is called ARM_SWITCH and has code 29.
  • 2026.6: 30 flags. New is AUTOPILOT_SW (code 29), ARM_SWITCH has code 30.

So if a quad on 4.5 beeps code 26, it means the arm switch; from 2025.12 on, code 26 is FLIP_SWITCH.

Once it arms again

With the reason fixed, it’s time to fly. As soon as you arm, the blackbox records, provided logging is on; how to set that up is in Blackbox logging: setup and downloading your log. With the log, the free check shows you how you use your stick and whether your rates fit. If the quad flies but feels twitchy, see Twitchy quad: causes and fixes; how to set rates is in Setting up Betaflight rates.

Sources

As of 11 November 2026, checked against Betaflight 2026.6.2 (firmware and App from 16 September 2026, the latest versions on that day):

Last updated: Nov 11, 2026 · checked with Betaflight 2026.6.2