Showing posts with label Rus-Ny. Show all posts
Showing posts with label Rus-Ny. Show all posts

1 August 2016

FM13 weather reports messages in CW


Oceanographic and Hydrographic observations are sent daily by the Hydrographic ships of the Russian Navy at fixed times 00, 06, 12 and 18 UTC on 12464 KHz.  Such messages are not sent directly to GSVMF ground stations but forwarded via Naval HQs:

RJP99 547 18 4 2214 547 = FOR RJH74 RJH45 = ... (via RIT, NSF HQ Severomorsk)
RMCW 6T2 18 23 16TT 6T2 = SML FOR RJE73 RJH45 =... (via RCV, BSF HQ Sevastopol))

In fact, looking for example at the FM-13 reports (at least here in Southern Europe) you may see that most of these messages almost always report two recipients, mostly RJE73 RJH45 or RJH74 RJH45, usually using the "sml" priority indicator: I do not know if the recipients are local GSVMF offices at each HQ naval bases (RIT, RCV,...) or just GSVMF central offices:

RJH45 = MOSCOW NAVAL METEO
RJE73 = BLACK SEA FLOT METEO
RJH74 = NORTHERN FLEET METEO
RJD38 = BALTIC FLOT METEO
RJE65 = BLACK SEA FLOT HQ, NOVOROSSIYSK
 

They use the standard observation method as described by NOAA in their observation handbook [1], and within this message format there is a Lat/Long position report for where the observation took place: so you are able to localize the positions of the ships by decoding the Code FM-13-X-SHIP (or shortly FM-13). This ships synoptic code is comprised of 23 groups of symbolic letters representing meteorological and oceanographic elements, report identification and ship location data (see resources later at the end of this post).

1) Ship current position is coded in the Ships Synoptic Code Section 0:
... 99LaLaLa QcLoLoLoLo ...
... 99662 10345 ...

99 Data on Position Follow

LaLaLa (662) Latitude in degrees and tenths of a degree. Always coded with three digits, the first two digits are actual degrees, the last digit for tenths of a degree (66.2)

Qc
(10) Quadrant of the globe (specify whether the latitude is north or south and the longitude east or west). 
If north of the equator (north latitude):
- 1 when east of the Greenwich Meridian (east longitude)
- 7 when west of the Greenwich meridian (west longitude)
If south of the equator (south latitude):
- 3 when east of the Greenwich meridian (east longitude)
- 5 when west of the Greenwich meridian (west longitude)



LoLoLoLo (345) Longitude in degrees and tenths of a degree. Always coded with four digits, with the leading (hundreds) figure coded as 0 or 1. The first three digits are actual degrees, the last digit for tenths of a degree (34.5)

2) the ship movement data is coded in Section 2:
... 222DsVs ...
... 22232 ...

222 indicator
Ds (3)
true ship’s course made good during the three hours preceeding the time of observation:
0
Ship hove to
1
NE
2 E
3 SE
4 S
5 SW
6 W
7 NW
8 N
9 Unknown
/ Not reported

Vs (2) Ship’s average speed, in knots, made good during the three hours preceeding the time of observation:
0
0 knot
1 1 to 5 knots
2 6 to 10 knots
3 11 to 15 knots
4 16 to 20 knots
5 21 to 25 knots
6 26 to 30 knots
7 31 to 35 knots
8 36 to 40 knots
9 Over 40 knots
/ Not reported

Examples:

VVV RJD99 DE RBC89 QSA? QTC RBC89 572 9 5 0955 572 = FOR RJD90 RJH74 =
050?? 99662 10345 41/96 9230? 00050 40000 52020 70222 89/// 22232 00030 20202 232// 40302 88000 05016 = + RBC89


in plain text:
"ship  RBC89 (calling RJD99) at (Moscow) time 0955 was at 66.2N 34.5E , heading SouthEast @ 6-10kts"
the position of RBC89 is decoded from 99|662 10|345, with the heading/speed obtained from 222|32.

CW "771 19 9 1551 771 ...99548 10198...22242...AR RMWT K"
in plain text:
"ship RMWT position at 1551 Moscow time: 54.8N 19.8E  heading South @ 6-10kts"


Since the time of reception differs from the one indicated in the preamble (does not matter if UTC or Moscow Time), it is presumed that the preamble time is the time when the message was prepared and not the time of the transmission: i.e. the data relate to the observation at 1603 Moscow Time (1203z) but sent (and then received) at 1220z.

[1] http://www.vos.noaa.gov/...compliant.pdf

14 December 2014

Russian Navy radio Centers

Here is a list of the main Russian Navy radio Centers, set your web/mail browser to read cyrillic in order to see the Russian names of these sites correctly.

Radiocoverage area World wide
N  р/с 2201 (poss 2200)

Москва / Moscow
РИВ / RIW (+ RJE56)
Прогресс / Progress


Radiocoverage area Northern Fleet,
Arctic regions, North Atlantic Ocean, North sea, Norwegian Sea, white Sea, Northern inland waterways
N  р/с 2202

Североморск /Severomorsk
РИТ / RIT (+ RJH57 ?)
Вольфрам /Wolfram

Северодвинск / Severodvinsk
РЙД-99  / RJD99
Цветок / Swetok, "Flower"

Иоканьга*  / Iokanga aka Jagernaja / Ostrovnoj aka Gremikha aka Murmansk-140
РЙД-80  / RJD80
Светлана / Svetlana

