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 412.9 km/s
Aurora 1
Updated 14:00 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

Phonetics on the air: when to use the ITU alphabet, when "creative" phonetics hurt, and how to handle callsigns, names, numbers and nets

ci_cover.jpg

I'd like to collect practical thinking on phonetics in one place. Here are the questions I want to cover.

1) Is the ITU/NATO alphabet the best default for ham callsigns, or do traditional ham-style words (and the funny ones) work just as well? 2) What do you do when conditions are poor and the other station still can't copy you? 3) How should names and locations be spelled without turning every transmission into a spelling bee? 4) How do numbers, prosigns and procedural words fit in, especially on nets and emergency traffic?

To start the discussion: the ITU/ICAO alphabet is 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 odd spellings "Alfa" and "Juliett" exist so that speakers of different languages pronounce the words as intended. The words were chosen to be distinct across many language backgrounds, which is why they work well on international bands. Words like "Adam, Boy, Charlie" or "Able, Baker" are older or regional traditions and don't have that testing behind them.

On the rules side, an amateur phone ID is normally given in English in many countries, and in the US the FCC rules encourage a phonetic identifier without requiring one. Check your own licensing authority's wording rather than relying on memory. In practice, the standard alphabet is the safest choice when you can't be sure who is listening.

So where do you draw the line between standard and improvised phonetics?

  • Replies 2
  • Views 50
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

My rule of thumb is to default to the ITU words and improvise only as a repair tool. If someone keeps getting one letter wrong, switching to a different word for that letter is legitimate. Say "M as in Mike" the first time, and if it still doesn't copy, try a clearly different word. The point is to change what the ear receives, not to be clever.

The trouble with freelance phonetics is that a listener has to decode the word and then map it back to a letter. If you say "Kilowatt" for K, a weak-signal listener may hear only "-watt" and wonder whether you meant W. Your own favorites also vary a lot by region and generation, so a word that is obvious to you may be a coin flip for a DX station. Words that sound alike are the worst offenders, such as "Mexico" and "Texas" in noise, or "Nancy" and "Mary" when the consonants are masked.

For delivery, a few habits make the standard alphabet more effective. Keep a steady, slightly slower pace. Give each word its natural stress, like KEY-loh, LEE-mah, keh-BECK and pah-PAH. Pause briefly between the prefix, the number and the suffix. For example, with a US-style call, say the prefix letters, the digit, then the suffix as separate chunks. Then repeat the whole callsign once at a measured pace rather than rattling it off faster the second time.

  • Moderators

Numbers, prosigns and nets each have their own conventions, so here are some thoughts on each.

Numbers: say digits individually, and use "zero" rather than "oh" in callsigns and grid squares so there's no confusion with the letter O. "Niner" for 9 is widely used because "nine" can be mistaken for "five" or "nein" on a bad channel. The full ITU number words (Nadazero, Unaone, Bissotwo and so on) are rarely heard on ham bands, and most operators would be puzzled by them. Grid squares are handled as letters and digits, so FN31 is Foxtrot November three one.

Names and locations: say the word naturally first, then spell it, because the word gives the listener context for the letters. For a place, say the town, then the state or country, and spell only the unusual part. Don't phonetically spell "Smith" every time, but do spell a surname with an ambiguous spelling or a name the other op will likely have to log.

Prosigns and procedure: on CW, prosigns like AR (end of message), SK (end of contact), BT (break), KN (go ahead, named station only) and K (go ahead) carry procedural meaning. On voice, use plain words: "over" or "go ahead", "clear" or "this is [call] clear", and "break" for interrupting. Avoid saying "over and out" together, since the two have opposite meanings (expecting a reply vs. finished).

Nets: many nets ask for check-ins by suffix or last two or three letters, then the net control repeats the full call phonetically to confirm. Wait for net control to finish before transmitting, and answer only to your own call. For emergency traffic, use plain language, say exactly what you need, give the key details (who, what, where, how many), and spell only critical or unusual items. Voice nets generally discourage Q-signals and 10-codes because plain English leaves no room for mismatched meanings. Always follow the net's or served agency's own procedures if they differ from this.

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.