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

Planning a combined POTA and WWFF activation: KFF references, the 44-QSO line, and logging

ci_cover.jpg

I'd like to collect practical notes on running WWFF (World Wide Flora and Fauna) activations, especially when the same site is also a POTA entity. The programs overlap a lot, but they are not identical, and the differences are where people tend to get caught out.

References. WWFF references use a national prefix plus FF and a number. In the US that is KFF-####, Germany is DLFF-####, Australia is VKFF-####, and so on. POTA uses K-#### in the US. A national park, state park, wildlife refuge or nature reserve may carry both references, but the boundaries and the mapping are not always one-to-one. One POTA park can sit inside a larger WWFF area, and sometimes the reverse. Check both reference lists and maps before you leave, not from the operating position.

Activation thresholds. As I understand it, POTA counts an activation at 10 QSOs, while WWFF asks for a minimum of 44 QSOs for an activation to be valid. That 44 figure changes how you plan the session. Ten contacts on 20 m SSB is a normal POTA outing. Forty-four needs a decent band, a good spot, and probably a second band or mode. Please confirm the current wording on the WWFF site, including how multi-day or multi-session QSOs are treated, because rules get updated.

Operating. On the air, I'd keep it simple: "CQ POTA, CQ WWFF" followed by your callsign, and give both references when asked. Hunters chasing only one program will usually tell you which reference they need. Self-spot on whichever spotting systems apply to each program, and update the frequency if you move. If you change bands, post a new spot, or hunters will keep looking at the old one.

Logging. Keep the references straight in your logging software. For ADIF, the usual approach is MY_SIG and MY_SIG_INFO for your own reference, with WWFF and POTA each needing their own correct entries. Many people export separate files per program to avoid mismatched references. Then upload the WWFF log through the official WWFF logging or upload system and the POTA log through the POTA site. Check each system's accepted format before upload day.

Permissions. This is the part that no award rule can settle. Parks and reserves differ on antenna masts, tripods, vehicles off-road, hours, fees and permits. Some sites forbid anything that stakes into the ground or goes up a tree, so read the site's own rules first.

Questions for the thread: How do you handle a site that has a POTA reference but no WWFF reference, or the other way around? What is your approach to reaching 44 contacts without turning the activation into a marathon? And which ADIF and logging workflow keeps your two uploads clean?

  • Replies 2
  • Views 68
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On the 44-QSO target, I'd plan for two bands from the start rather than hoping one holds up. A common approach is to start on the band with the best expected propagation for the time of day, work the pileup until it thins out, then move and re-spot. Hunters who missed you on the first band often show up on the second. If the park allows it, CW and SSB together can also help, because it pulls in two different groups of hunters. FT8 or other digital modes can fill the gap if the rules allow them, but check that the WWFF program accepts that mode for the award or activation you're after.

On dual-reference operating, I'd also say the reference twice in each exchange, one program at a time, so the hunter can log it without asking. Something like "KFF-1234 and K-5678" gets old fast, but it prevents repeats when the band is noisy.

  • Administrators

For logging, the main trap is that a single log with both references stuffed into one field can break one upload or the other. I'd keep the master log in whatever logger you normally use, then export per program with the correct reference in the field the importer expects. Before leaving, do a test import of a couple of dummy QSOs if the system lets you, or at least compare a sample record against the format described on the WWFF site and the POTA site.

The other thing I'd check is callsign handling. If you operate with a portable suffix or a reciprocal prefix, make sure the callsign in your log matches what hunters would have logged. Mismatches there cause more confusion than reference typos. And if the site only exists in one program, just activate it for that program. It is better to have a clean, valid log for one than a questionable double-credit for two.

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.