Полярный   / Polyarny
РИР-2  / RIR2
Природа / Priroda, "Nature"

Мурманск  / Murmansk
РЙД-56  / RJD56
Флюгер / Flüger, "Vane"

Radiocoverage area Baltic Fleet

Baltic Sea, North sea, English Channel, Inland waterways
N  р/с 2203

Калининград / Kaliningrad
РМП  / RMP (+RJD71?)
Вестник / Westnik, "Herald", "Messenger"

С-Петербург / St. Petersburg
РЙД-85  / RJD85
Скакун  / Skakun, "Race horse", "Jumper"

Балтийск  / Baltiysk
РЙД-69  / RJD69
Искатель / Iskatelx, "Seeker"

Radiocoverage area Black Sea Fleet
Black Sea, Mediterranean Sea, Caspian Sea, Red Sea, inland waterways
N  р/с 2204

Севастополь / Sevastopol
РЦЖ / RCV  
Гвоздика / Gwozdika, "Cloves"

Новороссийск / Novorossiysk
РЙЕ-65  / RJE65
Тополь / Topolx, "White Poplar"

Radiocoverage area Caspian Flotilla
Caspian Sea, inland waterways
N   р/с 2205

Астрахань  / Astrakhan
РЙД-52 / RJD52
Зазор / Zazor, "Clearance" or poss "Gap"

Radiocoverage area Pacific Fleet
North Pacific Ocean, South Pacific Oceans, Bering Sea, inland waterways
N   р/с 2206

Владивосток / Vladivostok
РЙС   / RJS
Грейдер / Grejder "Grader"

Стрелок  / Strelok aka Pavlovsk Bay
РЙД-97  / RJD97
Чинара / Öjnara "Sycamore"

П.-Камчатский  / Petropavlomsk Kamchatskiy
РЦЦ  / RCC
Деканат / Dekanat "Deanery (Deans office)"

Совгавань /  Sowgwanx aka Sovjetskaya Gavan
РЙД-93  / RJD93
Флейта / Flejta "Flute"

Владивосток / Vladivostok
РЙЦ-60  / RJC60
Юрист / Ürist "Lawyer (Jurist)"


Radiocoverage area Indian Ocean
Indian Ocean, South Atlantic Ocean, inland waterways
N   р/с 2207

Бишкек  / Bishkek
РЙХ-25  / RJH25
Сибиряк  / Sibiräk "Siberian"
From my good friend Trond Jacobsen in Norway.

27 October 2014

the poor-man guide for ship plotting


using Google Earth to display positions of the ships

from my logs of 25 October:

12464.0 RMCW: Russian Navy ship "Donuzlav" 1205z
CW "RCv DE RMCW = SML FOR RJE73 RJH45 = ...99417 1T296...22212"
-> position 41.7N 29.6E Heading North-East @6-10 knots


12464.0 RMGB: Russian Navy ship "Iman" 1207z
CW "RCV DE RMGB = SML FOR RJH45 RJe73 = ...99351 10239...22262"
-> position 35.1N 23.9E Heading West @6-10 knots


12464.0 RJC20: Russian Navy unid ship 1210z
CW "RCV DE RJC2Ø = SML FOR RJH45 RJE73 =...99351 10235...22232"
-> position 35.1N 23.5E Heading South-East @6-10 knots



Now we want to plot (and save) the above ships positions using google earth. You have to know that you may create your own google-earth kml files (Keyhole Markup Language)  in order to show the ship's position on google-earth or google-maps. Just write a single kml file for each ship you want to trace then save the file with then ".kml" extension. 

First creates a special directory in your documents folder, naming it as you want (assume "ships positions"). Then in order to create your kml files use this very very basic default schema:

<?xml version="1.0" encoding="UTF-8"?>
<kml xmlns="http://www.opengis.net/kml/2.2">
  <Placemark>
    <name>placemark name shown in the map</name>
    <description>description shown by clicking on the placemark</description>
    <Point>
      <coordinates>
longitude(E or W),latitude (N or S)</coordinates>
    </Point>
  </Placemark>
</kml>

for example, file for RJC20 tracking:
<?xml version="1.0" encoding="UTF-8"?>
<kml xmlns="http://www.opengis.net/kml/2.2">
  <Placemark>
    <name>RJC20</name>
    <description>Russian Navy RJC20, position at 25 October</description>
    <Point>
      <coordinates>23.1E,35.1N</coordinates>
    </Point>
  </Placemark>
</kml>

Then save the file using a self-explaining name and the appropriate extension such as "RJC20-25-oct.kml" in the directory that you created earlier (i.e. "ships positions").
PAY ATTENTION you may use the basic block-notes program by Windows but remember to select all files mode when you save the file so to give it the right extension (.kml), otherwise the file will be saved with the ".txt" extension.

Now start your google-earth program and click File > Open, navigate to your "ships positions" directory, select your previous saved .kml file, and click Open. The file will be added to the Temporary Places section of your Places panel and the position will be imported and displayed. By clicking on Temporary Places - file name you may the refine the map and store it... et voila' !





24 October 2014

BATHY, TESAC, TRACKOB reports and GSVMF

Russian Navy Morse | BATHY, TESAC, TRACKOB reports and GSVMF

