26.10.2014 Views

Admiralty Lists of Radio Signals - The Tyneside Nautical Charts ...

Admiralty Lists of Radio Signals - The Tyneside Nautical Charts ...

Admiralty Lists of Radio Signals - The Tyneside Nautical Charts ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

VI<br />

PAGES 402 & 403, TURKEY, ÇANAKKALE BOĞAZI AND İSTANBUL<br />

BOĞAZI (DARDANELLES AND BOSPORUS), Vessel Traffic Service<br />

and Reporting System (TŪBRAP), REPORTING, section (1) Sailing<br />

Plan (SP1).<br />

Delete section and replace by:<br />

(1) Sailing Plan 1 (SP1):<br />

(a) Masters, owners or agents <strong>of</strong> vessels carrying dangerous cargo or vessels <strong>of</strong><br />

500 gt and over should submit a written Sailing Plan 1 (SP1) to the relevant VTS<br />

Centre (VTSC) at least 24h prior to entry into the Turkish Straits<br />

(b) Masters, owners or agents <strong>of</strong> vessels between 200m and 300m LOA and/or<br />

vessels with a draught over 15m should submit a written SP1 at least 48h prior<br />

to entry<br />

(c) Owners or operators <strong>of</strong> vessels over 300m LOA; vessels propelled by nuclear<br />

power; and vessels carrying nuclear cargo or nuclear waste must provide<br />

information regarding their characteristics and cargo to the Administration<br />

during the planning stage <strong>of</strong> the voyage. <strong>The</strong> TSVTS and, if necessary, the<br />

Administration, based upon this data, shall inform the relevant vessel’s owner,<br />

operator or Master, <strong>of</strong> any requirements and recommendations necessary to<br />

ensure a safe passage through the Turkish Straits. <strong>The</strong>se vessels must submit<br />

a written SP1 at least 72h in advance.<br />

(d) <strong>The</strong> SP1 report shall contain the following information:<br />

ID Information Required<br />

A Vessel’s name, call sign, fl ag, IMO No & MMSI No<br />

B Date and time (UTC)<br />

C Reporting position (lat/long)<br />

F Continuous manoeuvring speed (in knots) including decimals<br />

G Port <strong>of</strong> departure<br />

H Date and time <strong>of</strong> entry into İstanbul Boğazi or Çanakkale Boğazi (UTC)<br />

I Port <strong>of</strong> destination<br />

Request for Pilot (yes/no) for İstanbul Boğazi, Sea <strong>of</strong> Marmara or<br />

J<br />

Çanakkale Boğazi<br />

Draught (forward and aft), maximum air draught (at the entrance to the<br />

O<br />

Strait)<br />

Cargo type and quantity, description <strong>of</strong> dangerous, noxious and pollutant<br />

P goods (UN No, name, class and quantity) (IMDG/IGC/IBC/GC/INF codes).<br />

In case <strong>of</strong> weapon shipment End User Certifi cate, date, number and copy<br />

Q Any defects, damage, defi ciencies or other limitations<br />

Vessel’s agent or representative (including tax number), name and<br />

T<br />

surname <strong>of</strong> Master<br />

Type <strong>of</strong> vessel, LOA & beam (in metres), gt/nt, double or single hull tanker,<br />

U<br />

year <strong>of</strong> construction<br />

W Number <strong>of</strong> crew and passengers<br />

P and I information (club name, policy number & validity) Bunkers onboard<br />

X (FO/DO/LO)<br />

Last PSC date<br />

(e) Vessels carrying dangerous cargo and/or vessels <strong>of</strong> 500 gt and over leaving<br />

ports in the Sea <strong>of</strong> Marmara shall submit an SP1 to the relevant VTSC at least<br />

6h prior to departure<br />

(former amendment 29/11)<br />

Turkish Straits VTS Guide, (RSDRA2011000229870), 52/11<br />

PAGE 403, TURKEY, ÇANAKKALE BOĞAZI AND İSTANBUL BOĞAZI<br />

(DARDANELLES AND BOSPORUS), Vessel Traffic Service and<br />

Reporting System (TŪBRAP), REPORTING, section (4) Call Point<br />

Report.<br />

Delete and replace by:<br />

(4) Call Point Report; Active Participant Vessels should make a Call Point<br />

Report (vessel’s name and position) as follows:<br />

(a) When intending to pass through İstanbul Boğazi and/or Çanakkale Boğazi, at<br />

the entrance and exit <strong>of</strong> each sector, to the relevant VTSC<br />

(b) When passing through the VTS areas in the Black Sea and Aegean Sea but not<br />

intending to pass through İstanbul Boğazi and/or Çanakkale Boğazi, the report<br />

should be sent to the relevant VTSC at the entrance and exit <strong>of</strong> each sector<br />

(former amendment 29/11)<br />

Turkish Straits VTS Guide, (RSDRA2011000229870), 52/11<br />

PAGES 404 & 405, TURKEY, ÇANAKKALE BOĞAZI AND İSTANBUL<br />

BOĞAZI (DARDANELLES AND BOSPORUS), İstanbul Boğazi VTS<br />

Centre.<br />

Delete section and replace by:<br />

İstanbul Boğazi VTS Centre<br />

NOTE:<br />

Sailing Plan 1 (SP1) reports shall be submitted to the VTSC.<br />

CONTACT DETAILS:<br />

Telephone: +90(0)212 3234800 (Switchboard)<br />

Fax: +90(0)212 3234806<br />

+90(0)212 3234807<br />

+90(0)212 3234808<br />

Sector Türkeli<br />

Call: Sector Türkeli<br />

VHF Frequency: Ch 11<br />

Sector Kandilli<br />

Call: Sector Kandilli<br />

VHF Frequency: Ch 12<br />

Sector Kadiköy<br />

Call: Sector Kadiköy<br />

VHF Frequency: Ch 13<br />

Sector Marmara<br />

Call: Sector Marmara<br />

VHF Frequency: Ch 14<br />

VTS SECTOR LIMITS:<br />

(1) <strong>The</strong> N limits <strong>of</strong> the İstanbul VTS comprise a line joining the following positions:<br />

(a) 41°10′·50N 29°35′·00E<br />

(b) 41°32′·50N 29°35′·00E<br />

(c) 41°32′·50N 28°45′·00E<br />

(d) 41°19′·00N 28°45′·00E<br />

(2) <strong>The</strong> S limits <strong>of</strong> the İstanbul VTS comprise a line joining the following positions:<br />

(a) 40°52′·50N 29°13′·80E<br />

(b) 40°48′·50N 29°09′·00E<br />

(c) 40°39′·90N 29°09′·00E<br />

(d) 40°41′·00N 28°10′·00E<br />

(e) 40°51′·60N 28°10′·00E<br />

(f) 40°55′·10N 28°43′·40E<br />

(g) 40°58′·20N 28°43′·40E<br />

Continued on next page<br />

Wk52/11<br />

6.18

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!