Thoroughly Organizing RTK Error Causes｜8 Factors That Make Corrections Unstable

Even though you're using RTK, the position isn't as accurate as you expected. It was stable yesterday, but today the corrections are noisy. You thought it was fixed, but each measurement gives slightly different values. These problems are not caused only by faulty positioning equipment. In practice, multiple factors—how satellites are visible, surrounding reflection environments, communication conditions, the relationship with the reference station, initialization status, small differences in operational procedures—often combine and manifest as errors.

RTK is widely used as a high-precision positioning method, but the same accuracy is not guaranteed at all times. By its nature, even a slight deterioration in observation conditions can make corrections unstable, and positions that should be within a few centimeters (a few inches) can appear significantly offset. Moreover, in the field the cause of an error is rarely a single factor, so it can be hard to know where to start investigating.

This article organizes eight representative causes of large RTK errors and explains them step by step so practitioners can easily check them on site. It doesn’t stop at theory: it explains why each factor disrupts corrections, in what situations they occur most often, and how to distinguish them. Systematically understanding RTK error causes directly reduces remeasurement, prevents rework, and improves the ability to explain positioning results.

Table of contents

• Why do RTK errors occur?

• Factor 1 Poor satellite reception environment

• Factor 2 Influence of reflected signals

• Factor 3 Unstable correction information communication

• Factor 4 Large distance or condition differences with the reference station

• Factor 5 Insufficient initialization and fixed-solution checks

• Factor 6 Problems with antenna setup or equipment handling

• Factor 7 Mismatch in coordinate systems or correction settings

• Factor 8 Insufficient observation time and rechecks

• How to isolate RTK errors on site

• Summary

Why do RTK errors occur?

To correctly understand RTK error causes, you first need to grasp how RTK achieves high accuracy. RTK improves accuracy by correcting the moving receiver’s observations using the reference station’s observation results instead of determining position from the moving receiver’s satellite signals alone. This is why higher accuracy than standalone positioning can be expected, but conversely it requires stable observations at both the reference and rover stations and that correction information be delivered appropriately.

What’s important here is that RTK errors do not typically appear suddenly in the positioning result itself but surface as the accumulated effect of disturbed observation conditions. For example, in a location where the sky is not open, there may be too few satellites; near buildings, reflected signals mix in. If communication is weak, correction information is interrupted; if the difference from the reference station is large, atmospheric and ionospheric effects are less likely to match. Even if equipment appears to have a fixed solution, insufficient initialization or mismatched coordinate settings can make the numbers look clean while the actual field positions are offset.

What makes this troublesome in practice is that error causes don’t necessarily happen alone. For instance, in mountainous sites you may have poor satellite reception, unstable communication, and frequent reinitializations all at once. In urban areas, communication may be stable but reflected signals can make values fluctuate. In other words, RTK error countermeasures are not a simple “do this and it’s solved” story; you need to calmly separate which factors are involved and to what extent.

Also, some errors are easy to see and others are not. Errors that make values swing widely with each measurement are noticeable, while errors that slowly drift in one direction are easy to overlook. The latter may look stable on site but only become a problem when compared with known points or drawings. Therefore, it’s important to understand each RTK error cause and have checkpoints to verify before, during, and after observations.

Factor 1 Poor satellite reception environment

The most basic and most frequent RTK error cause is the satellite reception environment. If satellite signals cannot be received sufficiently, no matter how good the equipment, high-precision positioning cannot be achieved. RTK relies on stable reception of multiple satellites and refines position based on each observation; when the number of receivable satellites is low or their spatial distribution is poor, the positioning solution tends to be unstable.

Common on-site situations include places where the sky appears somewhat open but is actually partially obstructed by trees, slopes, heavy machinery, temporary structures, utility poles, or building facades. Such obstructions make satellites in certain directions harder to receive and bias the satellite geometry. Even if the number of satellites is adequate, poor spatial balance reduces solution accuracy. In particular, valley terrain or dense building clusters can cause reception conditions to change depending on timing, so stability can vary by time of day at the same site.

What makes this factor tricky is that operators often assume “the sky is a little visible, so it’s fine.” However, in RTK merely seeing the sky is sometimes insufficient. Low-elevation satellites can be blocked, or only certain directions may be open, making conditions worse than they appear. If you have trouble obtaining a fixed solution, cannot maintain a fixed solution, or see large observation scatter, first suspect the reception environment.

In practice, moving only a few meters (a few ft) can improve conditions. Stepping away from a building edge, avoiding being directly under a tree canopy, or moving away from heavy machinery can drastically change satellite visibility. Conversely, before suspecting device settings or software problems, it is often best to re-evaluate the reception environment itself. When investigating RTK error causes, the first thing to check is not whether corrections are present but whether you are standing where satellites can be stably observed.

