Heard Island DXpedition (VK0EK) live via WBCQ tonight

heard-live-with-text

(Source: ARRL)

[…]At 0000 UTC on March 23 (the evening of Tuesday, March 22, in US time zones), Tom Medlin, W5KUB, host of the weekly “Amateur Radio Roundtable” video webcast and radio program, hopes to make ham radio media history by interviewing the DXpedition team live on his webcast. Audio will be simulcast on international shortwave broadcaster WBCQ on 5130 kHz.

Heard Island is an Australian protectorate, part of a subantarctic island group(Heard Island and McDonald Islands) in the southwest Indian Ocean, some 4000 kilometers (approximately 2480 miles) southwest of Western Australia and 1000 kilometers (approximately 620 miles) north of Antarctica. 

 I will certainly be listening to WBCQ tonight and, hopefully, recording the show for the SRAA.
For updates about the Heard Island DXpedition, check out their website (and admire Jeff Murray’s excellent official DXpedition artwork while you’re at it!).

 

Spread the radio love

9 thoughts on “Heard Island DXpedition (VK0EK) live via WBCQ tonight

  1. Carl

    The DX says there will be two days before the rigs/antennas will be set-up for amateur operation. I think he said he’s on an Iridium phone right now.

    Reply
  2. Carl

    I have it 59 here in So. Carolina via USB and a Quantum Loop antenna. It is pretty noisy on AM and the longwire. 01:10 UTC, 5129.75 MHz.

    Reply
  3. DanH

    The W5KUB webcast is up and running right now on YouTube. The noise on 5130 kHz is impossible right now. Sunset is almost 90 minutes away.

    Reply
  4. DanH

    I suspect the time for the webcast and WBCQ broadcast is actually 0200 UTC, not 0000 UTC. WBCQ reception is iffy here in Northern California but I will give it try. There was only noise here on 5130 kHz at 0000 UTC.

    Reply
  5. Steven Crawford

    No luck in Beaumont, TX with a Sony SW7600GR or CountyComm GP-5/SSB both with 20′ wires added to the whips.

    Reply
    1. Thomas Post author

      I believe they made a mistake on the time. I believe it should be 1:00 UTC, not 00:00 UTC. Try again in a few minutes.
      -Thomas

      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.