Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[VHFcontesting\]\s+FM\s+Contesting\s+This\s+Weekend\s*$/: 4 ]

Total 4 documents matching your query.

1. [VHFcontesting] FM Contesting This Weekend (score: 1)
Author: "Jim Worsham" <wa4kxy@bellsouth.net>
Date: Wed, 5 Sep 2018 23:35:29 -0400
Going to try to work some FM contacts on 2M during the contest this weekend. It used to be that you couldn't use 146.52 for contesting and everyone around here seemed to use 146.55. Now that 146.52 c
/archives//html/VHFcontesting/2018-09/msg00014.html (6,877 bytes)

2. Re: [VHFcontesting] FM Contesting This Weekend (score: 1)
Author: John Young via VHFcontesting <vhfcontesting@contesting.com>
Date: Thu, 6 Sep 2018 22:49:54 +0000 (UTC)
Jim, Here in Va (and out a couple hundred miles) 146.520 is the place to call CQ if you are running FM.  In the North East a lot of folks use 146.550 so when I worked in Central PA last January I cal
/archives//html/VHFcontesting/2018-09/msg00026.html (9,469 bytes)

3. Re: [VHFcontesting] FM Contesting This Weekend (score: 1)
Author: Bob K0NR - email list <list@k0nr.com>
Date: Thu, 6 Sep 2018 18:52:10 -0600
I'd encourage everyone to be thoughtful about how you use 146.52 MHz for contesting. John's email below has some good ideas. If 52 gets overrun with contesting CQs, we'll have a mob of non-contesting
/archives//html/VHFcontesting/2018-09/msg00027.html (10,323 bytes)

4. Re: [VHFcontesting] FM Contesting This Weekend (score: 1)
Author: John Young via VHFcontesting <vhfcontesting@contesting.com>
Date: Fri, 7 Sep 2018 05:44:42 +0000 (UTC)
A couple hints on FM: Dont be shocked if people dont know how to do an exchange or if they dont know their grid square.  Explain the exchange to them and pass them their grid square so they can give
/archives//html/VHFcontesting/2018-09/msg00030.html (12,710 bytes)


This search system is powered by Namazu