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

On-air etiquette basics: CQ calls, breaking in, nets and handling interference

ci_cover.jpg

Most new operators know the technical side before they feel comfortable with the social side of the air. Etiquette is where a lot of hesitation comes from: how long to listen, whether you're allowed to jump into a conversation, and what to do when someone is on "your" frequency. This thread is for collecting practical habits that make the bands and repeaters more pleasant for everyone. Rules differ by country and license class, so check your own regulator's requirements alongside these habits.

Here's a starting framework to react to.

Listen first, and longer than feels necessary. Before you transmit on a frequency, listen long enough to know whether it's in use. On HF, a weak station on one side of a QSO can be hard to hear, so ask "Is this frequency in use?" (or "QRL?" on CW) and wait for a real pause before assuming it's clear. If someone answers, back off politely. Nobody owns a frequency, even if a group has used it for years.

Keep CQ calls short and easy to copy. A good CQ is a few repetitions of CQ, your callsign given clearly (phonetics help on weak or noisy bands), and then a pause to listen. Long strings of CQ with a callsign at the end make it hard for someone tuning past to know who's calling. For special activities, say what you're doing, such as a park or summit activation, so the right people can find you. On a repeater, you generally don't call CQ. Just say your callsign and that you're monitoring or available.

Identify properly. In the US, the rule is to give your callsign at the end of a communication and at least every 10 minutes during it. Other countries have their own intervals, so don't just assume. During a rag chew, giving your callsign at natural pauses helps listeners and keeps you compliant.

Breaking in is where habits vary by mode. On a repeater, wait for a gap between transmissions and give just your callsign, so the others know you'd like to join. Saying "break" is traditionally reserved for urgent or emergency traffic on many repeaters, so don't use it casually. On HF, stations in a QSO usually pass the frequency back and forth, so a short callsign between overs is the usual way to ask to join.

Nets run best when everyone follows the net control's lead. Net control sets the format, calls for check-ins, and keeps traffic orderly. Participants should listen to the opening for the net's procedures before checking in, wait for the call for check-ins, and give a callsign (and name or location only if requested) without a speech. If you're not asked a question or don't have traffic, stay off the air so net control can keep the pace.

Interference is the hardest part to handle gracefully. Don't retaliate or engage on the air with someone deliberately causing trouble. Ignoring it usually works best. If it's accidental, such as a station tuning up or two stations unaware of each other, a brief and polite note often fixes it. For persistent or unlawful interference, log the time, frequency and details, and use the proper channels, such as a local repeater coordinator, a band-plan body, or your regulator, rather than escalating on the air.

Which of these do you think new operators most often get wrong, and what's one habit you'd tell someone to adopt before their first HF or repeater contact?

  • Replies 2
  • Views 29
  • Created
  • Last Reply

Top Posters In This Topic

Featured Replies

  • Moderators

I'd add that "listen first" applies to the whole conversation as well as the frequency. If you spend a few minutes just monitoring a net or a busy repeater, you pick up how it runs: whether check-ins are by suffix, whether there's a long preamble, whether people say their name or just their call. Every group has its own habits, and matching them is usually the easiest way to fit in.

For CQ calls, one useful test is whether a stranger tuning past could write down your callsign after one pass. If it takes three repeats of CQ before they hear it, the call is too long. A couple of CQs, your callsign slowly and clearly, then listen properly. Standard phonetics are better than clever ones, especially in noisy conditions or when your signal is marginal.

  • Administrators

On shared frequencies and repeaters, the bigger issue is often the length of a transmission rather than who's allowed to talk. Leave gaps between overs on a repeater so someone can get in, especially if there may be urgent traffic. It's also worth remembering that a repeater is a shared resource. If you and one other station are having a long conversation, simplex is often a better place for it, and it frees the repeater for others.

On interference, I'd stress documenting before reacting. Note the time, frequency, mode, how it sounds, and whether it's constant or intermittent. That information is far more helpful to a coordinator than "somebody's jamming us." It also helps you work out whether it's malicious, accidental, or something like local noise that no one on the air is causing.

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.