Skip to content
View in the app

A better way to browse. Learn more.

Ham Radio Base

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Ham Radio Base — Education, Resources, Projects and Community
☀ Solar
SFI 99
SN 26
A 6
K 0 Quiet
X-Ray B2.3
Wind 412.9 km/s
Aurora 1
Updated 14:00 UTC HamQSL · N0NBH
Day 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor
Night 80/40m Good 30/20m Good 17/15m Fair 12/10m Poor

Callsign Lookup
_
Vanity Call Signs Available
Enter filters above and click Search.
ⓘ Callsign lookups are in real time via the FCC database. Vanity callsign availability is refreshed daily at 6:00 AM CST. The vanity search may be unavailable for a few minutes during this update.
Live DX spots
Live DX Spots — 70cm via PSKReporter · scroll or pinch to zoom
Band
Mode
Time
Loading map data…
MHz DX Spotter Info
Recent spots —
Select a band above to load spots
Ready — select a band to fetch live spots

Checking a band before you call CQ: how do you combine SFI, K-index, WSPR and beacons?

ci_cover.jpg

Predictions and real-time tools don't always agree, so I'd like to compare how people actually decide whether a band is worth trying. Here is a rough framework to pick apart.

1. Start with the big picture (solar flux and sunspots). The 10.7 cm solar flux index (SFI) is a convenient proxy for the ionizing radiation that builds the F2 layer. In general, a higher SFI means a higher MUF, so 15, 12 and 10 meters are more likely to support F-layer paths. At the low end of the ~11-year cycle, 20 meters carries most of the daytime DX and the higher bands are often dead except for sporadic E. SFI is a daily number, though. It tells you what is possible, not what is open right now.

2. Check for disturbance (A and K). The K-index is a 3-hour measure of geomagnetic disturbance on a 0 to 9 scale, and the A-index is a daily average on a linear scale. Quiet conditions (low A, K of 0 to 2) usually give stable F-layer paths. A rising K, especially on paths crossing high latitudes, often means deeper fades, flutter and weaker signals. Storms can also depress the MUF. Flares are a separate problem. An X-ray burst increases D-layer absorption on the sunlit side of the Earth and can cause a sudden HF blackout, which mostly affects lower HF in daytime.

3. Think in layers. The D layer exists only in daylight. It absorbs 160, 80 and 40 meters during the day, which is why those bands are mostly local then and open up for DX after dark. The F layer (F1 and F2 by day, merging at night) does the long-distance refraction. The MUF is the highest frequency that will be returned for a given path, and the useful window is between the MUF and the lowest usable frequency, where absorption starts to win. Sunrise and sunset along the path matter too: the gray line, or terminator, can give enhanced low-band paths because D-layer absorption is falling at one end of the path while the other end is still favorable.

4. Don't forget the non-F2 modes. Sporadic E gives short-skip openings on 10 and 6 meters, sometimes 2 meters, and is most common in the Northern Hemisphere in early summer, with a smaller peak in midwinter. It is not tied to the sunspot cycle in a simple way. Tropospheric ducting is a weather effect that depends on temperature inversions and high pressure, and it extends VHF and UHF well beyond line of sight. It is common along coasts and over water. NVIS is a different goal altogether: near-vertical paths for regional coverage out to a few hundred miles. You pick a frequency below the critical frequency of the F layer, typically 80 or 40 meters (or 60 meters where allowed), depending on time of day, and use an antenna with a high takeoff angle.

5. Use real-time evidence. VOACAP and similar tools give monthly median predictions from a smoothed sunspot number. They are good for planning which bands and hours to try, not for telling you whether the band is open this minute. For that, I'd use:

  • WSPR: low-power signals on a 2-minute schedule, with reception reports posted to wsprnet. It's great for seeing real paths and SNR, but spots depend on who is transmitting and listening, so an empty map doesn't prove a band is closed.
  • Beacons: the NCDXF/IARU network on 14.100, 18.110, 21.150, 24.930 and 28.200 MHz rotates through a 3-minute cycle, with each station stepping down in power during its slot. Hearing the 100 W transmission but not the 1 W one tells you something about margin. There are also beacons on 50 MHz and above for 6 meters and VHF.
  • Spotting networks: Reverse Beacon Network and PSKReporter show who is hearing whom on CW, RTTY and digital modes.

So my questions for the thread: what order do you check things in? When the forecast says a band should be open and the beacons say otherwise, which do you trust? And has anyone found a good way to correct for the biases in WSPR data?

  • Replies 2
  • Views 33
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

I'd treat the forecast as a hypothesis and the beacons as the test. A common routine is to look at SFI and K to decide which band to try, then tune to the NCDXF frequency for that band and listen through one full 3-minute cycle. Because each beacon steps down from 100 W to 100 mW, you can see how much margin the path has. If you only hear the 100 W transmissions, the band is marginal and it may not support a normal CQ. If you hear the 1 W or 0.1 W slots, there is a lot of signal to spare.

The caveat is geography. The beacons only cover the paths from where they are, so a quiet frequency might just mean none of them have a path to you, not that the band is shut. That's where WSPR or PSKReporter help, because you can see your own transmitted signal being decoded at distant stations, which is the direct answer to "can they hear me?"

  • Moderators

On the WSPR bias question, the main things to keep in mind are that the spots reflect where the receivers are, not where the propagation is. Heavily populated regions show lots of paths, while the ocean and polar regions look empty because nobody is listening there. Also, WSPR uses very low power and a narrow decode bandwidth, so a path with a good WSPR SNR can still be too weak for SSB. A rough rule is to compare SNR figures with what your mode needs. Digital modes can work at a negative SNR, but SSB needs a strongly positive one in a 2.5 kHz bandwidth, so a path at -20 dB in WSPR is nowhere near enough for voice.

For a fair comparison, use the same transmit power and antenna across tests, and look at many spots over an hour instead of a single one. For VHF, remember that sporadic E and tropo ducting can be short-lived and patchy, so spot clusters on 6 or 2 meters change quickly, and a map that was lively ten minutes ago may not mean much now. And for NVIS planning, a VOACAP run for short paths, or a look at ionosonde critical-frequency data if you have access, will say more than SFI will.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Affiliate Disclosure: As an Amazon Associate, Ham Radio Base earns from qualifying purchases. Some links throughout this website may be affiliate links. If you purchase a product through one of these links, we may earn a commission at no additional cost to you. Your support helps us continue creating free articles, tutorials, reviews, and resources for the amateur radio community. N0TLB © Ham Radio Base - Powered by the Ham CQ DX Community. All rights reserved.

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.