Military operational pictures traditionally centered on ground forces and organic sensors. As littoral operations and joint operations with naval and air components became standard, the need to incorporate maritime and air domain awareness into the COP became unavoidable. AIS (Automatic Identification System) and ADS-B (Automatic Dependent Surveillance-Broadcast) are the civilian standards that carry most maritime and air track data, and integrating them into a military fusion architecture requires solving several specific technical problems: format normalization, coverage gap handling, deduplication against organic radar tracks, and — critically — spoofing detection.

AIS: Format, Coverage, and Message Types

AIS is an NMEA 0183-based system operating on VHF frequencies 161.975 MHz and 162.025 MHz. Vessels transmit position reports as VDM (VHF Data-link Message) and VDO (VHF Data-link Own-vessel) sentences, which encode AIS payload data in a 6-bit ASCII encoding scheme. The payload is decoded to produce structured messages defined by the ITU-R M.1371 standard.

The most operationally relevant AIS message types are:

Message Type 1/2/3 (Position Report Class A): Transmitted by large vessels (SOLAS class) at intervals of 2–10 seconds when underway, 3 minutes when anchored. Contains MMSI number (vessel identity), latitude, longitude, speed over ground (0.1 knot resolution), course over ground, true heading, and navigation status. This is the primary track data message.

Message Type 5 (Static and Voyage Data): Transmitted every 6 minutes. Contains vessel name, call sign, IMO number, type, dimensions, destination, and estimated time of arrival. This is the vessel identification message — it provides the context that makes a track useful.

Message Type 18 (Standard Class B Position Report): Used by smaller vessels not required to carry Class A transponders. Shorter reporting interval, less precise position encoding. Covers the "grey zone" of smaller vessels that may be operationally relevant in littoral environments.

Message Type 21 (Aid to Navigation Report): Broadcast by navigation aids (buoys, lighthouses). Useful for map layer accuracy but not track data.

AIS coverage gaps are a significant operational limitation. VHF AIS operates on line-of-sight — shore-based receivers typically cover out to 40–60 nautical miles from the coast. Vessels beyond this range are invisible to terrestrial AIS unless satellite AIS (S-AIS) is available. S-AIS has global coverage but with update intervals of 5–10 minutes, not seconds. Defense integration systems must explicitly model coverage zones and flag tracks entering coverage gaps rather than silently dropping them.

ADS-B: Message Structure and Military Transponders

ADS-B operates on 1090 MHz (for aircraft with Mode S transponders) and transmits aircraft state via Extended Squitter (ES) messages. Each message is 112 bits carrying a 24-bit ICAO address (aircraft unique identifier), message type field, and payload. The relevant message types include:

Airborne Position Message (Type 11): Contains latitude, longitude, altitude (barometric or GNSS), and horizontal containment radius indicator. Position is encoded in Compact Position Reporting (CPR) format — a locally unambiguous encoding that requires decoding against either a reference position or a previous CPR message.

Airborne Velocity Message (Type 19): Contains ground speed, heading, and vertical rate. Provides kinematic state for track association.

Aircraft Identification Message (Type 1/2/3/4): Contains callsign and aircraft category. This is the identification data equivalent to AIS Message Type 5.

Military aircraft represent a significant gap in ADS-B coverage. Most military aircraft do not equip ADS-B Out transponders or operate with them disabled in tactical environments. Military aircraft in controlled airspace may carry Mode C or Mode S transponders that return radar interrogations without broadcasting ADS-B. Defense COP systems must handle the reality that ADS-B provides a civilian air picture that is systematically incomplete with respect to military aircraft.

Track Normalization: Building a Unified Schema

AIS and ADS-B tracks must be normalized to a unified track schema before fusion with other data sources. The unified schema must accommodate both maritime and air domain attributes while being extensible to ground tracks from other sensors.

Critical normalization tasks include:

