
Failsafe scenarios: drop, land, GPS rescue
Failsafe is the plan for when the control link dies. The wrong plan over a crowd or a lake is worse than a controlled drop onto open grass. Software can’t remove your responsibility, but the right configuration prevents predictable disasters.
Failsafe covers receiver link loss, the FC’s staged response, and optionally GPS Rescue. Each must match where you actually fly, not where YouTube pilots fly.
When the link dies

The receiver stops hearing the transmitter, and Betaflight (or iNav) responds according to your configured stages. On ELRS, LQ on the OSD shows the margin shrinking before it runs out; set it up with OSD essentials.
Fix the link first: a bent RX antenna, a VTX too close to the RX antenna, and urban multipath all cause failsafes that look like a "bad receiver." Read ELRS link budget and antenna placement before blaming firmware.
| Signal | Meaning |
|---|---|
| LQ trending down | Turn back, reduce distance, check antennas |
| Sudden failsafe at one spot | Multipath or body blocking; note the location |
| Failsafe as soon as you arm | Wiring, protocol or wrong UART |
Drop (cut motors)
Drop is Betaflight’s default Stage 2 procedure.
Use when: you fly close and low over open ground, and want zero flyaway risk.
Behaviour: the motors stop and the quad falls. Gravity is reliable; it won’t wander off.
Risk: it falls from wherever it is: fine over grass, bad over people, roofs, water or vehicles.
| Environment | Drop appropriate? |
|---|---|
| Open club grass | Usually yes |
| Urban terrace | Still the least bad option; the real fix is keeping flights close |
| Over water | Only if you accept a swim |
| Near spectators | Don’t fly there in the first place |
Common mistake: assuming drop is "safe" at height. A quad that loses link 40 metres up still falls from 40 metres.
Land (descent / auto-land)
Use when: you have height and space for the quad to come down gently. Betaflight levels the quad and descends; exactly how depends on your version and settings, so check the docs for yours.
Set the descent sensibly: too fast slams into the ground; too slow drifts on the wind into a road.
India wind note: afternoon thermals and gusty pre-monsoon weather can carry a "gentle landing" into a neighbour's wall. Test over open ground you have walked.
GPS rescue
Use when: you have a reliable GPS fix, open sky, and a configuration you have tested over open ground.
Not when: you are among buildings, the battery is low, the setup is untested, or it is your first flight after installing GPS.
GPS Rescue is a feature, not a substitute for a good link. It needs enough satellites, a correct home point and sensible climb settings, and you remain responsible for where the quad goes (insurance).
| Prerequisite | Check |
|---|---|
| Home point set | Wait for the fix before arming |
| Enough satellites | OSD shows a steady count |
| Rescue switch | Deliberate, not bumpable |
| Clear path home | Open sky, no buildings in the way |
Configuration map (mental model)
Link lost → Stage 1 (short guard period with fallback channel values)
→ Stage 2 procedure (Drop / Land / GPS Rescue)
Match the Stage 2 procedure to where you fly THIS monthRadio side: check your arm and mode switches in EdgeTX after copying a model, so nothing fights the FC’s failsafe.
Test script: non-negotiable
1. Bench, props OFF, battery in: arm, then switch the radio off
2. Confirm the OSD shows failsafe and the motors do what you configured
3. Switch the radio back on; confirm the link recovers and it won’t re-arm by itself
4. Optional, for Land or GPS Rescue: test low over open grass with nobody around
5. Repeat after any receiver, FC or firmware change
6. Note the result in the model notes ("drop tested 2026-07-01 OK")Never test failsafe for the first time over people, property or water. After crash repair, test again; a replacement receiver changes everything.
Choosing a scenario: decision tree
Where do you fly most?
├─ Open-field freestyle
│ └─ Drop (or a short Land); no flyaway risk
│
├─ Mixed obstacles, moderate height
│ └─ Land if configured and tested
│
├─ Long range, open sky, GPS fitted
│ └─ GPS Rescue, only after open-field tests
│
└─ Urban, terrace, anywhere near people
└─ Drop, and never fly where the link margin is thin
(see the terrace guide and the 2.4 GHz urban RF guide)OSD and warnings

Low-voltage and link warnings should fire before failsafe (OSD essentials). Failsafe is the last resort; landing on time is the everyday skill (LiPo safety).
Video loss vs control loss
Losing video is not a control failsafe. You can lose video and still have control, or lose control while the video looks fine. Set up your ELRS link separately from your analog VTX channels.
iNav vs Betaflight
Return-to-home behaviour differs between firmwares. The ideas here apply to both, but iNav pilots should follow the iNav docs and test over open ground the same way. Don’t carry Betaflight assumptions over to an iNav wing.
Liability mindset
Failsafe reduces predictable harm; it doesn’t make flying over people or property acceptable. Spot choice, insurance and local norms matter more than any setting.
When to re-test immediately
- New receiver, or a different UART
- FC replacement
- Major firmware update
- A crash that hit the receiver antenna or FC
- Changed arm-switch mapping on the radio
Add "failsafe OK + date" to the model notes in EdgeTX; you will forget otherwise.
On terraces near railings, drop beats anything that keeps the motors running; a quad that keeps flying without a link can clear a parapet in one gust. Pair this with terrace flying habits.
Betaflight stage reference
Menus change between versions, so check your Configurator. The model stays the same.
| Stage | Typical behavior | Good for |
|---|---|---|
| Stage 1 (guard period) | Channels go to their fallback values for a short delay (about 1.5 seconds by default) | Riding out brief dropouts |
| Stage 2: Drop | Motors stop and the quad disarms (default) | Open grass |
| Stage 2: Land | Levels out and descends | Moderate height, open area |
| Stage 2: GPS Rescue | Climbs, turns and flies home | Open sky, tested GPS |
GPS Rescue is one of the Stage 2 options, not a separate layer after Land or Drop.
Setup order:
1. Fix the link first: antennas, LQ on the OSD
2. Check the receiver’s failsafe output (ELRS receivers default to sending no signal, which Betaflight detects)
3. Pick the Stage 2 procedure (Drop, Land or GPS Rescue) for your terrain
4. GPS Rescue switch: deliberate and tested
5. Bench test, props off
6. Note the date and result in the radio’s model notesCommon failsafe configuration mistakes
| Mistake | Outcome |
|---|---|
| Return or land modes over a city | Quad drifts across roads |
| First GPS Rescue over trees | Test it over open ground first |
| No test after a receiver swap | Surprise behaviour mid-session |
| Land descent too slow in wind | Drifts into obstacles |
| Assuming video loss = control loss | Two links, two setups |
Failsafe is insurance you hope never pays out. Configure it for where you fly this month, test again after any hardware change, and keep enough LQ margin that it rarely triggers.
See also
- ELRS in the field
- GPS module install for return-to-home basics
- OSD essentials every pilot should configure
Fly with pilots near you
Every city page has an open FPV Grind group you can join with your account, plus where to fly, when the weather allows it and what the airspace rules say. Find FPV pilots near you.
Discussion
Comments aren't open on this post yet. Share it with your build group, or start a thread on X.