Factor 2 Influence of reflected signals

If satellites are visible but errors occur, the next prime suspect is reflected signals. Reflected signals occur when satellite transmissions bounce off building facades, metal surfaces, glass, water, vehicles, fences, etc., before being received. In addition to the direct signal, slightly delayed reflected signals mix in, making it difficult for equipment to correctly judge the true distance. As a result, even with corrections applied, positions can be slightly offset or the quality of the fixed solution can degrade.

Reflections are particularly likely in urban areas or equipment-dense sites. For example, along building exteriors, near metal racks in material yards, where guardrails or large vehicles line up, or close to banks and water, the reflection environment can be harsher than it appears. Field staff are prone to overlook this factor especially when the sky looks open yet errors persist, because good-looking visibility does not guarantee low reflection. Visibility and low reflections are separate issues.

When reflections are affecting your results, the position tends to drift or wobble subtly rather than jump dramatically. Phenomena such as a fixed solution that does not match known points, repeated measurements at the same point differing by several centimeters (a few inches) to a dozen-some centimeters (several inches to about 4–8 in), or values that are oddly unstable only near building edges suggest reflection. Reflections also do not always occur at constant strength; they vary with nearby vehicle movement, people, or slight differences in antenna placement, so they can appear as low-reproducibility errors.

The basic countermeasure is to put distance between the instrument and likely reflection sources. Before relying on equipment performance, check whether simply changing the measurement location improves results. Especially near walls or metal structures, don’t unquestioningly trust a point’s plausibility—re-measure from a different position or verify against known points. To spot RTK error causes in the field, think not just “can I see satellites?” but “am I picking up unwanted signals?”

Factor 3 Unstable correction information communication

RTK assumes not only satellite observations but also stable reception of correction information. Therefore, if communication delivering corrections is unstable, positioning quickly becomes unstable. This often-overlooked point is crucial for maintaining RTK accuracy. If corrections do not arrive continuously, keeping a fixed solution is difficult, and reinitializations or solution degradation occur more readily.

On site, common situations with unstable communication include mountainous areas, reclaimed land, structures near underground features, some coastal areas, and regions with weak telecom coverage. Even if the device appears connected, data delays or brief interruptions may be occurring. In such states, the screen may seem to be updating, but correction updates cannot keep up and the positioning values wobble or a fixed solution suddenly drops.

Communication-induced errors are tricky because their symptoms resemble poor reception or reflections. If a solution won’t fix, won’t stay fixed, or values aren’t stable, you may mistakenly blame satellite conditions. However, if communication is the cause, moving location may not improve things and problems can persist even in apparently open areas. Therefore, separate satellite reception and communication quality in your thinking.

Moreover, communication is not simply “connected or not.” Weak but connected, yet unstable, is the hardest state to judge. If you rush the survey and continue observing under such conditions, the site may appear fine at the time but discrepancies can surface when coordinates are overlaid later. Especially when measuring multiple points in sequence, a temporary communication degradation can reduce accuracy only for that period, introducing inconsistencies across the dataset.

When considering RTK error causes from the communication side, pay attention not just to whether you’re connected but whether corrections are arriving continuously and without delay. In sites with questionable communication, don’t be reassured by the raw observation values alone—confirm continuity of the fixed state and consistency across multiple points before trusting the results.

Factor 4 Large distance or condition differences with the reference station

RTK accuracy tends to be more stable when the rover and the reference station experience similar error environments. Conversely, when the reference station is too far away or their environmental conditions differ significantly, the correction effect weakens and residual errors can remain. This is an important point related to RTK principles: applying the errors observed at the reference station to the rover only works well when both share similar error conditions.

For example, if the reference station is observing stably on a plain while the rover is in mountainous terrain affected by masking or localized atmospheric variation, observation conditions do not match. In such cases, correction data from the reference station may not fully apply, leaving residual errors. The farther apart they are, the more ionospheric and tropospheric differences become non-negligible, so corrections tend to deviate.

Users may not always be aware of this factor. Being able to connect to a correction service makes people complacent and assume “corrections mean high accuracy.” But receiving corrections and corrections being fully effective are not the same. Even with a fixed solution, poor relationship conditions with the reference station may mean accuracy is lower than expected.

Be mindful of this in wide-area sites, areas far from reference stations, or terrain with strong relief. Even within the same region, elevation differences and local weather can change how well corrections apply. If “it was fine yesterday but not today,” the issue might not be simple device trouble but changes in the relationship with the reference station or atmospheric conditions.

