Forums
The Racing Rules of Sailing |
1860 Posts
|
|
Rule 18 and Room at the Mark |
176 Posts
|
|
Protest Committee & Hearing Procedures |
110 Posts
|
|
Race Committee & Race Management |
84 Posts
|
|
Rules 2 and 69 |
49 Posts
|
|
Match and Team Racing Rules |
47 Posts
|
|
Training Materials, Presentations and Classes |
60 Posts
|
|
Share Your SI/NOR Language |
49 Posts
|
|
Event Management & Forum System (Q's, Comments & Suggestions) |
178 Posts
|
|
Regole e dintorni - Italian Channel |
50 Posts
|
Note: This forum is not affiliated with World Sailing and comments on this forum do not represent an official interpretation of the rules, definitions, cases or regulations. The only official interpretations are those of World Sailing.
Recent Posts
-
10 CommentsNiko Kotsatos, Yesterday 23:54
-
8 CommentsMichael Moradzadeh, Yesterday 00:53
-
9 CommentsRichard Reitmeyer, Mon 04:03
-
2 CommentsPPaul Zupan, 26-Aug-06 22:03
-
35 CommentsJustin Scott, 26-Aug-06 15:22
Recent Comments
-
As Christian says, we don't expect boats to be sailed expertly. We all make mistakes. We all have bad luck from time to time. That's a reasonable expectation of sailing. There is no rule against making mistakes or having bad luck. It would not be reasonable to make such rules. (Don't quote 14 here - that's a circular reference.)
As Philip implies, releasing mainsheet in close quarters is problematic. So ROW was restrained from having bad luck or making a mistake (or even freely trimming) by W's close proximity.
You both forget to juxtapose the rule 11. The 'close-quarters' restrained L. That restraint effectively meant that L had to constantly take avoiding action (don't make mistakes and have only good luck). This breaks rule 11.
So your question should now be...
"Does that reasonable bad luck / mistake turn unreasonable when the rule 11 buffer of protection was illegally infiltrated by another boat?"
I'm not sure it does.Benjamin Harding Today 18:22 -
We have had this come up a few times at our club and have defined the winner of the trophy/prize/money as the person who entered the boat and paid the entry fee.
- A Club enters a boat, and the boat wins the prize, the club takes the prize.
- A skipper enters a boat, and the boat wins the skipper takes the prize.
- A sponsor enters a boat, and the boat wins the sponsor takes the prize. etc
It is a good idea to set this out in NOR so that it is clear, especially when there is a large sum of money riding on the prize.Anthony Howes Today 16:41 -
Michael, yea ... thats a great format for longer range planing .. but having a very simple table with the following is key
Set TWD (mag)
Leg# Mrk1 Mrk2 Bearing TWA(p/s) Dist
That could easily fit width wise on a phone.
When setting the marks, if they are govt marks hyperlinking to details regards bells/flash height etc .. avail as a pop-up will keep the list clean.Angelo Guarino Yesterday 15:31 -
Richard, thank you for your open minded response, but i agree with Sue that relaxing the promptness of the hail and RRS 44 penalty requirements would be undesirable.
One of the purposes of the suggestion was to reinforce the requirements for prompt hail and prompt response.
If you let go of those requirements you will get into all sorts of disputes about:- what incident the hail referred to,
- whether the hailed boat ever took a penalty for that incident, and
- whether there was advantage.
John Allan Tue 14:31 -
AIUI the purpose of making the respondent (not a word in this RRS) field mandatory is that the system automatically messages that entity that they are the subject of a hearing. Naming a boat there will make it appear that that boat has been protested.
Wouldn't a better solution for requests fo redress be to either omit the respondent field or make it non mandatory, and message the race committee that a request has been received in every case?John Allan Tue 14:20