Satellite AIS vs. Terrestrial AIS: Understanding the Coverage Difference

Satellite AIS versus terrestrial AIS coverage comparison diagram

The Automatic Identification System was originally designed for collision avoidance and vessel traffic service (VTS) management in coastal and port waters. VHF radio transmissions from AIS transponders reach receivers on shore and on nearby vessels, giving harbormasters and coastal authorities a real-time picture of traffic within their jurisdiction. For decades, this worked well within its design parameters — but it left 70% of the planet's surface, and a substantial fraction of the global commercial fleet operating in deep-ocean trades, essentially invisible.

Satellite AIS changed the equation. By placing AIS receivers in orbit, it became possible to receive vessel broadcasts from anywhere on Earth's surface, closing the coverage gap over open oceans that terrestrial networks simply cannot reach. Today, the combination of satellite and terrestrial AIS provides genuinely global vessel tracking — but the two technologies have fundamentally different characteristics, and understanding those differences is essential for anyone building maritime monitoring applications or making operational decisions based on vessel position data.

How Terrestrial AIS Works and Where It Excels

Terrestrial AIS receivers are shore-based antennas — mounted on coastal headlands, port buildings, offshore platforms, and buoys — that receive the VHF transmissions from vessel transponders. Class A AIS transponders (mandatory on vessels over 300 GT and all passenger ships) transmit on two VHF channels (161.975 MHz and 162.025 MHz, known as AIS Channel 87B and 88B) using TDMA (Time Division Multiple Access) protocols. The transmission interval varies with vessel activity: 2 seconds for vessels underway above 23 knots, up to 3 minutes for anchored vessels.

The effective range of terrestrial AIS is typically 15 – 40 nautical miles, depending on antenna height, terrain, and atmospheric conditions. High-elevation antennas on coastal headlands can achieve 60+ nm range under favorable propagation conditions, while antennas in sheltered harbors may have an effective range of 10 – 15 nm. In high-density traffic areas like the English Channel, the Dover Strait, or Singapore Strait, terrestrial networks achieve near-complete coverage with position updates every few seconds for vessels underway.

This low latency and high update rate is terrestrial AIS's primary advantage over satellite alternatives. For vessel traffic services, collision avoidance support, port approach management, and any application requiring near-real-time vessel positions in coastal waters, terrestrial AIS remains the gold standard. The data is essentially live — operators monitoring vessels approaching a port berth or navigating a narrow channel need position updates measured in seconds, not minutes, and satellite systems cannot yet provide this in most areas.

How Satellite AIS Works and What Makes It Different

Satellite AIS (S-AIS) works by placing AIS receivers aboard satellites in low Earth orbit (LEO). As each satellite passes over a region, it receives AIS transmissions from vessels below, stores them, and downlinks the data to ground stations. The fundamental technical challenge of satellite AIS is the message collision problem: in areas with high vessel density, hundreds or thousands of vessels transmitting simultaneously on the same TDMA channels create collisions that corrupt individual messages. Early S-AIS satellites struggled with message detection rates below 50% in high-density areas like the South China Sea or North Sea.

Advances in receiver technology, signal processing algorithms, and satellite constellation design have substantially improved detection rates over the past decade. Modern S-AIS providers using constellation of dozens to hundreds of satellites with sophisticated multi-channel receivers report detection rates exceeding 95% for individual vessels in most ocean areas. Dense coastal regions still present challenges, but the gap with terrestrial systems has narrowed significantly.

The key limitation of S-AIS that cannot be eliminated by technology is revisit time — the interval between successive satellite passes over a given location. LEO satellites orbit at altitudes of 500 – 1500 km, completing an orbit roughly every 90 – 100 minutes. A single S-AIS satellite provides coverage of a given ocean area for a few minutes per orbit, so a small constellation might achieve one update per vessel every 30 – 90 minutes in deep-ocean areas. Larger constellations — the leading commercial providers now operate 50 – 100+ satellites — can achieve update intervals of 10 – 20 minutes in many areas, but this is still orders of magnitude less frequent than terrestrial reception rates in busy coastal waters.

Practical Implications for Fleet Monitoring

