CW POTA
a field manual

Parks on the Air is a year-round operating program where one operator sets up in a designated park and makes contacts with everyone else listening from home.

Think of it as a standing invitation: pick a park from the registry (pota.app), go outside, put a radio on the air from inside the park's boundary, and work as many people as you can in one sitting. The operator in the park is the activator. Everyone chasing them is a hunter. Make ten or more contacts in a single day and the activator earns credit for that park; hunters rack up credit for every activator they catch.

The program is free, global, and entirely built around voluntary log submissions. There are no mandatory exchange formats, no timing windows, no organizers on the air. Just operators, parks, and the honor system.

You pick a side each time you sit down. Both are rewarding. Activators work harder; hunters get credit faster.

A single POTA QSO in CW takes less than thirty seconds on a quiet band. Here is one, decoded.

Newcomers read through a decoded exchange and decide they aren't ready. They are. POTA CW is the most forgiving Morse environment you will ever find — slower, warmer, and designed for people learning on the air.

On speed. Most POTA activators run between 15 and 20 words per minute. Some run slower on purpose — 12, even 10 WPM — when the bands are quiet. This is nothing like contesting. If an activator is going faster than you can copy, send QRS ("slow down") or simply ?. Almost every activator will slow down happily.

On minimum viable copy. You do not need to decode every character. For a hunter, the entire exchange hinges on three things:

Everything else — the TU ES GM, the pleasantries, the double-sent state — is decoration. Miss it all and you still have a valid QSO in the log.

On the question mark

The single most useful character in CW is ?. It means "I didn't copy that — please repeat." Sent alone, it's universally understood. Sent after a fragment, like W6?, it means "I got W6, please send the rest again."

You will send ? constantly when you're starting out. Everyone does. Experienced operators send it too. Asking for a repeat is not a confession of incompetence; it's just normal CW traffic. The only failure is sitting silent and letting a QSO collapse.

Hunters don't wander the bands hoping for luck. They watch the spots.

Open pota.app in a browser and click Spots. Every active CW station in a park shows up there, with their frequency, callsign, park reference, and how fresh the spot is. Filter by mode = CW and you have a live list of people calling you to work them. Click a row, tune the radio, wait for them to finish their current QSO, and answer.

A second channel runs in parallel: the Reverse Beacon Network (reversebeacon.net). Skimmers around the world decode CW CQs automatically. Activators who self-spot via RBNgate also land on pota.app within seconds. If you're an activator running QRP from a new park, the RBN is how the hunters find you.

CW operators tend to congregate around these frequencies. Of these, 20 meters is the undisputed center of gravity for POTA — it's where the most activators run, the most hunters listen, and the most contacts happen. If you have time for only one band, make it 20.

POTA runs on log submissions. Hunter credit is automatic. Activator credit requires a file upload. Here is the minimum each operator needs to capture.

Every QSO needs six fields: the other operator's callsign, the date and time in UTC, the frequency or band, the mode (CW), the RST you sent, and the RST you received. Activators additionally need to tag the whole session with their park reference (e.g. K-0802) and, if the park is in more than one POTA entity, each reference gets logged separately.

1. Pick a logger

   A few good options, depending on platform and taste:

   • Carrier Wave — native macOS/iOS app purpose-built for POTA and contest CW. Integrates with pota.app spots, handles park references automatically, and syncs across your devices.
   • Ham2K Portable Logger (POLO) — iOS / Android / desktop. Excellent field UX. Popular with activators who log on a phone.
   • HAMRS — free cross-platform desktop app. POTA-aware out of the box.
   • N3FJP — Windows. Well-established. The choice if you already live in a Windows logging ecosystem.
   • Paper — a waterproof notebook and a pencil. Transcribe to ADIF when you get home. Never runs out of battery, never crashes, never asks for an OS update. Thomas K4SWL has run paper logs for years and makes a compelling case that it keeps you focused on the radio instead of the screen.

   All of them (except paper) export .adi (ADIF), which is what pota.app wants.

2. Log in real time, not from memory

   Write down the callsign as you copy it. The exchange is short but you will forget the third QSO by the time the fifth finishes. Times are UTC — set your logger to UTC once and never think about it again.

3. Export to ADIF

   After the activation, export the session to a .adi file. Double-check that every record has STATION_CALLSIGN (you), MY_SIG_INFO or POTA_REF (the park), and CALL (the hunter). Most POTA-aware loggers fill these automatically.

4. Upload to pota.app

   Sign in. Click My Stats → Submit Logs. Pick the park reference, the UTC date, and drop in your .adi. The system parses the file, shows you a preview, and posts the activation within minutes. Hunters get their credit the moment your upload is processed.

5. Hunters: do nothing

   Seriously. POTA doesn't want your log. Hunter credit comes from the activator's submission matching your callsign. You can still track personal stats by exporting your own log to LoTW or QRZ, but that's for you — not for POTA.