If your drone RTK fixed status is not showing, the problem usually comes down to satellite quality, correction delivery, or configuration mismatches.
This guide explains how RTK works and the exact checks that restore fixed positioning more reliably.
What RTK Fixed Means on a Drone
RTK, or Real-Time Kinematic positioning, improves GNSS accuracy by combining satellite data with correction information from a base station, NTRIP caster, or network service.
A fixed RTK solution means the receiver has resolved carrier-phase ambiguity, which typically delivers centimeter-level accuracy.
When a drone shows float instead of fixed, or never shows fixed at all, the receiver is receiving corrections but cannot confidently solve the position.
That can happen even when the drone appears to have good satellite count, so the issue is not always obvious from the map screen.
Why RTK Fixed Status May Not Appear
Several technical factors can prevent a drone from reaching fixed status.
The most common are related to GNSS geometry, correction latency, firmware compatibility, and environmental interference.
- Weak satellite geometry due to low elevation angles or partial sky obstruction.
- Insufficient correction data from a base station, CORS network, or NTRIP connection.
- Incorrect coordinate or datum settings in the flight app or ground station.
- Firmware mismatches between the aircraft, controller, RTK module, or app.
- Multipath interference from buildings, metal structures, trees, or vehicles.
- Poor cellular or radio link causing delayed or dropped corrections.
- Incorrect antenna installation or hardware damage on the RTK module.
How to Fix Drone RTK Fixed Not Showing
1. Confirm the drone is actually receiving corrections
Start by checking whether the RTK source is connected and active.
If you use an NTRIP service, verify the mountpoint, username, password, host, and port.
If your system uses a local base station, confirm the base is powered, broadcasting, and set to the right reference position.
Look for correction indicators in the flight app.
Many DJI Enterprise and similar systems show whether RTCM messages are being received.
If corrections are missing or interrupted, the receiver cannot reach fixed status.
2. Move to an open sky environment
RTK performance depends heavily on satellite visibility.
Takeoff near tall buildings, dense trees, hills, or radio towers can keep the receiver in float mode.
For testing, move the drone and controller to a wide open area with a clear 360-degree view of the sky.
Even a strong satellite count can be misleading if the geometry is poor.
A good test location reduces multipath and helps the receiver converge faster.
3. Wait for convergence after power-up
RTK systems often need time to initialize and converge after startup.
If you launch too quickly, the drone may still be calculating the solution.
Power on the aircraft, controller, and RTK source, then wait a few minutes before takeoff so the receiver can stabilize.
Also avoid rapidly moving the drone immediately after startup if the platform recommends a stationary initialization period.
Some systems achieve fixed faster when they remain still during convergence.
4. Check satellite count and quality indicators
Most RTK-capable drones need more than a basic GNSS lock.
They benefit from multi-constellation support such as GPS, GLONASS, Galileo, and BeiDou, plus enough satellites with strong signal quality.
Review the app’s GNSS metrics, not just the raw satellite count.
- Look for healthy signal-to-noise ratios.
- Avoid flying with very low elevation satellites only.
- Check whether the receiver is using dual-frequency bands correctly.
5. Verify firmware and app versions
Firmware incompatibility is a frequent reason RTK fixed does not appear.
Update the aircraft firmware, remote controller firmware, RTK module firmware, and flight app to compatible versions.
After updates, restart all devices in the correct order.
If the issue started after an update, review release notes.
Some firmware revisions change RTK behavior, supported correction formats, or connection methods.
6. Inspect the RTK and GNSS antennas
Physical hardware matters.
Make sure the RTK antenna is installed correctly, unobstructed, and not damaged.
Loose connectors, bent pins, water ingress, or shield damage can reduce the quality of satellite tracking and correction reception.
If your drone uses an external base or ground antenna, ensure the antenna has a clear view of the sky and is mounted away from reflective surfaces.
7. Confirm coordinate system and base station settings
An incorrect coordinate reference can prevent a stable fixed solution.
Check that the base station is configured with the right datum, geodetic system, and position mode.
If using a surveyed base point, make sure the coordinates are accurate and entered in the expected format.
For network RTK, confirm the CORS service region matches your operating area.
Some providers require a specific mountpoint or correction format such as RTCM 3.x.
8. Reduce correction latency and connection drops
RTK corrections must arrive quickly and continuously.
If you rely on mobile data, poor coverage can keep the receiver from locking into fixed.
If your setup uses a radio link, interference, distance, antenna orientation, or wrong channel settings can break the stream.
- Test with a different SIM or carrier.
- Move closer to the base station if using local RTK.
- Keep the controller antenna oriented correctly.
- Use a stable internet connection for NTRIP.
9. Reboot and rebind the RTK system
A full power cycle often clears temporary glitches.
Turn off the aircraft, controller, RTK source, and any connected app session.
Then restart in the manufacturer’s recommended order and reconnect the correction service from scratch.
If possible, delete and re-enter the RTK account or NTRIP profile.
Corrupted settings or expired credentials can silently block corrections.
How to Diagnose the Problem Step by Step
If you want a structured approach, isolate each part of the RTK chain one at a time.
- Check GNSS reception in an open area with a clear sky view.
- Verify corrections are arriving from the base, network, or NTRIP service.
- Confirm firmware compatibility across aircraft, controller, and app.
- Inspect antennas and cables for physical damage or poor installation.
- Test a different location to rule out multipath and obstruction.
- Restart and reconfigure the RTK connection if needed.
Common Drone Models and RTK Behavior
Popular enterprise drones such as the DJI Mavic 3 Enterprise RTK, Matrice series, and Autel RTK platforms typically show different GNSS states depending on correction availability and satellite quality.
The specific wording may vary between apps, but the underlying status logic is similar across manufacturers.
Some systems show single, float, and fixed; others use icons or numerical indicators.
Always check the manufacturer’s manual for the exact meaning of each status label, since terminology can differ even when the RTK technology is the same.
When the Problem Is Hardware-Related
If RTK fixed never appears after checking corrections, firmware, and location, hardware failure becomes more likely.
A damaged GNSS board, defective antenna, or internal connector issue can block the receiver from solving a fixed position.
In that case, compare the drone against another unit of the same model if available.
If one drone reaches fixed quickly and the other does not in the same environment, the issue is likely device-specific.
Contact the manufacturer or an authorized service center for diagnostics.
What a Stable RTK Setup Should Look Like
A healthy RTK workflow usually includes a clear sky view, steady correction delivery, compatible firmware, and a properly configured base or NTRIP source.
When all of those elements align, the drone should transition from no RTK status to float and then fixed within a reasonable time.
If you are trying to understand how to fix drone RTK fixed not showing, focus on the chain from correction source to antenna to receiver.
That is where most failures occur, and that is where the fastest gains usually come from.