safety for swiftsure
play

Safety for Swiftsure Fundamentals Special Safety Considerations - PowerPoint PPT Presentation

Safety for Swiftsure Fundamentals Special Safety Considerations Key Players Racers Swiftsure Organizing Authority Safety Agencies Fundamentals Safety of boat and crew is sole and inescapable responsibility of the person in charge (SER


  1. Safety for Swiftsure Fundamentals Special Safety Considerations Key Players Racers Swiftsure Organizing Authority Safety Agencies

  2. Fundamentals  Safety of boat and crew is sole and inescapable responsibility of the person in charge (SER 1.2 & RRS 46)  Designated person to take over as person in charge in event of incapacitation (SER 1.2)  Decision to participate in a race or to continue racing is hers alone (RRS 2013 -2016 #4)  Must give all possible help to any person or vessel in danger (RRS 1.1)  Crew is responsible to wear PFDs adequate for the conditions (RRS 1.2)

  3. Special Safety Considerations  Long courses within both Canada and USA  Transit a major Vessel Traffic Management area  Sailing in dark and/or fog without radar  Wide variety of sailboats in size & seaworthiness  Crews vary widely in age, competency and experience  Wind and sea state varies due to conditions & tidal current  Sea temperature is cold (about 10 0 C, 50 0 F)

  4. Key Players for Safety Racers Swiftsure Organizing Authority Safety Agencies

  5. Key Players: Racers  Culture of safety on each boat  Skipper/owner sets the tone  A shared responsibility with crew  Training (e.g..; MOB recovery, location & use of safety equipment, aids to navigation, emergency radio operation)  Prevent and mitigate emergencies  Division of responsibilities with back up

  6. Racers cont’d  Role of Person in Charge  Boat preparation  Seaworthy boat  Sound hull, spars, rigging, sails, and gear  Safety equipment properly maintained and safely stowed  Crew selection and organization Sufficient ability and experience to face bad weather   Crew knows where safety equipment is kept and how to use it  Crew briefing  Decision to sail or continue to race  Monitor weather conditions and forecasts

  7. Racers cont’d  All crew members  Personal readiness (physical fitness, personal safety gear)  Safely perform role on boat  Contribute to safety of boat and other crew  Know Racing Rules of Sailing 2013-2016  Read Sailing Instructions and Notice of Race (PRO will not present them at Skippers’ meeting!)  Comply with Safety Equipment Requirements

  8. Racers cont’d  Safely cross Traffic Separation System  VTS broadcasts on VHF 09 of commercial traffic every half hour  Continuously monitor VHF 16 (low volume if DSC)  MMSI and GPS enabled  Safe handling of boat (e.g.; gear down in heavy weather, maintain look out)  For emergencies (activate DSC, call Coast Guard via VHF 16, cellular/satellite phone, email), activate EPIRB, PLB Updated crew lists – in case of SAR   Position reporting (Four Long Courses)

  9. Key Player: Swiftsure Organizing Authority Safety Policy Safety Equipment Requirement Conduct of Race

  10. Swiftsure Safety Policy  Promote a Culture of Safety for Swiftsure  Safety Advisor – Don Thain  Protocol when to not start the race, or to abandon race due to wind & sea state conditions  Minimum safety requirements  Location of boats in event of emergency  Position reporting (Four Long Courses)  SPOT Tracker System  Accurate crew lists

  11. PIYA Safety Equipment Requirements  Located on Swiftsure website ( Registration tab, Notices of Race sub tab )  Separate SERs for monohulls and for multihulls  Swiftsure Inshore Classic is ‘Inshore’ category  Four Long Courses are ‘Coastal’ category  A number of the SERs for monohulls have been modified by the NORs  Changes are described in the SER on the website  Any questions email/phone the Chair of Swiftsure

  12. Conduct of Race  Trained and capable Race Committee  Rigorously adhere to NORs and SIs  Regular monitoring of wind and sea state via Environment Canada  Communications capability in whole race area  VHF 26  Dedicated radio operators at CRD & Sombrio Point  Safety compliance inspection  Coordination with Safety Agencies prior to race, and JRCC during race

  13. Key Players: Safety Agencies  SAR interoperability of Canadian Coast Guard & US Coast Guard (Puget Sound Sector)  Air and Marine Emergency Response JRCC positions SAR units of Canadian Coast Guard  Royal Canadian Air Force CH-149 Cormorant from 442 Squadron  relocated to Victoria Royal Canadian Marine Search and Rescue  Oak Bay (Unit 33)  Victoria (Unit 35)  Sooke (Unit 37)  Secondary SAR role of Royal Canadian Navy vessels   Vessel Traffic Service (Puget Sound Sector) and Marine Communication & Traffic Services half hourly broadcast of commercial traffic on VHF 09  South Island Marine Safety Unit, Royal Canadian Mounted Police

  14. Safety  Is a shared responsibility  Is relative, not absolute  Reduce subjective risks (what we can control)  Assess objective risks (what we do not control)

  15. Hint: Dr. Richard Dewey’s hourly Tidal Current Charts Download and email from Swiftsure website ( Race Info, Currents During Race ) to smart phone or tablet for use during race Study before race  Tidal Current Charts 09:00 May 23 to 00:00 May 25: Oak Bay: Victoria to Haro Strait  Tidal Current Charts 09:00 May 23 to 09:00 May 25: Juan de Fuca East: Victoria to Race Passage  Tidal Current Charts 09:00 May 23 to 06:00 May 25: Juan de Fuca East: Victoria to ODAS-46088  Tidal Current Charts 12:00 May 23 to 18:00 May 24: Central Juan de Fuca Strait  Tidal Current Charts 15:00 May 23 to 18:00 May 24: Juan de Fuca Western Entrances

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend