ⓘ 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 — 70cmvia PSKReporter · scroll or pinch to zoom
Band
Mode
Time
Loading map data…
MHzDXSpotterInfo
Recent spots—
Select a band above to load spots
Ready — select a band to fetch live spots
Planning a first POTA activation: park references, 10 QSOs, spotting and logging basics
Putting together a checklist for a first Parks on the Air activation, and I'd like input on what trips people up most often. Here is the basic framework as I understand it. Please correct anything that has changed, because the official POTA rules and the pota.app documentation are the final word.
Park references. Every park has a reference made of a entity prefix and a number, such as K-0001 for a US park. Other countries use their own prefixes. Look up the exact reference in the POTA app or on the park's page before you go, and write it on your log sheet or enter it in your logger. Some places have more than one reference, which is where two-fers come in.
Activator vs. hunter. The activator operates from inside the park boundary. The hunter works the activator from anywhere, including home. Each role has its own credit and its own awards track. You can do both, but the log and upload steps differ.
The 10-QSO line. An activation is generally counted as valid once you have 10 contacts from the park within a single UTC day. Plan around UTC, not local time, especially if your operating window crosses midnight UTC. Contacts made before and after the UTC rollover are counted on different days, so they don't add up to one activation.
Spotting. Hunters find you through spots on pota.app. You can self-spot through the site or app, and on CW and some digital modes automated spotting may pick you up. A good spot has the right frequency, mode and park reference. If you move frequency, update the spot. When you finish, post a QRT or sign-off note so hunters don't keep calling a dead frequency.
Logging. Most people log in a program that exports ADIF, and the upload needs the park information in the correct fields. The POTA-related fields are SIG and SIG_INFO for the park you worked, and MY_SIG and MY_SIG_INFO for the park you are in. Check the current upload guidance on the site, because malformed logs are a common reason for credit not showing up.
Antennas and power. There is no required power level, so anything from QRP to 100 W is workable. What matters more is a station you can deploy quickly within what the park allows. Common options include an end-fed half-wave, a linked dipole, a vertical with radials, or a portable mast. Check the park's rules on trees, stakes, mast guying and vehicles, since these vary and some parks restrict them. Also check whether a permit or a different park manager's approval is needed.
Rove and two-fer. A rove means activating several parks in the same outing or day. Each park still needs its own 10 contacts in the UTC day to count. A two-fer or multi-fer is a location covered by two or more park references, such as overlapping park designations. You log each contact for every reference you're in, and each reference needs 10 contacts to be valid. Say both references when you call or spot so hunters can log them correctly.
Questions for everyone: What is the best way to schedule band changes when you're short on contacts? How do you decide between SSB, CW and FT8 for a first activation? And what is the one piece of kit you'd add to a minimal go-bag?
Putting together a checklist for a first Parks on the Air activation, and I'd like input on what trips people up most often. Here is the basic framework as I understand it. Please correct anything that has changed, because the official POTA rules and the pota.app documentation are the final word.
Park references. Every park has a reference made of a entity prefix and a number, such as K-0001 for a US park. Other countries use their own prefixes. Look up the exact reference in the POTA app or on the park's page before you go, and write it on your log sheet or enter it in your logger. Some places have more than one reference, which is where two-fers come in.
Activator vs. hunter. The activator operates from inside the park boundary. The hunter works the activator from anywhere, including home. Each role has its own credit and its own awards track. You can do both, but the log and upload steps differ.
The 10-QSO line. An activation is generally counted as valid once you have 10 contacts from the park within a single UTC day. Plan around UTC, not local time, especially if your operating window crosses midnight UTC. Contacts made before and after the UTC rollover are counted on different days, so they don't add up to one activation.
Spotting. Hunters find you through spots on pota.app. You can self-spot through the site or app, and on CW and some digital modes automated spotting may pick you up. A good spot has the right frequency, mode and park reference. If you move frequency, update the spot. When you finish, post a QRT or sign-off note so hunters don't keep calling a dead frequency.
Logging. Most people log in a program that exports ADIF, and the upload needs the park information in the correct fields. The POTA-related fields are SIG and SIG_INFO for the park you worked, and MY_SIG and MY_SIG_INFO for the park you are in. Check the current upload guidance on the site, because malformed logs are a common reason for credit not showing up.
Antennas and power. There is no required power level, so anything from QRP to 100 W is workable. What matters more is a station you can deploy quickly within what the park allows. Common options include an end-fed half-wave, a linked dipole, a vertical with radials, or a portable mast. Check the park's rules on trees, stakes, mast guying and vehicles, since these vary and some parks restrict them. Also check whether a permit or a different park manager's approval is needed.
Rove and two-fer. A rove means activating several parks in the same outing or day. Each park still needs its own 10 contacts in the UTC day to count. A two-fer or multi-fer is a location covered by two or more park references, such as overlapping park designations. You log each contact for every reference you're in, and each reference needs 10 contacts to be valid. Say both references when you call or spot so hunters can log them correctly.
Questions for everyone: What is the best way to schedule band changes when you're short on contacts? How do you decide between SSB, CW and FT8 for a first activation? And what is the one piece of kit you'd add to a minimal go-bag?
Link to comment
https://www.hamradiobase.com/forums/topic/11164-planning-a-first-pota-activation-park-references-10-qsos-spotting-and-logging-basics/Share on other sites