09.10.2014 Views

VTS Manual - Belfast Harbour

VTS Manual - Belfast Harbour

VTS Manual - Belfast Harbour

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Port of <strong>Belfast</strong><br />

<strong>VTS</strong> MANUAL<br />

Revision No.: 02<br />

Issue No.:<br />

a<br />

Issue Date: 18 th August 2008<br />

Ref.:<br />

A1000-BHC-02


Section: i Rev No. 02<br />

Title: Document Control Issue No. a<br />

Document Control<br />

Document Name/Reference:<br />

<strong>VTS</strong> <strong>Manual</strong> / Port of <strong>Belfast</strong> – Standard<br />

Operating Procedures For Port Control<br />

Revision Number: 02<br />

Issue Number:<br />

a<br />

Revision Date: 18 th August 2008<br />

Copy Holder (in red pen):<br />

Copy Number (in red pen):<br />

Signed (Document Controller):<br />

Document Distribution<br />

The Document Controller shall:<br />

<br />

<br />

<br />

<br />

Distribute copies of this document and future updates to all relevant persons.<br />

Allocate copy numbers in red pen.<br />

Maintain a distribution list of copy-holders and their number.<br />

Ensure that superseded or obsolete copies are removed from circulation and<br />

destroyed.<br />

The current list of copy-holders is presented below:<br />

Copy No. Copy Holder Role Organisation<br />

Electronically Intranet<br />

BHC<br />

Date: 18.08.2008<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: i Rev No. 02<br />

Title: Document Control Issue No. a<br />

<strong>VTS</strong> Review Control:<br />

Port Controller Date Read and understood<br />

Ashley Moore 08/2008<br />

Richard Bates 08/2008<br />

Neil Scott 08/2008<br />

Simon Ferran 08/2008<br />

Darren Byers 08/2008<br />

Bridget Beattie 08/2008<br />

Document Control recorded in Operations <strong>Manual</strong><br />

Date: 18.08.2008<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: ii Rev No. 02<br />

Title: Table of Contents Issue No. a<br />

TABLE OF CONTENTS<br />

1. SCOPE .......................................................................................................................... 1-1<br />

1.1 PURPOSE .......................................................................................................... 1-1<br />

1.2 AIMS .................................................................................................................. 1-1<br />

1.3 OBJECTIVES...................................................................................................... 1-1<br />

1.4 RESPONSIBILITIES OF PORT CONTROL OFFICERS (PCOS)............................ 1-1<br />

1.5 ABBREVIATIONS ................................................................................................ 1-2<br />

2. INTRODUCTION ......................................................................................................... 2-1<br />

2.1 BACKGROUND ................................................................................................... 2-1<br />

2.2 PILOTAGE ......................................................................................................... 2-2<br />

2.3 RECREATIONAL VESSEL ACTIVITY ................................................................... 2-3<br />

2.4 INFORMATION FOR RECREATIONAL USERS ....................................................... 2-3<br />

2.5 FISHING ACTIVITY ............................................................................................. 2-5<br />

2.6 ANCHORING ...................................................................................................... 2-5<br />

2.7 VHF GUARD ..................................................................................................... 2-5<br />

3. TRAFFIC MANAGEMENT ......................................................................................... 3-1<br />

3.1 GENERAL .......................................................................................................... 3-1<br />

3.2 PROVIDING TRAFFIC INFORMATION.................................................................. 3-9<br />

3.3 TRAFFIC ORGANISATION ................................................................................ 3-11<br />

3.4 DETENTION OF VESSELS BY MCA.................................................................. 3-21<br />

3.5 INTERNATIONAL VESSEL AND PORT SECURITY (ISPS) CODE ...................... 3-21<br />

3.6 PORT WASTE .................................................................................................. 3-21<br />

3.7 MANAGEMENT OF SHIPPING MOVEMENTS ..................................................... 3-22<br />

3.8 TRAFFIC MANAGEMENT - SPECIAL CIRCUMSTANCES & EMERGENCIES ....... 3-24<br />

4. COMMUNICATIONS PRINCIPLE ............................................................................ 4-1<br />

4.1 LANGUAGE ........................................................................................................ 4-1<br />

4.2 TIME .................................................................................................................. 4-1<br />

4.3 COMMUNICATIONS CONTROL ........................................................................... 4-1<br />

4.4 PRIORITY OF COMMUNICATIONS ...................................................................... 4-1<br />

4.5 ESTABLISHING COMMUNICATIONS .................................................................... 4-1<br />

4.6 PORT CONTROL VHF CHANNEL GUARD ......................................................... 4-2<br />

4.7 RATE OF SPEECH ............................................................................................. 4-3<br />

4.8 STANDARD PHRASEOLOGY ............................................................................... 4-3<br />

4.9 CALLING INTERVALS ......................................................................................... 4-3<br />

4.10 PORT CONTROL UNABLE TO RESPOND IMMEDIATELY ...................................... 4-3<br />

4.11 DOUBTFUL RECEPTION .................................................................................... 4-3<br />

4.12 VHF NON-CONFORMITIES ................................................................................ 4-3<br />

4.13 GENERAL CALL ................................................................................................. 4-4<br />

4.14 ENDING A CALL ................................................................................................. 4-4<br />

5. LOG KEEPING ............................................................................................................ 5-1<br />

5.1 PRINCIPLES ...................................................................................................... 5-1<br />

Date: 18.08.2008 Page: 1-1<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: ii Rev No. 02<br />

Title: Table of Contents Issue No. a<br />

5.2 CORRECTIONS .................................................................................................. 5-1<br />

5.3 CENTRE LOG IDENTIFICATION .......................................................................... 5-1<br />

5.4 CENTRE LOG ENTRIES ..................................................................................... 5-1<br />

5.5 VESSEL TRAFFIC ACTIVITIES ............................................................................. 5-2<br />

5.6 VESSEL ACTIVITY INFORMATION ....................................................................... 5-2<br />

5.7 INCIDENTS AND ACCIDENTS ............................................................................. 5-2<br />

5.8 OCCURRENCE REPORT .................................................................................... 5-2<br />

5.9 WEATHER CONDITIONS .................................................................................... 5-3<br />

5.10 RECORDING FACILITIES .................................................................................... 5-3<br />

5.11 EQUIPMENT OPERATION RECORD ................................................................... 5-4<br />

5.12 MANDATORY ENTRIES ...................................................................................... 5-4<br />

5.13 CENTRE LOG - ARCHIVING................................................................................ 5-5<br />

5.14 ELECTRONIC DISTRIBUTION SYSTEMS............................................................. 5-5<br />

5.15 AUDIO/VIDEO RECORDINGS .............................................................................. 5-5<br />

5.16 RELEASE OF LOG INFORMATION ....................................................................... 5-5<br />

5.17 DEALING WITH REQUESTS FOR INFORMATION FROM THE PUBLIC .................... 5-6<br />

5.18 PUBLIC RELATIONS .......................................................................................... 5-6<br />

5.19 ENQUIRIES FROM THE MEDIA ........................................................................... 5-6<br />

6. WATCH KEEPING RESPONSIBILITIES ................................................................ 6-1<br />

6.1 GENERAL .......................................................................................................... 6-1<br />

6.2 WATCH HANDOVER BRIEFING .......................................................................... 6-1<br />

6.3 ACCEPTING THE WATCH ................................................................................... 6-2<br />

6.4 DURING THE WATCH ......................................................................................... 6-2<br />

6.5 COMPLETION OF WATCH ................................................................................... 6-2<br />

6.6 EQUIPMENT CHECKS ........................................................................................ 6-2<br />

6.7 EQUIPMENT SHUTDOWNS ................................................................................ 6-3<br />

6.8 LEGAL RESPONSIBILITIES ................................................................................. 6-4<br />

6.9 QUALITY ASSURANCE....................................................................................... 6-4<br />

6.10 CERTIFICATION OF PERSONNEL ....................................................................... 6-4<br />

7. ANNEXES ..................................................................................................................... 7-1<br />

7.1 ANNEX I: <strong>VTS</strong> REPLAY ..................................................................................... 7-1<br />

7.2 ANNEX II: BURNING TO DISK ............................................................................ 7-3<br />

8. FORMS ......................................................................................................................... 8-1<br />

8.1 DAILY MOVEMENT SHEET ................................................................................ 8-1<br />

8.2 PORT CONTROL LOG........................................................................................ 8-2<br />

8.3 PORT CONTROL LOGSHEET ............................................................................. 8-3<br />

8.4 PORT CONTROL CHECKLIST ............................................................................ 8-5<br />

Date: 18.08.2008 Page: 1-2<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 1 Rev No. 02<br />

Title: Scope Issue No. a<br />

1. Scope<br />

1.1 Purpose<br />

This manual provides <strong>Belfast</strong> Port Control staff with guidance in the form of<br />

Standard Operating Procedures and must be administered in accordance with the<br />

Port of <strong>Belfast</strong> Safety Management System. Attention of staff is drawn in<br />

particular to: Section 2.5 “Traffic Monitoring” and Section 5 “Management of<br />

Navigation”.<br />

1.2 Aims<br />

The aims of <strong>Belfast</strong> Port Control are to provide a service for the marine<br />

community and the public at large to ensure:<br />

<br />

<br />

<br />

<br />

Safety of life<br />

Efficient movement of vessel traffic<br />

Protection of the environment<br />

Port Security<br />

1.3 Objectives<br />

<strong>Belfast</strong> Port Control will achieve the above stated aims by:<br />

<br />

<br />

<br />

<br />

Monitoring and co-coordinating vessel traffic movements<br />

Managing integrated marine information systems<br />

Screening vessel status<br />

Co-ordination of communications related to distress, urgency and safety<br />

The operational service level presently in place at the Port of <strong>Belfast</strong> is intended<br />

to be Information Service (INS) and Traffic Organisation Service (TOS) as defined<br />

in the United Kingdom Marine Guidance Notices (MGN) 238, 239 and 240<br />

published by the Maritime and Coastguard Agency (MCA).<br />

1.4 Responsibilities of Port Control Officers (PCOs)<br />

PCOs are responsible for the following key activities:<br />

Date: 18.08.2008 Page: 1-1<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 1 Rev No. 02<br />

Title: Scope Issue No. a<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

Ensure that <strong>Belfast</strong> Port Control is operated within port, national and<br />

international guidelines and legislation.<br />

Operate equipment installed for the detection, surveillance and tracking of<br />

and communication with Vessels within and approaching <strong>Belfast</strong> Lough.<br />

Maintain records and associated databases.<br />

Follow operating procedures for Port Control and for the implementation of<br />

contingency plans.<br />

Report any apparent non-compliance or infringement of laws and<br />

directions to the appropriate Authority.<br />

Maintain appropriate standards of communications on channels assigned<br />

for Port Control purposes.<br />

Act within vested and delegated authority.<br />

Develop productive working relationships with colleagues, allied agencies<br />

and stakeholders.<br />

Dispatch pilots, pilot boats and other personnel, vessels or vehicles in<br />

support of the port‟s operation, safety and security.<br />

Give directions as authorised and on behalf of the <strong>Harbour</strong> Master.<br />

Comply with the <strong>Belfast</strong> <strong>Harbour</strong> Health & Safety Policy and the Port<br />

Control Lone Worker System.<br />

Perform other related duties as directed by the <strong>Harbour</strong> Master.<br />

1.5 Abbreviations<br />

This section presents the abbreviations used throughout this document:<br />

AIS<br />

AOR<br />

BHC<br />

CCTV<br />

ETA<br />

ETD<br />

GT<br />

HM<br />

HSS<br />

Automatic Identification System<br />

Area of Responsibility<br />