Coordinate system normalization: AIS uses WGS84 decimal degrees with resolution to 0.0001 minutes (approximately 0.18 meters). ADS-B CPR encoding achieves approximately 5-meter position accuracy. Both should be stored as WGS84 decimal degrees with 6 decimal places (approximately 0.1-meter resolution at equator) in the unified schema.

Timestamp normalization: AIS timestamps from shore-based receivers carry receiver-applied UTC timestamps with ±1 second accuracy. ADS-B timestamps from SDR receivers carry GPS-disciplined timestamps with millisecond accuracy. For fusion purposes, all tracks should carry a nanosecond-precision UTC timestamp and a source accuracy estimate.

Speed and heading: AIS reports speed over ground in knots (0.1 resolution) and course over ground in degrees (0.1 resolution). ADS-B reports ground speed in knots and track angle. These are conceptually equivalent but encoded differently. Normalization should produce a unified velocity vector (speed, heading, vertical rate where applicable) in the canonical schema.

Identity fields: AIS identity is primarily the MMSI number (9-digit integer) supplemented by IMO number, call sign, and vessel name. ADS-B identity is the ICAO 24-bit address supplemented by callsign. Neither maps directly to military track identity schemes (which typically use unit designators or equipment serial numbers). The fusion layer must maintain cross-reference between civilian identity schemes and military identity attribution.

Spoofing Detection: AIS Manipulation Techniques and Countermeasures

AIS spoofing — transmitting false AIS messages to create phantom vessels or mask real ones — is a known adversarial technique used for deception, sanctions evasion, and maritime gray-zone operations. Documented techniques include:

Position falsification: A vessel transmits false position coordinates, appearing at a different location than its actual position. Often used to create an alibi location (vessel appears in permitted waters while actually in restricted waters) or to confuse maritime traffic services.

MMSI spoofing: A vessel transmits using another vessel's MMSI number, impersonating a different ship. Can be used to make a suspect vessel appear to be a known legitimate vessel.

Dark shipping: Not spoofing per se, but disabling or not transmitting AIS entirely. Common practice among vessels engaged in ship-to-ship transfers in sanctioned jurisdictions. A vessel that drops off the AIS track without entering port is a high-priority anomaly.

Algorithmic countermeasures for AIS spoofing detection:

Speed validation: Compute the minimum speed required to travel from the vessel's last valid position to its current reported position in the elapsed time. If this exceeds the vessel's maximum speed (obtainable from vessel type databases), the current report is flagged as a likely spoofed position.

Multi-receiver triangulation: A legitimate AIS signal is received by multiple shore stations with consistent signal strength profiles and timing offsets. A spoofed signal injected into the AIS data stream without a physical transmitter may be consistent with only one receiver or show anomalous time-difference-of-arrival patterns.

Behavioral consistency checking: Apply PoL analysis to AIS tracks. A cargo vessel that has operated on a consistent route for months suddenly appearing in an unusual position is a behavioral anomaly that warrants further scrutiny even if the signal itself passes physical validation.

Key insight: AIS and ADS-B data are cooperative — vessels and aircraft voluntarily broadcast their positions. In military contexts, the assumption of cooperation is often invalid. Build your fusion architecture with explicit coverage modeling, explicit spoofing detection, and explicit handling of "no report" states as a data point, not as an absence of data.

Integration with the COP: Rendering the Sea/Air Picture

AIS and ADS-B tracks enter the unified track store alongside radar and other sensor tracks. The COP rendering layer should differentiate between track sources — a cooperative AIS track with AIS-reported identity should render differently from a radar-only track with no identity attribution. Standard military COP symbology (MILSTD 2525 or APP-6) provides track symbols for both cooperatively identified and unidentified vessels and aircraft.

Track deduplication between AIS/ADS-B and organic radar is a significant data association problem. A vessel detected by both coastal radar and AIS will generate two candidate tracks. The fusion engine must associate them based on position, speed, and heading consistency, then produce a single merged track with AIS identity attribution. Track merging quality directly affects the analyst's ability to build a coherent recognized maritime picture (RMP) or air recognized picture (ARP).