Topband
[Top] [All Lists]

Re: Topband: K5P good job!

To: <topband@contesting.com>
Subject: Re: Topband: K5P good job!
From: "Larry" <lknain@nc.rr.com>
Reply-to: Larry <w6nws@arrl.net>
Date: Sun, 17 Jan 2016 14:01:24 -0500
List-post: <topband@contesting.com">mailto:topband@contesting.com>
If the op gives in to the pummeling then even worse chaos generally ensues. Of course, trying to hold out kills the rate. The op may have "heard" a call that really wasn't there or a station that finally just fell out of the propagation range. It's a challenge to decide when to abandon a call and to go on.

73, Larry  W6NWS
-----Original Message----- From: lmlangenfeld@tds.net
Sent: Sunday, January 17, 2016 12:40 PM
To: topband@contesting.com
Subject: Re: Topband: K5P good job!

Message: 16
Date: Sun, 17 Jan 2016 09:55:36 -0400
From: "Mike Smith VE9AA" <ve9aa@nbnet.nb.ca>
To: <topband@contesting.com>
Subject: Topband: K5P good job !

If the DX said WB6Z? I certainly wouldn't call.  Full credit to the K5P op
who tried to stick with it til he figured the original caller wasn't hearing
him or they were getting pummeled so badly from calls not even close to the
original, that he moved on.  Rate is king when time is limited.(dxpeditions
only have so many days)

gah !

Mike VE9AA

**************************


Mike, you're quite right. There seems to be a real epidemic of those constantly calling out-of-turn (COOTs??) lately, and there's no question Q-rates are suffering as a result of this senseless (and now seemingly pervasive) QRM. There's no rational excuse for it.

Both yesterday and this morning I heard many more than a few "easy" Qs fail to go to completion when K5P diligently and accurately tried to reply to callers who responded with nothing more than relentless repetitions of their calls. Apparently you did , too.

Jeepers!

73,

Mark -- WA9ETW
_________________
Topband Reflector Archives - http://www.contesting.com/_topband
_________________
Topband Reflector Archives - http://www.contesting.com/_topband

<Prev in Thread] Current Thread [Next in Thread>