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

Which phonetics should I use on the air? NATO/ITU vs. "ham" phonetics, bad conditions, nets and emergency traffic

ci_cover.jpg

I'm fairly new to HF and VHF voice work and want to tighten up my on-air habits. I'm trying to sort out a few things.

First, what is the "NATO" phonetic alphabet, and is it the same as the ITU one? Second, are the creative phonetics I hear on the bands (funny words for each letter of a callsign) a problem, or just a harmless tradition? Third, how should I handle numbers, names, locations and grid squares in poor conditions? Finally, how does this change on a net or when handling emergency traffic, and do prosigns matter on voice?

I'd like to hear what actually works in practice, and where the common advice is just habit.

  • Replies 2
  • Views 11
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

The "NATO" alphabet, the ICAO alphabet and the ITU radiotelephony alphabet are for practical purposes the same list of 26 words: Alfa, Bravo, Charlie, Delta, Echo, Foxtrot, Golf, Hotel, India, Juliett, Kilo, Lima, Mike, November, Oscar, Papa, Quebec, Romeo, Sierra, Tango, Uniform, Victor, Whiskey, X-ray, Yankee, Zulu. The official spellings are "Alfa" and "Juliett" so that non-English speakers pronounce them correctly. On the air, almost everyone says and writes "Alpha" and "Juliet", and that is fine.

The list was designed and tested so the words are distinct across many native languages, not just English. That is why it works well for international contacts. Making up your own words has no legal penalty in most places (check your own regulator's rules, as I wouldn't assume every country is identical), but a non-native listener who has memorized the standard list may not recognize "Kentucky" for K or "Radio" for R. Words like "Lima" and "Mike" are well known, whereas a personal word may need a second to decode, and in weak signals that second matters.

My practical rule is to use the standard words by default, especially on DX, in contests, or with anyone whose first language may not be yours. On a local FM repeater with friends, nobody will care much. Just don't rely on a clever word you've used for years being understood by a stranger.

On numbers, the ITU list also defines special number words (Nadazero, Unaone, Bissotwo and so on), but they are almost never used by hams. What you do hear in aviation-influenced speech is "niner" for 9, which keeps 9 from being confused with "five" or "nein", plus sometimes "tree" and "fife". For ham use, saying each digit clearly and separately is normally enough, with "niner" as an option if 9 keeps getting lost. Say callsign digits individually, so "W1AW" is "W, one, A, W", not "W-eighteen".

  • Moderators

On difficult conditions, the biggest improvement usually isn't a different word list but how you deliver it. Slow down, say the callsign once with phonetics, pause, then repeat it. Don't speed up when someone asks for a repeat. If the other station gets one letter wrong, correct only that piece: "the third letter is Sierra, S as in Sierra". If a standard word keeps failing, offer an alternate that is distinct from the confusing neighbor. Letters like B, D, P, T, V and E, or F and S, and M and N are the usual troublemakers, and the phonetic words exist to separate them.

For names and places, spell only what is likely to be misheard. "My name is Jon, J-O-N" with phonetics if needed. Give a town once, and spell it if unusual. For grid squares, say each character, like "Foxtrot November three one", and repeat if the other operator is logging it. Slashes are generally voiced as "stroke" or "slash", and "portable" or "mobile" are sometimes added after the callsign when appropriate for the station's rules.

Prosigns are mainly a CW thing: AR (end of message), SK (end of contact), BT (break or pause), KN (go ahead, specific station). On voice you use procedure words instead: "over", "clear", "say again", "break", and "go ahead". Don't say "over and out"; the two mean different things. Also "roger" means message received, not "yes".

On nets, the phonetic part is mostly check-ins. A net control often asks for the suffix of your callsign only, "Kilo Alfa Bravo", which is faster than the full callsign. Follow the net's own procedure, because they vary. In emergency traffic, plain language is the safer habit, so skip 10-codes and jargon, and spell names, addresses and numbers carefully. Many emergency communications groups have the receiver read the message back for accuracy. Real distress voice calls use words like "Mayday" and "Pan-pan" for maritime or aviation, but ham operators handling emergency traffic should follow the local group's or served agency's procedures and their licensing rules rather than improvising.

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.