The pilot who says “I get about 2 kilometers on this setup” usually means “I flew 2 kilometers once and didn’t failsafe.” That’s not a range test. It’s lucky. When your quad drops behind a treeline at 1.5 km and the link goes from 99% LQ to zero in 200 milliseconds, you learn that one data point isn’t a map — it’s a single dot on a page you haven’t drawn yet.
Systematic Range Testing: A Repeatable Protocol
Step 1: Choose the Right Test Site
Find an open area with line of sight for at least 3 km if you’re testing long-range gear. A large agricultural field, a dry lake bed, or a coastal cliff with clear over-water visibility works. The ground should be flat — elevation changes introduce multipath interference that makes results unrepeatable.
Mark waypoints at 500 m, 1 km, 2 km, and 3 km using Google Earth or a handheld GPS. Walk or drive the course first to verify the waypoints are accessible and obstruction-free. A 500-meter test with a tree in the Fresnel zone tells you nothing about the equipment.
Step 2: Configure Logging Before You Fly
Betaflight’s OSD log records RSSI, Link Quality (LQ), and GPS coordinates to the flight controller’s onboard flash or SD card. Verify these are enabled before takeoff:
- RSSI: Set to display on OSD and confirm it matches the raw value in the Receiver tab. An RSSI reading that stays at 99% for the entire flight means the scaling is wrong.
- Link Quality (LQ): Only available with CRSF and ELRS receivers. LQ is more useful than RSSI for range testing because it tells you how many packets are getting through, not just signal strength. 100% LQ at -95 dBm means your link is healthy even at the edge of sensitivity. 60% LQ at -70 dBm means interference, not range, is your problem.
- GPS Coordinates: Log at minimum 5 Hz into the blackbox. Without GPS data, your RSSI and LQ numbers have no spatial context — you don’t know where the signal dropped.
Step 3: Fly the Pattern
Fly the course at constant altitude — 100 meters is a good reference height for initial testing. Hold a steady cruise speed (40-60 km/h). Do not punch out or change altitude mid-run — throttle spikes create voltage sag that can drop VTX output power and muddy the video signal data.
For each 500-meter leg, record:
– RSSI at entry and exit
– LQ at entry and exit
– Video signal quality (subjective 1-5 scale noted in a voice recording or OSD timestamp)
– Any momentary drops in LQ and the corresponding GPS position
Step 4: Analyze the Logs
After the flight, open the blackbox log in Betaflight Blackbox Explorer or Plasmatree PID Analyzer. Plot LQ vs distance. The graph should show a gradual decline. Sharp drops at specific distances suggest Fresnel zone obstructions (a tree line, a building, a hill) rather than equipment limits.
Calculate the distance at which LQ dropped to 80% — that’s your reliable control range with a 20% margin. For video, the range at which the image became unflyable (frozen frame, total breakup) is your hard ceiling.
Range Testing Parameter Reference
| Parameter | Minimum | Recommended | Notes |
|---|---|---|---|
| Test altitude | 50 m | 100 m | Consistent altitude for repeatable results |
| Cruise speed | 30 km/h | 40-60 km/h | Steady throttle, no punch-outs |
| GPS log rate | 2 Hz | 5 Hz | Higher rate = finer spatial resolution |
| LQ threshold (warning) | 70% | 80% | Return at 80% LQ for margin |
| Blackbox log rate | 1 kHz | 2 kHz | Captures sub-second link events |
| Minimum distance markers | 2 | 4+ | 500 m, 1 km, 2 km, 3 km |
Common Range Testing Mistakes
Mistake 1: Testing with the quad facing away. Antenna nulls are real. If your receiver antenna is parallel to the ground and the quad is flying away from you, the null points directly at the transmitter. Rotate the quad at each waypoint to map the radiation pattern — you’ll find weak spots that could failsafe at 500 meters even though max range is 3 km.
Mistake 2: One flight = one test. Link conditions change. Temperature, humidity, ground moisture, and RF noise floor all vary between flights. Run the same course three times on different days before publishing a “max range” number. If the results vary by more than 20%, you have an environmental factor you’re not controlling.
Mistake 3: Logging RSSI without calibrating the scale. Betaflight RSSI can be received as a raw value from the receiver (0-100%) or as an analog voltage on the RSSI pad. If the scaling is off, “90% RSSI” might actually be 50%. Always verify the RSSI reading against the receiver’s telemetry screen on your radio — they should match.
Mistake 4: Ignoring the control link while obsessing over video. Video breaks up gradually — you see it coming. Control links drop instantly. If you’re testing range, the control link (LQ) matters more than video quality. When LQ hits 50%, turn back. When video gets snowy, you can still fly home. When LQ drops to zero, you’re in GPS Rescue or on the ground.
Mistake 5: Testing behind obstacles and calling it “range.” Flying behind a building at 200 meters and failsafing is not a 200-meter range test. It’s a penetration test. Obstacle penetration depends on frequency, power, and material — concrete blocks 2.4 GHz almost completely; 900 MHz punches through. Don’t confuse penetration distance with clear-air range.
⚠️ Regulatory Notice: Range testing at distances beyond visual line of sight (BVLOS) requires specific authorization in most countries as of 2026. The FAA requires a Part 107 waiver with a documented beyond-visual-line-of-sight safety case. EASA’s 2026 U-space framework mandates that BVLOS flights occur within designated U-space airspace with electronic conspicuity. In the UK, the CAA classifies BVLOS range testing as a specific category operation requiring an operational authorization. Always check whether your test location and distance fall within VLOS limits or require a waiver.
Our guide to long-range FPV flight planning covers the flight planning side — once you’ve mapped your control link range, the next step is building battery and wind strategies around it.
For pilots testing ELRS range limits, the ELRS packet rate tuning guide explains how 50 Hz mode extends control range dramatically at the cost of a few milliseconds of latency.
Accurate RSSI and LQ logging starts with a flight controller that has clean analog inputs. The uavmodel F722 flight controller provides dedicated RSSI filtering on the ADC input, eliminating the voltage ripple that causes RSSI readings to bounce ±5% in flight — your range test data will actually mean something.