SuperbaKnowledge Demonstration release
Platforms
Superba ecosystem
SuperbaHubEcosystem overview — how the environments connect, and the architecture behind them
Live demonstrations
Superba KnowledgeYou are hereOperational maritime knowledge
Carbon Easy MapsMaritime decarbonisation, mappedPSC Easy MapsPort State Control, understood as a system
Training
LearningTraining delivery
ENIT
Superba ecosystem
SuperbaHubEcosystem overview — how the environments connect, and the architecture behind them
Live demonstrations
Superba KnowledgeYou are hereOperational maritime knowledge
Carbon Easy MapsMaritime decarbonisation, mappedPSC Easy MapsPort State Control, understood as a system
Training
LearningTraining delivery
Home › Navigation › Electronic Navigation and GNSS Resilience
Operational guide · Operational procedure

Electronic Navigation and GNSS Resilience

Multi-band, multi-constellation, RAIM, authentication and CRPA may mitigate GNSS risk but do not guarantee a valid fix during jamming or spoofing: plausibility checks and independent sources remain necessary.

GNSSjammingspoofingelectronic navigation

Operational Explanation

Jamming may deny the signal and spoofing may produce plausible but false PNT. RAIM checks measurement consistency, not universal authenticity; multi-band and other technologies improve resilience only within their limits. Decisions must be performance-based and tied to equipment actually installed.

Regulatory Reference

SOLAS V/19 and applicable performance standards; joint IMO/ICAO/ITU statement on GNSS interference. Equipment manuals, bridge procedures and SMS define degraded/denied-PNT response.

Scope of Application

Every ship dependent on GNSS for position, velocity or time. Technological mitigations are not universal SOLAS requirements for every ship and area.

Procedure / How to Complete It

  1. Know capabilities, inputs, alarms and failure modes of installed equipment.
  2. Monitor time/position jumps, speed/course anomalies, sensor disagreement and plausibility.
  3. Cross-check with radar, visual/celestial fixes, echo sounder and DR/INS where available.
  4. On degradation isolate suspect inputs and enter the ship-specific denied-PNT procedure.
  5. Record and report interference through applicable Company, coastal and navigational-warning channels.

Practical Example

A RAIM-enabled receiver gives no alarm but radar ranges and soundings disagree: the team does not declare GNSS valid; it moves to independent checks and degraded procedure.

What Typically Goes Wrong

Promising accurate position with L1/L2/L5 during complete interference or making multi-band/RAIM universally mandatory.

Common Mistakes Mistake Library

MistakeConsequenceHow to Avoid It
Promising accurate position with L1/L2/L5 during complete interference or making multi-band/RAIM universally mandatory.Incorrect operational decision or regulatory statusUse the primary reference and ship-specific procedure

What the PSCO Checks

Sensor familiarity, alarms, cross-checks, fallback, passage plan, records and interference reporting.

Operational Tips

Preparation checklist

FAQ

Does RAIM prove signal authenticity?
No. It checks measurement integrity/consistency within its design, not every spoofing attack.
Does multi-band always retain accurate position?
No. It may improve resilience, but wide-band interference or sophisticated spoofing may degrade or deceive it.
What makes the response resilient?
Plausibility monitoring, independent sources and a tested ship-specific procedure.

Related Topics

ECDIS (Electronic Chart Display and Information System)Passage Planning in Polar Waters

Last substantive revision of this page: 31 August 2026 · page fingerprint 08abae3c2c7e