Other than the basic FM 13 weather observations, the oceanographic and hydrographic ships of the Russian Navy send other specialist messages containing information about sea temperature, salinity and current at different depths. Think: salinity and sea temperature versus depth could be vital to a commander of a submarine who needs to hide his boat under a halocline or thermocline layer (it was discovered that thermal layers affect sonar performance; below a thermal layer, a submarine's active sonar performed poorly when trying to acquire a target. Conversely, a surface ship's sonar pings were reflected and scattered by the layer as well, allowing the submarine to hide beneath it).These messages are known as BATHY, TESAC and TRACKOB reports and, as well as the FM 13 ones, are sent to the Hydrographic Service of the Russian Navy. First, let's take a look at this service.

The Hydrographic Service of the Russian Navy (GSVMF) is one of the important national bodies responsible for the safety of navigation. Although the Hydrographic Service forms a part of the Navy, it also meets the requirement of merchant and fishing fleets and vessels of other ministries and agencies.  The Hydrographic Service is under the direction of the Department of Navigation and Oceanography of the Russian Federation Ministry of Defense (DNO of the RF MD), which is traditionally located in St Petersburg.

The principle functions of the DNO of the RF MD are:

— to carry out oceanographic, hydrographic and geophysical surveys in the World Ocean
— to compile and produce Nautical Charts, Publications and Guides to Navigation
— to develop and produce Guides, Instructions, Regulations and Methodical Directions on carrying out the World Ocean surveys and processing of their results
— to equip the coast of the Russian Federation by aids to navigation
— to organize mariner notification about changes in navigational conditions and regime
— to develop up navigational instruments and complexes.


As reported by defencerussia "In 2014, survey vessels of three fleets of the Russian Navy will make long trips [...] The main objectives of the campaign are comprehensive oceanographic studies of the Mediterranean Sea, the collection of data for the next hydro-navigation proof nautical charts, manuals and handbooks on shipping, a study of the navigation system, ensuring the presence and demonstration of the flag of the Russian Navy,” the Russian Navy Captain of the 1st Rank Igor Dygalo said. 
To carry out ocean ographic surveys some special units have been created as a part of the Hydrographic Service of the Navy, such as expeditions and parties. 
The surveys are being run by oceanographic and hydrographic ships of up to 9000 tons displacement, equipped with modern navigational and oceanographic facilities. Ships may have anti-terror team on board consisting of marines in order to maintain security during the cruise. 

The Oceanographic and Hydrographic observations are sent daily by the Hydrographic ships (FM 13 reports at fixed times 00, 06, 12 and 18 UTC) to the ground stations of the GSVMF.  Such messages are not sent directly to ground stations but forwarded via Naval HQs:

RJP99 547 18 4 2214 547 = FOR RJH74 RJH45 = ... (via RIT, NSF HQ Severomorsk)
RMCW 6T2 18 23 16TT 6T2 = SML FOR RJE73 RJH45 =... (via RCV, BSF HQ Sevastopol))

In fact, looking for example at the FM-13 reports (at least here in Southern Europe) you may see that most of these messages almost always report two recipients, mostly RJE73 RJH45 or RJH74 RJH45 usually using the "sml" priority indicator: I do not know if the recipients are local GSVMF offices at each HQ naval bases (RIT, RCV,...) or just GSVMF central offices.
As reported by  planesandstuff site, the observed calls of GSVMF ground stations are:
REG98
RJD38
RJD90
RJE69
RJE73
RJF41
RJH45
RJH48
RJH74
RMSZ

and  the observed calls related to survey/research ships are:
RFE76 Sibiriyakov
RHO62 Admiral Vladimirskiy
RJP30 Senezh
RJP99 Gorizont (belonging to the Northern Fleet)
RKB92 *
RMCW Donuzlav (belonging to the Black Sea Fleet)
RMIB *
RMQW *
RMWT *
RMX62 *
(* = not confirmed)

RJH45 = MOSCOW NAVAL METEO
RJE73 = BLACK SEA FLOT METEO
RJH74 = NORTHERN FLEET METEO
RJD38 = BALTIC FLOT METEO
RJE65 = BLACK SEA FLOT HQ, NOVOROSSIYSK


The BATHY, TESAC and TRACKOB reports are described here with tables and instructions about their decode: the data collected by these reports are sumarized below (from the same source).


The BATHY report should be used for recording temperature observations versus depth taken with instruments which provide the temperature with a resolution of 0.1 degrees Celsius or less, such as mechanical or expendable Bathythermographs, thermistor chains or others. The TESAC report should be used for temperature values with a higher resolution and/or when salinity or current versus depth are reported (see later). In addition to the temperature information, the BATHY report makes provision for encoding sea-surface current measurements and depth to the bottom, as well as other environmental information. 
Report information is designed according to the reporting code FM 63-X Ext BATHY.

The TESAC report should be used if one or all of the following data sets are available: Temperature versus depth with a resolution of 0.01 degrees Celsius, Temperature and salinity versus depth, Current versus depth. 
Report information is designed according to the reporting code FM 64-IX TESAC.

example of a TESAC message (from planesandstuff)

1836z RJP99 911 28 4 2216 911 = FOR RJH74 RJH45 =
KKXX 04093 1545/ 17000 03601 88870
20000 31149 20010 31110 20020 31096
20030 30876 20050 30402 22075 30344
30100 30344 20?43 30288 00000 55555
10144 04025 = + RJP99


The TRACKOB report should be used for recording of conventional oceanographic observations at the sea surface taken along a ship's track. The report form permits the collection and transmission of one or more parameters such as water temperature and/or salinity and/or ocean currents in terms of direction and speed.

