Operational guide · Operational procedure

VTS Traffic Management

Participating ships take information, advice and warnings into account; VTS requirements and instructions issued within the applicable framework are complied with unless contradictory safety or marine-environment-protection reasons exist.

VTSvessel traffic serviceSOLAS V/12maritime traffic

Operational Explanation

A.1158(32) distinguishes information/advice/warnings from requirements/instructions. The former inform decision-making; the latter, when issued within VTS authority and framework, are complied with by a participating ship unless contradictory safety or environmental-protection reasons exist. The Master's ultimate responsibility is unchanged.

Regulatory Reference

SOLAS V/12 and A.1158(32), sections 3.2, 6 and 7. Local procedures, sailing directions and port regulations define participation, reporting and each VTS's authority.

SOLAS V/12.3 permits mandatory use of VTS only in sea areas within the coastal State’s territorial sea. Check published limits and participating categories; distinguish VTS from other reporting systems. The international legal regimes referred to in V/12.5 remain unaffected. IMO: SOLAS V/12.

A.1158(32), 6.1: provide required reports and report pollution and navigational dangers to VTS. Promptly clarify ambiguous messages and communicate defects or limitations affecting compliance with instructions under local procedures. IMO A.1158(32).

Scope of Application

Designated participating ships and other ships taking part in VTS under the promulgated framework. Always distinguish message category and applicable authority.

Procedure / How to Complete It

Before entry read reporting points, channels, language and local requirements.
Classify the message as information/advice/warning or requirement/instruction.
Take the former into account and comply with applicable requirements/instructions.
If an instruction conflicts with safety/environment, protect the ship and immediately communicate intention and reasons.
Record communications and maintain lookout, COLREG and Master's responsibility.

Practical Example

VTS issues a traffic-sequencing instruction. The ship follows it; if an immediate safety condition prevents compliance, it informs VTS, gives the reason and takes the necessary safe action.

What Typically Goes Wrong

Treating every VTS message as a binding order or, conversely, reducing every instruction to a mere recommendation.

Common Mistakes Mistake Library

Mistake	Consequence	How to Avoid It
Treating every VTS message as a binding order or, conversely, reducing every instruction to a mere recommendation.	Incorrect operational decision or regulatory status	Use the primary reference and ship-specific procedure

What the PSCO Checks

Knowledge of local procedures, listening watch, reports, message distinction, compliance or documented reason for deviation.

Operational Tips

Read back critical instructions.
Use clear and concise phraseology.
Do not confuse ultimate responsibility with a general option to ignore VTS.

Preparation checklist

Local VTS requirements available
Message category recognised
Applicable instruction followed
Safety exception communicated
COLREG/lookout maintained
Record available

FAQ

Are VTS indications always recommendations?

No. A.1158(32) distinguishes advice/warnings from requirements and instructions.

May an instruction be disregarded?

Only for contradictory safety or marine-environment-protection reasons, communicated promptly.

Who retains final responsibility?

The Master retains ultimate responsibility for operation and safe navigation.

VTS Traffic Management

Operational Explanation

Regulatory Reference

Scope of Application

Procedure / How to Complete It

Practical Example

What Typically Goes Wrong

Common Mistakes Mistake Library

What the PSCO Checks

Operational Tips

Preparation checklist

FAQ

Related Topics