<strong>Belfast</strong> <strong>Harbour</strong> Commissioners<br />

Close Circuit Television<br />

Estimated Time of Arrival<br />

Estimated Time of Departure<br />

Gross Tonnage<br />

<strong>Harbour</strong> Master<br />

High Speed Service<br />

Date: 18.08.2008 Page: 1-2<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 1 Rev No. 02<br />

Title: Scope Issue No. a<br />

INS Information Service<br />

IOM Isle of Man<br />

IRIMS Incident Reporting Information Management System<br />

ISPS International Ship and Port Facility Security Code<br />

LOA Length Overall<br />

LNG Liquefied Natural gas<br />

LPG Liquefied Propane Gas<br />

MCA Maritime & Coastguard Agency<br />

MGN Marine Guidance Note<br />

NAS Navigation Assistance Service<br />

OPRC Oil Pollution Preparedness Response and Co-operation Convention<br />

PCO Port Control Officer<br />

QA Quality Assurance<br />

SAR Search & Rescue<br />

SITREPS Situation Reports<br />

SMCP Standard Marine Communication Phrases<br />

SOP Standard Operating Procedures<br />

SOSREP Secretary of States Representative<br />

TOS Traffic Organisation Service<br />

UTC Coordinated Universal Time<br />

VHF Very High Frequency<br />

VTMIS Vessel Traffic Management Information System<br />

VT3 Victoria Terminal 3<br />

<strong>VTS</strong> Vessel Traffic Service<br />

Date: 18.08.2008 Page: 1-3<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 2 Rev No. 02<br />

Title: Introduction Issue No. a<br />

2. Introduction<br />

2.1 Background<br />

The Board of <strong>Harbour</strong> Commissioners of the Port of <strong>Belfast</strong> implemented a Port<br />

Control System in 1994. The Operations Centre is located at the Port Operations<br />

Building.<br />

Radar scanners are located at Black Head and Kinnegar, which together provide<br />

coverage of the navigable areas, docks and anchorages within <strong>Belfast</strong> <strong>Harbour</strong>‟s<br />

Area of Responsibility (<strong>Belfast</strong> AOR).<br />

There are closed circuit television (CCTV) cameras located at:<br />

<br />

<br />

<br />

Victoria Channel / River Lagan<br />

Victoria Channel (Turning Circle to Barnetts Dock)<br />

Musgrave Channel<br />

The <strong>Belfast</strong> AOR includes all waters within the <strong>Belfast</strong> Dock and extends to a line<br />

drawn between Grey Point and Carrickfergus Castle. A channel, dredged to 9.1<br />

metres extends from the Fairway Buoy to the entrance of <strong>Belfast</strong> Docks.<br />

Environmentally sensitive areas include:<br />

<br />

<br />

<br />

<br />

<br />

<br />

<strong>Belfast</strong> Lough Ramsar (Wetlands)<br />

<strong>Belfast</strong> Lough Special Protected Area<br />

Island Magee Area of Special Scientific Interest<br />

Blue Flag Beaches and Environmental Agency Bathing waters<br />

Earth Science Conservation Review Sites<br />

Country Park<br />

Date: 18.08.2008 Page: 2-1<br />

Doc: MSMS-<strong>VTS</strong> <strong>Manual</strong> 1.11.doc


Section: 2 Rev No. 02<br />

Title: Introduction Issue No. a<br />

2.2 Pilotage<br />

Compulsory pilotage will apply to all Vessels navigating inside the port limits, i.e.<br />

inside a line joining Grey Point and Carrickfergus Castle, subject to the following<br />

exemptions:<br />

a. Vessels less than 75m in overall length<br />

b. Vessels over 75m and above, but under 100m in overall length navigating<br />

in the outer harbour<br />

c. HM Vessels and foreign war ships;<br />

d. General Lighthouse Authority tenders;<br />

e. Vessels that are moving from one berth to another within a dock or within<br />

the same channel<br />

f. Vessels navigating to or from Carrickfergus <strong>Harbour</strong>.<br />

g. These exemptions will not apply to:<br />

<br />

<br />

<br />

<br />

<br />

Vessels with a Passenger Certificate.<br />

Vessels carrying dangerous goods in bulk, including bitumen and<br />

vegetable oil.<br />

Vessels in ballast that are not gas free<br />

Vessels not fitted with a working radar installation when due to fog,<br />

mist falling snow or heavy rainstorm, or any other similar causes,<br />

visibility is less than 2.5 cables<br />

Vessels or their tows if any having one of the following defects:<br />

­ Are unseaworthy in any respect;<br />

­ Have defects to main engine, steering gear, or auxiliary<br />

machinery which may affect the manoeuvring of the Vessel;<br />

­ Have inoperable capstan, windlass, mooring winches or<br />

anchors that are not cleared or ready for use;<br />

­ Have a list of over 5 degrees or are excessively out of trim;<br />

­ Have any hull or machinery damage which may affect the<br />

safety of the Vessel or the containment or safety of the<br />

cargo or bunkers.<br />

Date: 18.08.2008 Page: 2-2<br />

Doc: MSMS-<strong>VTS</strong> <strong>Manual</strong> 1.11.doc


Section: 2 Rev No. 02<br />

Title: Introduction Issue No. a<br />

The <strong>Harbour</strong> Master may temporarily suspend any of these directions from time<br />

to time, without notice, as in his opinion, may be necessary.<br />

2.3 Recreational Vessel Activity<br />

There are eight (8) yacht clubs operating within the Lough.<br />

A full range of recreational activity, including races, takes place within the <strong>Belfast</strong><br />

AOR. Port Control Officers should monitor recreational activity for potential<br />

conflicts with other port users.<br />

2.4 Information for recreational users<br />

All vessel movements within <strong>Belfast</strong> <strong>Harbour</strong> Limits are under the control of the<br />

<strong>Harbour</strong> Master.<br />

All recreational craft entering <strong>Belfast</strong> <strong>Harbour</strong> are required to contact <strong>Belfast</strong><br />

<strong>Harbour</strong> Radio on VHF Channel 12 prior to entering the Victoria Channel or<br />

departing from the Laganside Pontoon.<br />

Vessels transiting <strong>Belfast</strong> <strong>Harbour</strong> from Lagan River are required to contact<br />

<strong>Belfast</strong> Port Control on VHF Channel 12 before passing the Lagan Weir.<br />

All vessels operating within <strong>Belfast</strong> <strong>Harbour</strong> Limits are required to maintain a<br />

listening watch on VHF Channel 12. If it is necessary to change to another VHF<br />

Channel, for example to call <strong>Belfast</strong> Coastguard, the vessel should return to<br />

Channel 12 as soon the communication ends.<br />

There are a limited number of berths for recreational users within <strong>Belfast</strong> <strong>Harbour</strong>.<br />

Recreational craft wishing to use the pontoons are required to seek permission<br />

prior to entering <strong>Belfast</strong> <strong>Harbour</strong>. Transits to and from the recreational berths are<br />

not permitted in poor visibility or at night. All recreational crafts transits will be<br />

considered as others commercial transits.<br />

Navigation within the channel is only permitted under power.<br />

Date: 18.08.2008 Page: 2-3<br />

Doc: MSMS-<strong>VTS</strong> <strong>Manual</strong> 1.11.doc


Section: 2 Rev No. 02<br />

Title: Introduction Issue No. a<br />

Vessels without VHF are not permitted to operate within the inner port, or the<br />

main channel, at any time.<br />

Recreational craft must notify <strong>Belfast</strong> <strong>Harbour</strong> Radio by radio or by telephone, of<br />

any incident, close-quarters situation or accident observed or experienced within<br />

the harbour and any defective aid to navigation.<br />

Any Clubs or Organisations wishing to organise an event within <strong>Belfast</strong> <strong>Harbour</strong><br />

Limits should notify to the <strong>Harbour</strong> Master, in writing, as soon as practicable no<br />

later that one month prior to the event.<br />

Recreational users of the harbour are advised to keep well clear of the main<br />

channels whenever possible.<br />

When main channels have to be crossed, this should be done as nearly as<br />

practicable at right angles only after contacting <strong>Belfast</strong> <strong>Harbour</strong> Radio on VHF<br />

Channel 12 prior to crossing the channel.<br />

Recreational users of the port area should remind themselves of and observe, the<br />

Collision Regulations, <strong>Belfast</strong> <strong>Harbour</strong> Byelaws and Local Notices to Mariners.<br />

Notices to Mariners are available on the <strong>Belfast</strong> <strong>Harbour</strong> website:<br />

<br />

http://www.belfast-harbour.co.uk/marine-pilotage.htm<br />

Date: 18.08.2008 Page: 2-4<br />

Doc: MSMS-<strong>VTS</strong> <strong>Manual</strong> 1.11.doc


Section: 2 Rev No. 02<br />

Title: Introduction Issue No. a<br />

2.5 Fishing Activity<br />

Mussel farming activities take place outside the navigation channel.<br />

Fishing vessels are not permitted to cross the navigation channel without<br />

permission of Port Control. When permission is given, the vessel should cross the<br />

channel at right angles to it.<br />

2.6 Anchoring<br />

Vessels are NOT to anchor within the Port Limits (i.e., West of a line between<br />

Grey Point and Carrickfergus Castle). PCOs will not advice (i.e., recommend)<br />

vessels with anchorage positions.<br />

2.7 VHF Guard<br />

Vessels within <strong>Belfast</strong> Lough are required to maintain a continuous listening<br />

watch on VHF Channel 12 while in transit, and both Channel 12 and 16 when at<br />

anchor.<br />

Date: 18.08.2008 Page: 2-5<br />

Doc: MSMS-<strong>VTS</strong> <strong>Manual</strong> 1.11.doc


Section: 3 Rev No. 02<br />

Title: Traffic Management Issue No. a<br />

3. Traffic Management<br />

3.1 General<br />

3.1.1 Monitoring VHF, Radar and AIS<br />

VHF frequencies, Radar displays and AIS displays should be monitored on a<br />

continuous basis. If other related duties are seen to detract from this duty during<br />

periods of critical vessel activity, they must be prioritised and either delegated to<br />

others or postponed until after the critical activity is sufficiently ended.<br />

3.1.2 Positive Identification<br />

All vessels transiting in the <strong>Belfast</strong> <strong>Harbour</strong> Limits are required to participate<br />

in Port Control and comply with the local and national laws and directions.<br />

If a vessel fails to participate, continue to monitor its movements to determine its<br />

present or future impact on traffic patterns or the movements of other vessels. If it is<br />

affecting other traffic, attempt to make radio contact, determine the master‟s or<br />

operator‟s intentions and provide such information, advice, warning or instruction as<br />

is appropriate to avoid a dangerous situation. If it is not possible to make radio<br />

contact with a non-participating vessel and if its conduct is posing a risk to vessel<br />

traffic or to the general safety and security of the port, use all available resources to<br />

enforce compliance. Report any apparent non-compliance or infringement of laws<br />

and directions to the appropriate Authority.<br />

A vessel shall be identified by as many of the following methods as is practicable:<br />

<br />

<br />

<br />

<br />

Comparing radar derived track and speed information (target) with information<br />

about the vessel;<br />

By AIS or VHF radio;<br />

Information from database on scheduled movements within a port or<br />

anchorage;<br />

A report from another vessel of visual sighting and identification;<br />

Date: 18.08.2008 Page: 3-1<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 3 Rev No. 02<br />

Title: Traffic Management Issue No. a<br />

<br />

<br />

Confirmation by CCTV if available; and<br />

Visual confirmation if feasible<br />

3.1.3 Loss of Identification or Mis-identification<br />