For fleet operators monitoring vessels in oceanic trades, satellite AIS provides visibility that was simply impossible without it. A Capesize bulk carrier transiting the South Atlantic, a VLCC crossing the Indian Ocean, or a gas carrier navigating Arctic waters can be tracked throughout their voyage, not just when they enter the range of a coastal receiver. This has transformed fleet operations management: voyage progress can be monitored continuously, ETAs recalculated with actual track data rather than estimated progress, and deviations from planned routes detected promptly.

The latency introduced by S-AIS revisit time must be understood and managed. A position showing a vessel at coordinates X as of 20 minutes ago does not mean the vessel is currently there — at 15 knots, the vessel has traveled approximately 5 nautical miles since the last fix. For most fleet monitoring applications this is acceptable, but for any safety-critical use (collision avoidance, search and rescue, emergency response) only terrestrial AIS or other real-time data sources should be relied upon.

The MMSI (Maritime Mobile Service Identity) — the unique nine-digit identifier assigned to each vessel — is the key linking field that allows positions from both satellite and terrestrial receivers to be merged into a single vessel track. A data fusion platform that receives S-AIS position fixes for a vessel at sea, then transitions to high-frequency terrestrial positions as the same vessel approaches port, provides a seamless tracking experience that neither source could achieve alone. The challenge for analytics platforms is managing the handoff cleanly, dealing with the inevitable data quality issues — timestamp inconsistencies, position spoofing, MMSI conflicts — that arise when fusing data from different receiver networks.

Data Quality and Integrity Considerations

A critical but often underappreciated difference between satellite and terrestrial AIS is the signal-to-noise ratio and data quality profile of each source. Terrestrial receivers, operating at close range with strong signal strength, typically achieve high message integrity — position fixes are accurate, timestamps are reliable, and false detections are rare. The principal data quality challenge in terrestrial networks is coverage gaps in mountainous or archipelago regions where line-of-sight coverage is difficult.

Satellite AIS data, particularly in high-density areas, has a higher rate of corrupted messages, false detections (a known artifact of multi-vessel signal collisions producing syntactically valid but semantically incorrect messages), and timestamp uncertainty introduced by the downlink chain. A maritime analytics platform that ingests raw S-AIS data without robust quality filtering will produce position plots with occasional "ghost vessels" — positions that appear to show vessels in impossible locations or moving at impossible speeds, artifacts of message collision decoding errors.

SOLAS Chapter V requires vessels to maintain accurate AIS transmissions, but deliberate AIS manipulation is a documented phenomenon, particularly in sanctioned areas. Vessels involved in ship-to-ship transfers, sanctions evasion, and other illicit activities may disable their AIS transponders, broadcast false positions, or use spoofed MMSI numbers. Satellite AIS is more vulnerable to manipulation detection gaps than terrestrial systems, simply because the longer revisit time means a vessel can disable and re-enable its transponder between satellite passes without generating an obvious gap in the terrestrial record.

Choosing the Right Data Source for Your Application

The practical answer for most maritime analytics applications is "both." Terrestrial AIS provides the high-frequency, low-latency coastal coverage essential for port operations, vessel traffic management, and near-real-time monitoring applications. Satellite AIS fills in the ocean coverage that terrestrial networks cannot provide, enabling continuous fleet tracking across entire global trade lanes.

The allocation of data sources by use case should be explicit. Port congestion analytics, arrival time calculation, and berth scheduling all depend on frequent position updates and should be driven by terrestrial AIS where available. Voyage progress monitoring, ETA calculation for vessels in open ocean, and historical track reconstruction benefit from S-AIS coverage. Regulatory compliance applications — CII monitoring, DCS fuel consumption reporting, MARPOL compliance — need complete voyage coverage and should fuse both sources, using terrestrial data in coastal zones and S-AIS for ocean segments.

For applications requiring the highest reliability in open-ocean areas — offshore installation monitoring, polar route tracking, search and rescue coordination — supplementing AIS with additional position reporting systems is advisable. Iridium-based satellite communication systems, VDES (VHF Data Exchange System, the next-generation successor to AIS), and direct VSAT position reporting all provide complementary coverage with different latency and cost profiles. The evolution of VDES, which the IMO is progressively implementing through 2024 – 2030, promises to address many of the S-AIS limitations by using a wider frequency band and two-way communication capability — but that transition is still in its early stages.

← Back to Blog