When considering RTK error causes, looking only at the rover is insufficient. Consider the relationship with the reference station that produces the corrections to see the whole picture. Don’t judge solely on whether corrections exist—operate in places with large distance, terrain, or environment differences assuming verification by known points and multiple checks.

Factor 5 Insufficient initialization and fixed-solution checks

Obtaining a fixed solution is a key condition for RTK accuracy, but it’s dangerous to be satisfied merely by the “fixed” indicator. If initialization is incomplete or you start observing immediately after a fix, the fix may appear but still be unstable. This is a common operational cause of RTK errors.

Initialization is the ramp-up process that stabilizes a high-precision solution based on satellite observations and corrections. If reception is poor, communication unstable, or the observation posture unsettled during this stage, not only does it take longer to get a fix, but quality may remain unstable even after a fix. In the field, prioritizing efficiency, operators sometimes adopt values the instant a fixed indicator appears, which tends to introduce errors.

Be especially careful right after reinitialization. If a previously stable solution drops and then fixes again, it does not guarantee the same quality as before. If observing conditions have not improved, the solution may drop again or give subtly suspicious values despite being fixed. The term “fixed solution” creates a false sense of security; in practice you must check whether the fixed state is stable and continuous rather than simply whether it exists.

During continuous observation, operators can become so used to screen indicators that they miss changes. If you don’t carefully check switches between fixed and float, declines in quality indicators, or correction update irregularities, you may not notice that only some points suffered degraded quality. Later, when comparing with drawings or known points, you won’t understand why certain points are off.

To reduce RTK error causes, treat a fixed solution as a waypoint, not the finish. After fixing, wait a moment and check the value’s stability; remeasure important points to check consistency; perform turnaround checks at known points. This operational stance is effective for preventing subtle errors. It’s more important to judge whether a value is trustworthy than merely to have a number.

Factor 6 Problems with antenna setup or equipment handling

While attention often focuses on satellites and communication, antenna setup and equipment handling are common real-field causes of RTK errors. No matter how good the positioning environment is, incorrect handling or installation prevents stable correct positions. Height handling, tilt, insecure mounting, and nearby influences are fundamental but easily overlooked.

For example, even a slightly tilted pole shifts the tip position laterally. Operators may think they are holding it straight but on slopes or uneven ground they unconsciously tilt and vary posture between observations. On unstable ground, even when you believe the pole is properly set, its position can move slightly. These are not satellite-derived errors and can occur even with good communication and fixed states.

A common cause is misunderstanding antenna height input or the device’s reference point. If the height reference is ambiguous in operation, elevations may be offset even if horizontal positions match, or consistency in deliverables may be lost. In practice, horizontal accuracy often gets more attention, but RTK also requires proper handling of elevation; misconfiguration or input errors directly affect results.

Ignore neither mounting condition nor surrounding accessories. Loose mounting, touching the instrument during observation, or placing reflective objects near equipment can all reduce stability. Neglecting pre- and post-observation equipment checks can make field errors look inexplicable, when in fact they are due to physical handling mistakes.

When considering RTK error causes, view the entire system. Accuracy management includes not only satellites, corrections, and communication but also the operator’s actions that translate the position to a survey point. The finer the required accuracy—on the order of a few centimeters (a few inches)—the more operator variability becomes a direct error. Therefore, before trusting device performance, ensure setup and operation meet the needed positioning accuracy.

Factor 7 Mismatch in coordinate systems or correction settings

When the field says “RTK is off,” the cause can actually be a mismatch in coordinate systems or settings rather than positioning itself. This is a very important point. The device may be positioning stably, but if the coordinate frame, geodetic datum, elevation reference, or correction assumptions differ from the comparison target, the result will appear offset. If values are stable but don’t match known points, consider this possibility.

For example, a drawing may use a particular coordinate system while the field observations use another, causing a uniform shift when overlaid. Since the values don’t fluctuate, the anomaly is not obvious during work. The stability can lead teams to assume “RTK is fine,” and issues often only become apparent in downstream processes. Many cases only reveal discrepancies when survey results are compared with existing drawings, design data, or other survey outputs.

The same issue occurs with elevation. Horizontal positions may mostly agree while only height differs—this likely stems from differing elevation references rather than observation conditions. Height reference differences are less visually obvious on site and can lead to significant rework later.

Correction settings also matter. Using a correction method or assumptions without understanding them can lead to misdiagnosed errors. Don’t be reassured solely by the presence of corrections and a fixed state; verify what reference those results are expressed in. This mismatch becomes more likely when multiple sites, several operators, or multiple deliverables are involved.

