A route line can be correct while the ship symbol is wrong

An approved route displayed on ECDIS does not guarantee that the ship’s plotted position is reliable. When a GNSS receiver is jammed, it may lose a usable signal. When it is spoofed, it may produce a convincing but false position, course, speed, or time input. The second case can be harder to detect because the display may continue to look normal.

MARAD’s active Hormuz advisory says significant GNSS interference, spoofing, and jamming continue in the Persian Gulf, Strait of Hormuz, and Gulf of Oman. It recommends greater reliance on radar ranges, visual bearings, and cross-checking ECDIS inputs with secondary navigation systems.

The US Coast Guard’s public problem-report database contains 2026 user reports from Fujairah, the Gulf of Oman, Bahrain, Das Island, Ras Tanura, and other regional locations. Reports described signal loss, displaced positions, and ships using dead reckoning or manual fixes. These are user reports with stated analytical limitations, not a complete official attribution of interference. They still show why a bridge team cannot wait for a total equipment failure before questioning its position.

Whether the voyage can continue depends on the ship’s location, independent fixing capability, traffic, visibility, route constraints, equipment status, crew competence, and current threat. There is no safe universal instruction to proceed or stop.

Detection begins before the alarm

A spoofed receiver may not generate a clear alarm. Detection depends on comparing independent evidence. Radar ranges and bearings to charted fixed objects, visual bearings, depth information, parallel indexes, speed-log and gyro data, and the expected movement of nearby targets can reveal inconsistencies.

Two satellite receivers do not necessarily provide full independence. They may share antennas, signal conditions, processing assumptions, or vulnerable constellations. A display that combines several satellite systems can still be affected. The bridge team should understand the actual architecture rather than count screens.

Unexpected changes in position, speed over ground, course over ground, time, AIS target behavior, radar overlay alignment, or autopilot response are warning signs. A ship symbol moving ashore is obvious; a small lateral shift toward a hazard is not. Frequent terrestrial fixes can expose gradual drift before it becomes dangerous.

The May 2026 Hormuz industry guidance recommends planning on the assumption that GNSS may be unavailable or unreliable for the entire transit. It calls for paper-chart backup where appropriate, advance identification of landmarks and fixed aids suitable for radar plotting, a GNSS-loss drill, and proficiency in terrestrial navigation.

That standard turns degraded navigation from an improvised emergency into a rehearsed operating mode.

Set conditions for continuing, slowing, or suspending

The passage plan should define what minimum independent navigation capability is required in each segment. Open water with clear radar references presents a different case from a congested, narrow, mined, or authority-controlled corridor. The plan should state when manual steering, increased bridge manning, additional lookouts, reduced speed, or a master’s presence is required.

The industry quick-reference card proposes active GNSS cross-checks, parallel indexes, frequent fixes, continuous radar sweep, reinforced lookout, manual steering, and radar overlay. These are useful planning prompts, but the master must adapt them to the ship and current instructions. A fixed six-minute interval may be too long in one situation and unnecessarily short in another.

A decision to slow or stop must consider traffic and security exposure. Holding in a narrow approach can create more danger than continuing under reliable radar navigation. Drifting or anchoring may make the ship predictable or place it in congestion. Reversing course may conflict with traffic flow or authority instructions.

Abort criteria can include loss of all reliable independent fixes, radar failure, inability to reconcile position within a defined tolerance, loss of steering or communications, excessive bridge workload, unexpected hazard proximity, or a new security event. The company should support the master’s decision without allowing schedule pressure to lower the minimum standard.

Separate navigation data from commercial tracking

Shore teams often see the same corrupted position through AIS or a commercial platform and assume it is true. A track jumping toward Iran can trigger false deviation, sanctions, casualty, or detention alarms. Conversely, a frozen position can be mistaken for anchoring when the ship is moving under degraded communications.

The company should establish an authenticated ship-to-shore verification process. The bridge can report the independently fixed position, method, time, confidence, and operational status through an appropriate channel. Commercial teams should label platform data as unverified when interference is known and avoid distributing it as fact.

Charterers and cargo interests may need updated arrival estimates, but the bridge should not be overloaded with repeated position requests. A shore coordinator can consolidate inquiries and issue controlled updates. The revised ETA should include uncertainty caused by slower speed, added fixing work, route coordination, or a pause.

Incident reports should distinguish jamming, suspected spoofing, equipment fault, mapping error, and unexplained anomaly. Attribution to a State or armed group requires evidence beyond the effect observed aboard. Preserving screenshots, equipment logs, radar plots, times, and reports can help authorities analyze the event.

Build commercial resilience around degraded navigation

A voyage estimate should allow for reduced speed, added bridge resources, delayed movement, and possible route suspension. Those allowances are scenarios, not automatic costs. Their value is to prevent a ship from being economically committed on the assumption that satellite navigation will remain normal.

Owners should verify that officers are competent with the installed ECDIS, radar, paper backup where carried, and manual position plotting. Equipment maintenance and sensor configuration matter as much as written policy. A drill that reveals weak radar fixing before Hormuz creates time to correct it.

Contracting teams should understand that a navigation pause can be a safety decision rather than a discretionary commercial delay. The consequences for hire, laytime, deviation, and notices depend on the governing wording and facts. Clear contemporaneous records reduce later disagreement.

Zeaclub’s direction in agentic maritime workflows can help compare ship reports with commercial tracking, detect impossible movements, prevent corrupted coordinates from updating an ETA automatically, and route a verified anomaly to marine and security teams. It should not calculate a “safe” position from the same compromised feed or overrule the bridge. The essential control is independent navigation by a prepared crew.

This article distinguishes verified source material from ZeaClub analysis, recommendations, forecasts and hypothetical scenarios.

Sources