NavList:

   

Reply

Chuck:

You're absolutely right about VTS.  Lack of outreach and education of
the recreational marine community causes two problems:

1.  Recreational mariners assume commercial traffic is monitoring Ch 16.
  But the VTS users manual specifically quotes a section of US law that
relieves them of that responsibility and allowing them to instead
monitor the VTS frequency (while the second bridge radio must stay tuned
to Ch 13).

2.  The ability to query VTS about nearby traffic (and even the channel
they communicate on!) seems to be little publicized, at least here in
the San Francisco Bay, where we do have a VTS, where commercial traffic
isn't necessarily monitoring Ch 16, and little is done to make the
recreational marine community aware of this.

Lu Abel

Chuck Taylor wrote:
> In Puget Sound, large commercial traffic must follow the Vessel Traffic Service
> (VTS) rules. We can use VHF Channels 5 (north sound) or 14 (south sound)  in
> addition to Channel 13 to communicate with large vessels.  Vancouver (Canada)
> traffic uses Channel 11, and Tofino (Canada) traffic uses Channel 74.  For an
> explanation of VTS, go to
>
>        http://www.uscg.mil/d13/psvts/
>
> and click on the link "VTS Users Manual", which translates to
>
>        http://www.uscg.mil/d13/psvts/docs/userman032503.pdf
>
> to download a pdf version of the 46-page VTS User Manual.  If you are out
> in the fog and you aren't sure your radar is working adequately, you can call
> VTS on the radio and they will tell you whether or not there is any large
> commercial traffic nearby.
>
> Chuck Taylor
>   48 N
> 122 W
>
>
>
>
>
>
>
>
> 
____________________________________________________________________________________Boardwalk 
for $500? In 2007? Ha! Play Monopoly Here and Now (it's updated for today's 
economy) at Yahoo! Games.
> http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to NavList@fer3.com
To , send email to NavList-@fer3.com
-~----------~----~----~----~------~----~------~--~---

   

Reply