APPENDIX TS
TRAFFIC SEPARATION SCHEMES
Version 1 – November 2019

Under Regulation 28.1.5(b), World Sailing has approved the use of Appendix TS as a test rule. The appendix applies only if the relevant version of the test appendix is referred to in the notice of race and if a copy of the appendix (or a specific link to it) is provided to competitors. Comments on this test rule are welcome. Please send them to rules@sailing.org.

This appendix proposes wording for race committees to consider to replace rule 48.2 that can be more strictly interpreted by boats and protest committees. Rule 48.2 makes all parts of IRPCAS rule 10 applicable to boats that are racing. IRPCAS rule 10 is shown below to point out certain phrases that would be difficult for boats or protest committees to interpret. Those phrases, which are not precise and not usually found in the RRS, are underlined in the text below.

—INTERNATIONAL—
Steering and Sailing Rules


RULE 10
Traffic Separation Schemes

(a) This Rule applies to traffic separation schemes adopted by the Organization and does not relieve any vessel of her obligation under any other rule.
(b) A vessel using a traffic separation scheme shall:
     (i) proceed in the appropriate traffic lane in the general direction of traffic flow for that lane;
     (ii) so far as practicable keep clear of a traffic separation line or separation zone;
     (iii) normally join or leave a traffic lane at the termination of the lane, but when joining or leaving from either side shall do so at as small an angle to the general direction of traffic flow as practicable.
(c) A vessel shall, so far as practicable, avoid crossing traffic lanes but if obliged to do so shall cross on a heading as nearly as practicable at right angles to the general direction of traffic flow.
(d) (i) A vessel shall not use an inshore traffic zone when she can safely use the appropriate traffic lane within the adjacent traffic separation scheme. However, vessels of less than 20 meters in length, sailing vessels and vessels engaged in fishing may use the inshore traffic zone.
     (ii) Notwithstanding subparagraph (d)(i), a vessel may use an inshore traffic zone when en route to or from a port, offshore installation or structure, pilot station or any other place situated within the inshore traffic zone, or to avoid immediate danger.
(e) A vessel other than a crossing vessel or a vessel joining or leaving a lane shall not normally enter a separation zone or cross a separation line except:
     (i) in cases of emergency to avoid immediate danger;
     (ii) to engage in fishing within a separation zone.
(f) A vessel navigating in areas near the terminations of traffic separation schemes shall do so with particular caution.
(g) A vessel shall so far as practicable avoid anchoring in a traffic separation scheme or in areas near its terminations.
(h) A vessel not using a traffic separation scheme shall avoid it by as wide a margin as is practicable.
(i) A vessel engaged in fishing shall not impede the passage of any vessel following a traffic lane.
(j) A vessel of less than 20 meters in length or a sailing vessel shall not impede the safe passage of a power-driven vessel following a traffic lane.

Section A, Section B, or Section C of this appendix applies to a specified traffic separation scheme (TSS) if the notice of race so states. For long races that encounter multiple TSSs, the race committee may choose to handle specific TSSs in different ways and decide that Section A, Section B, or Section C be used for one or more TSS.

Note that neither the RRS nor race committees can modify IRPCAS. Local maritime authorities, however, can make special rules regarding their harbors and roadsteads under rule 1(b) of the IRPCAS. As noted below, a race committee may change rule 48.2 using Section A or Section C of this appendix only if it has obtained the agreement of local maritime authorities.


Section A
Section A is appropriate for a TSS in which marine authorities only require boats to not impede power-driven vessels in traffic lanes. This change requires the agreement of the local maritime authorities.

Suggested wording for the notice of race:
     Appendix TS, Version ___, Section A applies to the following TSS ______________.
Insert the name of the TSS.
TS1. Rule 48.2 is changed to:
48.2
(a) A Traffic Separation Scheme (TSS) shall be understood to mean an area shown on a nautical chart, or in the notice of race, as a TSS.

(b) A boat shall not impede, or present a threat of impeding, the safe passage of a power-driven vessel in a TSS traffic lane.

(c) If a commercial, government, or naval power-driven vessel in a traffic lane makes five short and rapid blasts on her whistle (a danger signal, see IRPCAS rule 34(d)) and the boat causing the danger signal can be identified, then the boat is subject to protest under rule 48.2(b).

(d) If an official complaint/action is lodged against a boat by a commercial, government, or naval power-driven vessel, by a pilot, by vessel traffic service (VTS), or by other local government authority, it shall be presumed that the boat has broken rule 48.2(b).

(e) The race committee will cooperate with and provide relevant information to VTS and other governmental authorities regarding investigations of boats impeding a power-driven vessel.

Application and background:

Approaches similar to TS1 have been shown to work in areas like San Francisco, where extensive racing takes place within multiple TSSs, precautionary areas, and deep-water routes that are tightly managed by San Francisco’s vessel traffic service (VTS). The VTS and pilots appreciate the consideration shown by racers, and racers appreciate being able to race in the waters of the TSSs and other VTS controlled areas. In the San Francisco experience, boats nearly always lose protests filed by the race committee in response to an official complaint/action lodged against a boat by a ship pilot, ship captain, or the VTS, and so boats pay careful attention to not impeding the passage of ships.
Cookies help us deliver our services. By using our services, you agree to our use of cookies. Learn more