Power-on is not interoperability

A radio can transmit, receive and pass a routine test while lacking the channel arrangements used by a coastal authority. The failure may appear only when the ship needs VTS, weather or urgent navigational information.

IMO identified the compatibility issue

MSC.1/Circ.1460/Rev.5 recognizes possible incompatibility between ship and shore VHF equipment after changes to the ITU Radio Regulations channel arrangements.

The compliance date has nuance

IMO says relevant SOLAS VHF equipment, including duplicated equipment, should comply by the first radio survey scheduled on or after 1 January 2028, or earlier as appropriate.

Coastal implementation may be earlier

Some administrations may use new available channels before the final shipboard date. Voyage planning must check the actual region rather than treating 2028 as permission to ignore compatibility.

GMDSS distress is not the whole issue

The cited changes do not affect GMDSS distress functions in the same way, but they can affect meteorological, navigational, urgent marine, port-operation and VTS communications.

Channel numbers can conceal different frequencies

Operators may believe both parties selected the same label while equipment channel plans differ. Verify frequency mapping and approved configuration through technical records.

Duplicated equipment needs duplicated compliance

An upgraded primary and obsolete backup leave a hidden single point of failure. Inventory every fixed and required duplicated installation by model, serial, firmware and channel plan.

Portable radios have a separate role

Survival-craft or onboard portable sets may not provide the same services as fixed VHF. Do not assume a handheld closes a channel-plan gap without checking approvals and capability.

Software may be the remedy

MSC.1/Circ.1389 addresses software and firmware updates driven by IMO and ITU regulatory change. Manufacturers should provide version and compliance information, and owners should keep equipment current.

Hardware may also be necessary

Older units may lack memory, synthesis range, type approval or vendor support for the new plan. Lifecycle budgets should include replacement, installation, testing and crew familiarization.

Type approval remains central

Unofficial programming can create prohibited transmissions, invalid certification or unexpected behaviour. Use approved manufacturer and authority routes.

Survey timing is not operational assurance

A certificate says the installation met applicable requirements at survey. The master still needs to know whether the ship can communicate with services in the next area.

Port agents are useful but not authoritative

An agent can identify local practice, yet technical compatibility should be verified through administration, VTS, official publications and equipment information.

Build a regional channel matrix

List coastal-State services, purpose, channel or frequency, implementation status, language, hours and fallback contact. Date the matrix and cite its sources.

Channel 16 remains disciplined

IMO Resolution A.954(23) reserves Channel 16 for distress, urgency, brief safety communication and calling before transfer to a working channel. It is not a substitute for missing routine channels.

Do not congest the calling channel

If a working channel is unavailable, transmit only the necessary call and explain the limitation concisely. Repeated technical discussion on Channel 16 can obstruct distress traffic.

DSC needs its own checks

Verify MMSI, watch receiver, test procedures, position and time inputs, and the equipment's applicable channel configuration. Voice success does not prove DSC readiness.

VTS contact affects navigation

IMO describes VTS as providing traffic, hazard and movement information while leaving navigation with the master. Incompatibility can remove a valuable shore layer during congestion.

Hormuz coordination increases consequence

IMO's operational FAQ says vessels may be contacted on Channel 16 in certain circumstances and then coordinate with coastal States. The fallback calling path does not remove the need for compatible working communications.

Authentication remains necessary

Reaching the expected channel does not prove caller identity. Apply published call signs, callback routes and instructions while preserving concise radio discipline.

Record failed calls

Log time, position, channel, equipment, signal, station, attempts and alternate method. This separates coverage or congestion from a channel-plan defect.

Test with shore where permitted

Use authorized non-distress calls and procedures. Do not create unnecessary traffic or use distress functions to prove compatibility.

Maintenance needs controlled updates

Authenticate firmware, preserve the prior version, update one redundant unit at a time where approved and test channel selection, audio, DSC, power and recording.

Crew interface may change

New channel labels, duplex modes or menu paths require familiarization. Update bridge cards and remove obsolete handwritten lists.

Cybersecurity protects the channel plan

Restrict programming access, portable media and vendor credentials. An unauthorized channel change can be both a communications defect and a security event.

Owners need a fleet gap analysis

Compare models and versions against manufacturer compliance statements and trade routes. Prioritize unsupported vessels entering early-adopting regions.

Masters need a no-surprise report

Before departure, receive a clear statement of compatible services, limitations, alternate contacts and planned rectification. Do not bury the issue in a technical defect list.

Fallbacks need more than a phone number

Satellite voice, email, agent relay or another coastal station may support coordination, but each path has delay, authentication, coverage and workload limits. Test the authorized alternative before entry, define who monitors replies and establish the point at which unreliable communications require holding outside constrained traffic.

Charterers should plan service downtime

Radio replacement and survey can affect schedule. Commercial planning should allow safe maintenance rather than pushing an incompatible vessel into a high-workload route.

Brokers must avoid simple equipped labels

Saying a ship has VHF does not answer channel compatibility. Ask for the applicable configuration when communication capability affects a fixture.

Insurers need the compliance trail

Preserve manufacturer statements, inventory, update logs, tests, survey evidence, defects and voyage checks. After an incident, the distinction between powered and compatible will matter.

Hypothetical: the silent VTS

The ship hears Channel 16 but cannot select the local working channel. It reports the limitation, uses an official alternate path and delays entry until traffic coordination is reliable.

Hypothetical: the unequal pair

The primary radio has new firmware and the backup does not. A pre-voyage audit catches the mismatch and prevents false redundancy.

Hypothetical: the unauthorized programmer

A contractor adds channels outside approved procedure. The owner quarantines the unit, restores certified configuration and investigates access across the fleet.

Forecast

VDES and revised channel use will increase digital traffic and authentication capability. Mixed-generation fleets will face a transition period in which disciplined inventories and regional verification remain essential.

ZeaClub view

Communication capability is an end-to-end condition between the ship, channel plan and coastal service. Inventory every set, follow the dated transition, verify the trading area and preserve a tested fallback. A radio that lights up but cannot reach the authority is not ready.

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

Sources