[Dx-qsl] OY Busted

Mon Apr 14 15:02:01 2003

I think a lot depends on (a) the call busted and (b) if/when the station
finds out his call was busted.

If you know or suspect, while the operation is in progress, that it's
busted, and an on-line log (in reasonable time) is not available for
whatever reason, then try for an insurance contact -- if possible on another
mode on the same band.  This may be one of the few reasons that an insurance
QSO is reasonable; you don't KNOW whether or not you got through, therefore
you must assume you didn't.

But the bigger problem is tracking down the QSO after the fact.  Some
managers are very strict on how accurate the log is.  Others may give you
the benefit of the doubt if there's a reasonable chance that it wasn't
someone else.  (I just went through this with the manager for an Antarctic
station -- thanks to DX Central spotting logs & a lot of help getting me the
data, I was able to show him that the station had been on a different band
than the log showed, which indicated that the DX station had simply
forgotten to change bands in his software!)

I sometimes wonder how many DX cards end up with N3VAW & N3EAW!   (I know
N3VAW is in the ZL7C log on 30 CW... fortunately I got through again the
next day with less static and better condx)

What I find as a bigger aggravation are those who QRM the frequencies that
the DX station is listening to, which is a frequent cause of log errors.  I
& many others missed out on a certain Central American entity on 75 phone
last year because of QRM being applied to their listening frequencies by
someone upset about their allocated call, and to a Oceania entity on 30 CW
for the same reason.  But you can't get upset about it, just shrug it off
and try again.

73, ron wn3vaw

And now, the 2003 Version of the Jack Bogut Memorial Joke:
Why aren't they serving beer at PNC Park this year?
Because (drumroll please), the Pirates lost the Opener!

----- Original Message -----
From: "HK3CW" <[email protected]>
To: <[email protected]>
Sent: Monday, April 14, 2003 1:50 PM
Subject: RE: [Dx-qsl] OY Busted

I sure do not want to raise a polemic here, and I'm all for John and his
busted call, it just depends on who your dealing with. I had a couple of
busted calls for  a major DXP a few months back (SK3CW, HK3CR) and I had
worked them more on the same band just different modes so I didn't fight it,
I'm HK3CW of course, but the manager would not allow it and put both my
qso's as not in log. Some are very strict ..they dont care about the qrm ...

Just my two pennies worth.

73 de HK3CW  ROB
----- Original Message -----
From: John C Owens <[email protected]>
To: <>
Sent: Sunday, April 13, 2003 4:55 PM
Subject: [Dx-qsl] OY Busted

> My thanks to all who helped check the OY log for my contact on 30M. It
> was nearly unanimous that I was not in the log, except for a gentleman
> named Rob Snieder - PA5ET, the QSL manager for the operation.  He found
> my contact with the call N7HEJ (vs N7SEJ, my call). I told you there was
> lots of QRM. It definitely pays to fully check out these things as it may
> bean the difference between getting or not getting a card for a rare
> contact. Thanks Rob and all of the rest of you who helped me out. Nice
> guys!!
>
> John Owens (N7SEJ)
>
> ________________________________________________________________
> Sign Up for Juno Platinum Internet Access Today
> Only $9.95 per month!
> Visit www.juno.com
> Now, more than ever, QSL.NET is in urgent need of your financial support.
> Please help QSL.NET by sending a donation now.
>
Now, more than ever, QSL.NET is in urgent need of your financial support.
Please help QSL.NET by sending a donation now.