Meteor scatter

Thousands of tiny meteors burn up in the upper atmosphere every hour. Each one leaves a short-lived trail of ionized gas that can reflect VHF signals for a fraction of a second, occasionally for several seconds. Meteor scatter (MS) uses those "pings" to make contacts out to about 1,300 miles (2,100 km), at any time of day, with no help needed from the ionosphere or the weather.

The mode that made it easy is MSK144 in WSJT-X. It sends a short message over and over for 15 seconds, so any ping long enough to carry one copy completes that part of the QSO. Technicians have full privileges on every band where MS is used.

Independent guide, not affiliated with ARRL, the WSJT Development Team, or any meteor organization. Settings below are from the WSJT-X User Guide. Your region's operating practice may differ.

Meteor scatter v1.0 · written 2026-10-08 · WSJT-X version, frequencies and contest dates checked as of Oct 2026

What to expect

The WSJT-X User Guide puts it plainly: meteor scatter QSOs can be made any time on the VHF bands at distances up to about 2,100 km. Completing one takes longer in the evening than in the morning, longer on higher bands, and longer near the maximum distance. With patience, 100 W or more and a single yagi, it can usually be done, even on 432 MHz.

BandHow it behaves
6 mThe easiest band. Pings are longer, and most are long enough for full-length messages.
2 mA popular MS band with plenty of activity. Pings are shorter; expect longer QSOs and more patience.
70 cmPossible but slow. Short-format messages help.

Distance: contacts near the 1,300-mile limit take longer. Very short paths are not where MS shines either; for nearby stations, tropo or plain SSB is usually easier. Point the antenna at the other station.

When it works best

Setting up MSK144 in WSJT-X

From the MSK144 section of the WSJT-X User Guide:

  1. Choose MSK144 from the Mode menu and Fast from the Decode menu.
  2. Set the receive audio frequency to Rx 1500 Hz and the frequency tolerance to F Tol 100.
  3. Set the T/R period to 15 s (or 30 s where that's the local standard). 15 s is recommended for most purposes.
  4. Click Monitor and watch the percentage on the Receiving label in the status bar. If it's well under 100%, raise decoding to Normal or Deep and F Tol to 200. Most modern computers handle Deep and 200.
  5. Check Auto Seq. Fifteen-second periods don't leave time to pick messages by hand.

MSK144 fills the whole SSB passband, always centered on 1500 Hz audio. Keep your transmit audio clean and flat across roughly 300 to 2700 Hz, and your clock within a second of UTC.

Calling frequencies

BandWSJT-X default (North America)
6 m50.260 MHz
2 m144.150 MHz
70 cm432.360 MHz

These are where people listen and call. When the calling frequency is busy, WSJT-X's Tx CQ nnn option lets you call CQ on the calling frequency and hold the QSO on a clear frequency of your choice. A station that double-clicks your CQ nnn message is moved there automatically. It needs CAT control with Split operation turned on. The User Guide's "Offset CQ" section walks through it.

How a QSO goes

A standard MSK144 QSO looks like any FT8 QSO. One station transmits in the first 15-second period, the other in the second. WSJT-X sets this when you answer a decode.

CQ K1ABC FN42
K1ABC W9XYZ EN37
W9XYZ K1ABC +02
K1ABC W9XYZ R+03
W9XYZ K1ABC RRR
K1ABC W9XYZ 73

On 2 m and up, WSJT-X can send short-format (Sh) messages for the report, RRR and 73. They last 20 ms instead of 72 ms, so even very short pings carry them. Short messages hash the two call signs, so only your QSO partner can decode them; they appear in angle brackets, such as <K1ABC W9XYZ> R+03. The User Guide says they give little or no advantage on 6 m, where standard messages fit in most pings.

Each transmission period, WSJT-X repeats the same message until it hears the next step. Don't give up after a few minutes. On 2 m, a contact can take much longer than on 6 m.

Meteor scatter from a park

MSK144 is a practical park mode on 6 m:

Habits / gotchas / checklist

Sources (checked Oct 2026)

Notes & edits