Identification shall be considered lost or incorrect when an observed target acts in a<br />

manner inconsistent with other information received from the vessel in question. The<br />

vessel shall then be re-identified.<br />

When assessing the possibility of a lost radar target, take into account the present<br />

weather conditions, known radar blind sectors and the overall performance of the<br />

radar.<br />

3.1.4 Risk Assessment<br />

To determine if risk of collision, grounding or striking exists the following should be<br />

considered:<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

Spatial separation of vessels<br />

Vessel domain<br />

The geographical constraints of the waterway<br />

Manoeuvring characteristics of the vessels involved<br />

Dangerous goods on board (if any)<br />

Weather constraints<br />

<strong>Harbour</strong> bye-laws<br />

3.1.5 Relevant Traffic<br />

In determining relevant traffic in a particular area, assess:<br />

<br />

<br />

<br />

<br />

Possibility of domain intrusion<br />

Clarity of vessel‟s intentions<br />

A change in a previously reported situation<br />

Indication of any situation in the waterway that could cause a „knock-on‟ effect<br />

Date: 18.08.2008 Page: 3-2<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 3 Rev No. 02<br />

Title: Traffic Management Issue No. a<br />

Note: There may also be circumstances, depending on context, where the vessel is<br />

deemed relevant traffic in spite of a negative assessment of the foregoing.<br />

3.1.6 Sailing Plan & Passage Plan<br />

Sailing Plan to have the following information:<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

Vessels name<br />

Masters Name<br />

Position<br />

ETA @ Fairway Buoy (or ETD)<br />

Destination (Berth or Next Port)<br />

Intended Route (Turning Location etc)<br />

Pilotage requirement<br />

Tugs required<br />

Any defects / deficiencies<br />

Dangerous goods declaration<br />

Passage Plan to have the following:<br />

<br />

<br />

Master / Pilot Exchange - See Master / Pilot Exchange Form<br />

If no Pilot required – Master to confirm that Passage Plan has been prepared.<br />

3.1.7 Reporting Points<br />

Vessels Inward should report as follows:<br />

a. Not less than 2 hours before arrival at the Fairway buoy (54°41‟.71N<br />

5°46‟.23W)<br />

b. 15 minutes prior passing the Fairway buoy for Traffic Clearance<br />

c. On passing the Fairway buoy<br />

d. On passing Light Beacon No 12<br />

Date: 18.08.2008 Page: 3-3<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 3 Rev No. 02<br />

Title: Traffic Management Issue No. a<br />

e. On anchoring or berthing<br />

Vessels Outward or Shifting Berth should report as follows:<br />

a. ETD should be sent at least 2 hours in advance if a Pilot is required or 15<br />

minutes in advance if a Pilot is not required.<br />

b. When ready to depart requesting Traffic Clearance<br />

c. On departing the berth<br />

d. On passing Buoy No 12<br />

e. On passing the Fairway buoy<br />

Note: this section excludes pilot boats, work boats and tugs; these vessels report<br />

only when departing the berth.<br />

3.1.8 Vessel Transit Reports<br />

The following reports should be Vessel-initiated; however, prompt the vessel with a<br />

reminder if necessary.<br />

3.1.8.1 Pre Arrival Information - Prior Entry to <strong>Belfast</strong> AOR<br />

3.1.8.1.1 Vessels requiring Pilot<br />

Vessels requiring a pilot are required to send ETA off the Fairway Lt Buoy (54°<br />

41‟.71N 005° 46‟.23W) 6 hours and 2 hours in advance stating:<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

Vessel‟s name<br />

Maximum draught<br />

Last port<br />

Master‟s name<br />

Any defects / deficiencies<br />

Dangerous goods declaration<br />

If less than 100m LOA and not carrying hazardous cargo in bulk pilot boarding<br />

position required (Fairway buoy or Beacon No 12)<br />

Date: 18.08.2008 Page: 3-4<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 3 Rev No. 02<br />

Title: Traffic Management Issue No. a<br />

Vessels not requiring Pilot<br />

Vessels not requiring a pilot should contact <strong>Belfast</strong> <strong>Harbour</strong> Radio 2 hours prior to<br />

arrival off the Fairway Light Buoy stating:<br />

<br />

<br />

<br />

<br />

<br />

<br />

Vessel‟s name<br />

Maximum draught<br />

Last port<br />

Master‟s name<br />

Any defects/deficiencies<br />

Dangerous goods declaration<br />

3.1.8.2 Information Exchange - Vessels Inward<br />

1. When vessel reports (makes its first VHF call) 2 hours prior to entering the<br />

<strong>Belfast</strong> AOR:<br />

<br />

Obtain the following information:<br />

­ Name<br />

­ Position<br />

­ Maximum draught<br />

­ Master‟s Name<br />

­ ETA Fairway Buoy<br />

­ Destination (Berth or Anchorage)<br />

­ Confirm ETA Pilot Station if vessel is taking a pilot (Inner or Outer<br />

Pilot Station)<br />

­ Any defects/deficiencies<br />

­ Dangerous goods declaration<br />

<br />

Inform the vessel to re-establish contact 15 minutes prior to arrival at the<br />

Fairway Buoy. In some circumstances, it will be advisable to have the<br />

vessel contact <strong>Belfast</strong> Port Control 1 hour prior arrival. These<br />

Date: 18.08.2008 Page: 3-5<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 3 Rev No. 02<br />

Title: Traffic Management Issue No. a<br />

circumstances will include no berth available or anticipated changes or<br />

updates to information exchange.<br />

<br />

Update VTMIS<br />

2. When a vessel reports 15 minutes prior to entering the <strong>Belfast</strong> AOR:<br />

<br />

<br />

<br />

<br />

Issue or withhold a traffic clearance<br />

Provide traffic/waterway information/ Update information with allied<br />

services<br />

Inform the duty pilot and pilot boat as required<br />

Update VTMIS<br />

3. When a vessel enters the <strong>Belfast</strong> AOR:<br />

<br />

Update VTMIS<br />

4. When a vessel passes the Fairway Buoy or when the Pilot boards:<br />

<br />

<br />

Provide traffic/waterway information<br />

Update VTMIS<br />

5. When a vessel passes the Beacon 12:<br />

<br />

<br />

Provide traffic/waterway information<br />

Update VTMIS<br />

6. When a vessel arrives at a berth:<br />

<br />

<br />

Obtain time all fast<br />

Update VTMIS<br />

Date: 18.08.2008 Page: 3-6<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 3 Rev No. 02<br />

Title: Traffic Management Issue No. a<br />

3.1.8.3 Berth Occupied<br />

Any vessel entering the <strong>Belfast</strong> AOR, scheduled to a berth that is occupied must:<br />

<br />

<br />

<br />

If the situation is short-term, adjust ETA at pilot station if possible, or<br />

Proceed to a safe anchorage, or<br />

Have a suitable lay-by berth available for immediate use.<br />

Lay-by berths are considered to be any available berth where the vessel can be<br />

securely moored and remain afloat. Permission to use a lay-by berth must be<br />

granted by the duty <strong>Harbour</strong> Master.<br />

Vessels passing F/W with berth occupied is on authority from HM in especial<br />

circumstances except regular calling ferries to the same berth.<br />

3.1.8.4 Vessel inward for Victoria Terminal (VT) 3<br />

If a vessel is bound for VT3 terminal confirm with Coastal that gantry cranes are<br />

clear of the berthing area prior to the vessel passing Buoy No.12; if not, inform<br />

vessel.<br />

3.1.8.5 Information Exchange - Vessels Outward<br />

3.1.8.5.1 Prior departure<br />

1. When a vessel reports ETD (at least 2 hours in advance if a Pilot is required<br />

or 15 minutes in advance if a Pilot is not required) obtain the following<br />

information:<br />

<br />

<br />

<br />

Name<br />

Position<br />

ETD<br />

Date: 18.08.2008 Page: 3-7<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 3 Rev No. 02<br />

Title: Traffic Management Issue No. a<br />

<br />

<br />

<br />

<br />

<br />

Maximum draught<br />

Master‟s Name<br />

Destination<br />

Any defects/deficiencies<br />

Dangerous goods declaration<br />

2. Inform vessel to ‘call again when ready to depart’.<br />

3. Provide traffic/waterway information.<br />

4. Update VTMIS.<br />

3.1.8.5.2 When ready to depart<br />

1. Issue or withhold traffic clearance for the vessel to depart the berth.<br />

2. Provide traffic/waterway information.<br />

3. Inform vessel to call when underway.<br />

3.1.8.5.3 On departure<br />

When a vessel reports completion of departure manoeuvre:<br />

1. Record time of departure<br />

2. Provide traffic/waterway information<br />

3. Update VTMIS<br />

3.1.8.5.4 Additional reports<br />

When any of the following reports are received, record and distribute the information<br />

as required.<br />

Any incident or accident such as but not limited to the following:<br />

Date: 18.08.2008 Page: 3-8<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 3 Rev No. 02<br />

Title: Traffic Management Issue No. a<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

Fire aboard a vessel;<br />

The involvement of a vessel in a collision, grounding or striking;<br />

Any defect to a vessel‟s hull, machinery, steering system, radars, compasses,<br />

communications, anchors and cables;<br />

Any discharge or threat of discharge of a pollutant;<br />

Another vessel in apparent difficulty;<br />

An obstruction to navigation;<br />

An aid to navigation that is not functioning correctly or is off position;<br />

The presence of any pollutant in the water;<br />

The presence of any vessel that may impede the movement of other Vessels;<br />

Weather conditions that may be detrimental to safe navigation;<br />

Dangerous occurrences.<br />

3.2 Providing Traffic Information<br />

3.2.1 Results Oriented<br />

All Port Control communications should be conducted to ensure that intentions are<br />

clear and avoid terminology that could be interpreted as conning instructions.<br />

3.2.2 Timing<br />

Provide relevant vessel traffic information:<br />

<br />

<br />

<br />

<br />

When requested by any vessel;<br />

As soon as practicable after a vessel, including a recreational or fishing<br />

vessel, has acknowledged its Traffic Clearance whether arriving or departing;<br />

When a vessel has reported at a Reporting Point;<br />

At any time that a potential traffic conflict has been identified.<br />

3.2.3 Content<br />

Communications concerning relevant traffic shall contain:<br />

<br />

Name and type of vessel<br />

Date: 18.08.2008 Page: 3-9<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 3 Rev No. 02<br />

Title: Traffic Management Issue No. a<br />

<br />

<br />

<br />

Information concerning its position, track and intentions<br />

Waterway and terminal data<br />

Any information that could affect the operation of the vessel<br />

Alert vessels in transit or at anchor of all relevant operations or interactions such as<br />

but not limited to:<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

The position and intention of vessels manoeuvring to embark or disembark a<br />

pilot;<br />

Vessels meeting at critical points;<br />

Vessels carrying dangerous goods;<br />

LPG/LNG vessels at appropriate berths;<br />

Diving and bunkering operations;<br />

Men working on the waterline;<br />

Positions of specified vessels underway;<br />

Positions of all deep draught vessels underway;<br />

Positions of vessels constrained by draft; and<br />

Any other operations that may have impact on vessels in the <strong>Belfast</strong> AOR.<br />

Alert vessels intending to depart of any of the foregoing information items which may<br />

impact the Master‟s intention to depart.<br />

3.2.4 Format<br />

Provide relevant information by identifying vessels by their complete name or callsign.<br />

When it may be of assistance, include the type or class of vessel(s) that will be<br />

encountered, together with their direction of movement, position, relevant data and<br />

intentions. Use the message marker “Traffic Information” to precede the message.<br />

Example<br />

