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

POTA basics: getting from a park reference to 10 logged QSOs (activator and hunter notes)

ci_cover.jpg

I'd like to pull together a practical checklist for people new to Parks on the Air, from either side of the pileup. Please correct anything that has changed or that I've oversimplified, because the official POTA site and each park's page are the final word.

Park references. Every park has a reference made of a entity prefix and a number, such as K-0001. K is the prefix for the United States, and other countries use their own. Look up the exact reference on the POTA site before you go. Similar names, adjacent units and parks that share a boundary can all trip you up, so confirm that the reference you spot and log matches the park you are standing in.

Activator. You operate from inside the park boundary and need at least 10 QSOs on a single UTC day for the activation to count. UTC is the part people forget, since your local evening can straddle UTC midnight. Check the park's rules and access hours first. Rules on antenna supports, vehicles, fires, and where you may set up vary from park to park, and the park manager's rules apply on top of anything POTA says.

Hunter. A hunter works activators from home, mobile or portable. Hunters have no 10-contact threshold. Each confirmed park QSO counts toward hunter totals once it matches the activator's uploaded log. That means a clean exchange of callsigns and a correct log entry matter more than a long chat.

Spots. Activators typically self-spot on the POTA site or app with their callsign, frequency, mode and park reference, and hunters watch that list. A spot is worth updating if you QSY. Before you spot, listen to make sure the frequency is clear, and after you spot, be ready for a pileup to form quickly.

Antennas and power. This is a wide-open area. Many people use a QRP rig with an end-fed half-wave or a vertical with a few radials, while others bring 100 W and a dipole on a mast. Either way works, and band choice and timing often matter more than raw power. Keep gear from creating a trip hazard or damaging trees, and respect any local limits on how you put up wire.

Logging. Use a logger that can record the park reference in the proper ADIF fields, then upload the log to the POTA site after the activation. Some loggers have POTA-specific templates. If you rove or work a two-fer, check that the references on every QSO are exactly right.

Questions for the thread: How do you handle logging for a two-fer? Do you have a routine for roving between parks in one UTC day? And what is the most useful habit you'd recommend to someone about to run their first activation?

  • Replies 2
  • Views 35
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On two-fers and roving, the key point is that each park is evaluated separately. A two-fer is a location that sits inside two (or more) POTA references, for example a state park overlapping another designated area. You work one set of contacts, but each QSO is logged against each reference. Each park needs its own 10 QSOs, and the same contacts can count toward both if you log them correctly. Many loggers let you enter multiple park references on one QSO, but check how yours exports, because a malformed multi-park field is one of the more common reasons a log fails to match.

For a rove, plan the UTC day, not your local day. Each park is a separate activation with its own log, so it helps to keep separate ADIF files, or to confirm that your logger splits them cleanly. Also allow for setup and teardown time. It is easy to underestimate how long it takes to reach 10 contacts when band conditions are poor, so have a fallback plan, such as a second band or mode, before you decide to move on.

  • Moderators

From the hunter side, a few habits make life easier for activators. Listen for the full callsign before you call, because an activator is often working through a stack and a partial call wastes everyone's time. Keep your exchange short, which is usually callsign and signal report, and leave extra conversation for a quiet moment. If you are chasing a rare entity or a first-time park, spotting yourself on the activator's frequency is not a thing to do. The activator spots, and you hunt.

Also upload your own hunter log, or confirm that the site matches your contacts automatically, depending on how your logging setup works. If a QSO doesn't appear, the likely cause is a mismatch in time, callsign or park reference between the two logs, so compare the details before assuming the activator missed you. On awards, the site lists the hunter and activator milestones and endorsements. Check it directly for the current criteria rather than relying on what people remember, since programs adjust over time.

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.