To correctly isolate RTK error causes, clarify not only observation conditions but also the frame in which you compare coordinates. Setting mismatches lurk more quietly than device failure or satellite issues, and once missed they affect not only the field but also office processes. If results are stable but don’t match, carefully check settings and references first.

Factor 8 Insufficient observation time and rechecks

The final factor is insufficient observation time and lack of rechecks. This is more an operational design issue than a device or environmental problem. In sites where you want many points quickly, confirmation time per point tends to be short. But RTK results cannot be judged reliable from the instant numbers appear. Only after verifying stability, reproducibility by remeasuring the same point, and overall consistency can survey results be used in practice.

Adopting an important or reference point from a single quick measurement is risky because that instant may coincide with poor conditions, and that value becomes the basis for deliverables. The faster the operation, the more likely single-shot adoption happens. However, considering the time required to review everything later, spending time to check critical points usually pays off.

Insufficient observation time makes it hard to detect post-fix instability, momentary communication glitches, or slow bias from reflections. Without rechecks you cannot tell whether a measured value is plausible or just coincidentally appears so. “It doesn’t look wildly off” at the site is not equivalent to “trustworthy as a deliverable.”

Lack of rechecks affects both single points and overall consistency. For example, if a known point checked at the start does not match the known point checked at the end, the reliability of the entire point set measured in between is questionable. Without a turnaround check, you won’t know when conditions changed. Even if problems occur during observation, without recheck procedures you cannot detect them.

Reducing RTK errors requires workflow design as well as observation technique. Incorporate repeated checks of important points, pre/post comparisons at known points, and delayed remeasurements in poor locations to confirm reproducibility. High-performance equipment can make the job look deceptively easy, but careful checking procedures ultimately protect deliverables.

How to isolate RTK errors on site

You’ve now seen eight factors, but in practice merely memorizing them is insufficient. The key is having an order of suspicion for when errors appear. Many factors have similar symptoms, which causes field confusion: not fixing, not staying fixed, unstable values, or not matching known points can all be caused by multiple issues. Therefore, instead of randomly changing settings, follow a diagnostic order.

Start by checking the satellite reception and reflection environment. Assess sky openness, nearby walls or metal, and trees to see whether the measurement point itself is unreasonable. If this is poor, no amount of checking communication or settings will solve the root cause. Next, examine whether correction communication is continuously stable. It’s not enough that you’re connected—you need to see if disturbances occur during observation and whether fixed status continues.

Then consider the relationship with the reference station and correction conditions. In wide-area sites or places with large topographic differences, corrections may inherently be less effective. After that, review whether fixed-solution confirmation procedures are followed and whether reinitializations are handled properly. If inconsistencies remain after these checks, examine antenna height, setup posture, and coordinate system or setting matches.

This order works because the first checks are quick to perform on site. Reception and reflections are visible, and communication state can be tracked. Settings and coordinate mismatches are often noticed back in the office, so even when things “look measurable” on site you should keep them in mind as possible causes. Finally, always finish with rechecks. Without verification against known points or remeasuring key points, theoretical reasoning alone cannot guarantee deliverable reliability.

The aim when addressing RTK error causes is not perfect prediction but rapid detection and small corrective actions. You can’t eliminate all bad days or places, but by organizing suspected causes and addressing them you can minimize errors and reduce rework.

Summary

RTK errors commonly surface from a combination of conditions rather than a single fault. Poor satellite reception, mixed reflections, unstable correction communication, large differences with the reference station, lax initialization and fix checks, variability in antenna setup and operation, mismatched coordinate systems and settings, and insufficient observation time and rechecks—each can independently cause errors, and in practice two or three may occur together.

Therefore, don’t leave RTK accuracy entirely to the equipment. The higher the precision mechanism, the more result quality depends on proper use and verification. Don’t be reassured only because a value is displayed; cultivate the ability to explain why you can trust that value. Standardizing operations that include known-point checks and remeasurements helps suppress variability even when personnel change.

Stable RTK operation on site requires not only knowledge of error causes but also tools and workflows to detect causes early. If you want to efficiently carry out daily quick surveys, stakeout, quality checks, or alignment with photos and point clouds, ease of use and verifiability should be key selection criteria. LRTK, as an iPhone-mounted GNSS high-precision positioning device, makes RTK easier to use on site and offers an option for leveraging high-precision positioning in daily operations. For sites troubled by RTK errors and shaky confidence in each measurement, choosing a method that fits into routine work while understanding the positioning mechanism will help you balance accuracy and productivity.