Marinex<br />

This is<br />

Date: 18.08.2008 Page: 3-10<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 3 Rev No. 02<br />

Title: Traffic Management Issue No. a<br />

<strong>Belfast</strong> <strong>Harbour</strong> Radio<br />

Traffic Information<br />

Vessel Inward - Tanker Enerchem<br />

Approaching pilot station to embark pilot<br />

Vessel Outward - Ferry Seaprince<br />

Passed buoy 10 in Victoria Channel<br />

Over<br />

3.2.5 Sequence<br />

Provide relevant information to a vessel in order of relative importance. Often<br />

crossing or contra-flow traffic is of most impact and should be given priority;<br />

however, there are instances where an overtaking situation will dictate that this<br />

information be given first.<br />

3.3 Traffic Organisation<br />

3.3.1 Results Oriented<br />

All Port Control communications should be conducted to ensure that intentions are<br />

clear and avoid terminology that could be interpreted as conning instructions.<br />

3.3.2 Traffic Clearance<br />

A Traffic Clearance is an authorisation to proceed under specified conditions. This<br />

shall be issued if considered safe after an analysis of the Port Control Sailing Plan<br />

and the known traffic and waterway conditions.<br />

3.3.2.1 Checks before issuing a Traffic Clearance<br />

<br />

<br />

<br />

Assess the information for completeness and accuracy - if necessary request<br />

additional information.<br />

For vessels inward - ensure that a berth is available or is being made ready.<br />

Analyse known and expected relevant traffic to determine if the intended<br />

movement is safe and that Vessel domains of all relevant traffic have been<br />

Date: 18.08.2008 Page: 3-11<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 3 Rev No. 02<br />

Title: Traffic Management Issue No. a<br />

adequately protected according to the circumstances of the intended<br />

manoeuvre and operation.<br />

3.3.2.2 Lead time for Traffic Clearance<br />

Under normal conditions issue a traffic clearance to a vessel when it is ready in all<br />

respects to depart an anchorage or berth; or, 15 minutes prior to entering the <strong>Belfast</strong><br />

AOR or departs a berth or anchorage within the <strong>Belfast</strong> AOR.<br />

Note: Under some conditions it may be necessary to extend or shorten the lead time<br />

for Traffic Clearance. Guidance from the <strong>Harbour</strong> Master should be sought if<br />

circumstance warrants and permits.<br />

When a vessel calls Port Control to inform that it is ready to depart, PCO to<br />

acknowledge and give Traffic Clearance if appropriate.<br />

3.3.2.3 Traffic Clearance Format<br />

3.3.2.3.1 Vessel Outward or Shifting<br />

The following format is used when issuing a Traffic Clearance for a vessel<br />

proceeding from a berth or anchorage<br />

(Name of Vessel)<br />

This is <strong>Belfast</strong> <strong>Harbour</strong> Radio<br />

Traffic Clearance<br />

(Name of Vessel) has permission to (manoeuvre requested)<br />

At (time that the manoeuvre is to begin)<br />

Proceed when safe to do so<br />

Call when underway<br />

Over<br />

Example<br />

Departex<br />

Date: 18.08.2008 Page: 3-12<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 3 Rev No. 02<br />

Title: Traffic Management Issue No. a<br />

This is <strong>Belfast</strong> <strong>Harbour</strong> Radio<br />

Traffic Clearance<br />

Departex has permission to depart York Dock at 1445 for sea<br />

Proceed when safe to do so<br />

Call when underway<br />

Over<br />

Note: this section excludes pilot boats, work boats and tugs; these vessels are<br />

considered to have traffic clearance in all instances unless specifically instructed to<br />

the contrary and will report only when departing the berth.<br />

3.3.2.3.2 Vessel Inward<br />

3.3.2.3.2.1 Pilot on board OR Pilot not required<br />

The following format is used when issuing a Traffic Clearance for a vessel<br />

proceeding from outside the <strong>Belfast</strong> AOR to a berth:<br />

(Name of Vessel)<br />

This is <strong>Belfast</strong> <strong>Harbour</strong> Radio<br />

Traffic Clearance<br />

(Name of Vessel) has permission to proceed to (berth)<br />

At (time that the manoeuvre is to begin)<br />

Over<br />

Example<br />

Arrivex<br />

This is <strong>Belfast</strong> <strong>Harbour</strong> Radio<br />

Traffic Clearance<br />

Arrivex has permission to proceed to VT1, port side to<br />

At (time permission is given)<br />

Over<br />

Date: 18.08.2008 Page: 3-13<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 3 Rev No. 02<br />

Title: Traffic Management Issue No. a<br />

3.3.2.3.2.2 Pilot required but not yet on board<br />

The following format is used when issuing a Traffic Clearance for a vessel<br />

proceeding from outside the <strong>Belfast</strong> AOR toward a berth, which requires but has not<br />

yet embarked a pilot.<br />

(Name of Vessel)<br />

This is <strong>Belfast</strong> <strong>Harbour</strong> Radio<br />

Traffic Clearance<br />

(Name of Vessel) has permission to proceed to Pilot boarding position<br />

At (time that the manoeuvre is to begin)<br />

Have Pilot call when on bridge<br />

Over<br />

Example<br />

Arrivex 2<br />

This is <strong>Belfast</strong> <strong>Harbour</strong> Radio<br />

Traffic Clearance<br />

Arrivex 2 has permission to proceed to Pilot boarding position<br />

At (time permission is given)<br />

Have Pilot call when on bridge<br />

Over<br />

3.3.2.4 Delaying or withholding a Traffic Clearance<br />

If analysis determines that a requested manoeuvre may not be carried out in safety,<br />

or if it falls within an activity prohibited by the <strong>Harbour</strong> Master, Traffic Clearance<br />

should be delayed; or in some cases, withheld until conditions are sufficiently<br />

changed so as to permit the manoeuvre.<br />

If the vessel is already in transit when a deficiency or other condition that would<br />

result in a delaying or withholding a Traffic Clearance occurs, the vessel should be<br />

Date: 18.08.2008 Page: 3-14<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 3 Rev No. 02<br />

Title: Traffic Management Issue No. a<br />

given an amended Traffic Clearance or advised not to proceed beyond a specified<br />

location and to standby for further information.<br />

Delayed or withheld Traffic Clearance is normally associated with, but not limited to<br />

the following circumstances:<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

non-availability of a required berth<br />

pollution or reasonable apprehension of pollution<br />

an obstruction to traffic<br />

hazard to life<br />

hazard to navigation<br />

the proximity of vessel navigating in an unsafe manner<br />

defects or deficiencies to the vessel, its equipment or machinery<br />

deficiencies in charts or publications that are required by regulation<br />

congested waterway that constitutes unacceptable risk<br />

3.3.2.4.1 Delayed / Withheld Traffic Clearance format<br />

Vessel Outward<br />

(Name of Vessel)<br />

This is <strong>Belfast</strong> <strong>Harbour</strong> Radio<br />

Remain Alongside<br />

(Reason)<br />

Standby this channel / or, Call in :xx minutes<br />

Over<br />

Example<br />

Departex<br />

This is <strong>Belfast</strong> <strong>Harbour</strong> Radio<br />

Remain Alongside<br />

A deep draft floating crane is restricting use of Victoria Channel<br />

Call in 15 minutes<br />

Date: 18.08.2008 Page: 3-15<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 3 Rev No. 02<br />

Title: Traffic Management Issue No. a<br />

Over<br />

Vessel Inward<br />

(Name of Vessel)<br />

This is <strong>Belfast</strong> <strong>Harbour</strong> Radio<br />

Do not proceed past Pilot Station<br />

(Reason)<br />

Standby this channel / or, Call in :xx minutes<br />

Over<br />

Example<br />

Departex<br />

This is <strong>Belfast</strong> <strong>Harbour</strong> Radio<br />

Do not proceed past Pilot Station<br />

Your Pilot/Berth is unavailable until XX:00 Hours<br />

Over<br />

3.3.3 Vessel response<br />

3.3.3.1 Compliance<br />

If a vessel complies with the delay, Traffic Clearance shall be issued as soon as<br />

circumstances permit.<br />

3.3.3.2 Non-compliance<br />

If a vessel does not comply with the delay, inform or warn other traffic according to<br />

the risk posed by the situation. Provide all Vessels with a full INS and TOS response.<br />

Monitor the situation and file a full non-compliance report to the <strong>Harbour</strong> Master as<br />

soon as time permits.<br />

3.3.3.3 Reassessment requested by the vessel<br />

When reassessment indicates the situation is safe, issue a Traffic Clearance.<br />

Date: 18.08.2008 Page: 3-16<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 3 Rev No. 02<br />

Title: Traffic Management Issue No. a<br />

If reassessment shows that the intended movement is still unsafe, issue an<br />

instruction to remain alongside.<br />

3.3.4 Advice (Recommendation)<br />

Advice may be given as authorized by the <strong>Harbour</strong> Master. This is normally done<br />

when it is evident that a vessel should take action in response to a circumstance<br />

identified by the PCO.<br />

Advice may relate to:<br />

<br />

<br />

<br />

General marine information such as berth availability;<br />

Traffic information, such as the general intention of other traffic; or,<br />

Navigation information, such as designated preferred channels as indicated<br />

by the <strong>Harbour</strong> Master.<br />

Advice shall be preceded by the message marker “ADVICE”, and given in a clear<br />

concise manner so that the Mariner is in no doubt as to what action is<br />

recommended.<br />

Example<br />

Seatrax<br />

This is <strong>Belfast</strong> Port Control<br />

INFORMATION - your berth is not available until 1600 hours<br />

ADVICE - Proceed to anchorage and contact your Agent<br />

Over<br />

3.3.5 Instructions<br />

Instructions may only be given on the authority of the <strong>Harbour</strong> Master.<br />

When an Instruction is issued, ensure that the language used is clear, concise and<br />

conveys the intended meaning.<br />

Date: 18.08.2008 Page: 3-17<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 3 Rev No. 02<br />

Title: Traffic Management Issue No. a<br />

An instruction shall be preceded by the message marker “INSTRUCTION”, and<br />

given in a clear concise manner so that the Mariner is in no doubt as to what action<br />

is necessary.<br />

Never issue an instruction that implies that you are taking the control of the vessel.<br />

Details concerning the issue of any instruction shall be entered in the Port<br />

Operations Logbook.<br />

Example<br />

Yacht Blue Lagoon<br />

This is <strong>Belfast</strong> Port Control<br />

INFORMATION - Ferry Marine Greyhound is turning in mid-channel<br />

INSTRUCTION - Remain outside the Victoria Channel<br />

Over<br />

3.3.5.1 Non-compliance with an Instruction<br />

Organise other traffic taking into account the non-compliance with an Instruction and<br />

its effect on other traffic. Enter details concerning the non-compliance in an Incident<br />

Reporting Information Management System (IRIMS) report.<br />

3.3.6 <strong>Harbour</strong> Master‟s Directions<br />

The <strong>Harbour</strong> Master may give General and Special Directions through the Port<br />

Control Officer:<br />

1. For designating areas, routes or channels which vessels are to use or refrain<br />

from using;<br />

2. For securing that vessels move only at certain times or during certain periods;<br />

3. For prohibiting:<br />

a. entry into or movement in the port by vessels at times of poor visibility<br />

due to the weather or for any other reason; and,<br />

b. entry into the port by a vessel which for any reason would be, or is likely<br />

to become, a danger to other vessels;<br />

Date: 18.08.2008 Page: 3-18<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 3 Rev No. 02<br />

Title: Traffic Management Issue No. a<br />

4. Requiring the master of a vessel to give information relating to the vessel<br />

