[Mldxcc] Fwd: [NCDXC Chat] VK9WA LoTW QSLs

Rick WA6NHC wa6nhc at gmail.com
Mon Dec 7 02:19:27 EST 2015


It was a mixed bag for me.  15 CW was first call, my jaw dropped. 12 
meters was a challenge because they'd show up as the band closed here... 
some of it was a slog, some wasn't bad... but once I got ATNO, then a 
few more, I tried for a sweep.  I needed something on 160 and it simply 
wasn't workable (their antenna broke), I didn't get the band sweep but 
I'm tickled about 16/21 slots filled.  It's going to take two QSL cards 
unless they print VERY tiny letters. ;-)

I don't think they put in enough (for the US) time on RTTY, but I got 
one there too so I have all modes.

While it's not THAT rare, I figure at my age, if it's another 20 years 
until the next trip there, I'll be a bit more doddering by then.  :-)

All I have is the dipole not far above dirt, but I had the seat time to 
spend which made all the difference (and following multiple DX clusters 
at the same time to focus on different areas by selective filtering).

It makes me hopeful for Heard (later this month?) but that's on the 
other side of Oz, MUCH harder from here.

Which island?  Mele kalikimaka, aloha,
Rick nhc

PS I wasn't being piggy, I only oops duped on one band slot, waited for 
the online log to confirm (or try again, but they were THAT good, I 
didn't need insurance dupes).

On 12/6/2015 10:27 PM, Alan Maenchen wrote:
> Tks for the reminder Rick.
>
> I originally saw the post here about QRV. It's a chip shot from here 
> so I tuned up the 40 dipole and tried.
> Talk about easy .. first or second call on 10, 12, 17, and 20 CW all 
> within about an hour. Next day I checked ClubLog and only found 
> confirmation on 10, 12, and 20. Odd since I'm pretty sure I worked 
> them cleanly on 17. Then I tried K5BTU. Sure enough, that was showing 
> up on 17 CW. I used the "busted call feedback" form on their web site 
> and suggested that K5BTU is probably KH6TU and gave the exact time and 
> date. Sure enough, now KH6TU shows up on 17 as well as the other bands.
>
> Not sure I need it, but who cares? It's just fun breaking the pileups.
>
> 73, Alan  AD6E / KH6TU
>
>
>
>
> On Sun, Dec 6, 2015 at 7:24 PM, Rick WA6NHC <wa6nhc at gmail.com 
> <mailto:wa6nhc at gmail.com>> wrote:
>
>     So far 9 of the 16 contacts I have in their log have shown up...
>     so check it out!
>
>     Rick nhc
>
>
>
>     -------- Forwarded Message --------
>     Subject: 	[NCDXC Chat] VK9WA LoTW QSLs
>     Date: 	Sun, 6 Dec 2015 20:34:20 -0800
>     From: 	Mike Flowers via Chat <chat at ncdxc.org> <mailto:chat at ncdxc.org>
>     Reply-To: 	Mike Flowers <mike.flowers at gmail.com>
>     <mailto:mike.flowers at gmail.com>
>     To: 	Chat NCDXC <chat at ncdxc.org> <mailto:chat at ncdxc.org>
>
>
>
>     Showing up now in LoTW
>
>     -- Mike Flowers, K6MKF, NCDXC - "It's about DX!"
>
>     _______________________________________________
>     Chat mailing list
>     Chat at ncdxc.org <mailto:Chat at ncdxc.org>
>     http://mail.ncdxc.org/mailman/listinfo/chat_ncdxc.org
>     Message delivered towa6nhc at gmail.com <mailto:wa6nhc at gmail.com>
>
>
>
>
>     _______________________________________________
>     Mldxcc mailing list
>     Mldxcc at contesting.com <mailto:Mldxcc at contesting.com>
>     http://lists.contesting.com/mailman/listinfo/mldxcc
>     Need list help? Contact mldxcc-owner at contesting.com
>     <mailto:mldxcc-owner at contesting.com>
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.contesting.com/pipermail/mldxcc/attachments/20151206/8c5b65fa/attachment-0001.html>


More information about the Mldxcc mailing list