It is designed to report spot values as well as averaged data over a selected time period. The instruments used should provide the temperature with a resolution of 0.1 degrees Celsius or less, the salinity in 0.01 of practical salinity units, the current speed with a resolution of 0.1 metres/second or 0.1 knots, and the current direction to at least 10°.
Report information is designed according to the reporting code FM 62-VIII Ext. TRACKOB. 
 
Mediterranean hydrographic vessel “Donuzlav” (defencerussia.wordpress.com)


10 October 2014

Russian Navy Morse


This short text does not claim to be complete or exact, it is just an attempt to collect and consolidate sparse notes about the Rus Navy way to Morse. I did examined my own logs, browse some Navy and Defense websites, mainly from Russia, N&O columns / Spooks newsletters, public available sources and public sites/forums on the web (later reported). You have to know that this document is always-under-construction and may be outdated, incomplete or even wrong.
Comments are welcome.

Morse code: it's just beeps in the air

Morse CW is cheap and straightforward; many examples suggest, it often is used as last attempt in case of technical - or propagational problems with fast transmission modes. It is however absolutely clear: the vast amount of data is exchanged by transmission lines via satellite or landline.
The Russian Navy (and other Russian Forces) still use the Morse Code and during these peacetime periods they openly transmit Morse Code references to activate voice and data links. They transmit the frequencies in Morse in the clear and the recipient ship-shore station transmits/receives according to the information received.  The Russians wouldn't be sending such open transmissions if the deployment wasn't peacetime operations.
Monitoring such transmission is not illegal, it is not an hostile behavior!
Ask yourself why the Russians still use Morse Code? You seriously think that all transmissions used by an adversary, or potential adversary is not routinely monitored by the other side? Do you not think that signals intelligence collection agencies interested also routinely monitor these open broadcasts? 

....  .  .-.  .     .--  .     --.  ---
tips
they use T ( _ ) as an abbreviation for zero ( _ _ _ _ _ ); 

the char K indicates that the recipient(s) are asked to confirm or just a "fast exchange" between two stations;
the sequence '+ ar' (end pf message) may be replaced by +, K, 'RPT AL QLN +', or similar endings such 'RPT AL QLN K' repeat back online (see later the section "procedural signs"); 
WLHN (rare) is believed to be a collective call, ie for all forces, and believed to be originated from Moscow HQ; 
<BT> is the prosign for = and in some cases it could depend on the decoder (see later the section "procedural signs");

common preamble format (if present)

preamble example: 
162 30 18 1202 162 = 517 = [message]

162 message number
30   groups count
18   day of month
1202 local time
517 (if present) appointment code, a specific person or dept at the address


the preamble may include the senders callsign too;
the preamble is not used in plain requests and replies using the Q-code (radio checks, ec.);  

the preamble may precede:
- encrypted messages: 
 [preamble] = [ 5FG or 5ALG with or without encryption group and coded end-group]

- weather reports:   
[preamble] = recipients = [FM-13 synoptic data]

status/priority of the message
RKT (rocket) higher in the hierarchy;
XXX flash message, can be compared with the USAF EAMs messages since they seem to use a certain set of codewords. It should be something like a "get attention" for a message of high priority;
SML (aircraft) a precedence higher than routine;
UUU as preface means routine;

Q-codes
They use an extended set of Q-Codes. Some are known, many others not.
QTC I have a message (message follows)
QWH I start send on frequency (KHz)
QWH 9700/rptd = 12056/rptd will send on 9700, alternatively on 12056
QWH 9700/8536 = 12056/12572 the link will run with two parallel frequencies
QYR I start working on 81 Baud RTTY (presumed)
QYS I start working on duplex RTTY
QYT4 I start use MS-5 system
QYT4 QMO adjust your MS-5 system
QSX I will listen on frequency (KHz)
QSX 8440/rptd = 12414/rptd I will listen on 8440, alternatively on 12414
QLS use (upper) alternative frequency or change frequency
QRS send slower
QCM your transmission is affected by technical problems
QLN  rpt via landline
QSA radio check (request and reply)


plain Q-code example messages (from my logs)
"VVV RIT RIT RIT DE RMWT RMWT QSA? QTC K"
"RBEG QSL 435 K"
"RGR70 DE RIW K"
“RAL2 DE RHW2 QSA 2 ? K”
"RMDV DE RIT QYT4 QMG 1"
"RDNK RDNK DE RIW RIW QSA? K"
"RCV DE RJT22 QYT QSX 5736 K"
"RCV DE RMGB QSA2 QRV K"
"RCV DE RMGB QSU1 QSX 8770 K"
"RMI93 OK QRU k"


weather reports messages
Ships send weather reports every 6 hours (usually 0000, 0600, 1200, 1800 UTC) for their current location. They use the standard observation method as described by NOAA in their observation handbook, and within this message format there is a Lat/Long position report for where the observation took place: so you are able to localize the positions of the ships by decoding the Code FM-13-X-SHIP (or shortly FM-13). This ships synoptic code is comprised of 23 groups of symbolic letters representing meteorological and oceanographic elements, report identification and ship location data (see resources later at the end of this post).

1) Ship current position is coded in the Ships Synoptic Code Section 0:
... 99LaLaLa QcLoLoLoLo ...
... 99662 10345 ...

99 Data on Position Follow

