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 you use standard NATO/ITU phonetics on the air, and when are ham-style alternatives okay?

ci_cover.jpg

Looking for a practical answer on phonetic alphabet use in amateur radio. The ITU/ICAO/NATO alphabet (Alfa, Bravo, Charlie and so on) is the usual recommendation, but on the air you also hear "Kilowatt," "Washington," "Sugar," and creative words made up on the spot.

Specific questions:

1. Is there any rule that requires a particular phonetic alphabet for callsigns?
2. Are the older or informal ham phonetics a problem, or just a habit?
3. What works best in poor conditions, with QRM, QSB or a weak signal?
4. How should names, towns and grid squares be spelled without wasting airtime?
5. How do numbers, "over," "out," and prosigns fit in, especially in nets and emergency traffic?

  • Replies 2
  • Views 30
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

Rules first. In the US, FCC Part 97 requires identification in English on phone, and it encourages, but does not require, a phonetic alphabet. Other countries differ, so check your own regulator. Nothing I know of mandates one specific alphabet, but the ITU/ICAO set is the sensible default because it was designed to be understood across languages and bad audio. The official spellings are Alfa and Juliett, though most operators just say Alpha and Juliet.

Informal ham phonetics are not wrong, but they are a gamble. Words like "Kilowatt" for K, "Texas" for T or "Mexico" for M often get through fine between locals, but they depend on the listener knowing the habit. They also vary by region, and they can fail with a non-native English speaker or a weak signal. Made-up words are the worst case, because the listener has to decode the word and then guess which letter you meant. A good rule is to use the standard alphabet for your callsign whenever you are not sure the other station has you solid.

For difficult conditions, a few things help more than fancy words:

Say the callsign slowly and evenly, in the same rhythm each time. Give it once, in full, with phonetics, rather than rushing it three times. If the other station only needs a part, send just the suffix after the full call is established, and ask for confirmation if there is any doubt. The letters that get confused most are the ones that sound alike on a noisy channel: B/D/P/T/V, M/N, and F/S. Standard phonetics exist to separate exactly those. Also avoid phonetics for the whole sentence. Use them for the callsign, a name or an unusual word, and speak normally otherwise.

A typical callsign exchange, using W1AW as the example: "W1AW, this is ... Whiskey One Alfa Whiskey." Zero is "zero," not "oh," so there is no confusion with the letter O.

  • Moderators

Adding to the above, here are names, places, numbers and procedure.

Names: say the name normally first, then spell it only if needed. For example, say "Name is Smith" and, if it's not copied, "Sierra Mike India Tango Hotel." Repeating the word before and after the spelling helps the listener check what they wrote. Spell the unusual part, not every letter of a common word.

Locations: for a town, say it, then spell it once with standard phonetics if the other station asks. For grid squares, say the letters phonetically and the digits plainly, for example FN31 as "Foxtrot November three one." Where you are is your QTH, but on voice plain words are usually clearer than Q-signals when conditions are bad.

Numbers: ITU radiotelephony has special pronunciations for aviation and maritime use ("tree," "fower," "fife," "niner"), but most amateurs just say the digits clearly. The one worth borrowing is "niner" for nine, because "nine" can be confused with "five" on a noisy channel or with the German "nein." Use "decimal" or "point" for a frequency, and be consistent.

Procedure words and prosigns: on CW, prosigns like AR, SK, BT and KN have defined meanings. On voice, you use words instead. "Over" means "I'm done, your turn"; "out" means "I'm finished and not expecting a reply." Saying "over and out" together is contradictory and is a common mistake. In conversation, plenty of hams drop both and just pass the callsign, which is fine on ordinary contacts.

Nets and emergency traffic: a net control station wants short, predictable check-ins, so give your callsign once with phonetics, then wait to be called. In emergency traffic, accuracy matters more than speed. Read the message at a pace the writer can copy, spell names and numbers, and use "say again" rather than guessing. Do not use "Mayday" or "Pan-Pan" unless it is a true distress or urgent situation. Many nets also have their own rules for priority traffic, so follow the net's stated procedure.

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.