Your Ship Is in the Black Sea. AIS Says It Is in Peru: Inside Maritime’s 12,000-km Navigation Problem

🔔 Subscribe to ShipUniverse Weekly →

Navigation Integrity Incident File

The 12,129-Kilometre AIS Error

Four vessels off Bulgaria transmitted 27 AIS positions placing them inside the same small area of Lima. A terrestrial receiver in Varna heard the transmissions locally. The ships had not crossed the Atlantic. Their position data had.

Reported position error
12,129
Kilometres
Ships 4 tankers
Reports 27
Reported area ~1 km
Receiver Varna
Radio received in Bulgaria · Coordinate says Peru

A vessel can transmit a perfectly valid AIS radio message containing a completely invalid position. That appears to be the central lesson from a September incident detected off Bulgaria.

The receiver location makes the anomaly unusually easy to diagnose. Terrestrial AIS is short-range VHF. If a shore receiver in Varna hears the transmission directly, the transmitter has to be somewhere within terrestrial radio reach, not 12,000 kilometres away in Lima.

But a 12,129-kilometre error is almost too obvious. The harder navigation problem begins when the false position moves only far enough to remain believable.

Black Sea anomaly
27
Position reports from four vessels placed around central Lima.
Gulf event
1,702
Impossible position jumps reported across 379 vessels from September 2–9.
GNSS-connected systems
20+
Systems identified in the RIN modern-vessel connectivity study.
System categories
7
Navigation is only one category using GNSS position or time.

The radio signal and the position field tell two different stories

This is what makes terrestrial AIS reception useful for integrity checking. The radio has its own physical geography.

Physical radio evidence

Receiver says Black Sea

Varna

A nearby terrestrial VHF receiver directly heard the vessels' AIS broadcasts.

VS
Encoded navigation data

AIS position says Peru

Lima

The position embedded in the received messages was roughly 12,129 kilometres from the ships' operating area.

The useful distinction
AIS did not physically transmit from Peru. The AIS unit transmitted locally while carrying a false geographical position. That points the investigation toward position integrity rather than physical vessel location.

The bad coordinate can enter AIS before the radio ever transmits

AIS depends on positioning information supplied by GNSS or another approved position source. Once that source is wrong, the AIS radio can accurately broadcast the wrong answer.

Simplified corruption path

Position source → shore display
01

GNSS signal

Receiver accepts misleading position or timing information.

02

Ship position source

False coordinates become an apparently valid ship position.

03

AIS transponder

AIS incorporates the position into its normal outgoing message.

04

VHF transmission

The radio broadcasts normally from the vessel's real physical area.

05

Tracking platform

The impossible coordinate may be displayed, flagged or removed as an outlier.

Lima is the easy case. A believable lie is harder.

The following scale is an operational illustration, not a universal alarm threshold. The point is that spectacular errors are easier for people and software to reject than plausible ones.

12,129 km

Obviously impossible

A tanker heard by a Bulgarian terrestrial receiver cannot simultaneously be transmitting VHF from Lima.

50 km

Operationally suspicious

Radar, coastlines, expected track and nearby traffic should make a displacement of this scale apparent quickly.

2 km

Potentially believable

The displayed ship may still appear to be in the correct general channel, anchorage or traffic area.

300 m

Small enough to trust

Near shoals, traffic lanes or port approaches, a plausible error can matter more than a spectacular teleport.

ShipUniverse operational inference
Automatic data cleaning can remove an absurd Lima position. It is much harder to automatically reject a position that remains geographically plausible but is wrong enough to change a navigational decision.

GNSS is not one screen on the bridge

Modern ships distribute position and precise time into systems far beyond a standalone GPS receiver. A spoofed position can therefore become a vessel-wide data-integrity problem.

Navigation

ECDIS, radar and track control

Electronic navigation equipment may consume GNSS position, speed or timing directly or indirectly.

Identification

AIS

False position data can be redistributed to other vessels and shore receivers.

Emergency

GMDSS and distress systems

Distress equipment can depend on GNSS position or timing when creating emergency information.

Communications

LRIT and satellite services

Position and time can also feed long-range reporting and connected communications equipment.

Operations

DP and automated functions

Position-dependent automation requires particular attention when GNSS integrity becomes uncertain.

Records

VDR, clocks and digital logs

Incorrect position or timing can contaminate records used later to reconstruct an event.

One position should never win just because it is digital