reasonably required by the <strong>Harbour</strong> Master.<br />

The <strong>Harbour</strong> Master will indicate at the time if this is a General or a Special<br />

Direction.<br />

3.3.6.1 Manner of giving <strong>Harbour</strong> Master’s Directions<br />

Ensure that:<br />

Any HM‟s direction is clear and unambiguous<br />

Any HM‟s direction is issued as in instruction and not as a request<br />

An acknowledgement is received<br />

There is no doubt that the HM direction has been understood.<br />

3.3.6.2 Master’s responsibility to be unaffected<br />

The giving of a general direction or a special direction shall not diminish or in any<br />

other way affect the responsibility of the master of the vessel to which the direction is<br />

given in relation to his vessel, persons on board, its cargo or any other person or<br />

property.<br />

A master can contravene berthing instructions, but as soon as it becomes evident<br />

that it is not safe, HM, stevedores and agents have to be informed.<br />

3.3.6.3 Failure to comply with Directions<br />

1. The master of a vessel who fails to comply with a General or Special direction<br />

shall be informed that a report will be filed with the <strong>Harbour</strong> Master.<br />

2. It shall be a defence to the Master of a vessel charged with an offence under<br />

subsection (1) of this section to prove that he had reasonable ground for<br />

supposing that compliance with the direction in question would be likely to<br />

imperil his vessel or that in the circumstances compliance was impracticable.<br />

Date: 18.08.2008 Page: 3-19<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 3 Rev No. 02<br />

Title: Traffic Management Issue No. a<br />

3.3.6.4 Non-compliance with Regulations and Bye-laws<br />

Inform the vessel by VHF of the observed infraction; if necessary request intentions<br />

and/or request compliance.<br />

If a vessel does not respond to a request to comply, an instruction may be issued if<br />

authorized by the <strong>Harbour</strong> Master.<br />

3.3.7 Reporting contraventions<br />

Complete an IRIMS Report.<br />

File a report with the <strong>Harbour</strong> Master concerning any contravention, violation,<br />

infringement or irregularity with respect to non-compliance with Regulations and Byelaws.<br />

When reporting contraventions of the <strong>Harbour</strong> Regulations or bye-laws, the following<br />

information shall be contained in the report.<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

Date and time<br />

