[CQ-Contest] The danger of packet/cluster use

[Randy Thompson K5ZD]

Both UZ5UA and US2IR are in my log at or before the time of the spots.

Both of them submitted logs.  Since they don't show up as busts for me, they
must have copied my call correctly.  Does make one wonder.

The lesson remains the same.  It is up to the users of the DX cluster to
make sure they know who they are working.  I send my call after every QSO,
so there is no excuse for the errors due to a bad spot.

Randy, K5ZD 

> -----Original Message-----
> From: cq-contest-bounces at contesting.com 
> [mailto:cq-contest-bounces at contesting.com] On Behalf Of 
> Robert Chudek - K0RC
> Sent: Friday, October 29, 2010 12:01 AM
> To: cq-contest at contesting.com
> Subject: Re: [CQ-Contest] The danger of packet/cluster use
> 
> hmmm... looks fishy to me... two Ukraine spots within 12 
> minutes of each other. Neither of which show up in your 
> (revealed) log segment as worked. Or do they show up in your 
> log properly but specifically having posted a bad spot?
> 
> 73 de Bob - KØRC in MN
> 
> 
> On 10/28/2010 6:22 PM, Randy Thompson K5ZD wrote:
> > I received my log checking report for the 2010 Russian DX 
> Contest the 
> > other day.  These guys do a very high level of log checking and I 
> > commend them for it.
> >
> > I found the following in my report.
> >
> >   3.5 CW  03:35 UA6LCN     743  RO    KH7D in UA6LCN log
> >   3.5 CW  03:36 RA6YDX     744  AD    KH7D in RA6YDX log
> >   3.5 CW  03:37 VA3OBR     747  094   KH7D in VA3OBR log
> >   3.5 CW  03:38 S51DX      751  798   KH7D in S51DX log
> >   3.5 CW  03:41 UW1M       757  1438  KH7D in UW1M log
> >   3.5 CW  03:43 LZ4TX      761  755   KH7D in LZ4TX log
> >   3.5 CW  03:43 UU6JJ      760  898   KH7D in UU6JJ log
> >   3.5 CW  03:44 US2WU      762  411   KH7D in US2WU log
> >   3.5 CW  03:46 CR6K       768  1607  KH7D in CR6K log
> >   3.5 CW  03:48 4O3A       775  1750  KH7D in 4O3A log
> >           ...............  775  1750  Correct exchange is 1751
> >   3.5 CW  03:48 RF3C       773  MA    KH7D in RF3C log
> >   3.5 CW  03:49 DL5KUT     777  732   KH7D in DL5KUT log
> >   3.5 CW  03:50 P3F        778  2025  KH7D in P3F log
> >   3.5 CW  03:51 RM3Q       781  VR    KH7D in RM3Q log
> >   3.5 CW  03:52 DF0SAX     785  527   KH7D in DF0SAX log
> >   3.5 CW  03:56 RU3LA      795  SM    KH7D in RU3LA log
> >   3.5 CW  03:57 IK4RQE     798  243   KH7D in IK4RQE log
> >
> >
> > Given that all of the QSOs are in relatively short order, it would 
> > appear a bad packet spot was to blame.  Sure enough, a search on DX 
> > Summit reveals the following.
> >
> > UZ5UA           3505.7 KH7D                                 
>            0344
> > 21 Mar   Hawaii
> > US2IR           3505.7 KH7D         RDXC                    
>            0332
> > 21 Mar   Hawaii
> >
> > This is a great example of how blindly (no relation to the running 
> > thread on blind skimmer) following spots can cost you points.
> >
> > Pay attention to what you spot and make extra sure the 
> people you work 
> > are who you think they are!  And don't use the cluster if you are 
> > claiming to be single operator!!!
> >
> > 73,
> >
> > Randy, K5ZD
> >
> >
> > PS - The RDXC penalizes ME for all of the QSOs where someone 
> > packet-logged my call incorrectly.  That seems unfair, but 
> that's another story.
> >
> >
> >
> > _______________________________________________
> > CQ-Contest mailing list
> > CQ-Contest at contesting.com
> > http://lists.contesting.com/mailman/listinfo/cq-contest
> >
> _______________________________________________
> CQ-Contest mailing list
> CQ-Contest at contesting.com
> http://lists.contesting.com/mailman/listinfo/cq-contest