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

When should hams stick to the standard phonetic alphabet, and when are alternatives acceptable?

ci_cover.jpg

I'm trying to sort out good practice for phonetics on the air. The NATO/ITU alphabet (Alfa, Bravo, Charlie and so on) is what most people point to as the standard. On the bands, though, you hear plenty of improvised words, especially for callsigns.

The questions I'd like help with:

1. Is there a rule that says which phonetic alphabet you have to use, or is it just convention?
2. When conditions are poor, does it help to swap in different words, or does that make things worse?
3. What's the best way to handle names, place names, numbers and prosigns?
4. Do nets and emergency traffic call for stricter habits than a casual ragchew?

I'm after practical answers, not just "use the standard one."

  • Replies 2
  • Views 21
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

On the rules: in the US, the FCC's station identification rule allows a phonetic alphabet but doesn't mandate one specific list. The wording is about using an easily understood phonetic alphabet, so the regulation doesn't force NATO words. Other countries differ, so check your own regulator. The practical standard is the ITU/ICAO/NATO list. Its words were chosen and tested to stay distinguishable across languages and noisy channels. The official spellings are Alfa and Juliett, and Whiskey, X-ray and Yankee round out the tricky ones.

Improvised words are fine in a good-signal ragchew, and plenty of operators like a personalized suffix. The problem is that a station copying you through noise or an accent has to guess whether your word is meant as a letter. Words like "Lima" and "Mexico" are well known, but novelty words can be misheard as a different letter. For your callsign, especially when working DX or a pileup, the standard words win because the listener expects them.

In difficult conditions the usual advice is to slow down rather than change the words. Say the callsign at an even pace, give it once or twice, and don't run the letters together. If the other station keeps getting one letter wrong, repeat only that letter with its standard word. The most commonly confused letters are B, D, P, T, V and E, plus M and N and F and S, so those are the ones where phonetics matter most. If the other operator suggests a different word for the letter, switch to it. The goal is that they copy it, not that you stick to a pet word.

Older sets like "Able, Baker, Charlie" (a WWII-era list) or local police-style lists still turn up. Each has its own words, so mixing two systems in one callsign can confuse a listener. Pick one list per transmission.

  • Moderators

Adding to the above for names, numbers, prosigns and nets.

Names and locations: say the word normally first, then spell only if needed. For example, give the town name, then say "I spell" and go through the letters phonetically. Don't spell every word in a sentence, because it just slows the exchange. For locations you might add a Maidenhead grid square or coordinates when the name is unusual. Spelling the first few letters is often enough to resolve it.

Numbers: speak digits one at a time. Say "one four seven" rather than "a hundred forty-seven" for anything that must be copied exactly, like frequencies, grid squares, serial numbers or addresses. The ICAO-style pronunciations ("niner" for 9, and so on) are used in aviation and some ham circles, but they're a convention rather than a requirement. "Niner" is common because "nine" can be confused with "five" or with the German "nein" in some environments, but plain digits are fine on most ham bands as long as they're clear.

Prosigns: in voice, the equivalents are words. "Over" means you're handing the channel back and expect a reply, and "clear" or "out" means the contact is finished. "Over and out" is contradictory, so avoid it. In CW, prosigns are sent as a single run-together character, such as AR for end of message, SK for end of contact, K or KN to invite a reply, and BT as a separator. Don't mix CW prosigns or Q-signals into plain voice traffic where listeners may not know them.

Nets: net control usually asks for check-ins by callsign suffix, the last letters of the call, to keep things fast. If you check in, say your suffix phonetically once and wait for acknowledgement. Don't give long-winded signoffs, because net control is managing a queue. Say your location and status or traffic if asked, and keep to the net's format.

Emergency traffic: during a real emergency, clarity beats style. Break in only with emergency or priority traffic, say it plainly, and use phonetics for callsigns, names and anything that can't be mistaken. Many served-agency and incident-management guidelines recommend plain language over ten-codes or personal shorthand, since different agencies use different codes. In an exercise, the traffic should clearly state that it is an exercise so no one mistakes it for a real event. Repeat critical items, such as names, addresses and numbers, and read them back to confirm.

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.