Being unassisted is not the issue.
Last year, a group of us operated as 6Y3T. I was sending a bit fast, and a
friend (not using the cluster) *thought* he was working BY3T. When I
worked him, I sent "Bill" - a quick hello. That put an even bigger smile
on his face!
He went and told his XYL "I just worked China!! And the op there knows me
- said 'hi Bill'" So his XYL asks "So - who do you know in China?" That
got him thinking, and the few names he came up with as possibles were back
from that part of the world. So - he went back to listen some more, *then*
copied me as 6Y3T, and everything fell into place :-)
So - might be some click & shoot stuff in there, but some folks may have
just out and out busted the call.
Knowing propagation will go a LONG way in avoiding these types of errors.
Tom - VE3CX
On Thu, Jun 15, 2017 at 12:54 PM, Barry <w2up@comcast.net> wrote:
> Be interesting to see how many of those ops submitted logs as unassisted.
>
> Barry W2UP
>
>
> On 6/15/2017 08:39, Mike Tessmer wrote:
>
>> ************* Stations Copying 6Y2T Incorrectly **************
>>>
>>
>> So some ops are incapable of understanding propagation and likely
>> callsigns
>> and this is 6Y2T's fault?
>>
>> A quick perusal of the list of busts that Yuri provided seems to indicate
>> ample evidence of Clueless Cluster Clicking.
>>
>>
>> 73, Mike K9NW
>>
>> _______________________________________________
>> 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
|