LaLaLa (662) Latitude in degrees and tenths of a degree. Always coded with three digits, the first two digits are actual degrees, the last digit for tenths of a degree (66.2)

Qc
(10) Quadrant of the globe (specify whether the latitude is north or south and the longitude east or west). 
If north of the equator (north latitude):
- 1 when east of the Greenwich Meridian (east longitude)
- 7 when west of the Greenwich meridian (west longitude)
If south of the equator (south latitude):
- 3 when east of the Greenwich meridian (east longitude)
- 5 when west of the Greenwich meridian (west longitude)



LoLoLoLo (345) Longitude in degrees and tenths of a degree. Always coded with four digits, with the leading (hundreds) figure coded as 0 or 1. The first three digits are actual degrees, the last digit for tenths of a degree (34.5)

2) the ship movement data is coded in Section 2:
... 222DsVs ...
... 22232 ...

222 indicator
Ds (3)
true ship’s course made good during the three hours preceeding the time of observation:
0
Ship hove to
1
NE
2 E
3 SE
4 S
5 SW
6 W
7 NW
8 N
9 Unknown
/ Not reported

Vs (2) Ship’s average speed, in knots, made good during the three hours preceeding the time of observation:
0
0 knot
1 1 to 5 knots
2 6 to 10 knots
3 11 to 15 knots
4 16 to 20 knots
5 21 to 25 knots
6 26 to 30 knots
7 31 to 35 knots
8 36 to 40 knots
9 Over 40 knots
/ Not reported

Examples:

VVV RJD99 DE RBC89 QSA? QTC RBC89 572 9 5 0955 572 = FOR RJD90 RJH74 =
050?? 99662 10345 41/96 9230? 00050 40000 52020 70222 89/// 22232 00030 20202 232// 40302 88000 05016 = + RBC89

in plain text:
"ship  RBC89 (calling RJD99) at (Moscow) time 0955 was at 66.2N 34.5E , heading SouthEast @ 6-10kts"
the position of RBC89 is decoded from 99|662 10|345, with the heading/speed obtained from 222|32.

CW "771 19 9 1551 771 ...99548 10198...22242...AR RMWT K"
in plain text:
"ship RMWT position at 1551 Moscow time: 54.8N 19.8E  heading South @ 6-10kts"
https://goo.gl/maps/fwcRV

Since the time of reception differs from the one indicated in the preamble (does not matter if UTC or Moscow Time), it is presumed that the preamble time is the time when the message was prepared and not the time of the transmission: i.e. the data relate to the observation at 1603 Moscow Time (1203z) but sent (and then received) at 1220z.

about the procedural signs (wikipedia)

In Morse code, prosigns or procedural signals are dot/dash sequences that do not represent text per se, but have a special meaning in a transmission: they are generally not copied down, they are a form of control character.
They are used to indicate formatting of the text being copied or to indicate operational changes in transmission. They may be written as if they were composed of two or three ordinary alphabetic characters but they are sent "run together", omitting the normal inter-character spaces that would occur if they were being sent as normal text. These ligatures are often represented in print either by a ligating bar (overline above the letters) or by surrounding the run-together letters with angle brackets (such as <BT>), indicating that they are linked and sent as one contiguous sequence.




Sources and References
Informations in this document was submitted by independent radio monitors or has been obtained from public available sources and public sites on the web. Wherever data was obtained via the web or elsewhere, references and/or links to these sources have been noted.


http://www.numbersoddities.nl/
http://www.vos.noaa.gov/ObsHB-508/ObservingHandbook1_2010_508_compliant.pdf
http://en.itar-tass.com/military-defense 
http://defencerussia.wordpress.com/ 
http://www.cvni.net/radio/nsnl/nsnl072/nsnl72mil.html 
http://sp8wjt.cba.pl/TELEGRAFIA/rus_navy.html 
http://planesandstuff.wordpress.com/ 
 

14 September 2014

Russian Naval Air Transport / Naval Aviation (M32b/RNAv)


Russian Navy   Russian Naval Air Transport / Naval Aviation   Russian Navy Morse
 
This short text does not claim to be complete or exact, it is just an attempt to collect and consolidate sparse notes about the Rus Navy way to Morse. I did examined my own logs, browse some Navy and Defense websites, mainly from Russia, N&O columns / Spooks newsletters, public available sources and public sites/forums on the web (later reported). You have to know that this document is always-under-construction and may be outdated, incomplete or even wrong. Comments are welcome.

The Russian Naval Aviation (Aviatsiya Voenno-morskogo Flota Rossii) is the air arm of the Russian Navy, having superseded the Soviet Naval Aviation.
The air forces of the most important fleets, the Northern and Pacific fleets, operate long range Tu-142 anti-submarine warfare aircraft and Il-38 medium-range ASW aircraft. Formations operating supersonic Tu-22M3 bombers were transferred to the Russian Air Force's Long Range Aviation in 2011. The relatively small fleets, the Baltic and Black Sea, currently have only tactical Su-24 bombers and ASW helicopters in service. The small Caspian Flotilla operates An-26 and Mi-8 transports, Ka-27PS rescue helicopters, as well as some Ka-29 and Mi-24 armed helicopters.
On July 15, 2014, a modernised version of the Ilyushin 38N anti-submarine plane was officially delivered to the Russian Navy. 
 

