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 first POTA rove: UTC rollover, two-fers, 10 QSOs per park, and logging without headaches

ci_cover.jpg

I'm putting together a plan for a one-day rove through several parks and want to sanity-check the details before anyone gets burned by a logging mistake. The basics as I understand them: every park has a reference like K-0001 (country prefix, dash, number), an activator needs at least 10 valid QSOs in a single UTC day to get credit for that park, and hunters get credit by working activators, with the credit tied to the activator's uploaded log.

Here are the points I'd like the group to poke at.

First, the UTC day. If you start at a park in the late afternoon local time and the clock passes 0000Z mid-session, the QSOs split across two UTC dates. You can end up with 6 contacts on one date and 6 on the next, and neither counts as a valid activation. Checking what time 0000Z falls in your local time before you leave is cheap insurance.

Second, two-fers and three-fers. Some parks overlap, for example a state park inside a larger national trail or forest, each with its own reference. You can activate all of them from one spot if you're physically inside each boundary. Each reference needs its own 10 QSOs, and your log needs to carry every reference. The usual approach is to put the references in the park field of your logger, comma-separated, and then confirm how the upload handles it. Mapping boundaries ahead of time is worth the effort, because the parking lot can be inside one park and the picnic table you actually set up at can be in another.

Third, spotting and logging. I plan to self-spot on the POTA site or app with frequency, mode and park reference, and update the spot if I move. Spots from the Reverse Beacon Network can show up for CW and digital if you call CQ POTA, but I wouldn't count on it in a weak-signal location. For logging, I'll keep a paper backup, log in a program that supports POTA ADIF fields, and export one file per park per UTC day for upload. Does anyone have a workflow for roves that keeps those files from getting mixed up?

Fourth, equipment and rules. Power isn't a factor in the 10-QSO requirement, so QRP is fine, but each park has its own rules on things like antenna supports, trees, drones, vehicles off pavement and quiet hours. I'd rather read the land manager's page than assume an end-fed wire thrown over a branch is acceptable.

What have you found works best for rove logistics, and what would you check before leaving the driveway?

  • Replies 2
  • Views 32
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

The UTC rollover is the one that catches people. If you'll be near 0000Z, a simple fix is to put a UTC clock on your phone's home screen and plan the park order so the one most likely to run long isn't the one straddling midnight UTC. If you do end up straddling, the QSOs on each side of the line need to be counted separately, so don't assume they'll be added together.

On the two-fer, make sure your logging program is writing the references the way the POTA upload expects. If you log to a single reference by habit, you'll only get credit at one park and have to sort it out later. Do a few test entries and look at the exported ADIF before you leave home. Also remember that the 10 contacts have to be valid for each reference, so the two-fer doubles the benefit but doesn't reduce the work.

For roves, I'd keep one log per park, named with the reference and the UTC date, and I'd upload them as soon as you have signal. That way a corrupted file or a missed park shows up while you're still on the road and can still fix it.

  • Moderators

A few operating tips for getting to 10 contacts efficiently. Pick a band with a decent chance of working your target area for the time of day. 40 m and 20 m are the usual workhorses for HF, with 17 m or 15 m possible when conditions allow. Call CQ POTA clearly, give your park reference at least once per call or two, and put up a spot as soon as you're on the air. Hunters often watch the spots page, so a good spot with correct frequency and mode makes a real difference.

Don't forget that duplicates on the same band and mode generally don't count toward your 10, so if the pile thins out, changing band or mode can help you finish. Park-to-park contacts are good too because you're logging a contact that's valuable to both ends.

For antennas, a simple resonant wire or vertical works fine. The main points are that it's safe, doesn't obstruct anyone, and is allowed by the park. A longer coax run can lose a surprising amount of QRP signal, so keep the feedline short if you can.

As for awards, there are activator and hunter award tiers on the POTA site, and I'd check the current list there instead of relying on memory, since the criteria and endorsements can change.

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.