CQ-Contest
[Top] [All Lists]

Re: [CQ-Contest] Prohibiting Interleaved CQs - killing Inovation

To: k9yc@arrl.net, cq-contest@contesting.com
Subject: Re: [CQ-Contest] Prohibiting Interleaved CQs - killing Inovation
From: garyk9gs <garyk9gs@wi.rr.com>
Date: Thu, 16 Mar 2017 14:34:59 -0500
List-post: <cq-contest@contesting.com">mailto:cq-contest@contesting.com>
I'm the most recent ARRL phone contest a ZD7 showed up on 20m in the afternoon. 
He was not in the contest but if asked he would give a signal report and power. 
 He was also very loud, at least in W9.
As you can imagine,  the pileup was HUGE and growing bigger by the minute and 
more unruly too.   It got to the point that he was only working one QSO every 
minute or more..until he went split.  His rate shot up and many more were able 
to work a new mult.
In this case, split was a great idea.  He was high in the band and the impact 
on others was minimal.  Much better to work split than to have him go QRT in 
frustration. Then no one benefits and the next contest he might just leave the 
radio off that weekend. 




73-Gary K9GS 
-------- Original message --------From: Jim Brown <k9yc@audiosystemsgroup.com> 
Date: 3/16/17  12:58 AM  (GMT-06:00) To: cq-contest@contesting.com Subject: Re: 
[CQ-Contest] Prohibiting Interleaved CQs - killing Inovation 
On Wed,3/15/2017 5:52 PM, Radio K0HB wrote:
> I agree that SO-Split is equally hoggish if it consumes two QRG's in a
> single band segment.

Operators should be DQed for working split during a contest. It consumes 
more than two frequencies, because the callers spread out, and others 
running on those frequencies get clobbered. I won't work ANYONE split 
during a contest.

73, Jim K9YC


_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
<Prev in Thread] Current Thread [Next in Thread>