Date: Mon, 13 Mar 2023 13:54:43 GMT
I think I got the strategy wrong this year. I chose a 24hr entry instead of 12hr, always planning a 3hr rest in the middle of the night. When I closed down at 01:30 Sunday morning I had 314 QSOs in the log. Returning at 04:30 and sticking it out to the end only added a further 31 QSOs for 5.5hr operating. The last two hours, even with lots of CQing only produced 3 QSOs in each hour, and one of those was a dupe. Final tally was 345 QSOs (including 7 dupes).
I’ve participated many times in BERU/CC but this is the first I failed to work VK or ZL on 80m. Perhaps I took my eye of 80m because the higher bands were in good shape, but as others have pointed out LF conditions were down. I also failed to work ZL on 10m. embarrassing!
A couple of interesting QSO: worked S79/AE0BF at 05:59 on 10m, high in the band when he was CQing with no other callers. I had to go split to work VU2TMP on 10m, had to have a proper QSO with ZL3XDJ at the bottom end of 40m in order to claim a contact. A similar story for AP2TN on 10m.
I managed a clean sweep of the Gx5WS and GB5CC stations with the exception of GD5WS which I was expecting to hear but suspect wasn’t on.
The band breakdown is:
BAND QSO BONUS HQ DUP POINTS
———————————
80 25 10 6 0 120
40 55 34 6 2 275
20 101 58 8 2 505
15 86 50 10 2 430
10 71 46 6 1 355
———————————
TOTAL 338 198 36 7 1685
=================================
FINAL SCORE: 6 365
Station was: FTdx101D, ADOM 1K amp, inverted V at 12m for 40, 20, 15 & 10 plus 45m end fed at 15m for 80m. Logging with DXLog.net.
To pick up on another thread in the reports – my sympathy to Don (G3BJ) for having to use a call ending in a S (G5WS) – I tell you it’s even worse ending with H (G3WPH). I don’t think G3WPS has been active for many years or was even a DXer, but suspect I have worked DXCC for him.
With the exception of the last couple of hours it was enjoyable and I thank all for participating, especially those who travelled or put on special stations.
Mike /G3WPH/G3P