Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
The standard was developed by IEC TC 80 (Maritime navigation and radiocommunication equipment and systems) in close collaboration with the Central Commission for the Navigation of the Rhine (CCNR) and the European Committee for Drawing Up Standards in the Field of Inland Navigation (CESAR). It supports the implementation of River Information Services (RIS) across European inland waterways and is compatible with similar initiatives on other inland waterway systems worldwide, including the Mississippi and Yangtze river systems.
IEC TS 62773 specifies modifications to the standard AIS message structure to accommodate inland navigation requirements. The key adaptation is the use of Application Specific Messages (ASM) to transmit inland-specific data that is not part of the standard maritime AIS message set. These extended messages include voyage-related information such as the vessel’s European Vessel Identification Number (ENI or CESAR number), dimensions and type, draught, cargo information, and convoy composition.
| Message Type | Content | Update Rate | Inland-Specific Features |
|---|---|---|---|
| Inland Ship Static and Voyage Data | ENI/CESAR number, vessel name, dimensions, ship type, cargo, convoy info | Every 6 minutes or on change | Blue board status, convoy formation, dangerous cargo indicator |
| Inland EMMA Warning Message | Water level information, lock status, bridge clearance, fairway warnings | As required by authority | Upstream/downstream water levels, restricted areas |
| Inland Water Level Message | Actual and reference water levels, gauge information | Periodic updates | Water level trend, shallow water warnings |
| Inland Signal Status Message | Traffic signal status, lock/bridge operating status | Real-time on change | Priority request status, estimated opening time |
| Inland Notices to Skippers | Navigational warnings, weather alerts, closures | As required | Geographic referencing, validity period |
One of the most important inland-specific data elements is the Blue Board (blue cone/light) status, which indicates whether a vessel carrying dangerous goods meets the requirements to navigate through tunnels or under bridges. The Blue Board system, widely used on European waterways, is integrated into the inland AIS message structure so that vessel status is automatically transmitted to lock operators, bridge keepers, and other vessels in the vicinity.
The standard specifies minimum display requirements for inland AIS equipment, which differ significantly from maritime AIS displays. Inland navigation requires presentation of water depth information, lock and bridge status, fairway dimensions, and speed limits in kilometres per hour (not knots). The display must support the ENI/CESAR number alongside the MMSI number, and must present convoy information when vessels are operating in pushed or hauled formations.
Display symbology includes inland-specific markers for lock chambers, bridge clearance gauges, water level stations, and restricted areas. The standard also requires the ability to display Electronic Navigational Charts (ENC) for inland waterways, which differ from maritime ENC in their data model and feature catalogue. The user interface must support local language requirements, with European displays typically supporting multiple languages for cross-border operations on international waterways.
From an engineering perspective, several aspects of IEC TS 62773 deserve particular attention. First, the coexistence of maritime and inland AIS on shared waterways (such as rivers with seagoing traffic near ports) requires careful management of VHF data link (VDL) load. The standard specifies transmission slot allocation algorithms that prioritise safety-related messages and prevent VDL overload in congested waterways. The VDL load management algorithm follows the principles of ITU-R M.1371 but with modifications to accommodate the higher density of AIS-equipped vessels typical of inland waterways.
Second, power supply and installation requirements for inland vessels differ from maritime installations. Inland vessels often operate with single-phase AC power systems and may have limited backup power capacity. The standard defines power consumption limits and includes requirements for operation during extended lock waiting periods where shore power may not be available. Equipment must be capable of operating on vessel battery power for at least 5 hours without recharging to ensure continuous operation during lock passage and waiting times.
Third, antenna installation on inland vessels presents unique challenges. Inland vessels frequently pass under low bridges where mast-mounted antennas must be lowered, and the standard requires that the AIS equipment maintain operation or gracefully recover after the antenna is re-deployed. The installation guidelines in Annex A provide specific recommendations for antenna placement to minimise the effects of superstructure shadowing, particularly on vessels with high container stacks or specialised cargo.
| Parameter | Maritime AIS (IEC 61993-2) | Inland AIS (IEC TS 62773) |
|---|---|---|
| Frequency | 161.975 / 162.025 MHz | Same (maritime VHF band) |
| Transmit power | 2 W / 12.5 W | 2 W typical (lower for dense traffic) |
| Position update rate | 2-10 seconds depending on speed | 2-10 seconds (same) |
| Vessel ID | MMSI (9-digit) | MMSI + ENI/CESAR number |
| Speed units | Knots | km/h |
| Water depth display | Not required | Required with gauge correlation |
| Convoy support | Not supported | Pushed/hauled convoy data |
| Language support | English | Multi-language (local requirements) |
Fourth, data security provisions are addressed through the standard’s requirements for equipment authentication and message integrity verification. While the maritime AIS system is inherently unencrypted and broadcast-based, the inland application includes additional data verification fields to prevent spoofing of water level, lock status, and signal status messages that could create safety hazards. Manufacturers must implement the message authentication framework specified in Annex B to ensure that authority-generated messages can be verified by receiving equipment.