[DX] Not in log

[Steven Wheatley KU9C]

I forget what year it was, but Martti OH2BH wrote an excellent article on
this subject, along with a number of 'real life' examples based on TX0DX, I
believe.

It's a pain in the neck to go the extra mile, but it's worth it.  Else you
have to assume the DXpedition is always correct.......and even with the best
operators, there will be an error rate.....hopefully small, but real.

I'm not sure why VP6DI chose to do this.......I was surprised with how they
plan to issue cards when the call is busted, and I doubt that will be
acceptable for any awards program (something like, this card is issued to
KU9C, but the log says KU8C).

73
----- Original Message -----
From: "Bogyo Istvan" <ha0du@freemail.hu>
To: <DX@mailman.qth.net>
Sent: Wednesday, July 03, 2002 3:36 AM
Subject: [DX] Not in log


> Dear Steve & List,
>
> Just compare what you wrote with the "Busted Call Policy"
> of VP6DI (available at VE3HO's web site).
>
> They will not change the log entries, even in cases where
> it is obvious that the expedition operator made a mistake,
> or simply a typo. I have collected about 300 of these from
> the VP6DI log, and a good protion of these would have not
> happened with an experienced operator (e.g. A4HXR instead
> A45XR, KL3ZA instead of DL3ZA, LH0EV instead of L50EV,
> Y6HQZ instead of YB5QZ, PA4DZN istead of PA3DZN, and
> unfortunately HA0DA and SA0DU instead of HA0DU...).
>
> 73 es DX
>
> Steve HA0DU
>
>
>
> _______________________________________________
> DX mailing list
> DX@mailman.qth.net
> http://mailman.qth.net/mailman/listinfo/dx
>