Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
SUK HT PROGRAMMING PROTOCOL (proposal)
7 November 2012, 12:10, (This post was last modified: 7 November 2012, 12:13 by OpSecRadio.)
#35
RE: SUK HT PROGRAMMING PROTOCOL (proposal)
Hi LS
as you've already covered 0 and 16 and as most preppers will be shorebased then
12 - Port Operations - 156.600 S 156.600
14 - Port Operations - 156.700 S 156.700
74 - Port Operations - 156.725 S 156.725
67 - Bridge to Bridge (1W) - 156.375 S 156.375
Would be useful channels for keeping track of comms and activity close to shore

For inter-group comms then any of the public correspondence channels would be ok e.g.
20 - Public Correspondance - 157.000 D 161.600
21 - Public Correspondance - 157.050 D 161.650
22 - Public Correspondence - 157.100 D 161.700
23 - Public Correspondence - 157.150 D 161.750

FYI Channel 16 isn't just for safety, it's also the generally accepted calling channel - be aware that this is monitored by the Coast Guard 24/7
73 de
OSR

The duty of a true patriot is to protect his country from its government ~ Thomas Paine
Reply


Messages In This Thread
RE: SUK HT PROGRAMMING PROTOCOL (proposal) - by Paul - 6 November 2012, 17:50
RE: SUK HT PROGRAMMING PROTOCOL (proposal) - by Paul - 7 November 2012, 00:22
RE: SUK HT PROGRAMMING PROTOCOL (proposal) - by OpSecRadio - 7 November 2012, 12:10
RE: SUK HT PROGRAMMING PROTOCOL (proposal) - by Paul - 15 November 2012, 21:49
RE: SUK HT PROGRAMMING PROTOCOL (proposal) - by Paul - 15 November 2012, 22:49
RE: SUK HT PROGRAMMING PROTOCOL (proposal) - by Paul - 17 November 2012, 15:21

Forum Jump:


Users browsing this thread: 1 Guest(s)