Last verified: October 2026. No bench testing was done for this guide — the diagnostic procedures below are documented Betaflight and manufacturer procedures; cause-frequency ordering reflects widely reported community patterns (r/fpv, IntoFPV), stated as such. Specs and procedures come from official documentation, linked where relevant.
The bottom line up front: almost every beginner FPV problem is one of twelve things, and almost every one of those twelve is fixed by checking things in the right order — not by knowing more. This guide teaches you that order first, then walks through each problem: the symptom, the most likely causes ranked by how often they actually occur, the five-minute checks that resolve most cases, and the honest verdict on when something is genuinely broken.
Bench safety, non-negotiable: remove the propellers before doing any troubleshooting that involves arming, spinning motors, or connecting to Betaflight with a battery plugged in. A 5″ quad at full throttle can cause serious injury. Props off, every time, no exceptions — this applies to tiny whoops too (they can still cut).
The order you check things
Memorize this sequence. It resolves the majority of FPV problems because most failures live in the first two steps:
- Power. Is everything actually receiving power? Battery charged and connected, USB data cable (not charge-only), VTX antenna attached before powering.
- Physical. Is everything plugged in, undamaged, and oriented correctly? Antennas seated, props on the right motors spinning the right direction, no pinched wires, no crash damage.
- Signal. Is the radio bound, the video on the right channel, the receiver talking to the flight controller? The entire middle layer of “it powers on but doesn’t work” lives here.
- Configuration. Is Betaflight (or your firmware) set up correctly? Modes, receiver protocol, arming flags, VTX tables. Check this last — beginners blame configuration first and it’s rarely the cause.
The pattern: power → physical → signal → configuration. Work the sequence every time instead of guessing, and you’ll fix things faster than pilots with five times your experience who skip steps.
Problem 1: The drone won’t arm
Symptom: you flip the arm switch and nothing happens — no motor spin, maybe a warning in the OSD or a sad tone.
Most likely causes, in order: (1) throttle not at zero or a switch in the wrong position; (2) the quad isn’t calibrated to see your throttle as “zero”; (3) an arming-disable flag (the flight controller refusing for a safety reason); (4) the receiver isn’t actually bound or connected.
The 5-minute checks: throttle stick fully down, all switches in their default positions. Then connect to the Betaflight Configurator, go to the Setup tab, and read the arming disable flags — they literally tell you why (“THROTTLE,” “RXLOSS,” “CLI,” etc.). In the CLI tab, typing status shows the same flags. Fix what the flag names, not what you guess.
When it’s actually broken: if flags show RXLOSS/RXFAILSAFE persistently, the receiver link is the problem (see Problem 4). If flags clear and it still won’t arm, check the Modes tab — the arm switch may not be assigned to a real switch range.
Prevention: verify arming on the bench (props off) after every firmware update or receiver change, before going to the field.
Problem 2: No video in the goggles
Symptom: goggles show static, a black screen, or “no signal” while the quad is powered.
Most likely causes, in order: (1) goggles and VTX on different channels/bands; (2) VTX antenna missing, loose, or damaged (or powered without one — which can kill a VTX in seconds); (3) VTX stuck in pit mode (near-zero power); (4) camera or VTX not receiving power (wiring/connector issue).
The 5-minute checks: confirm the VTX antenna is attached before applying power. Put the goggles in channel-scan/auto-search mode and sweep — most “no video” is a channel mismatch. Check whether the VTX has an LED indicating pit mode, and verify the camera lens cap is off (it happens to everyone exactly once).
When it’s actually broken: if the VTX was ever powered without an antenna, assume it’s dead — VTX units burn out fast with no load. A camera that shows a black screen with OSD visible means the camera (not the VTX) failed; OSD comes from the flight controller, video from the camera.
Prevention: antenna on before battery, every time. Set your VTX channel via SmartAudio/IRC Tramp so it can’t drift.
Problem 3: Betaflight won’t connect to the computer
Symptom: the Configurator doesn’t see the quad when you plug in USB.
Most likely causes, in order: (1) charge-only USB cable with no data wires — the single most common cause, by far; (2) missing drivers (notably the CP210x/STM32 VCP drivers on Windows); (3) the Configurator needs the quad powered by battery for some operations (or conversely, a driver conflict).
The 5-minute checks: try a different USB cable — specifically one you know transfers data (phone sync cables work; cheap charging cables don’t). Try a different USB port. Install the drivers from the Betaflight documentation page. On Windows, check Device Manager for the COM port appearing when you plug in.
When it’s actually broken: if no cable and no computer detects anything (no device-manager entry, no port), the flight controller’s USB port may be physically damaged — inspect for bent pins or a loose connector.
Prevention: keep one known-good data cable labeled as your “Betaflight cable” and never lend it out.
Problem 4: Radio won’t bind, or keeps losing bind
Symptom: the receiver never connects to the radio, or connects then drops.
Most likely causes, in order: (1) protocol mismatch — ELRS radio talking to a FrSky receiver, or vice versa (they are not interchangeable); (2) wrong bind procedure for the specific receiver (button vs. Betaflight bind command vs. power-cycling); (3) mismatched firmware versions between radio and receiver; (4) a failing receiver or antenna.
The 5-minute checks: confirm the receiver’s protocol matches the radio (check the product listing if unsure). Follow the manufacturer’s bind procedure exactly — ELRS receivers typically bind via the Betaflight CLI bind_rx command or a physical button. If it binds then drops, check antenna placement and update both sides to current firmware.
When it’s actually broken: a receiver that won’t enter bind mode at all (no LED response) after correct procedure is likely dead. Receivers are cheap; your time isn’t.
Prevention: buy the receiver protocol that matches your radio — this decision is made at purchase, not at the bench. Our ELRS explainer covers the protocol landscape.
Problem 5: Failsafe / RXLOSS — the quad drops or disarms mid-flight
Symptom: the quad suddenly disarms and falls, or the OSD flashes RXLOSS.
Most likely causes, in order: (1) you flew beyond your link’s range (most common — especially with stock antennas or low packet-rate settings); (2) receiver antenna damaged, poorly placed, or shielded by the carbon frame; (3) local interference (flying near broadcast towers, Wi-Fi-dense areas, or other pilots on overlapping frequencies); (4) a genuine hardware fault.
The 5-minute checks: inspect receiver antennas — carbon fiber blocks RF, so antennas must stick out clear of the frame. Confirm your failsafe procedure in the Configurator (Failsafe tab) is set to the safe default (drop/disarm). Range-test on the ground before flying far: walk away with the quad armed (props off, a friend watching) and note where the link degrades.
When it’s actually broken: failsafes at close range with good antennas point to a dying receiver or radio module. Don’t keep flying it — replace the suspect component.
Prevention: mount receiver antennas properly (clear of carbon, ideally in a V or T orientation), set a conservative failsafe, and respect your link’s real range — not its marketing range.
Problem 6: Motors spin but the drone flips on takeoff
Symptom: the moment you add throttle, the quad violently flips over.
Most likely causes, in order: (1) props on wrong — spinning the wrong direction or mounted on the wrong motors; (2) motor order wrong in Betaflight (the configurator’s motor numbering doesn’t match physical layout); (3) flight controller mounted rotated 90/180° without the board-alignment setting updated.
The 5-minute checks: props off, use the Configurator’s Motors tab to spin each motor individually and confirm the order matches the diagram (1 = rear right, 2 = front right, 3 = rear left, 4 = front left, in the standard Betaflight layout). Verify prop direction matches the “props in” or “props out” configuration. Check the Setup tab’s 3D model — tilt the quad by hand and confirm the model follows correctly; if it’s mirrored, the board alignment is wrong.
When it’s actually broken: this is essentially never a hardware failure — it’s always configuration. Don’t buy parts; fix the setup.
Prevention: after any rebuild or FC replacement, verify motor order and board alignment on the bench before the first flight.
Problem 7: Jello / vibration in the video or flight
Symptom: wavy, jelly-like distortion in the video feed (or in HD footage), sometimes felt as vibration.
Most likely causes, in order: (1) unbalanced or damaged props; (2) loose hardware — motor screws, stack screws, camera mount; (3) a bent motor bell from a crash; (4) frame resonance (some frame/prop combos just vibrate).
The 5-minute checks: fresh props first — it’s the cheapest fix and the most common cause. Tighten every screw you can reach. Spin each motor by hand (battery disconnected) and feel for grinding or wobble indicating a bent bell.
When it’s actually broken: a motor with a bent shaft or damaged bell needs replacement — they’re inexpensive. Persistent jello across multiple prop sets points to frame damage (check for cracked arms).
Prevention: replace props after hard crashes instead of “straightening” them; check motor screws periodically (vibration loosens them).
Problem 8: Short range / video breakup close by
Symptom: video gets snowy or breaks up much sooner than expected, or the radio link feels fragile.
Most likely causes, in order: (1) damaged VTX or goggle antenna (a cracked antenna looks fine and performs terribly); (2) antenna polarization mismatch — RHCP on one end, LHCP on the other; (3) VTX power set lower than you think (check SmartAudio settings — it may have reset); (4) flying with the VTX antenna blocked by the battery or frame.
The 5-minute checks: inspect both antennas for cracks or kinks. Confirm both ends are the same polarization (check the listing specs). Verify VTX power in the OSD or Configurator. Keep the VTX antenna clear of the battery and carbon.
When it’s actually broken: an antenna with internal damage won’t show it — if range collapsed suddenly after a crash, replace the antennas before suspecting the VTX.
Prevention: treat antennas as consumables; carry a spare set. Never coil or kink them for storage.
Problem 9: Drone drifts or won’t hold still in Angle mode
Symptom: in self-leveling mode the quad slides sideways or rotates slowly on its own.
Most likely causes, in order: (1) accelerometer needs calibration (the #1 cause); (2) radio stick not centered — check the Receiver tab for stick values at rest; (3) trim needed, set via the OSD or Configurator.
The 5-minute checks: place the quad on a level surface and calibrate the accelerometer in the Configurator (Setup tab). Check that all sticks read ~1500 at center in the Receiver tab — if not, calibrate the radio or adjust subtrim.
When it’s actually broken: a gyro/accelerometer that won’t calibrate after multiple attempts suggests a damaged flight controller — uncommon, but it happens after hard crashes.
Prevention: calibrate the accelerometer on a level surface after any hard crash or firmware update. (Note: drift in Acro mode is normal — Acro doesn’t self-level by design.)
Problem 10: OSD missing in the goggles
Symptom: you get video, but none of the overlay data (battery voltage, flight time, warnings).
Most likely causes, in order: (1) OSD not enabled for the right video format or UART in the Configurator; (2) on digital systems, the OSD canvas settings need adjusting; (3) the OSD chip wiring (on some AIO boards the OSD signal path can be damaged in crashes).
The 5-minute checks: in the Configurator’s OSD tab, confirm elements are actually dragged onto the preview and the OSD is enabled. For analog, verify the camera and VTX video wiring passes through the FC’s OSD circuit (some wiring diagrams bypass it).
When it’s actually broken: video with permanently no OSD after correct configuration, following a crash, suggests OSD circuit damage on the FC — the board still flies, but you’ll fly without overlay data (or replace the board).
Prevention: back up your Configurator settings (the “Backup” button) before changing anything — restoring is faster than re-diagnosing.
Problem 11: Buzzer/beeper patterns you don’t understand
Symptom: the quad beeps in patterns you didn’t command, or the startup tones sound wrong.
What the beeps mean: the startup tone sequence is a diagnostic: the first three beeps confirm the ESCs are powered and talking, the final two confirm the flight controller is communicating with them. If you hear only the first three, the ESCs have power but the FC isn’t reaching them — check the FC-to-ESC connection. Continuous beeping after arming usually means the beeper mode is active or a warning (low battery) is sounding.
The 5-minute checks: count the startup beeps and note where the sequence stops — that tells you exactly which link in the chain failed. Check the Modes tab to see what your beeper switch is assigned to.
When it’s actually broken: a quad that produces no tones at all on battery plug-in has no power reaching the ESCs — check the battery lead, XT60 connector, and for a blown fuse or damaged power wiring.
Prevention: learn your quad’s normal startup sound. You’ll diagnose half your future problems by ear in the first two seconds.
Problem 12: “It worked yesterday” — the post-crash systematic re-check
Symptom: everything was fine, then a crash (or a firmware update, or a settings change), and now something’s wrong.
The re-check order: this is where the method earns its keep. After any crash, work the sequence deliberately:
- Power: battery lead intact? Balance lead undamaged? Any burning smell?
- Physical: props — replace, don’t straighten. Motor bells spin freely? Frame cracked? Antennas still attached and intact? Camera lens clean and uncracked? Every connector still seated?
- Signal: still bound? Video on the right channel? Receiver antennas clear of the frame?
- Configuration: did anything reset? Check VTX power, modes, and rates — a hard crash can corrupt settings, and firmware updates reset everything to defaults.
When it’s actually broken: after a hard crash, the honest answer is that multiple small things are often wrong at once. Fix them one at a time, testing between changes — changing three things simultaneously teaches you nothing about which one mattered.
Prevention: the pre-flight check takes 60 seconds: props tight and undamaged, antennas secure, battery healthy, arm switch working, failsafe verified. Make it a ritual.
Your one-page bench checklist
Print this (or screenshot it) and keep it where you work on quads:
- ☐ Props OFF before any bench work involving power
- ☐ Battery charged, lead and connector undamaged
- ☐ VTX antenna attached BEFORE battery connects
- ☐ Data-capable USB cable for Configurator work
- ☐ Arming-disable flags read and understood
- ☐ Motor order + prop direction verified in Motors tab
- ☐ Receiver bound, protocol matched, antennas clear of carbon
- ☐ Video channel matched between VTX and goggles
- ☐ Failsafe set and tested
- ☐ Settings backed up before changes
Still stuck after working the sequence? The problem-specific deep dives (won’t-arm, no-video, failsafe, jello, range, Betaflight USB) expand each section above — and the FPV Dictionary decodes any term in this guide you haven’t met yet. When a fix requires parts, our batteries guide and video system guide cover the replacement decisions.
