There was one contest where I was punished twice for 1 busted call. I
believe it was the 10 meter contest. I don't remember what call I busted,
but it was something like K3WW which I copied as K2WW, or something like
that. I was penalized for that mistake, and K2WW (or whatever I miscopied
it as) turned in a log so I was also penalized for a not in log QSO for his
log.
Some days you just can't win.
73 John AF5CC
On Wed, Mar 13, 2019 at 10:11 PM Barry <w2up@comcast.net> wrote:
> I recall a CQWW CW 10+ years ago where I was dinged for a busted call.
> I had recorded the contest and went back to listen to the exchange. The
> guy sent his own call wrong! I sent the audio snippet to one of the
> CQWW committee guys for comment. It didn't affect any standings, so
> nothing was done with it.
>
> Moral of the story - you can to everything right and still lose points.
>
> Barry W2UP
>
> On 3/13/2019 4:50 PM, yuri wrote:
> > Actually, it was after I received a UBN for the 2001 Russian DX
> > Contest when I decided to change my very good VA3UZ call for current -
> > available at that moment (and not-so-good) VE3DZ. A couple of hundreds
> > guys logged me as "UA3UZ" due to some smart DX cluster spotters.
> >
> > I remember one year some W7 guy used to spot deliberately wrong calls
> > in the ARRL DX CW. And if you are not assisted, the only way to
> > suspect (even not to "know") that something is wrong is when all of a
> > sudden you start to work a lot of dupes.
> >
> > So, what does it have to do with accuracy of sending by the CQ'er??? I
> > have no idea why so many of you are in awe of RDXC, and why 2nd WRTC
> > in a row decided to give this contest a highest mark for selection
> > process putting it in the same row with CQ WW's...
> >
> > Again, penalizing an operator for something he's never done - what
> > could be more dumber? Then let the organizers change the exchange
> > procedure - make it an obligation for both guys to transmit both
> > calls, or make it similar to Sprint exchange... But like I said, even
> > that might not help.
> >
> > And don't forget that if you work a lot of uniques in this Contest -
> > for instance, staying over 14225 for General Class operators, these
> > contacts will be removed too.
> >
> > Yuri VE3DZ
> >
> > On 3/13/2019 12:04 PM, rjairam@gmail.com wrote:
> >> What if the other person not sure, deletes your call from their log?
> >> You end up losing that QSO.
> >>
> >> I don't have insight into log checking but I'd imagine that if the
> >> computer can determine that the call was busted, one side would get
> >> the Q credit - for example copying 6Y1V as BY1V, 6Y1V still gets the
> >> credit. If it's completely off like copying W1VE as HB9/DL1ABC (due to
> >> bad cluster spot) that you may lose the QSO point...
> >>
> >> Ria
> >> N2RJ
> >>
> >>
> > _______________________________________________
> > 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
>
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
|