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 384.8 km/s
Aurora 1
Updated 13:30 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

How do you combine SFI, K index, WSPR and beacons to decide which band to try?

ci_cover.jpg

There are many propagation numbers and tools, and they answer different questions. I'd like to compare approaches for turning them into a decision about where to point the antenna. This is the rough framework I use for thinking about it, so please correct it where it's wrong.

Long-term and seasonal: sunspot cycle, SFI, VOACAP. The 10.7 cm solar flux (SFI) is a convenient proxy for the solar ultraviolet that ionizes the F layer. Higher SFI generally means a higher MUF, so the upper bands (15, 12, 10 m) open more often and for longer. As a rule of thumb, an SFI near 70 is solar-minimum territory where 10 m is mostly dead except for sporadic E, and values well above 100 start to make the higher bands more reliable. VOACAP-based predictors use a smoothed sunspot number and give a monthly median, so they tell you what is likely at a given hour and season, not what is happening today. They're good for planning, such as which hours to try 17 m to a given region. They're not a live band report.

Day-to-day: A index and K index. The K index is a 3-hour measure of geomagnetic disturbance on a 0 to 9 scale, and the A index is a daily figure derived from it. Quiet conditions (low K) are usually better for HF, especially on high-latitude and polar paths. Disturbed conditions can depress F2 MUF, add auroral flutter and cause absorption on paths near the poles. Solar flares are a separate problem. They can cause a sudden increase in D-layer absorption on the sunlit side of the Earth, which blacks out HF for a while, mostly on the lower frequencies.

Layers and time of day. The D layer exists mainly in daylight and absorbs lower frequencies, which is why 160 and 80 m are mostly local during the day, and 40 m is limited to shorter distances. After sunset the D layer fades and the F layer carries the signal. The gray line, the day/night terminator, can give enhanced paths because you have low absorption at the sunset or sunrise end while the F layer is still working. Paths along the terminator are worth checking on the low bands.

Shorter-range and VHF modes. Sporadic E is not tied closely to SFI. It's patchy, short-lived clouds of ionization, mostly in late spring and early summer in the northern hemisphere, with a smaller peak around midwinter. It can open 10 m and 6 m for single-hop distances of roughly 1000 to 2300 km, and occasionally 2 m. Tropospheric ducting is a different thing. It's associated with temperature inversions and stable high pressure, often over water, and affects VHF/UHF and up. NVIS is for regional coverage of up to a few hundred kilometres. You pick a frequency below the critical frequency (foF2) so the signal goes nearly straight up and comes down on the area around you. It's often 80 or 60 m at night and 40 m during the day, but at low solar activity foF2 can drop enough that 40 m skips over you at night.

Real-time checking: WSPR and beacons. Predictions and indices tell you what should happen. Spots tell you what is happening. WSPR uses very low power and weak-signal decoding, so a 1 W or 5 W transmission can show which bands and paths are open, with reports on wsprnet.org. The NCDXF/IARU beacon network on 14.100, 18.110, 21.150, 24.930 and 28.200 MHz runs a repeating 3-minute cycle, so you can listen for a few minutes and see which regions are audible on each band. For CW, RTTY and digital modes, the Reverse Beacon Network and PSKReporter show who is hearing whom in near real time.

My question is about workflow. What do you check first before you sit down to operate: indices, a prediction program, or live spots? And how do you handle cases where the numbers look bad but the spots say the band is open (or the other way round)?

  • Replies 2
  • Views 34
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

I'd go spots first, indices second. Spots tell you whether a path is open right now, and the indices explain why or help you guess what happens next. If the WSPR map shows signals on 20 m into the region you want, it doesn't matter much that the SFI looks mediocre. The reverse also happens. A decent SFI doesn't help if there's a geomagnetic storm or a flare-related blackout.

Two caveats on the spot data. First, WSPR and RBN show where stations are active, not just where propagation exists. An empty area on the map can mean nobody is transmitting or listening there. Second, a path that shows at -25 dB in WSPR may be far too weak for SSB. Compare the report with what your mode needs. WSPR decodes signals far below the level at which a voice contact is workable.

I'd use VOACAP-type predictions to decide when to be at the radio, and live spots to decide what to do once you're there. For the low bands, also check the sunrise and sunset times at both ends. The gray-line window can be short, and the indices won't tell you when it is.

  • Administrators

For the VHF side, the usual indices matter much less. SFI and K have little to say about whether 6 m will open by sporadic E tomorrow, though a very high SFI and a strong F2 can also bring 6 m openings at the peak of a solar cycle. For E-skip, what helps is watching spots and the season. Look for 10 m and 28 MHz beacons opening, then 6 m. If you see 10 m sporadic E, it's worth checking 6 m too, because the MUF of the cloud can be higher than you think. Also, E-skip usually shows up as short-skip distances first, then multi-hop if the clouds are widespread.

For tropo, forget SFI altogether and look at weather: high-pressure systems, temperature inversions, calm conditions, and coastal or over-water paths. Forecast maps for tropo ducting are published by several weather and amateur sources, and they're more useful than solar numbers for 2 m and 70 cm.

On NVIS, one practical tip is to check foF2 from an ionosonde if one is near you. If you can see the critical frequency, you can choose between 80, 60 and 40 m instead of guessing. If the critical frequency is below your operating frequency, the signal goes through the layer instead of coming back, and you get a skip zone around you. That's a common cause of 'the band seems dead but I can hear distant stations.'

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.