Position-integrity evidence board Cross-check, do not vote by screen count
Source
What it tells the bridge
GNSS dependence
Use during suspected spoofing
Radar ranges / bearings
Physical relationship to coastline, targets and charted objects.
Low
Strong independent check when suitable targets are available.
Visual bearings
Direct observation of known terrestrial references.
None
Particularly valuable near identifiable coast or aids to navigation.
Dead reckoning
Expected position from prior fix, heading, speed and elapsed time.
None
Error grows with time but provides an independent plausibility check.
Echo sounder / depth
Physical depth that can be compared with charted bathymetry.
None
Useful corroboration where depth contours are distinctive.
Second GNSS receiver
Independent hardware may reveal a receiver-specific failure.
High
Agreement alone does not prove correctness during area-wide spoofing.
AIS target position
What another vessel's equipment says its position is.
High
Supplemental information only when GNSS integrity is in doubt.

The workload rises even when the bridge detects the problem correctly

2026 RIN maritime survey

Navigation falls back to people

GNSS interference does not only create a position error. It forces bridge teams to replace automated certainty with cross-checking, manual fixes, additional watchkeeping and sometimes changes to the vessel's operating plan.

Added bridge personnel 61% Reported response to increased workload.
Reduced speed 30% Reported operational response.
Unsafe / unlawful situation 14% Roughly one in seven survey responses.
Moderate / large workload effect ~75% Reported impact of interference regions.

When the screens disagree, rebuild position from independent evidence

01
Physical observations
Radar, visual bearings and identifiable charted objects test position against the physical world.
Independent
02
Motion history
Dead reckoning tests whether the new position is physically compatible with heading, speed and elapsed time.
Independent
03
Other position sensors
Independent PNT sources can strengthen confidence if they do not share the compromised dependency.
Verify source
04
AIS and GNSS displays
Multiple screens can agree because they are consuming the same corrupted position source.
Do not count twice

Navigation Position Trust Console

Start with the Lima event or build a more subtle scenario. The model asks whether the AIS coordinate agrees with the physical radio geometry and independent navigation evidence.

ShipUniverse Position Integrity Analyzer

Would you trust this coordinate?

The tool separates AIS message validity from position validity and shows how far a suspect GNSS input could propagate through a digitally integrated vessel.

Integrity check active
Geometry
AIS position displacement Distance between reported position and best independent fix.
Terrestrial AIS received locally Was the VHF message directly received near the ship's real operating area?
Independent physical fix Radar, visual, terrestrial or other non-GNSS evidence.
Position-source behavior
Other vessels affected Are nearby vessels showing related position anomalies?
GNSS receiver status What is the ship's positioning equipment reporting?
Track continuity Is the reported movement physically compatible with vessel speed?
Vessel integration
GNSS integration depth How widely is position or time distributed onboard?
Independent positioning available Can the bridge maintain position awareness without GNSS?
AIS coordinate assessment
Position Not Credible

The encoded coordinate conflicts with both radio geometry and independent physical evidence.

Coordinate trust 0 / 100
Displacement 12,129 km
Likely issue GNSS integrity failure
Systems to verify 6+ groups
Position confidence Reject
Integrity signals
Radio geometry
Conflict
Physical fix
Conflict
Track physics
Impossible
Regional pattern
Multiple ships
Navigation priority Treat GNSS-derived position as untrusted and rebuild the fix from independent navigation evidence.

Cross-check radar, visual or terrestrial position information, maintain appropriate bridge resource management, verify which systems consume the suspect GNSS feed and report interference through applicable operational channels.

ShipUniverse screening model only. It is not a replacement for the vessel's Safety Management System, Master's judgment, flag or coastal-state instructions, bridge procedures or equipment-manufacturer guidance. The simulator estimates position-integrity concern from observable inconsistencies; it does not identify the source, operator or intent behind interference.
Research basis: Worldwide AIS Network reporting of the September 2026 Black Sea and Gulf anomalies; U.S. Coast Guard Navigation Center AIS and GPS interference guidance; IMO, ICAO and ITU joint GNSS-interference statement; IMO BMP Maritime Security guidance; IALA AIS, VDES and resilient-PNT guidance; and the Royal Institute of Navigation 2026 report on the impacts of GNSS interference on maritime safety. The distance-scale examples and interactive trust model are ShipUniverse analytical illustrations unless identified as reported incident data.
Feedback Welcome

We welcome your feedback, suggestions, corrections, and ideas for enhancements.

Please click here to get in touch
By the ShipUniverse Editorial Team — About Us | Contact