Name and Section (#) of the regulation that has not been complied with<br />

Vessel name<br />

Call sign / MMSI number<br />

Nationality<br />

Destination<br />

Position at time of contravention<br />

VHF operational status<br />

Length<br />

GT<br />

Narrative<br />

Record events chronologically, detail actions taken to inform the vessel.<br />

Date: 18.08.2008 Page: 3-20<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 3 Rev No. 02<br />

Title: Traffic Management Issue No. a<br />

Sign, date the report, attach any relevant additional information and forward to the<br />

<strong>Harbour</strong> Master.<br />

3.3.8 AIS non-conformance<br />

AIS non-compliance should be reported to the MCA as a Notification of a Deficiency<br />

and recorded in the log. In assessing reportable non-compliance, the following AIS<br />

fields should be correctly transmitted as a minimum:<br />

<br />

<br />

<br />

Position<br />

Course Over Ground/Speed Over Ground<br />

Correct static data i.e. vessel name, MMSI number, IMO number, call sign,<br />

dimensions (based on correct transponder position).<br />

3.4 Detention of vessels by MCA<br />

The MCA may detain vessels that fail Port State Control inspections. Should the<br />

vessel in question request a Pilot before notification of release is received, notify the<br />

HM and MCA.<br />

3.5 International Vessel and Port Security (ISPS) Code<br />

Specific ISPS procedures are provided by the Port Security Officer. The International<br />

Vessel and Port Facility Security (ISPS) Code applies to the following types of<br />

Vessels engaged on international voyages:<br />

<br />

<br />

<br />

Passenger Vessels (including high speed passenger craft);<br />

Cargo Vessels (including high speed craft) of more than 500 GT; and<br />

Any berth that handles vessels on international voyages should be designated<br />

as an ISPS port facility.<br />

3.6 Port Waste<br />

Vessels must provide the <strong>Harbour</strong> Master with prior notification of their onboard<br />

waste and what they plan to discharge in port.<br />

Date: 18.08.2008 Page: 3-21<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 3 Rev No. 02<br />

Title: Traffic Management Issue No. a<br />

3.7 Management of Shipping Movements<br />

Passenger vessels will be deemed to be vessels operated with the following<br />

categories: Seacats, Stena Conventional, Stena HSS, Norfolkline, cruise<br />

liners, but not vessels carrying less than 12 passengers with no Passenger<br />

Certificate.<br />

<br />

<br />

All passenger vessels have priority on arrival or sailing under normal<br />

conditions.<br />

When two passenger vessels have priority then vessel on schedule or closest<br />

after schedule will have priority over the other passenger vessel under normal<br />

conditions. Priority will hold past scheduled time until next scheduled vessel<br />

is likely to be affected, then priority ceases and goes to second vessel.<br />

<br />

<br />

<br />

Conventional ferries can be overtaken within port limits by fast ferries.<br />

Fast Ferries passing each other within port limits will do so at a prudent<br />

speed, consistent with safety of vessel and passengers.<br />

Fast Ferries will not attempt to overtake other Fast Ferries unless agreement<br />

has been reached with the Fast Ferry to be overtaken and Port Control has<br />

been informed of the intended manoeuvre.<br />

<br />

<br />

All passenger vessels will agree passing or overtaking procedure with each<br />

other prior to execution of manoeuvre.<br />

All passenger vessels will communicate with Port Control when entering or<br />

leaving port limits and at No 12 beacon. On arrival they will indicate their<br />

expected swinging area when passing No 12 beacon. On departure they will<br />

give 20 minutes and 5 minutes notice of their intent to sail. All passenger<br />

vessels will keep constant listening watch on Channel 12 to receive shipping<br />

information relating to themselves or other vessels.<br />

<br />

<br />

<br />

All passenger vessels, when occupying an operational berth, will provide Port<br />

Control with means of communication to a responsible officer at all times.<br />

All passenger vessels may pass or overtake tankers in port waters with due<br />

regard to safety of navigation.<br />

A vessel not operating as a passenger ship can overtake a gas carrier.<br />

Date: 18.08.2008 Page: 3-22<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 3 Rev No. 02<br />

Title: Traffic Management Issue No. a<br />

<br />

<br />

<br />

Gas carriers will only be allowed to pass passenger vessels when<br />

circumstances indicate that unreasonable delay would result from any other<br />

planned movement.<br />

Priorities for passenger vessels will be maintained whenever practicable in<br />

poor weather but safety of navigation is paramount. In fog, port operations<br />

may apply a one way system for shipping movements. Passenger vessels<br />

will have priority in such a system. In strong winds passenger vessel at<br />

greatest risk will have priority over all other vessels.<br />

The <strong>Harbour</strong> Master may temporarily suspend or amend any of these<br />

directions from time to time, without notice, as, in his opinion, may be<br />

necessary.”<br />

3.7.1 Management of Shipping Movements in Herdman Channel and<br />

Musgrave Channel<br />

Vessels are not permitted to pass or overtake in Herdman or Musgrave Channels.<br />

3.7.2 Races, Regattas and Marine Events<br />

All initial requests to hold events should be directed to the <strong>Harbour</strong> Master.<br />

3.7.3 Tugs, mooring and line boats<br />

Vessel requests for tugs, mooring and line boats should be made direct by the<br />

vessel to the company concerned via their agent. When deemed appropriate by the<br />

<strong>Harbour</strong> Master, the PCO may order these resources on his behalf.<br />

Tugs to be provided as per Minimum Towage Requirements (Notice to Mariners no<br />

12 of 2.007).<br />

3.7.3.1 Tug Confirmation Procedure<br />

Vessel Inward requiring Tugs at Fairway Buoy - tugs to confirm their availability 1<br />

hour 30 minutes before vessel arrives at Fairway Buoy. PCO to contact tugs if they<br />

do not confirm by this time.<br />

Date: 18.08.2008 Page: 3-23<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 3 Rev No. 02<br />

Title: Traffic Management Issue No. a<br />

Vessel Inward requiring Tugs at No.12 - Tugs to confirm their availability 30<br />

minutes before vessel arrives at Fairway Buoy. PCO to contact tugs if they do not<br />

confirm by this time.<br />

Vessels requiring Tugs for Departure - Tugs to confirm their availability 30<br />

minutes before ETD. PCO to contact tugs if they do not confirm by this time.<br />

3.8 Traffic Management - Special Circumstances & Emergencies<br />

Note: ‘Special Circumstance’ in the context of this section will include but not be<br />

limited to: incidents, accidents, emergencies, special operations, diving operations,<br />

military or security exercises, reduced visibility, hazards or obstructions to navigation<br />

or any other activity or condition that is of a non-routine nature or requires distinct<br />

procedures.<br />

With respect to any special circumstance:<br />

Determine complete details of the situation by obtaining information from as<br />

many sources as possible.<br />

Notify vessels of information that may impact safety.<br />

If necessary, issue a VHF broadcast.<br />

Inform designated authorities and offices.<br />

Log the details of the circumstances.<br />

Ensure that the proper reports are completed.<br />

3.8.1 Adverse Weather<br />

When visibility drops below 1 nautical mile activate the foghorns in the area of low<br />

visibility and record this action in the Port Control Log.<br />

If visibility falls or is expected to fall below 0.5 nautical mile contact the duty Deputy<br />

<strong>Harbour</strong> Master to obtain authorisation to implement a one-way traffic movement<br />

system within the entire channel. Record this action in the Port Control Log.<br />

Date: 18.08.2008 Page: 3-24<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 3 Rev No. 02<br />

Title: Traffic Management Issue No. a<br />

Implement the one-way system with a Securité Broadcast, inform affected vessels<br />

and organise traffic accordingly. Pilot boats and tugs are exempt from complying with<br />

one way system whilst in force.<br />

Example<br />

Securité x 3<br />

All Stations x 3<br />

This is<br />

<strong>Belfast</strong> <strong>Harbour</strong> Radio x 3<br />

Navigational Warning<br />

A one-way system is now in operation in <strong>Belfast</strong> <strong>Harbour</strong>.<br />

This is <strong>Belfast</strong> <strong>Harbour</strong> Radio<br />

Out.<br />

Cancel the one-way system with a Securité Broadcast as follows:<br />

Example<br />

Securité x 3<br />

All Stations x 3<br />

This is<br />

<strong>Belfast</strong> <strong>Harbour</strong> Radio x 3<br />

Navigation Information<br />

One-way traffic in <strong>Belfast</strong> <strong>Harbour</strong> is withdrawn<br />

This is <strong>Belfast</strong> <strong>Harbour</strong> Radio<br />

Out.<br />

Other adverse conditions are considered on a case-by-case basis and the<br />

appropriate measures are implemented based on the instruction of the <strong>Harbour</strong><br />

Master.<br />

3.8.2 Search and Rescue (SAR)<br />

The Maritime and Coastguard Agency (MCA) has responsibility for managing all<br />

SAR incidents and should be informed immediately when any situation concerning<br />

the potential safety of life in or around the water is known.<br />

Date: 18.08.2008 Page: 3-25<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 3 Rev No. 02<br />

Title: Traffic Management Issue No. a<br />

Ensure that good two-way information flow is maintained between Port Control and<br />

Coastguard.<br />

Establish and maintain communications with the casualty or casualties until<br />

otherwise instructed by MCA. [Note: It is normal for a casualty to remain on the<br />

calling frequency unless a change of frequency is negotiated by the MCA - if so it is<br />

likely to be on Channel 16 or 67]; however, consider the transfer of other vessels<br />

from the incident channel to an alternative channel.<br />

3.8.3 Vessel in apparent or declared distress<br />

Obtain immediately the vessel‟s name, position, persons on board and nature of<br />

distress.<br />

If feasible, delegate a staff member to inform MCA.<br />

Continue to collect information appropriate to provision of assistance.<br />

Advise other stakeholders such as <strong>Harbour</strong> Master, Fire / Police, etc., in accordance<br />

with Contingency Plans.<br />

3.8.4 Issuing Warnings<br />

A warning may be given to a vessel if it is apparent that it is standing into danger.<br />

This is normally done when it is evident that a vessel should take action in response<br />

to a circumstance identified by the PCO.<br />

Warnings may relate to:<br />

<br />

<br />

traffic information, such as the activity of other traffic; or,<br />

navigation information, such as danger of grounding, collision, striking, etc.<br />

Date: 18.08.2008 Page: 3-26<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 3 Rev No. 02<br />

Title: Traffic Management Issue No. a<br />

A warning shall be preceded by the message marker “WARNING”, include the words<br />

“from my equipment” and given in a clear concise manner so that the Mariner is in no<br />

doubt as to what is causing the alarm.<br />

Example<br />

Seatrax<br />

This is <strong>Belfast</strong> Port Control<br />

WARNING - from my equipment, you are standing into of danger of grounding<br />

north of Victoria Channel.<br />

ADVICE - take immediate action.<br />

Over<br />

3.8.5 Vessel impeding navigation<br />

<br />

<br />

<br />

Identify the vessel impeding navigation<br />

Determine its location and intentions<br />

Issue a Warning to other vessels<br />

3.8.6 Malfunction of Aids to Navigation<br />

<br />

<br />

<br />

<br />

<br />

<br />

Identify the malfunctioning aid to navigation (boy, light, etc.).<br />

Verify the characteristics to determine if the aid is damaged, not functioning,<br />

on backup power, or is off charted position.<br />

Determine direction of drift if applicable.<br />

Record the position and time of first report.<br />

Issue a warning to other vessels.<br />

Inform both Deputy <strong>Harbour</strong> Masters and the Works Engineer by e-mail.<br />

3.8.7 Pollution<br />

Refer to Oil Pollution Contingency Plan (OPRC) and complete Incident Reporting<br />

and Information Management System (IRIMS) report.<br />

Date: 18.08.2008 Page: 3-27<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 3 Rev No. 02<br />

Title: Traffic Management Issue No. a<br />

3.8.8 Vessel overdue reports - Radar surveillance / VHF - reporting System<br />

When a vessel has failed to report within 15 minutes of expected arrival and is not<br />

observed on radar or AIS:<br />

<br />

<br />

<br />

<br />

Conduct a VHF communications search;<br />

Determine if the vessel‟s agent is in contact with the vessel;<br />

If unable to establish the vessel‟s whereabouts notify the MCA, providing all<br />

pertinent information about the vessel and actions taken to locate the vessel;<br />

When the location of the vessel that has failed to report has been determined,<br />

cancel all requests made to other agencies.<br />

3.8.9 Tidal Restricted Vessels<br />

Tidal restricted vessels must be provided sufficient time to safely complete their<br />

intended passage giving due consideration to environmental factors and relevant<br />

traffic. All safety parameters, including under keel clearances for the entire transit<br />

must be assessed for the entire passage before issuing any traffic clearance. 1<br />

metre under keel clearance must be maintained for all movements.<br />

When tidal restricted vessels are in transit:<br />

<br />

<br />

<br />

<br />

Ensure radars and environmental monitoring facilities are working<br />

Check that the time of high water will be as predicted<br />

Check tugs and watermen ordered<br />

Check weather forecasts<br />

3.8.10 Engine shutdown<br />

The <strong>Harbour</strong> Master‟s permission is required for a vessel to disable main propulsion<br />

machinery for repair while within the port limits either in transit or at the berth. If<br />

permission is granted and a vessel contacts Port Control:<br />

Date: 18.08.2008 Page: 3-28<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 3 Rev No. 02<br />

Title: Traffic Management Issue No. a<br />

<br />

<br />

<br />

Determine the duration and nature of repairs;<br />

Inform the vessel of predicted wind and weather and any known hazards;<br />

If possible, ensure that the position of the vessel is clear of traffic routes and<br />

other hazards and is located in good radar coverage area.<br />

3.8.11 Deviation from expected track and/or speed<br />

When aware of any deviation of anticipated or usual activity:<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

Inform the vessel of your observation<br />

Ask if a problem exists<br />

Determine the full extent of the problem<br />

Determine the intentions of the bridge team<br />

Determine if assistance is required<br />

Ensure that other vessels are informed<br />

Continue monitoring situation<br />

3.8.12 Requirement for speed reduction<br />

A request or instruction issued to reduce speed should be results oriented. E.g. From<br />

my equipment your speed is 15 knots over the ground. REQUEST - proceed at a<br />

slow safe speed.<br />

3.8.13 Shipboard Communication Equipment Malfunction<br />

If communications with a participating vessel cannot be established:<br />

<br />

<br />

<br />

<br />

Attempt to call on VHF 16 and any other possible frequency that the vessel<br />

may be monitoring.<br />

Closely monitor the vessel‟s movements.<br />

Inform other vessels if appropriate.<br />

File a non-compliance report via an IRIMS Report.<br />

Date: 18.08.2008 Page: 3-29<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 3 Rev No. 02<br />

Title: Traffic Management Issue No. a<br />

3.8.14 Equivalent reporting<br />

Certain vessels such as warships or other patrol vessels engaged in various<br />

operations that preclude open communications may be granted equivalent reporting<br />

status. These vessels would normally indicate the intentions by a closed<br />

communication to the Port Control centre.<br />

3.8.15 Evacuation of Operations Room<br />

Port Control Centre evacuation – Call duty Deputy <strong>Harbour</strong> Master and Pilot boat<br />

on Channel 6 and respond as per Port Emergency Plan<br />

Fire Port Control Centre – respond as per Port Emergency Plan<br />

3.8.16 Place of Refuge and SOSREP direction<br />

Should a request for a place of refuge be received from a vessel, the vessel‟s agent<br />

or any outside body (including SOSREP), the <strong>Harbour</strong> Master is to be informed<br />

before any decision is made.<br />

This applies to all vessels including those which are designed as „Dangerous<br />

Vessels‟ i.e. those carrying dangerous substances or which by the nature of their<br />

distress present a risk to the general public, port and the environment.<br />

3.8.17 Navigation Assistance Service<br />

Note: It is not intended that Navigational Assistance Service be provided except on<br />

the authorization of the <strong>Harbour</strong> Master.<br />

At no time have or attempt to have control of the vessel. Communications shall be<br />

expressed in such a manner as to ensure that the vessel is aware that the Port<br />

Control centre is not attempting to control the vessel.<br />

3.8.17.1 Conditions for provision of Navigation Assistance Service (NAS)<br />

On authorisation by the <strong>Harbour</strong> Master, Navigation Assistance Service (NAS) may<br />

be provided if:<br />

Date: 18.08.2008 Page: 3-30<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 3 Rev No. 02<br />

Title: Traffic Management Issue No. a<br />

A full risk assessment has been conducted of the operation by the <strong>Harbour</strong><br />

Master.<br />

Other alternatives (escort, pilot etc) are impracticable under the<br />

circumstances.<br />

Available equipment is fully operational and adequate to the task.<br />

Positive identification of the vessel has been made.<br />

An agreement been reached with the vessel‟s master as to action to be taken<br />

by the vessel. This agreement should include a prior discussion with the<br />

master concerning the vessel‟s intended route, any hazards and other<br />

information that may be useful to the vessel.<br />

Establish a „lost communication‟ contingency plan based on communications<br />

at fixed intervals.<br />

Inform the master that information provided is from your equipment.<br />

Ensure that the radar display is set at the lowest possible range scale.<br />

Ensure that audio and video recording equipment is operating.<br />

Request that the vessel inform you when assistance is no longer required.<br />

Ask the vessel to read back all information.<br />

Date: 18.08.2008 Page: 3-31<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 4 Rev No. 02<br />

Title: Communications Principle Issue No. a<br />

4. Communications Principle<br />

4.1 Language<br />

Communications shall be in English.<br />

4.2 Time<br />

24 hour clock will be used in all communications, normally using Local Time. If UTC<br />

is used it should be stated.<br />

4.3 Communications Control<br />

With the exception of distress and urgency communications, the control of all<br />

communications between Port Control and vessels lies with the Port Control Centre.<br />

4.4 Priority of Communications<br />

The order of priority for radio communications will be:<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

Distress calls, distress messages, distress traffic<br />

Communications preceded by the Urgency Signal (Pan Pan)<br />

Communications preceded by the Safety Signal (Securité)<br />

Communications related to safety of navigation<br />

Communications related to port operations<br />

Scheduled Marine Broadcasts<br />

Other communication<br />

When the calling vessel does not indicate priority, it will be understood to relate to<br />

routine port operations.<br />

4.5 Establishing communications<br />

When attempting to establish communications on VHF call the vessel by using the<br />

vessel‟s name or call sign not more than twice.<br />

Use the radio identification “<strong>Belfast</strong> <strong>Harbour</strong> Radio” at least once in all transmissions.<br />

Date: 18.08.2008 Page: 4-1<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 4 Rev No. 02<br />

Title: Communications Principle Issue No. a<br />

When communications are established, use the vessel‟s name or call sign once only.<br />

Once contact has been established on Channel 12 the words “this is” may be<br />

dropped; however the vessel‟s name or call sign and <strong>Belfast</strong>‟s radio identifier shall<br />

be maintained for each and every communication.<br />

4.6 Port Control VHF Channel Guard<br />

If you are aware that a vessel guarding (keeping a watch on) Port Control<br />

frequencies is being called on another channel, inform the vessel to change to that<br />

frequency to receive a communication.<br />

4.6.1 Use of channels<br />

Monitor all channels required by the Port Control Centre (VHF channels 12 and 16).<br />

Except for Distress and Urgency calls, all communications shall be made on a sector<br />

working frequency.<br />

4.6.2 Test transmissions<br />

Test transmissions shall include the name or call sign of the centre and shall be<br />

limited to 10 seconds or less.<br />

4.6.3 VHF channel interference<br />

Attempt to identify the source when communication interference occurs. As the<br />

controlling station, resolve the situation by having one or all interfering stations cease<br />

transmission on the Port Control channel and either stand-by or move to another<br />

frequency.<br />

4.6.4 Interruptions<br />

Normally a transmission that is in progress has priority over new calls; however,<br />

distress, urgency or safety communication to transmit shall be entitled to interrupt<br />

any transmission in progress that is of a lower priority. Any transmission may be<br />

made to effect the interruption followed immediately by the appropriate signal.<br />

Date: 18.08.2008 Page: 4-2<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 4 Rev No. 02<br />

Title: Communications Principle Issue No. a<br />

4.7 Rate of Speech<br />

The rate of speech shall be governed by prevailing conditions and the capability of<br />

the person receiving the message.<br />

Radio broadcasts shall be around 80 to 100 words per minute with pauses and<br />

repeats as necessary.<br />

In cases of distress, urgency and safety, speech shall be made slowly and distinctly<br />

with clear pronunciation.<br />

4.8 Standard phraseology<br />

Procedural words and phrases in accordance with SMCP shall be used where ever<br />

applicable. The phonetic alphabet shall be used when required.<br />

4.9 Calling intervals<br />

The VHF call shall normally be repeated 3 times at intervals of 2 minutes. Thereafter<br />

the call may be transmitted at three minute intervals.<br />

4.10 Port Control unable to respond immediately<br />

When unable to respond to traffic immediately, PCO‟s reply should state: Standby. If<br />

the delay is expected to exceed three minutes, the reason should be given.<br />

4.11 Doubtful Reception<br />

When a call believed to be for <strong>Belfast</strong> <strong>Harbour</strong> Radio is heard but you are uncertain<br />

of the calling station reply as follows:<br />

Station calling<br />

This is<br />

<strong>Belfast</strong> <strong>Harbour</strong> Radio<br />

Say again<br />

Over<br />

4.12 VHF non-conformities<br />

Vessels not maintaining a listening watch on Channel 12 are to be noted and logged<br />

in the log book. Consider dispatching the Pilot launch to vessels involved to alert the<br />

crew and report findings.<br />

Date: 18.08.2008 Page: 4-3<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 4 Rev No. 02<br />

Title: Communications Principle Issue No. a<br />

4.13 General Call<br />

When initiating broadcasts such as weather broadcasts to all vessels, use the<br />

following format:<br />

All stations (normally twice, but not more than 3 times)<br />

This is<br />

<strong>Belfast</strong> <strong>Harbour</strong> Radio (normally twice, but not more than 3 times)<br />

4.14 Ending a call<br />

When communication exchange has ended, say: “Out”<br />

Date: 18.08.2008 Page: 4-4<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 5 Rev No. 02<br />

Title: Log Keeping Issue No. a<br />

5. Log Keeping<br />

5.1 Principles<br />

Centre logs shall adhere to the following principles:<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

Activities and events shall be recorded in chronological order.<br />

All log entries shall be clear and intelligible.<br />

Written (printed) entries shall be in ink.<br />

All entries shall be factual and as complete as possible.<br />

All entries shall include the identification of the person making the entry.<br />

Approved abbreviations etc., shall be used where possible.<br />

Dates shall be recorded in dd/mm/yyyy format.<br />

Time shall be indicated in 24 hour notation Local Time. Adjustment of clocks<br />

shall be recorded.<br />

5.2 Corrections<br />

Log entries should only be corrected by the person who made the original entry and<br />

initialled.<br />

Corrections shall be made with a single line through the entry so that the original<br />

entry is still legible.<br />

Errors or omissions noted by another person shall be corrected by making a<br />

subsequent entry referencing the original entry.<br />

5.3 Centre Log Identification<br />

Centre logs shall be identified with the <strong>Belfast</strong> Port Control Stamp and/or a printed<br />

identification showing the name of the Centre and the date.<br />

5.4 Centre Log Entries<br />

5.4.1 Mandatory Entries<br />

The following shall be recorded:<br />

Date: 18.08.2008 Page: 5-1<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 5 Rev No. 02<br />

Title: Log Keeping Issue No. a<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

Identification of the person relieving and being relieved of watch duties<br />

(logging on and off).<br />

The watch briefing check sheet.<br />

Reference to any distress/urgency/safety messages either received or sent.<br />

Any deviation from the „Standard Operating Procedures”.<br />

The time of unscheduled broadcasts.<br />

The release of log information with identification of individuals concerned.<br />

Any information that will elaborate the Equipment Operation Record.<br />

5.5 Vessel traffic activities<br />

Maintain information about current and expected port activities by updating the<br />

<strong>Belfast</strong> VTMIS in accordance with the separate operating instructions and standards<br />

for that equipment.<br />

5.6 Vessel activity information<br />

Monitor marine traffic and record vessel activity information on all participating traffic<br />

and on unidentified traffic of consequence in transit within the <strong>Belfast</strong> AOR.<br />

All recreational crafts entering or leaving the port must be recorded in the Port<br />

Control Log.<br />

5.7 Incidents and Accidents<br />

The following records and reports should be forwarded to the <strong>Harbour</strong> Master in the<br />

event of any incident or accident:<br />

<br />

<br />

<br />

Logs<br />

Emergency Checklists (completed)<br />

Situation Reports (SITREPS)<br />

Also submit a written report if it will serve to clarify circumstances of the incident.<br />

5.8 Occurrence Report<br />

Complete the IRIMS Report whenever Port Control has taken action with a view to<br />

preventing a potential incident.<br />

Date: 18.08.2008 Page: 5-2<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 5 Rev No. 02<br />

Title: Log Keeping Issue No. a<br />

Situations, which should be reported include:<br />

<br />

<br />

<br />

Dangerous navigation: where navigation is in such a manner as to place<br />

vessels at serious or imminent risk<br />

Erratic navigation: where navigation is unsatisfactory, but vessels are not at<br />

serious or imminent risk<br />

Unidentified vessels: entering the Lough or Port Limits.<br />

Vessels Navigating in Contravention of Regulations, Pilotage Directions and Port<br />

Byelaws.<br />

Vessels meeting at critical areas, even though a warning, recommendation (Advice)<br />

or direction (Instruction) has been given by the Port Control Officer.<br />

5.9 Weather Conditions<br />

Maintain and provide to any stakeholder, information on the most recent forecast as<br />

well as the most current local information concerning the following:<br />

<br />

<br />

<br />

Wind speed and direction<br />

Visibility<br />

State and height of tide<br />

5.10 Recording facilities<br />

When recordings of video or audio data, they should be labelled and identified to<br />

include:<br />

<br />

<br />

<br />

<br />

<br />

Reference number<br />

Name of centre<br />

Date/Time begun<br />

Date/Time ended<br />

The initials of the person responsible for recording the data<br />

Date: 18.08.2008 Page: 5-3<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 5 Rev No. 02<br />

Title: Log Keeping Issue No. a<br />

<br />

The signature of any person removing or borrowing the media<br />

5.11 Equipment Operation Record<br />

An Operation Record shall be maintained for each piece of electronic equipment.<br />

This should be recorded in Port Control Daily Log sheet.<br />

Each Equipment Operation Record entry shall include:<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

Workstation identification<br />

Date/time of record<br />

Name of malfunctioning component<br />

Description of the malfunction<br />

Your initials<br />

The engineering technician‟s initials and time informed<br />

Reference number of broadcast notice if applicable<br />

Time equipment restored and engineering technician‟s initials<br />

Total outage time<br />

The initial of the PCO taking over watch.<br />

5.12 Mandatory entries<br />

Equipment Operations Record entries shall be made for any shutdown, failure,<br />

abnormal operation and change over from main to standby power of:<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

<br />

Radio systems<br />

Radar<br />

AIS<br />

Radio Beacons within the PORT CONTROL responsibilities<br />

Computers and printers<br />

Facsimile machines<br />

Console lights and associated console hardware<br />

Any other equipment<br />

Date: 18.08.2008 Page: 5-4<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 5 Rev No. 02<br />

Title: Log Keeping Issue No. a<br />

5.13 Centre Log - archiving<br />

Material deemed necessary to be retained as a hard copy shall be arranged in a<br />

chronological order and securely stored on a daily basis.<br />

Each daily package shall be labelled with workstation identification and date.<br />

5.14 Electronic Distribution Systems<br />

Copies of all material sent or received at the Port Control Centre over e-mail, fax, or<br />

other electronic means shall be retained in their original printed form. Should a<br />

message need to be edited a copy of the message shall be made.<br />

Electronic logging entries may be backed up on alternative computer storage media.<br />

A hard copy of sent/received faxes shall be retained.<br />

5.15 Audio/video recordings<br />

Changing<br />

Other than a scheduled change, recordings may be removed for the following<br />

reasons:<br />

<br />

<br />

<br />

<br />

<br />

Recording equipment failure<br />

Maintenance requirement<br />

When the <strong>Harbour</strong> Master deems it necessary.<br />

A blank media shall be used to replace the removed media<br />

On removal the media shall be labelled.<br />

Storage<br />

Media shall be stored in a secure place and away from extreme temperatures and<br />

strong magnetic fields.<br />

5.16 Release of log information<br />

All information comprising the Centre log with the exception of current operational<br />

information, weather data, and scheduled broadcast information, is considered<br />

Date: 18.08.2008 Page: 5-5<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 5 Rev No. 02<br />

Title: Log Keeping Issue No. a<br />

confidential and shall not be released to the general public or news media unless<br />

authorised by the <strong>Harbour</strong> Master.<br />

Release of log information shall be in accordance with the following standards:<br />

<br />

<br />

<br />

<br />

It shall not interfere with operational requirements.<br />

Details of any information released shall be recorded in the log.<br />

Information released shall be factual.<br />

Personal opinions and interpretations shall not be included or offered.<br />

5.17 Dealing with requests for information from the public<br />

All requests concerning marine occurrences shall be referred to the <strong>Harbour</strong> Master.<br />

The following may be given to the public:<br />

<br />

<br />

Name, point of departure, ETA, ETD of any vessel other than military, patrol<br />

and police vessels.<br />

General information - tides, weather, navigational warnings.<br />

5.18 Public Relations<br />

Detailed information on cargos, passenger numbers etc., should not be provided to<br />

the general public unless in a format approved by the <strong>Harbour</strong> Master.<br />

5.19 Enquiries from the Media<br />

Any enquiry for the media should be referred to the <strong>Harbour</strong> Master.<br />

Date: 18.08.2008 Page: 5-6<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 6 Rev No. 02<br />

Title: Watch Keeping Responsibilities Issue No. a<br />

6. Watch Keeping Responsibilities<br />

6.1 General<br />

It is essential that PCOs appreciate that the proper performance of their duties is<br />

necessary in the interests of the safety and efficiency of vessel traffic and for the<br />

prevention of pollution to the marine environment. The watch roster is designed to<br />

provide adequate rest periods during normal operating conditions. It is therefore the<br />

responsibility of every individual to:<br />

<br />

<br />

<br />

<br />

<br />

Be sufficiently rested prior to taking over a watch.<br />

Be free from the effects of alcohol and any other substance, including<br />

prescription drugs or other medication that may have a detrimental effect on<br />

the individual‟s judgement.<br />

Remain alert throughout the watch.<br />

Ensure there are no distractions caused by the use of domestic radios, music<br />

systems, personal computers, television sets, mobile phones, etc.<br />

Not hand over a watch, if you believe that the person taking over the watch<br />

may be unfit in any respect to take over. In such circumstances, inform the<br />

duty Deputy <strong>Harbour</strong> Master and continue keeping a watch until relieved by<br />

an authorised person.<br />

6.2 Watch Handover Briefing<br />

A watch handover briefing shall include all relevant information to permit the<br />

oncoming watch to acquire situational awareness.<br />

information such as but not limited to:<br />

This handover will include<br />

<br />

<br />

<br />

<br />

<br />

<br />

Detailed description of the traffic image<br />

Marine occurrences: accidents, incidents and anomalies<br />

Relevant traffic information: existing and anticipated<br />

Weather and tide conditions<br />

Special marine operations<br />

Equipment status and availability<br />

Date: 18.08.2008 Page: 6-1<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 6 Rev No. 02<br />

Title: Watch Keeping Responsibilities Issue No. a<br />

<br />

<br />

<br />

<br />

<br />

Pilotage information<br />

Information on other allied services<br />

Staff availability<br />

Work in progress<br />

Other issues or information that may impact the watch<br />

6.3 Accepting the watch<br />

<br />

Receive and acknowledge handover briefing<br />

<br />

Sign on watch, either electronically or in writing.<br />

6.4 During the watch<br />

Conduct equipment check, logs results, inform technical support of problems<br />

and/or non-conformance.<br />

<br />

<br />

<br />

<br />

<br />

<br />

Log waterway status (fixed/floating aids to navigation).<br />

Perform any other duties specific to the Port Control centre.<br />

Read any posted notices dealing with operations.<br />

Review Notices to Mariners and weather reports.<br />

Check operational orders, directives and memos.<br />

Enter significant occurrences in the Log.<br />

6.5 Completion of watch<br />

<br />

Provide full briefing<br />

<br />

<br />

<br />

<br />

Relief will be delayed if involved in duties requiring special attention<br />

Sign off the log (paper)<br />

Log off (electronically)<br />

Depart the operations room only when watch has been taken over by another<br />

qualified officer.<br />

6.6 Equipment Checks<br />

Monitor all electronic equipment for which Port Control has operational control to<br />

ensure that it is functioning correctly.<br />

Date: 18.08.2008 Page: 6-2<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 6 Rev No. 02<br />

Title: Watch Keeping Responsibilities Issue No. a<br />

6.6.1 Routine<br />

As soon as practicable after the beginning of each watch:<br />

<br />

<br />

<br />

<br />

Perform checks on each main and backup VHF transmitter/receiver frequency<br />

for signal strength and modulation.<br />

Check workstation lighting.<br />

Check the electronic logging system.<br />

Check the VTMIS.<br />

6.6.2 Special Check<br />

If at any time the electronic equipment controlled by the centre is believed to be<br />

malfunctioning or below standard, conduct a special equipment check. The results of<br />

this check shall be logged and reported to maintenance staff if the equipment is not<br />

operating to required specifications.<br />

6.6.3 Navigation aid check<br />

All navigation aids (buoys) in the vicinity of the Port Control Centre shall have their<br />

status monitored either continuously or at prescribed times.<br />

PCOs are required to forward any information regarding Navigations Aids to HM and<br />

Civil Works Department.<br />

6.6.4 Time Check<br />

Clocks in the Port Control Centre shall be checked and synchronized if necessary at<br />

the beginning of each watch.<br />

Any adjustments made shall be recorded in the log.<br />

6.7 Equipment Shutdowns<br />

Ensure that all equipment associated with workstation meets the operational<br />

requirements or is reported to maintenance staff.<br />

Date: 18.08.2008 Page: 6-3<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 6 Rev No. 02<br />

Title: Watch Keeping Responsibilities Issue No. a<br />

6.7.1 Scheduled shutdowns<br />

Scheduled shutdown of equipment may be delayed due to operational requirements.<br />

6.8 Legal Responsibilities<br />

PCOs must maintain confidentiality and not discuss matters of commercial interest or<br />

sensitive matters concerning port operations with unauthorised persons. Any official<br />

communication with outside agencies must be with the express consent of the<br />

<strong>Harbour</strong> Masters or the Duty Deputy <strong>Harbour</strong> Master.<br />

PCOs may be held liable as a result of negligence in performance or nonperformance<br />

of duties.<br />

6.9 Quality Assurance<br />

The work of PCOs will be subject to quality assurance (QA) audits to ensure that<br />

their performance meets approved quality standards for professional skills and<br />

competence. QA will be conducted through a process of:<br />

<br />

<br />

<br />

Random, periodic and annual assessments;<br />

Refresher training; and<br />

Revalidation of certification<br />

6.10 Certification of Personnel<br />

PCOs will be trained to the national occupational standard and hold appropriate<br />

certification issued by the Maritime and Coastguard Agency (MCA). This training will<br />

comply with the United Kingdom‟s <strong>VTS</strong> „Training and Certification‟ strategy<br />

established by the MCA and comprising of basic training and on-the-job training.<br />

The <strong>Harbour</strong> Master will provide resources and opportunities to PCOs to keep their<br />

knowledge, skills and competence to the required standard.<br />

PCOs have the personal responsibility to ensure that their knowledge, skills and<br />

competence are maintained to the required standard and that their certification<br />

remains<br />

valid.<br />

Date: 18.08.2008 Page: 6-4<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 7 Rev No. 02<br />

Title: Annexes Issue No. a<br />

7. ANNEXES<br />

7.1 Annex I: <strong>VTS</strong> Replay<br />

It is possible to play a sequence of <strong>VTS</strong> system screenshots with<br />

synchronized radio sound. Before recording, make sure that both machines have the<br />

same system time. This is important for synchronized playback.<br />

If an incident is within the last 30 days, the replay will be available on the hard<br />

disk. To review an “incident”, you must use the following steps.<br />

1. Mode – Traffic.<br />

2. Select Mode – Replay.<br />

3. Password: REPLAY. You will be able to read the message “Replay enabled”<br />

on the screen.<br />

4. Logging – Prepare Replay – Read Data from Disk – Enter Start and Stop<br />

times – Press Ok.<br />

5. Pop up window “Are you sure to read disk data?” – Select Yes.<br />

6. Wait for a while until Logging Tape/Disc Operation finished message is shown<br />

on the screen.<br />

7. Logging – Replay – Start.<br />

8. Pop up window: Select Channel / Phone. You can choose two options.<br />

Options are:<br />

CH 16<br />

CH 12 BH (Black Head)<br />

CH 12 POC (Port Operations Centre)<br />

MULTICHANNEL<br />

PHONE<br />

To enable them, click on the speaker icon until it goes green.<br />

9. Ensure playback button in the console is red.<br />

Date: 18.08.2008 Page: 7-1<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 7 Rev No. 02<br />

Title: Annexes Issue No. a<br />

When the replay is started the default radar video setting is OFF. Select Tillysburn<br />

or Blackhead as required.<br />

In replay mode it is not possible to acquire a target or to adjust any of the radar<br />

settings. However, the operator can control the display of video using the radar scan<br />

convertor which allows adjustment of the gain, afterglow and dynamic. All menus<br />

under DISPLAY are functional and available.<br />

When done, enter a describing name in the “Save As” dialog and the program will<br />

create a directory with this name in which the screenshot files have to be copied.<br />

When recording has finished, the screenshots are transferred onto the PC and put<br />

into the same directory as the recorded sound file.<br />

Date: 18.08.2008 Page: 7-2<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 7 Rev No. 02<br />

Title: Annexes Issue No. a<br />

7.2 Annex II: Burning to Disk<br />

Steps to follow:<br />

1. Double click shortcut to Nero Icon.<br />

2. Insert CD in lower CD drive (Yamaha).<br />

3. The Nero Wizard will appear.<br />

4. Select: Compile a new CD.<br />

5. Nero will then ask which type of CD to compile, select DATA.<br />

6. Choose to compile a new CD or to continue an existing recording.<br />

7. Click Finish.<br />

8. On the left hand side a File browser shows the drives and hard disks on the<br />

PC.<br />

9. Select drive F:\Replayer (Default drive and folder).<br />

10. Use the left side control key in-conjunction with the left mouse button to select<br />

several files at a time.<br />

11. Select the file and the folder of the same name as the file name. Also select<br />

Replayer.exe (this is the program file which allows replay to be viewed on<br />

another PC).<br />

12. Using the mouse left button, drag and drop the selected file, the associated<br />

folder and the program file replayer.exe into the left side ISO1 window under<br />

NAME.<br />

13. Select burn (Write CD Dialog button) on the toolbar.<br />

14. Nero prompts test or burn, select burn.<br />

15. When the burn process is finished the CD drive will eject the CD.<br />

Date: 18.08.2008 Page: 7-3<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 8 Rev No. 02<br />

Title: Forms Issue No. a<br />

8. FORMS<br />

8.1 Daily Movement Sheet<br />

DAILY MOVEMENT SHEET<br />

Date<br />

No Time Vessel Arriving Berth Time Vessel Departing Berth Check<br />

List<br />

No. Time From Berth Vessel Shifting Time To Berth Check<br />

List<br />

Date: 18.08.2008 Page: 8-1<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 8 Rev No. 02<br />

Title: Forms Issue No. a<br />

8.2 Port Control Log<br />

Port Control Log<br />

Page No.<br />

Date<br />

/Time<br />

Details<br />

________<br />

Reviewed by <strong>Harbour</strong> Master / Deputy <strong>Harbour</strong> Master<br />

Signature:<br />

Date:<br />

Date: 18.08.2008 Page: 8-2<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 8 Rev No. 02<br />

Title: Forms Issue No. a<br />

8.3 Port Control Logsheet<br />

PORT CONTROL LOGSHEET<br />

DATE:<br />

Name<br />

Time<br />

ON<br />

WATCH HANDOVER<br />

Traffic Weather<br />

Equipment<br />

In Out Exp & Tide Radar Atlas CCTV MIS<br />

Marine<br />

Ops<br />

Pilotage<br />

Time<br />

OFF<br />

Name<br />

PILOTS ON DUTY Pilot Boat in Service :<br />

Name Time ON Time<br />

OFF<br />

Additional Comments<br />

NAVIGATIONAL AIDS<br />

Location & I.D. Defective Repaired<br />

DEBRIS / DUNNAGE RETRIEVAL<br />

Location & Description Time Retrieved By<br />

MARINE OPERATIONS<br />

Location & Event Start Time Finish Time<br />

Date: 18.08.2008 Page: 8-3<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 8 Rev No. 02<br />

Title: Forms Issue No. a<br />

FOG HORN USAGE<br />

TIDES<br />

Location Time ON Time OFF Time Height<br />

Fairway<br />

LW<br />

No.5<br />

HW<br />

No. 12<br />

LW<br />

Dry Dock<br />

HW<br />

LW<br />

HW<br />

WEATHER (Precipitation)<br />

Time 0001 0100 0200 0300 0400 0500 0600 0700 0800 0900 1000 1100<br />

Precipitation<br />

(Dry, Light, Medium or<br />

Heavy)<br />

Time 1200 1300 1400 1500 1600 1700 1800 1900 2000 2100 2200 2300<br />

Precipitation<br />

(Dry, Light, Medium or<br />

Heavy)<br />

TIDAL GAUGE COMPARISON<br />

Time Predicted Ht <strong>VTS</strong><br />

Readout<br />

Visual Gauge<br />

By<br />

DAILY CHECKLIST<br />

Items Completed By Remarks<br />

Weather Forecast<br />

Y<br />

Daily Movement Sheet Y Send to Rates (Scan & E:mail)<br />

Master / Pilot Exchanges Y Deliver to Port Operations<br />

EQUIPMENT OPERATIONAL RECORD<br />

Equipment Fault Time<br />

Reported<br />

Time<br />

Repaired<br />

Remarks<br />

Reviewed by <strong>Harbour</strong> Master / Deputy <strong>Harbour</strong> Master<br />

Signature:<br />

Date / Time:<br />

Date: 18.08.2008 Page: 8-4<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>


Section: 8 Rev No. 02<br />

Title: Forms Issue No. a<br />

8.4 Port Control Checklist<br />

Port Control Checklist<br />

Date:<br />

Vessel<br />

Time<br />

of<br />

1 st Call<br />

Berth &<br />

Availability<br />

ETA /<br />

ETD<br />

Last / Next<br />

Port<br />

Masters<br />

Name<br />

Max<br />

Draft<br />

Haz<br />

Carg<br />

o<br />

Y /<br />

N<br />

Defects<br />

Y / N<br />

Pilotage<br />

I or F<br />

&<br />

Pilot Boat<br />

Time<br />

Informed<br />

Pilots<br />

Name<br />

&<br />

Time<br />

Informed<br />

Boatmen<br />

Company<br />

&<br />

Time<br />

Informed<br />

Time<br />

Traffic<br />

Clearance<br />

Given<br />

Time<br />

All Fast<br />

or<br />

Let Go<br />

Date: 18.08.2008 Page: 8-5<br />

Doc: <strong>VTS</strong> <strong>Manual</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!