Question 1

The DPO contacts the platform OIM and learns that another DP vessel nearby is reporting similar GNSS position jumps at the same time. What does this confirm, and what should be done with the information?

Accepted Answer

It strongly confirms an external GNSS interference source affecting the wider area, not a vessel-specific equipment fault — this should be reported promptly (to the OIM/field operator, and via appropriate channels such as NAVCEN or flag state advisories) so other vessels in the area can be warned before they unknowingly rely on corrupted GNSS A shared, area-wide GNSS problem is exactly the kind of finding that has real consequences for every other vessel and aircraft relying on GNSS nearby — prompt, wider notification (not just internal vessel reporting) is part of responsible practice during a known interference event, consistent with how real-world GPS interference advisories get issued.

Question 2

A DP2 vessel is holding position. Both DGNSS units (normally independent) suddenly show an identical, sudden position jump of 40 metres in the same direction at the same instant, while the Fanbeam shows no corresponding change. What should the DPO immediately suspect?

Accepted Answer

A GNSS-wide problem affecting both satellite receivers simultaneously (interference, spoofing, or a satellite constellation issue) rather than two independent sensor faults — the fact that both units moved identically and together is the key clue, since genuinely independent reference systems failing identically at the same instant is far less likely than a shared external cause The signature here is diagnostic: independent systems agreeing with each other but disagreeing with a genuinely different technology (Fanbeam) is a classic common-cause signature pointing at the GNSS signal environment itself, not the receivers. This is exactly the pattern seen in real GNSS jamming and spoofing incidents.

Question 3

The DPO checks the Fanbeam reading against the suspect DGNSS units and confirms the vessel has not actually moved 40 metres — the Fanbeam position is consistent with the pre-event position. What should the DPO do immediately?

Accepted Answer

Manually exclude both DGNSS units from the DP position solution immediately, relying on the Fanbeam (and any other unaffected reference) — do not wait for the DP system's automatic voting to resolve this, since two affected units may outvote the one correct reference if left to automatic logic This is precisely why blind trust in majority voting is dangerous during a common-cause GNSS event: two affected systems can outnumber the one unaffected system, and naive voting logic would pick the wrong answer. The DPO's own judgement, informed by cross-checking technology types, must override simple vote-counting here.