Common Beginner Mistakes Working Ham Radio Satellites
What trips up new operators, and how to fix it fast
Many beginners with ham radio satellites miss on their first satellite passes entirely — wrong frequency, wrong tone, and once, correctly tuned but pointed at the wrong horizon. None of these mistakes are complicated once someone tells you what they are. Here are the ones I see (and made) most often.
Picking a Low, Marginal Pass First
A pass that peaks at 10-15° elevation is a bad place to learn. Low passes are short, the signal is weak, and you're fighting terrain and horizon noise on top of everything else that's new. For your first several attempts, pick passes that peak above 40° elevation — ideally near 90°, straight overhead. Ham Sat Tracker sorts upcoming passes by max elevation, so use that to your advantage while you're learning.
Not Setting the CTCSS Tone
SO-50 requires a 67.0 Hz CTCSS tone on the uplink or it won't repeat you at all — you'll transmit into silence and assume the satellite is dead or you're doing something else wrong. This is the single most common reason a beginner's first SO-50 attempt fails. Double-check your tone is set correctly before you blame anything else.
Forgetting the Activation Timer
SO-50 also has a 10-minute inactivity timer. If nobody has used the satellite recently, it goes quiet, and a normal 67.0 Hz call won't wake it up. You need a brief burst of 74.4 Hz tone to activate it, then switch back to 67.0 Hz to operate. If you're calling into apparent silence, this is worth trying before you give up on the pass.
Ignoring Doppler Shift
As a satellite crosses the sky, the downlink frequency you hear shifts — higher than nominal at AOS, lower at LOS. On 70 cm this can be 8-10 kHz across a pass, enough to walk a station right out of your receive filter if you leave the radio parked on the nominal frequency the whole time. Nudge the downlink down in small steps as the pass progresses. See Understanding Doppler Shift in Satellite Communications for the mechanics.
Transmitting Too Long
FM satellites are shared, single-channel repeaters — every second you hold the PTT down is a second nobody else can get in. A satellite contact needs only your callsign and grid square, maybe a quick signal report. Long-winded exchanges that would be normal on a local repeater will earn you dirty looks (and jammed transmissions) on satellite. Keep it to a few seconds.
Wrong Antenna Polarization or Aim
Pointing a yagi at the satellite's position ten minutes ago, not its position now, is an easy trap when you're juggling a radio, a phone, and an antenna at the same time. Passes move fast, especially near TCA (time of closest approach) when a satellite can cross 20-30° of sky in under a minute. Keep the tracking app in view and adjust continuously rather than aiming once and holding still. See How to Read the Sky View Diagram for help visualizing where the satellite actually is.
Using Stale TLE Data
Orbital elements (TLEs) drift out of date within days to weeks depending on the satellite and how much drag it's experiencing. A tracker using week-old TLEs can be pointing your antenna several degrees off, or predicting AOS/LOS times that are minutes wrong. Use a tracker that pulls current data — Ham Sat Tracker refreshes from CelesTrak automatically so you're not troubleshooting a problem that's actually just stale data.
Trying to Do Too Much on the First Contact
New operators sometimes try to log a full exchange, work multiple stations, and correct Doppler shift all in one 90-second pass. Simplify. Your first goal is one clean callsign exchange. Everything else — grid squares, signal reports, logging software — can wait for pass two.
Every one of these mistakes is a five-minute fix once you know what to look for. Most operators, myself included, made all of them in the first month.
73 de VE3AKK