[CQ-Contest] CQWW Rules & SCP

Chris Plumblee chris.plumblee at gmail.com
Mon Jun 17 23:06:19 EDT 2013

I'm not one to typically get too bent out of shape about these draft rules,
but I think this one has a lot of unintended consequences

13. Call signs logged must be the same as those exchanged over the air
by the entrants during the QSO.

Two obvious flaws exist, I think. One is the S&P exception noted previously
by N2IC and NN3W. The other came up during the recent WPX CW contest at
N4WW's. Our 20m station worked DH0GSU late in the contest. One of our 40m
ops knew that to be a busted call because he had worked DH0GHU earlier in
the weekend, and furthermore he knew that DH0GHU is frequently busted to
DH0GSU. How could we correct such a mistake in a CQWW contest if it wasn't
identified while we were actually in qso with 'GHU?

N2IC sends the corrected call as a non sequitur later a few moments later
if he catches a typo or busted call. I think, since that correction was not
"exchanged over the air by the entrants during the QSO" that that
correction does not suffice. So, sending "DH0GHU TU" in isolation does not
allow you to replace DH0GSU in your log. I'm guessing that, to be correct,
you should somehow mark the earlier QSO as non-claimed and dupe the station
on that band/mode again. Good luck finding a part-time station who only
does S&P again for a second QSO that you both know to be a dupe.

I think the intent of this rule is admirable; to prevent post-contest log
massaging with databases of logs submitted or SCP databases or other tools.
However, I wonder if there is a more elegant way of preventing the behavior
that the rule is targeting? Perhaps by explicitly banning what the sponsors
are trying to prevent?

Chris WF3C

More information about the CQ-Contest mailing list