It's CLE time again!
'CLE's are 'Co-ordinated Listening
Events, and NDB DXers around the world focus their listening time on
one small slice of the NDB spectrum.
Propagation on MF has been excellent this past month and hopefully will continue to be good.
When tuning for NDBs, put your receiver in the CW mode and listen for the NDB's CW identifier, repeated every few seconds. Listen for U.S. NDB identifiers approximately 1 kHz higher or lower than the published transmitted frequency since these beacons are modulated with a 1020 Hz tone approximately.
For example, 'AA' near Fargo, ND, transmits on 365 kHz and its upper sideband CW identifier is tuned at 366.025 kHz while its lower sideband CW ident can be tuned at 363.946 kHz. Its USB tone is actually 1025 Hz while its LSB tone is 1054 Hz.
Often, one sideband will be much stronger than the other so if you don't hear the first one, try listening on the other sideband.
Canadian NDBs normally have an USB tone only, usually very close to 400 Hz. They also have a long dash (keydown) following the CW identifier.
All NDBs heard in North America will be listed in the RNA database (updated daily) while those heard in Europe may be found in the REU database. Beacons heard outside of these regions will be found in the RWW database. These databases have recently been re-vamped and are slicker than ever before!
From CLE coordinator Brian Keyte (G3SIA), comes the following CLE info:
It is time to confirm the details of our special Holiday Listening Event for you.
Between local midday on 25th December and local midday on 3rd January you are invited to ‘make a flight of your choice’ by logging NDBs along the way (as many pilots would have done in the old days!).
The main challenge is that you will be using your own receiver, probably from your home, for ALL your loggings. (Or you could use one Remote receiver if you prefer that).
Your log format can look just the same as usual for normal CLEs, but, very important, you must log your chosen NDBs in the correct time sequence for your journey. Your time between making two consecutive NDB loggings for your log could be minutes, hours - or even days! However, you won’t be able to go back and fill in a missed NDB earlier in your flight unless you re-log the NDBs from that one. It means that a bit of pre-planning will be very useful - and fun.
At the end of this email we have added a HELP SECTION of ‘Extras’ which include advice on how you can use the RWW database for your planning, with the help of its maps that show all of the known NDBs Worldwide.
You could choose a flight to your favourite holiday destination, or make a ‘round trip’ with interesting places along the way, or go a L O N G way, finishing far away, as NDB reception allows. You could choose to start – and/or to finish – at ANY active NDB that you can log. There is plenty of scope for you to choose something unusual and we hope that a lot of interesting and varied flights will be made.
In the Extras Section below there is also the log of an imaginary ‘flight’ using the real, active NDBs on a round trip between Rio de Janeiro and Buenos Aires in South America - and the flight map that was made from it.
In the CLE Combined Results we hope to include all of the separate flight maps, each of them made from our CLE flight logs. Each reporter’s map will probably sit nicely in a separate Excel Sheet of the results. (E.g. in Europe’s results, ‘CZE my’ in extra Sheet1, ‘DEU hw’ in extra Sheet2.. . and in Rest of the World’s results, ‘AUS SA rw’ in extra Sheet1, etc. .. )
Here are a few things to think about:
You could choose to start your flight from any NDB of your choice
- or from your local NDB.
- or from your ‘Home’ (your usual QTH) – just add the word HOME on the line immediately above your first NDB logging.
- or from your chosen Remote receiver - just add the word REMOTE on the line immediately above your first NDB logging. That remote receiver is your temporary ‘home’ for this CLE and ALL your loggings must be made using it.
The same NDB must NOT be logged more than once because your map would no longer be able to show your route – we would have to delete any same-NDB loggings after the first one.
However if you choose to start and end your flight at the same NDB (e.g. your nearest) that WILL be OK.
In normal CLEs we sometimes get the same log time for consecutive loggings. If this happens in your flight log PLEASE show the first one as 1 minute earlier (or the second one 1 minute later). If you don’t do that your flight map may go to the wrong NDB first and so have a strange zig-zag there.
PSKOV users - this applies to you too, after you have found your actual logging times (please see the Extras Section 3 below)
We don’t want to set a limit to anyone’s total count of NDBs (= loggings = flight ‘legs’). However, please bear in mind that the further away you go and/or the more NDBs you visit, your map will quickly become complex and hard to appreciate. Flights with a lot of zig-zagging and very long legs between loggings should also be avoided if you can.
Our thanks to those who have contacted us since the ‘Extra Early Advice’. There are already some good ideas and ‘themes’ for flights. We could mention what their ideas are, but that would ‘Steal their Thunder’!
Please look out for our Final Details about the Event on about 22nd December. It will have a little more quite important advice on log making, etc.
Brian and Joachim
HELP SECTION ‘EXTRAS’
1. USING RWW TO PLAN YOUR FLIGHT:
You will find the amazing (Worldwide) database RWW very helpful.
Go to https://rxx.classaxe.com/rww/signals
Select New (top right) then Signals (left) and √NDB (in the lower box).
Then select your chosen RWW Focus (Region) and, if needed, States, Countries or Grid Squares.
Finally choose Status: Active and, in the bottom line, Map
And – you’re away!
2. A SAMPLE ‘FLIGHT’:
Here is our ‘dummy run’ – an inland flight from Rio de Janeiro in Brazil, via Paraguay and Uruguay, to Buenos Aires in Argentina and back along the Atlantic coast. That would be practicable if you live in the south of Brazil or if you could find a good Remote receiver there (It would be a near miracle for any of us listening in Europe - and maybe from North America as well!)
The flight started and ended at NDB 330 YLA in Rio.
Test Log for a CLE263 ‘Flight’:
(any of the usual log formats will be OK)
dd UTC kHz Ident Location Cou.
26 2205 330 YLA ILHA (RJ) BRA
26 2236 285 BBC Barbacena (MG) BRA
26 2341 325 VGH Varginha (MG) BRA
27 0013 310 PSN Piracununga(SP) BRA
27 0255 380 BRU Bauru (SP) BRA
28 2317 320 MRN Maringa (PR) BRA
29 0024 200 CDE Cascavel BRA
29 0259 307 P Posdas ARG
29 1947 275 URG Uruguaiana BRA
29 2020 260 TBO Tacuarembo URG
29 2129 280 P PALMERO B.Aires ARG
31 1915 239 LS Capitan Corbeta URG
31 1945 312 UI Chui (RS) BRA
31 1951 290 RG Canal BRA
31 2048 300 FB Tramandai (RS) BRA
31 2209 280 JGN Jaguaruna BRA
31 2211 235 NVG Naveagantes(SC) BRA
31 2219 320 NX Domel (PR) BRA
31 2307 330 PP Metro (SP) BRA
31 2323 430 TBE Taubate (SP) BRA
31 2344 330 YLA ILHA (RJ) BRA
Flight Map, made from the above log:
(We may choose a different program to make the flight maps)
3. GUIDANCE FOR PSKOV USERS:
It seems that the rules for this CLE (log-times in sequence with NDB stop-overs, no two logs having the same minute) collide with the way the PSKOV Log Feature works.
PSKOV always automatically uses the start-time of a particular recording as the time logged for reception of the beacons on the recording.
However, PSKOV users will know that the log-time issue can be solved by either using short recordings in Skimmer mode or, for longer recordings, finding the exact time of reception in Viewing Mode.
The users have told us that the use of short recordings for this CLE is highly recommended.
Once a beacon has been found using Skimmer mode, it can be logged with the built-in Log Feature, then transferred by copy/paste to a CLE master log (e.g. in EXCEL or text editor) and changed to show the actual time of reception.
If you are interested in some remote listening - maybe
due to local difficulties - you could use any one remote
receiver for your loggings, stating its location and with
the owner's permission if required.
( e.g. see kiwisdr.com )
A remote listener may NOT also use another receiver,
local or remote, to make more loggings for the same CLE.
These listening events serve several purposes. They
• determine, worldwide, which beacons are out-of-service or have gone silent since the last CLE covering this range
• will indicate the state of propagation conditions at the various participant locations
• will give you an indication of how well your LF/MF receiving system is working
• give participants a fun yet challenging activity to keep their listening skills honed
Final details can be found at the NDB List website, and worldwide results, for every participant, will be posted there a few days after the event.
The NDB List Group is a great place to learn more about the 'Art of NDB DXing' or to meet other DXers in your region. There is a lot of good information available there and new members are always very welcome. As well, you can follow the results of other CLE participants from night to night as propagation is always an active topic of discussion.
You need not be an NDB List member to participate in the CLEs and all reports, no matter how small, are of much value to the organizers.
Remember - 'First-time' logs are always VERY welcome!
Reports may be sent to the NDB List Group or e-mailed to CLE co-ordinator, Brian Keyte (G3SIA), whose address appears above. If you are a member of the group, all final results will also be e-mailed and posted there.
Please ... give the CLE a try ... then let us know what NDB's can be heard from your location! Your report can then be added to the worldwide database to help keep it up-to-date.
Have fun and good hunting!