Naval aviation has a functional division into the following branches: Naval missile-carrying aviation, ASW (anti-submarine warfare) aviation, Attack aviation, Reconnaissance aviation and Auxiliary air units (of airborne early warning defense, electronic warfare, counter mining, guidance and communication support, aircraft fueling in flight, SAR, transport support and ambulance aviation).
Naval Aviation units are based in aerodromes and aircraft cruisers, divided into Shipborne and Shore-based Aviation.
 

As of 2012, the only fixed wing strike and fighter aircraft of Russian Naval Aviation are the Su-33 fighters and Su-25UTG attack aircraft of the 279th Regiment (forming the Admiral Kuznetsov's carrier air wing), plus the Su-24 bombers based in the Crimea. This sole bomber unit remained part of Naval Aviation as an exception to satisfy treaty requirements governing Russian forces deployments on Ukrainian territory (these must be part of the Black Sea Fleet). Buying brand new multirole Sukhoi Su-30SM for the Black Sea Fleet to replace Su-24 is in the planning stages. 
Naval aviation also retains the anti-submarine aircraft of the forces (the Tu-142 and the Il-38) and the helicopter arm.

frequencies

4198.5, 8131, 8816, 11354 kHz
Modes: CW + USB (voice)


callsigns

Ground
Below are the approaches I found, callsigns actually are in use. The allocations would make sense, but are absolutely not confirmed. 

RJF94 (tactical PROBOJ)
HQ Naval Air Transport - Moscow

RJC48 (tactical NORKA)    
Naval Air Transport Southern Sector / Black Sea Fleet Naval Aviation
South Crimea region, 7057th Airbase, Gvardeskoye and Kacha

RCB (tactical KRAKET)   
Naval Air Transport Western Sector / Baltic Fleet Naval Aviation
West Kaliningrad region, several airfields possible
Bases in Chkalovsk, Nivenskoye and Bykhov

RJC38 (tactical NOVATOR)    
Naval Air Transport Northern Sector / Northern Fleet Naval Aviation
Murmansk or Sevoromorsk
Bases in Olenia, Arkhangelsk, Severomorsk, Kipelovo

RCH84 (tactical MONOLOG)    
Naval Air Transport Eastern Sector / Pacific Fleet Naval Aviation
Wladivostok Region.  Airfield of Knevichi
Bases in Petropavlovsk, Sovetskaya, Gavan 
            
RJC62

RJE56
NCS station Moscow, has contact with many Navy stations

RJF95



* aircraft carrying cruiser "Admiral Kuznetsov"
the carrier (the only one of the Russian Navy) should have the callsign RKO81, but it's not absolutely confirmed. 


* Airport 
callsigns were 3-figure-codes in the past, today they give either normal ICAO Uxxx  codes or internal Xxxx codes (Xxxx is the same code as Uxxx).

Aircrafts
5 digit callsigns of aircraft correspond to the registration number and can be identified in most cases (only valid for Naval Air Transport fleet)

traffic

Simplex contacts with aircraft (5 figure codes) with flight status reports. They mix common ITU-Q-codes (e.g. QRE, QTH, QTR etc) and ICAO-codes (as QAY, QBG, etc) with internal codes (e.g. QQL, QQM).

QTC I have message for you.
QRV I am ready.
QTO I am airborne or I started at ... (hours).
QTR The time is ... (UTC used).
QRD I am bound for ... from ... .
QRE Estimated time of arrival at/over ... (place)is ... (time).
 
QAH Flight level/altitude is ... (in meters or barometric pressure)
QQL I have passed ... (place) at ... (time).
QBD Fuel endurance is ... (hours and minutes).
QAL  I estimate to land in ... (place) at ... (time).
QQM I will land in ... (place) at ... (time).


Message samples about aircraft (47944) working with Kaliningrad (RCB):

47944 QAY UWMS 1405 K
47944 passed UMWS (= Smorgon) at 1405 hrs

RCB RPT QAY K
RCB asks to repeat the location

RCB de 47944 QAY UMWS 1405 QAH 5500 QAL XMWS 1500 QBD 0230 K
 
47944 informs RCB that it passed UMWS at 1405 hrs and further its height (QAH) : 5500 metres its estimated time of arrival (QAL) in Kaliningrad (XMWB) at 1500 hrs and the amount of fuel (QBD) “My fuel endurance is 2 hours and 30 minutes”

Russian Navy   Russian Naval Air Transport / Naval Aviation   Russian Navy Morse
 


Sources and References:

30 August 2014

Russian Navy (M32a/RNv)



This short text does not claim to be complete or exact, it is just an attempt to collect and consolidate sparse notes about the Rus Navy way to Morse. I did examined my own logs, browse some Navy and Defense websites, mainly from Russia, N&O columns / Spooks newsletters, public available sources and public sites/forums on the web (later reported). You have to know that this document is always-under-construction and may be outdated, incomplete or even wrong.Comments are welcome.



The Russian Navy (Voenno-Morskoj Flot Rossii, lit. Military-Maritime Fleet of the Russian Federation) is the naval arm of the Russian military. The present Russian Navy was formed in January 1992, succeeding the Navy of the Commonwealth of Independent States, which had itself succeeded the Soviet Navy following the dissolution of the Soviet Union in December 1991.

Russian Navy is now probably the last fleet of the world that uses on such a large scale CW. Russians know that not everything can be converted into dollars in the pursuit of modernity and profit, and traditional communication systems such as Telegraphy still have their good sides, like simplicity, reliability, resistance to interference, and finally tradition.
 The Russian Navy possesses the vast majority of the former Soviet naval forces, and currently comprises the Northern Fleet, the Russian Pacific Fleet, the Russian Black Sea Fleet, the Russian Baltic Fleet, the Russian Caspian Flotilla other than the Naval Aviation, and the coastal troops (consisting of the naval infantry and the coastal missile and artillery troops.


The Northern Fleet is armed with nuclear-powered and torpedo submarines, missile-carrying and anti-submarine aircrafts as well as rocket-powered, aircraft-carriers and anti-submarine ships. It established as a modern formation in 1933, is headquartered at Severomorsk and spread around various bases in the greater Murmansk area. This is the main fleet of the Russian Navy. 

The Russian Pacific Ocean Fleet, established on 10 May 1731 and headquartered in Vladivostok, is another operational-strategic unit of the Russian Navy. In order to fulfill its military missions, the Pacific Ocean Fleet is armed with strategic rocket-powered submarine cruisers, multipurpose nuclear-powered and diesel submarines, surface ships for ocean and sea-zone maneuvers, marine rocket-carrying/anti-submarine and fighting aircrafts along with land forces and some land forces and coastal defense divisions.
The Black Sea Fleet ( BSF) is an operational-strategic association of the Navy of Russia in the Black Sea with the main base situated in Sevastopol. The Russian Black Sea Fleet, as a part of the Navy, is a means of ensuring Russia's military security in the south. To perform the tasks the Black Sea Fleet has in its composition diesel-driven submarines, surface ships for operations in oceanic and near-sea areas, naval missile-carrying aviation, anti-submarine and fighter aviation, units of coastal troops.
Currently, the main tasks of Russian Black Sea Fleet are as follows:
- Protection of the economic zone and areas of productive activities, suppression of illegal productive activities;
- ensuring safety of navigation;
- implementation of foreign policy actions of the Government in economically important areas of the oceans (visits, routine entries, joint exercises, actions as a part of peacekeeping forces, etc.)


The Baltic Fleet is an operational-strategic unit of the Russian Navy at the Baltic Sea. Main bases are Baltiysk (Kaliningrad region) and Kronshtadt (Leningrad region). They consist of surface ships division, diesel submarines brigade, service boats and search-and-rescue ships formations, the Air forces, coastal defense troops, rear technical and special security units.

The Caspian Flotilla, established on 4 November 1722, is based in Astrakhan and Makhachkala with its headquarters in Astrakhan.


(reported) CW frequencies 
(The main frequencies in use are 8345.0 kHz and 12464.0 kHz, although there are hundreds listed that have been used by the Russian Navy. They are all in CW)
583 3192 3338.5 4048 4079 4376.5 4478 4851 5019 5135.5 5213 5224 5343 5400.5 5775
6308 6345 6769 6827 6948 7015 7467 7566 7632 7664 7749 7763 7861 8136 8345 8816 8794
9068.5 9069.5 9145 9192 9373 9988 10203 10543 11000 11155 12464 13044 13636 13975
14556 15812 17468 17615 19201 19304 21438

(known) Callsigns:
RIW Navy Headquarters, Moscow 
Headquarters in Moscow is a very active station maintaining liaison with ships of all fleets, often at great distances from the so-called 'Dalnymi pohodami' or Russian naval expeditions to distant sea, and squadrons. 
HQ Moscow uses multiple broadcasting centers around Moscow, hence uses many callsigns, RIW is most commonly used, but they are also characters such as RAA (perhaps it is the commander's call sign WMF, or main headquarters WMF), and often RJE56 - it is broadcasting center in Manikinie near Moscow. Sign RJE56 is used only when XQ or communication between stations on land specifically allocated for this purpose frequencies. In the past, were also used in other characters, such as RMR

- Northern Fleet
RIT  Severomorsk, Northern Fleet Headquarter
RJD56 Murmansk, Naval Base
RJD99 Severodvinsk,  Naval Base

RIT main frequency 11155.0


- Baltic Fleet
RMP Kaliningrad, Baltic Fleet Headquarter
RJC66 ST. Petersbourg, Comm. Center
RJD69 Baltiysk, Naval Base
RJD85 Kronstadt, Naval Base


- Black Sea Fleet
RCV Sevastopol,
Black Sea Fleet  Heardquarter
RJE65 Istanbul, Naval Base

- Caspian Flotilla
RKN Astrakhan, Caspian Flotilla Heardquarter
RJD52 Caspiysk, Naval base


- Pacific Fleet
RJS Vladivostok, Pacific Fleet Heardquarter
RCC Petropavlovsk Kamchatskiy, Naval Base
RTS  Magadan, Naval Base (mostly abandoned)
Frequencies of RJS: 4048, 10203, 13636, 7632 kHz

some other known stations
RAB99 KHABAROVSK (Vladimirovka)
RJE56 MOSCOW (MANIKINO)
RJH25 KIRGHIZISTAN 
RJH63 KRASNODAR (MARTANSKAYA)
RJH66 CHALDOVAR, KZ (KARA-BALTA)
RJH69 CVILEIKA, BLR
RJH77 VILEIKA, BLR
RJH90 NIZHNY NOVGOROD
RJH99 DRUZHNIY


Notes: (Derived from Fritz’ excellent website at http://www.astrosol.ch/index.html) 
  • RIW is a function, not a location. There is evidence the RIW operators use several callsigns from the same desk. In certain cases RIW becomes RJE56. In normal traffic with any ship RIW suddenly becomes RAA for an hour just to continue as RIW again.
  •  RIT uses the collective callsigns RLO, RKZ, RKS and others for its fleet or for a certain task force.
  • RMP uses the collective callsigns REO, RMU, RKZ and others for its fleet or for a certain task force.
  • RCV uses the collective callsigns RKZ, RKS, RJV, RIP90, RBE86, RGX94 and others for its fleet or for a certain task force.
(known) Callsigns used by the ships
I recently found a good site by Tony Roper (planesandstuff) reporting an updated list of Russian Navy Callsigns that have been picked up on HF over the last few years. Where callsigns have been positively tied up to certain ships or stations, this is also shown.  
As Tony says, "it's an incomplete list and will be updated as new callsigns are picked up" anyway that's a good work and it is a list of great help for listeners who love that branch of HF trasmissions.The callsigns address is: http://planesandstuff.wordpress.com/russian-navy-callsigns/
 Quite a few ships have been tied up to the callsigns through their reports. This is achieved from the Russian Navy themselves as they publish news items everyday on the internet, especially when ships arrive at certain locations. I'd suggest also the use of a few other websites including Shipspotting.com and Bosphorus Navy News

--> Read more info about the Morse used by Russian Navy

ships tracking (listening to ships weather reports)

Russian Navy ships send weather reports every 6 hours for their current location. They use the standard observation method as described by NOAA in their observation handbook, and within this message format there is a Lat/Long position report for where the observation took place. This means you are able to track their positions.
Ships positition can be derived from the Code FM-13-X-SHIP (or shortly FM-13), the ships synoptic code. It is comprised of 23 groups of symbolic letters representing meteorological and oceanographic elements, report identification and ship location data.

- Ship current position is coded in the Ships Synoptic Code Section 0:
... 99LaLaLa QcLoLoLoLo


99, Data on Position Follow.
LaLaLa, Latitude in degrees and tenths of a degree.Always coded with three digits, the first two digits are actual degrees, the last digit for tenths of a degree.
 

Qc, Quadrant of the globe (specify whether the latitude is north or south and the longitude east or west).If north of the equator (north latitude), Qc is coded as 1 when east of the Greenwich Meridian (east longitude), or as 7 when west of the Greenwich meridian. If south of the equator (south latitude), Qc is coded as 3 when east of the Greenwich meridian, or as 5 when west of the Greenwich meridian.
LoLoLoLo, Longitude in degrees and tenths of a degree. Always coded with four digits, with the leading (hundreds) figure coded as 0 or 1. The first three digits are actual degrees, the last digit for tenths of a degree.


- the ship movement data is coded in Section 2:
222DsVs ...

222, indicator
Ds, true ship’s course made good during the three hours preceeding the time of observation:
0 Ship hove to
1 NE
2 E
3 SE
4 S
5 SW
6 W
7 NW
8 N
9 Unknown
/ Not reported


Vs, Ship’s average speed, in knots, made good during the three hours preceeding the time of observation.
0 0 knot
1 1 to 5 knots
2 6 to 10 knots
3 11 to 15 knots
4 16 to 20 knots
5 21 to 25 knots
6 26 to 30 knots
7 31 to 35 knots
8 36 to 40 knots
9 Over 40 knots
/ Not reported


So, looking at the following heard message:

VVV RJD99 DE RBC89 QSA? QTC
RBC89 572 9 5 0955 572 = FOR RJD90 RJH74 =
050?? 99662 10345 41/96 9230? 00050 40000 52020
70222 89/// 22232 00030 20202 232// 40302 88000
05016 = + RBC89


the ship  RBC89 (calling ship RJD99) at that time was at 66.2N 34.5E , heading SE @ 6-10kts: the position of RBC89 is decoded from 99662 10345, with the heading/speed 22232:


You can also do a quick check of MarineTraffic.com to see what it shows where a ship had reported its position...


other CW messages and Q-codes
other CW messages are QTC and QSA requests such as:
VVV RCV DE RFH70 QSA?

RCV DE RFH71 QSA 3 K

VVV RJD99 DE RBC89 QSA? QTC
RBC89 186 ?? 5 0730 186 = FOR RJD90 RJH74 = 05021 99662 10362 41/96 92207 00040 49980 54000 748?4 89/// 22272 00030 20202 319// 40402 88000 05016 = + RBC89

The following message is a radiocheck 
RCV DE RFH71 QSA 3 K
sent by ship Novocherkassk, Amphibious Landing (callsign RFH71) to HQ base of BSF in Sevastopol (RCV)


Novocherkassk

Other than the Q-codes meanings assigned by ITU, the following codes are used by the Russian Military:

QWH I start send on frequency

QWH 9700/rptd = 12056/rptd will send on 9700, alternatively on 12056
QWH 9700/8536 = 12056/12572 the link will run with two parallel frequencies

QYR I start working on 81Baud RTTY

QYS I start working on duplex radiotelephony


QYT4 I start use MS-5 system

QYT4 QMO Adjust your MS-5 system

QSX 8440/rptd = 12414/rptd I will listen on 8440, alternatively on 12414QLS Use (upper) alternative frequency or Change frequency!

QRS Send slower

so that a trasmission such as:
RMRV OK QYT 4 QWH 16680 K
means that ship RMRV will start to transmit in MS-5 multiplex mode on 16680.0 KHz 


 
Sources and References: