priyom.org

REA4

REA4 is the callsign of Russia's Long Range Aviation, and one of the callsigns used on its one-way Morse code strategic broadcast. It is present in both western and eastern Russia, transmitting simultaneously from Moscow and Khabarovsk.

Moscow broadcast

The Moscow broadcast uses on-off keyed CW, with 100 Hz dots serving as a channel marker.

  Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
Daytime 4649 kHz
09:00-16:00 MSK
? ? ? 4649 kHz
09:00-16:00 MSK
Nighttime 4179 kHz
16:00-09:00 MSK
? ? ? 4179 kHz
16:00-09:00 MSK

Khabarovsk broadcast

The Khabarovsk broadcast uses frequency-shift keyed CW with a shift of 1000 Hz, with 100 Bd reversals serving as a channel marker.

  Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
Daytime 10981 kHz
09:15-16:45 VLAT
? ? ? 10981 kHz
09:15-16:45 VLAT
Dawn/Dusk 7785 kHz
06:45-09:15 VLAT
16:45-18:45 VLAT
? ? ? 7785 kHz
06:45-09:15 VLAT
16:45-18:45 VLAT
Nighttime 6087 kHz
18:45-06:45 VLAT
? ? ? 6087 kHz
18:45-06:45 VLAT

"Monolith" type messages

Like other strategic networks of the Russian military, REA4 airs "Monolith" type messages of the standard format. The callsigns used include 1QRF, 7XMF, JUE4, JZLB, MJUR, MSK7, PABA, RLO92, and REA4 itself.

Weather bulletins

REA4 transmits hourly weather bulletins at 40 minutes past. The format used is a variation of SYNOP.

Not all groups may be present in a given message. The time consists only of the hours; midnight is represented as "24", not "00"; the timezone given can range from UTC-2 to UTC+3, although UTC-1 is the most common. The temperature is given in degrees Celsius, and is encoded as a 4-digit value as follows: "0" or "1" for positive and negative values respectively, followed by the 2-digit temperature, and then by a single decimal as the last digit.

REA4 covers six different airfields using the IDs noted below. Log pages for traffic analysis are linked from each ID and air base information from each name.

On November 19th 2018 we have received traffic for a 7th ID, 23746, for which no airfield location has yet been pinpointed. On December 15th 2018 an 8th ID has appeared, 23767, we have not yet deduced to which airfield this ID belongs. These two previously unknown IDs oddly share their first three digits and transmit in the same timeframe as one another.

Your browser is out-of-date!

Update your browser to view this website correctly. Update my browser now

×