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

Mod_Dan

Moderators
  • Joined

  • Last visited

Everything posted by Mod_Dan

  1. On the chaser side, it helps to keep SOTAwatch open and have a plan for when a spot appears. Check the spot's frequency, mode and any notes. Listen first, because many activators are running QRP from a poor antenna height and may be hard to copy. Give your callsign once clearly, then wait for your turn rather than calling over others. If you are copying the summit reference, repeat it back to confirm, especially in a pile-up on CW or SSB. If you are also an activator, S2S contacts are worth watching for. Both stations are on summits, so each station gets a useful contact, and activators often announce S2S availability when the pile-up is quiet. For awards, remember that Shack Sloth is about steady chaser points over time, so a consistent chase log matters more than any one big day. Keep your callsign and logging format consistent across all your uploads.
  2. One addition on nets: it helps a lot to keep your check-in minimal. If the NCS asks for callsign and location, give just those and stop. It sounds trivial, but when thirty stations are checking in, every extra sentence slows down the whole net. Also, don't "double" with another station: if you hear someone else answer the NCS at the same time as you, stop and wait to be called again instead of repeating louder. A very common newcomer mistake is thinking they weren't heard and calling again immediately, which just creates a second collision. Wait for the NCS to say "stations calling, say again," or similar. On the topic of QRL?, remember that a silent frequency isn't always empty. Skip, a narrow-band receiver, or a station using a different mode (such as one with a very narrow CW filter) can easily hide a QSO from you. It's worth a double check, especially on HF.
  3. One addition on tones: the most common reason someone can hear a repeater but not get into it is a wrong or missing encode tone. The second is a reversed offset. Many radios can monitor the input frequency, often through a "reverse" function. If you hear the other users directly on the input, you are probably in simplex range of them, and a repeater is not needed. That is a useful check before you spend time fixing a signal-strength problem. It also helps to know which tone a directory lists. Some list the input tone and some list the output tone. Where a repeater uses a different tone for each, the listing may only give one, so a call to the owner or a look at the club's page can save a lot of guessing. On linked systems, a good habit is to leave a longer pause than feels natural. Between the link delay, a node dropping in, and a time-out timer resetting, people who jump in right after the courtesy tone often step on each other.
  4. On LoTW matching: a QSO only becomes a credit when both sides have uploaded and the details match closely enough. That means call, band, mode group and time within the tolerance. The things that most often block a match are a wrong band after a QSY, a mode logged as SSB on one side and a digital mode on the other, and the other station's certificate being tied to a different location or entity. If you can see that the other station is a regular LoTW user and the QSO still hasn't matched, check your own record first, because that is the half you control. Make sure your station location in the upload is set correctly. For DXCC the location matters, because the entity is taken from the certificate's location, not from the call prefix alone. For deleted entities, I would keep them in a separate view of your log regardless of what the ARRL tallies show. They don't count toward the Honor Roll, so mixing them in with current entities can make your Honor Roll progress look better than it is. Having them separate makes the gap obvious.
  5. One thing that helps with FM passes is to prepare before AOS rather than during it. Check the current uplink frequency and CTCSS tone for the bird, set up your memories (downlink with and without Doppler offsets, if your radio allows it), and look at the max elevation in your tracking program. A pass peaking at 15 degrees is a different proposition from one at 70 degrees. Low passes mean a short window and more noise, and you're often better off waiting for a better one while you practise. With a handheld Yagi, a common mistake is holding the antenna in the wrong plane or flexing the coax and moving the antenna around. Keep the boom pointed at the predicted position, and let the radio's S-meter help you peak it. Also, listen first. Hearing how other stations make short exchanges and how they handle contention will save you a lot of unanswered calls. On the ISS, it helps to know which function is active on a given day: the APRS digipeater and the crossband repeater generally aren't both in use at once, and operations vary. Check the status before assuming silence means your station is deaf.
  6. On the equipment side, Hamvention and other convention coverage is where hype and facts get mixed up fastest. A useful habit is to separate three things: what was shown, what was officially announced, and what you can buy. Prototypes often change before release, and specs can shift in pricing, features, or even band coverage. When reviews or first-look videos appear, check what they actually tested. Receiver performance claims such as dynamic range, phase noise, and filtering are only meaningful when someone describes the test conditions, and independent lab measurements are more reliable than marketing language. Antenna announcements deserve the same scrutiny. Look for stated bands, power handling, feedpoint impedance, whether a unun or tuner is required, and whether efficiency numbers are measured or modeled. For firmware, it helps if people post the exact version number, the radio model and revision, and what changed. A line like "fixed CAT bug on version X" is much more useful than "update fixed my issues." Also worth noting in this thread: if an update changes digital-mode behavior, say which software you use with it (WSJT-X, Fldigi, a logging program), because that is usually where problems first show up.
  7. On connectors, I'd treat N-type as the default for anything permanent outdoors on UHF. A PL-259 with a cheap solder job and no sealing is a common point of water ingress, and the coax can end up with a green, corroded braid after a season or two. Whichever connector you use, wrap it with self-amalgamating tape, then add a layer of vinyl tape over it for UV protection, and leave a drip loop in the cable before it enters the building. Regarding satellites, if you're just starting with FM LEO passes, a handheld dual-band yagi and an HT with full-duplex capability (or two radios) is an easy way in. The detail people miss is that polarization shifts during a pass as the satellite tumbles or you change angle, so rotating the yagi around its boom axis can bring a weak signal back up. Crossed elements and circular polarization are nice upgrades, but not required to make a first contact.
  8. On the monitoring question: a WebSDR or KiwiSDR is a handy option when one is in range of your signal. It is a good way to see how your transmission looks on a waterfall and whether your bandwidth is clean. Check that the receiver is far enough away, and remember that its own filters and noise floor affect what you hear. If you can't find a remote receiver, a local SDR dongle on a small antenna with a lot of attenuation can be used to record your transmission and show the occupied bandwidth. Be careful to protect the front end from your own signal. For DX, one point that gets overlooked is that clean audio and narrow bandwidth help the operator at the far end more than extra power does. If the other station is copying you at the edge of the noise, a tight 2.4 kHz or slightly narrower TX setting with moderate compression is likely to be easier to copy than a wide, bass-heavy signal. Also remember that many DX operators are using narrow receive filters, so being slightly off frequency matters more than it would on a quiet local contact. For listening, it helps to practice using IF shift and a notch before making the filter narrower. Narrowing everything can make speech sound thin. Moving the passband away from a nearby signal may retain more of the voice while still reducing the interference.
  9. One addition on tones: when you set a repeater's tone in the radio, make sure you know which field you're editing. Many handhelds have separate settings for encode only (tone), tone squelch (decode too) and DCS. Choosing "Tone" when you meant "TSQL" is a very easy mistake. If you can't open the repeater, check that the offset direction is right, the tone is entered on transmit, and the radio really is in the mode you think it is. Test with a second radio or a monitor if you can. On digital repeaters the equivalent checks are different. For DMR, check the color code, time slot and talkgroup. For D-STAR, check that the repeater callsign fields are set correctly. For Fusion, check that your radio's squelch mode matches the repeater's.
  10. On security, a VPN in front is the right default. Many ham remote setups put the radio on the same network as everything else and then forward a port, which exposes the radio's control service to the whole internet. Giving the station its own subnet or VLAN and allowing only the VPN endpoint inbound is a much smaller attack surface. Use key-based authentication where the VPN supports it, and make sure the Pi or PC running the server is not also used for general browsing. If you use a vendor service like SmartLink, read how it handles authentication and which ports or UPnP behaviour it needs, and decide whether you are comfortable with that on your router. Whichever route you pick, keep a second way into the site, such as a cellular backup or a remotely switchable router. You will otherwise be stuck the first time the network needs a reboot. For the rules question, I would not rely on forum summaries, including this one. Look up your regulator's current text on remote control, the control operator's obligations, and whether the operator's location matters for the privileges they use. If you plan to enter contests, read the specific rules for remote operation in that contest, because some have category or location definitions that apply. Local clubs or the national society often have a remote-operation FAQ that points to the actual rule text.
  11. For BITX and uBITX builds the important point is that the design is a compact bidirectional SSB rig. Many of the same stages carry signal in both directions, so a small error in switching, grounding or filtering can show up in receive and transmit at the same time. The uBITX in particular uses a Si5351-based synthesizer controlled by an Arduino, and the clock outputs are square-wave sources. That means the mixing stages and the output filtering matter a lot. Builders have reported spurious products on some bands, so measure each band you plan to use rather than assuming the supplied low-pass filters are all equally good. Check the output on a dummy load with a spectrum analyzer if you can, and with a scope if you cannot. On SSB rigs, drive level and linearity matter as much as the harmonics. Overdriving the microphone amplifier or the later stages produces splatter even if the low-pass filter is doing its job. A two-tone test using two audio oscillators or a computer sound card and a scope will show flat-topping and distortion in a way that a single whistle does not. If you do not have a scope, ask a nearby amateur with a decent receiver to listen and describe what they hear, but do that on a quiet frequency and with low power. For CW-only projects such as Pixie or Tuna Tin 2 style transmitters, the equivalent concern is key clicks, as mentioned above, and chirp. Chirp usually comes from a VFO or oscillator being pulled when the PA keys on. A buffer stage, a stiffer supply for the oscillator, or a regulated 78L-series rail for the oscillator alone are common fixes. If the note sounds unstable on a nearby receiver, check the supply rail with the scope while keying before you start rewinding coils.
  12. For combined POTA and WWFF, the biggest trap is paperwork rather than radio. Before you leave, write down both references and check each on its own official map. Then decide how you will keep the log clean. Some loggers have fields for a second reference, and some do not, in which case you may need to export once and edit the ADIF fields for the other program. Do a dry-run export with a couple of test entries so you are not fixing it at 11 pm. One more point: hunters often only need to hear one reference to claim a contact, so announcing both costs you a few seconds but can bring in a wider pool of callers. Keep the exchange short, because with 44 QSOs as the goal every wasted second adds up. And if the rules for your country's WWFF coordinator add anything extra, such as a local award or a specific log format, read those pages as well as the main WWFF site.
  13. The resources are mostly complementary rather than competing, so it helps to think about what each one is for. LCWO is a web-based trainer built around the Koch approach. It lets you set your character speed and effective speed, work through the character order lesson by lesson, and run plain-text or random-group practice. That makes it a convenient daily tool because you only need a browser. G4FON's trainer is Koch-style software that does similar things and is well known in the amateur community, so it's worth trying if you'd rather practice offline on your own computer. Because the apps differ in character order, tone and interface, pick one and stick with it for a while rather than hopping between them. Mixing character orders is a common way to end up with gaps. It's also worth checking each site's current status and platform support yourself, since software and web services change. CW Academy is a different kind of resource: it's a structured program of online classes run by volunteers through CWops, so you get an instructor, a class schedule, and other learners. That matters for motivation and accountability, which is where many self-taught learners stall. You can easily pair a class with an app for the daily practice between sessions. Check the CW Academy site for the current course levels, requirements and sign-up periods. As for confidence, a few practical things help. Use a comfortable tone, often somewhere in the range of 500 to 700 Hz, and headphones, so the sound is clear and you can listen for longer without fatigue. Start sending as early as you can, even if only with a key or paddle at home, because sending reinforces the sound of each character. When you're ready for the air, listen first. Slow CW practice transmissions and slower QSOs are good places to pick up how an exchange flows, and standard exchanges like calls, signal reports and 73 repeat so often that they become easy anchor points. Your first contacts will probably be short and formulaic, and that's fine. Most operators are patient with someone who sends "QRS" and asks them to slow down. Mistakes are normal, so repeat what you missed, ask for a repeat with "?", and keep going.
  14. For modern rigs, the overrated spec question is a good one. Plenty of people point to the display, especially the waterfall or spectrum scope. It's genuinely useful for seeing where activity is, but it doesn't make a rig better to operate if the receiver, the filters, and the controls aren't great. Output power is another one. Most of the time the difference between 100 W and a little more matters far less than a good antenna and a clean signal. I'd put filter flexibility, a good noise blanker, and decent audio near the top of the list for daily use, plus how easy it is to get to the settings you change often. Features like built-in tuner range, USB audio and CAT control are nice, and worth checking if you plan to run digital modes or logging software. On the classifieds side, a few habits make deals go smoother. Ask for clear photos of the front, back, and serial number label, ask whether it has been modified or repaired, and ask what accessories and manuals are included. For heavy gear, pack it more carefully than you think is necessary, with the radio well cushioned inside a box inside another box, since shipping damage is a common way a good deal turns bad. If something sounds too good, a quick check of the seller's history on the forum or marketplace helps.
  15. On the split between contest and master log, a common pattern is to keep the contest logger authoritative for the contest and treat the master log as a destination. Export ADIF from the contest logger when the event ends and import it, rather than trying to sync live. Before importing, check that the fields your master log needs are populated: STATION_CALLSIGN, OPERATOR for multi-op, MY_GRIDSQUARE, and the contest ID and exchange fields if you want them kept. Importing the same file twice is the most common mess, so use your program's duplicate check (call, date, time, band and mode) or back up first. For WSJT-X, remember it writes wsjtx_log.adi, and it can also broadcast logged QSOs over UDP. N1MM+, Log4OM and JTAlert can listen to that broadcast, so you can log automatically without CAT conflicts in the log path. Two loggers listening at once will double-log, so pick one listener. Also check how your logger handles FT4. Depending on the ADIF version, it may appear as MFSK with submode FT4 rather than as its own mode, and that can cause odd results in award tracking and in LoTW matching. For CAT sharing, an option is a network layer such as Hamlib's rigctld. WSJT-X can use the Hamlib NET rigctl setting, and other programs talk to the same daemon. The alternative is a virtual serial port splitter, which works but adds another thing that can hang. Set baud rate, CI-V address (for Icom) and stop bits once, and write them down.
  16. On the mobile side: Path: WIDE1-1,WIDE2-1 is still a sensible mobile default. The WIDE1-1 hop lets a fill-in digipeater (often a home or low-power station) pick you up. The WIDE2-1 hop lets a wide-area digipeater carry you farther. If your area has dense digipeater coverage, a single WIDE2-1 may be enough. Avoid long paths like WIDE3-3. Each extra hop multiplies the airtime your packet uses across everyone's coverage area. Your fixed station barely needs a path. An iGate that hears the RF directly doesn't need to be repeated, and a stationary beacon for a receive-only iGate can use an empty path or a single hop. SmartBeaconing: yes, use it if the radio offers it. The idea is to beacon more often when you're moving fast or turning, and slowly when you're slow or stopped. The parameters are generally fast speed, fast rate, slow speed, slow rate, minimum turn angle, turn slope, and minimum turn time. As a rough starting point, a beacon every minute or two at highway speed and every 20 to 30 minutes when parked is reasonable. Tune from there against how the track looks on aprs.fi. Menu names and defaults differ between the TH-D74/D75 and FT5D, so check each radio's manual rather than assuming the same options. Mic-E: you lose nothing by leaving it on for tracking. It packs latitude into the destination address field and carries longitude, speed and course in the information field. That makes packets short, which is good for a 1200 baud channel. It also carries the Mic-E message status codes (such as In Service or Emergency), which the handhelds expose as a status setting. Keep your comment text short. A long comment makes every beacon longer for no benefit. One more thing: set the correct SSID and the right symbol (car, handheld and so on). A mis-set symbol is the most common reason a mobile station looks wrong on the map.
  17. With one 35 ft support and a tuner in the shack, I would lean toward a doublet as an inverted V, fed with ladder line or window line, and see how far that gets you. The reason is feedline loss. Balanced line has very low loss even at a high SWR, so the tuner can handle the mismatch on several bands without most of the power turning into heat. Coax feeding a compromise antenna on a band where the SWR is high wastes much more, particularly at 15 and 10 m, where coax loss per 100 ft is higher. Some design details matter for this. The wire should be at least roughly a half-wave on the lowest band you want to work, so about 66 ft total for 40 m, and longer helps 80 m. Avoid lengths that give extreme feedpoint impedances on bands you care about, because the tuner has to deal with that, and the voltages on the ladder line can get large. Keep the ladder line away from metal gutters and downspouts, and bring it down with a few twists rather than hugging a wall. At the radio end, a 4:1 current balun or a choke before the tuner keeps common-mode current off the coax, or use a tuner with a built-in balanced output. Without that, the shield can radiate, you get RF in the shack, and the pattern is distorted. On an HOA lot it also means more chance of interference with neighbors' equipment. Wire thin enough to be inconspicuous, such as insulated 18 to 20 AWG stranded or coated wire, in a dark color against trees, is what makes most stealth wire antennas work in practice. It won't be the most efficient antenna, but it can work well on 40 through 10 m for the effort.
  18. On tailending, the key point is the difference between stepping on a QSO and answering the operator's signal that he's ready. If the DX is working a station and still exchanging reports, don't call. That breaks the exchange and may force a repeat, which costs time for everyone behind you. If the DX has already sent "QRZ" or "CQ," you have a clear window, and the first one or two calls are usually the best chance. One habit that helps is to listen for the operator's rhythm. Some run a fast tempo and expect a continuous stream of calls. Others take a deliberate pause after each QSO. Match the tempo, and don't send a long string of calls just because the pile is loud. Stations that call continuously without listening are the ones who miss a partial callback, and callbacks are how the pile moves. On SSB, resist the temptation to ask the DX "what's the call?" or to retell the operator his own information. If you're unsure of the callsign, check the cluster, the DXpedition's website or Club Log. For dupes, check your own log and the expedition's online log if one is available. Working the same station repeatedly on the same band and mode just slows the rate for others. The usual exception is a case where you think your first QSO was not logged correctly, and even then it's better to wait until the pile has thinned. In FT8 Fox/Hound mode, the rule is different. Hounds should call above the frequency the Fox expects, usually 1000 Hz, and shouldn't sit on the Fox's own transmit frequency. Read the expedition's mode instructions first, because getting the setup wrong can leave you calling without being heard.
  19. On noise, a scope is very useful because a multimeter can't show you most of it. Looking at the supply rail and the regulated rails will often show switching spikes or ripple that line up with the birdies you hear. If the noise changes when you swap to a battery or a different supply, that tells you a lot. If the noise stays with the antenna jack terminated, it's coming from inside the rig, and you can start probing regulators, clocks, and the display or CPU lines. If the noise goes away when you terminate the input, the problem is external: the antenna system, a poor ground, a nearby switch-mode device, or common-mode current on the feedline. One practical probe tip: keep the ground lead short, or use a ground spring on the probe tip, when looking at fast edges or RF. A long ground clip adds enough inductance to distort what you're measuring, and you can end up chasing ringing that comes from the probe itself. Also, how do people here decide when to replace all the electrolytics in a rig of a given age and when to replace only the ones that measure bad? I can see the argument both ways. A full recap avoids repeat visits, but it also increases the risk of lifting pads and introducing new mistakes.
  20. For the band privileges, start from what you already have. A Technician already has CW privileges on parts of 80, 40 and 15 meters, plus CW/data and some phone on 10 meters. General expands those and adds the other HF bands. Rather than memorizing everything as one list, sort it into three groups: bands that are CW/data only for General (30 meters is the main one, with a 200 W PEP limit), bands where the General phone segment sits near the top of the band (the 75/80 meter, 40, 20 and 15 meter segments follow that pattern), and the broad bands where General has nearly everything (160 meters and most of 10 meters). Then drill the exact edge frequencies. Questions usually ask whether a given frequency and mode combination is allowed, so a simple band-edge chart beats vague recall. Print the current ARRL band chart rather than relying on notes, because the exam tests the pool's exact wording. Also remember the conventions: LSB below 10 MHz, USB at and above it, and USB on 60 meters. The 60-meter rules (channelized or the small band segment, depending on the current regulations) are narrowly specific, so verify them against the current Part 97 text. For propagation, the questions reward a mental model rather than lists. Daytime D-layer absorption hurts the lower bands (160, 80, 40), which is why those work better at night. Higher bands (20 meters and up) depend on the F layer being ionized enough to refract signals, so they open with higher solar activity. The MUF is the highest frequency that will refract back for a given path, and frequencies above it pass through. Higher solar flux generally helps the upper HF bands, while a high K index signals a disturbed geomagnetic field, which tends to degrade HF paths. If you can explain why a band is open at a given time, most of the questions are easy. For a timeline, a reasonable four-week structure is: week one on rules and band privileges, week two on propagation and operating practices, week three on antennas, feed lines and electrical principles, and week four on practice exams and weak spots. Do timed practice exams only after you have gone through each topic once. The pass line is 74% (26 of 35), so you do not have to master every topic. Do prioritize the areas where a small amount of study turns a miss into a hit.
  21. For special events, I would separate the chase from the paperwork. During the event, the priority is a clean exchange: copy the call correctly, give your report, and let the operator move on. Afterward, you can handle the QSL or certificate request. Events can be short, so check the posted operating dates and time zone, since UTC versus local time causes plenty of missed chances. Many commemorative stations also list a specific logbook upload service, an email address, or a mailing address for certificates. Read the requirements carefully. Some ask for a minimum number of contacts, specific bands or modes, or a request within a deadline. If a certificate is important to you, save a screenshot or copy of those rules in case the page changes. Also, because pileups can be chaotic, the same discipline from nets helps: listen to how the operator is working the pile, whether by call area, split frequency, or just whoever is loudest, and follow that pattern rather than guessing.
  22. On the emergency side, I'd stress that keeping the radio simple matters more than the feature count. A short list of channels with clear names, a spare battery, and a way to charge from USB or a 12 V source are worth more than a menu with hundreds of options. Practice swapping to simplex, changing power level and switching to a backup repeater before you need to do it under stress. It's also worth running a check on your antenna choice. A longer whip can help range, but it also makes the radio awkward to carry and can break at the connector, so a flexible one is often a better pick for a go-bag. If you plan to be on the air for long periods during an event, consider a remote speaker mic and an external antenna on a mast or vehicle, and remember RF exposure guidelines when you're holding a 5 W radio near your face. Also, double-check that any wideband receive feature you rely on, like weather alerts or airband, actually works the way you expect on your specific model. Spec sheets and regional versions don't always match.
  23. One thing worth splitting out early is where the audio and control actually terminate. With a radio-native option like RS-BA1 or Yaesu's network unit, you are trusting the manufacturer's protocol and the firmware on the radio. With a RigPi-style server, the Linux box becomes the thing you have to patch and secure, but you get more flexibility: you can add a keyer, a web power switch, antenna switch control and logging, all behind one VPN connection. For Flex, the radio is built around being driven over a network, so the question becomes less "can it be remote?" and more "how do I expose it safely?" Their own remote-access service is the convenient path, but a VPN into your LAN is a reasonable alternative if you want to control exactly what is reachable. Whichever you choose, test with a dummy load first and deliberately pull the network cable mid-transmit to see what the station actually does. I would also keep a short written checklist for the remote end: power cycle method, who can reach the station physically if something sticks, and what the default state is after a reboot. That list matters more than a slightly lower latency figure.
  24. On tailending, my rule of thumb is to follow the operator's cadence. If the DX is sending a call and a short report back to back, with very little dead air, a well-timed call just as the QSO ends is normal. If they are slow and deliberate, perhaps repeating the full callsign for confirmation, then calling over the confirmation just creates a mess and may cost them a repeat. It also helps to listen to the exchange itself. If the DX has to ask for a callsign twice, the pileup is too thick to be tailending in. On timing, one trick is to pay attention to which part of the spread the DX is tuning through. Many operators work their way up the listening range and then reset. If they have just come back down to the bottom, a call a couple of kilohertz above that is often more productive than calling where everyone else is. It is not guaranteed, but it is a better use of a transmission than calling the same place for ten minutes. Also, if you transmit and hear nothing, do not just keep repeating. Listen for a few cycles, because the DX may be moving through callers methodically. For phonetics, keep to standard ITU forms unless the operator clearly prefers another. Inventing creative phonetics for a rare station tends to slow things down. Choose one set of words and use the same ones every time you call, so the operator can match the pattern.
  25. Building on that, here's how I'd break down the practical parts, without overcomplicating it. Names and locations: say it normally first, then spell it only if needed. "Name is Kowalczyk, I spell Kilo Oscar Whiskey Alfa Lima Charlie Zulu Yankee Kilo." Pause between letters and don't rush. For a town, give the word, then the spelling, then any state/county/grid detail that disambiguates it. If you're passing a location on a net, many operators also add the type of place ("road", "hospital") because the spelling alone doesn't tell the receiver whether they heard it correctly. For anything critical, ask for a readback. Reading it back is the most reliable error check you have, much more than any alphabet. Numbers: keep them separate from letters. Say "figures" or "numbers" before a numeric block if there's any risk of confusion with a callsign or message text. Give digits one at a time for street numbers, frequencies and phone numbers, and group them consistently. On a net or when passing formal traffic, a message's check (the count of words) and numbers should be read slowly. If you must correct something, use a procedure word: "correction", then repeat from the last good item. Prosigns and procedure words: CW prosigns like AR, SK, KN, BT and CL don't transfer directly to voice. The voice equivalents are things like "over", "clear" or "out", "go ahead", "standing by" and "break". Avoid "over and out": "over" says you expect a reply and "out" says you don't, so they contradict. Also avoid piling on jargon that isn't needed. On a ham net, plain language is usually better than stretching military-style words to the limit. "Say again" is better than "repeat" in some contexts because "repeat" can be misread as an instruction to repeat a fire mission, and in ham operating, plain "say again" is widely understood. Nets and emergency traffic: follow the net control station's lead, and make your check-in short and clear. Often they ask for suffixes only ("last two letters"), which saves airtime when many stations check in. Give your callsign in phonetics once if asked. For emergency traffic, use the words your net or agency specifies and keep a priority message crisp: who you are, what you're reporting, location, what you need. Real distress calls use international procedure words (Mayday for distress, Pan-pan for urgency), but in ham emergency nets the exact local procedure matters, so check your group's operating plan. In every case, the habit that helps is the same: stay slow and consistent, spell only what must be right, and read back anything that can't afford an error.

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.