Recent Posts

Recent Comments

  • The general role of official encompases the role of competitor.  The only difference is that an individual indicating they are an official have the additional attributes of an official associated with their user ID.  Any individual logged in can sign up as a competitor for an event, and they will only have access to the public portions of that event unless they are given a role on the Event Panel for that specific event.  So you don't need to change the way you're setting up events or assigning roles for an event.  Also, there are situations where an individual is both a competitor and an official for an event (a competitor and sits on the protest committee for example).  Again, nothing changes except that individual has access to the Event Panel as well as the public pages.  
    Wed 15:38
  • I think COLREGS applies to a boat propelled by her motor whether we like it or not. 
    Juno v Endeavour says 
    … by entering a regatta with sailing instructions which unambiguously set forth special, binding “rules of the road,” the participants waive conflicting COLREGS and must sail in accordance with the agreed-upon rules 
    The RRS apply to sailing boats (Introduction, Terminology).  RRS 42 forbids boats from using motor propulsion while racing. 
    The RRS do not contemplate situations where a boat racing is being propelled by machinery, apart from permitting it in certain limited circumstances.  In my opinion, it follows that there is no conflict between the RRS and COLREGS in this regard, therefore COLREGS Rule 18(a)(iv) applies and a boat that is a power driven vessel and is required to keep out of the way of a sailing vessel. 
    Any 'confusion' on the part of other boats about whether a boat is being propelled by her motor or not is (at least hypothetically) resolved by COLREGS Rule 25(e) which requires a sailing vessel being propelled by machinery to display an inverted cone day signal.  In any case, I think the problem is a bit fanciful.  The preponderance of obligation is on the power driven vessel to keep out of the way of the sailing vessel and take early and positive action to do so:  that will, in effect mean that the sailing boat is keeping clear.  This is particularly so when coupled with a SI requiring a boat propelled by her motor to avoid interfering with other boats, which would mean that she would be required, if possible, to manoeuvre so that other boats did not need to take action to comply with any obligations they may have under COLREGS as a stand on vessel. 
    The requirement of RRS 22 for all boats, if possible, to avoid a boat that is trying to help a person or vessel in danger represents a 'carve-out' or exception to the COLREGS requirement.  I don't think that invalidates the general application of COLREGS Rule 18(a)(iv). 
    Tue 21:59
  • Gents,

    Thank you for your great comments and opinions. The initial situation I was envisioning was sailing races on another day for any reason but that was not identified in NoR or SI. The schedule in the Regata documents stated nothing about this situation and nothing was mentioned before the series started.

    I understand, that if we follow Appendix J, comply with RRS and be practical things must be defined beforehand.

    Another possible solution was to define a supplementary day in the NoR for sailing not-sail-races, but that is not practical. 

    I particularly liked the way John A frame it to find a solution.
  • > Per the diagram, it is clear
    True, but all diagrams are approximate reconstructions. With both boats protesting the PC will presumably be presented with two diagrams, one showing the overlap broken and one not.
    Isn't it down to last point of certainty? If the PC is certain the overlap was broken outside the zone then doesn't 18.2e support Red, but if the PC considers there is doubt that the overlap was broken then 18.2e supports Blue.
    24-Jun-06 22:16
  • Yea ..,that's it.  Thanks John 
    24-Jun-04 01:57
Cookies help us deliver our services. By using our services, you agree to our use of cookies. Learn more