Thanks to SDRplay, I was sent both their new RSPdx and older RSPduo SDRs at the end of January free of charge.
The main reason was to get them integrated into Procitec’s go2MONITOR and go2DECODE software, to increase the number of SDRs that the company’s products are compatible with.
This I’ve been successful in doing with the RSPdx – I’m still to unbox the RSPduo at this time of writing.
First of all though, I’ve been extremely pleased with the RSPdx in its own right. The SDRuno software works really well, is pretty easy to use – and it looks good too.
The fact that you can have up to 10 MHz of bandwidth is brilliant, and it isn’t too bad on the CPU usage either – running at around 25% with 10 MHz bandwidth on my ancient PC. Used with SDRConsole you can cover a good number of frequencies at once, and can record them if necessary. Of course, you can do this with SDRuno too, but at the moment only IQ – you can’t record individual frequencies.
Saying that, I’ve seen the SDRuno Roadmap for future releases and not only will recording of individual frequencies be possible, a more advanced scheduler is to be included. This is something I feel SDRConsole – amazing though it is – is lacking when it comes to single frequency recording. There is also the issue with SDRConsole that you are limited to recording only 6 hours worth of wav file per frequency.
Anyway, I digress. Back to the RSPdx and go2MONITOR.
To get the SDRs to work correctly with any of the go2 products means creating a configuration file and adding a ExtIO DLL file to the software. This is reasonably easy to do once you get use to it and it enables a GUI to become active so that you can control the SDR through go2MONITOR.
One interesting aspect with the RSPdx GUI is that regardless of what you enter as some of the parameters in the configuration file, the ExtIO file overrides these. Effectively, I just left some of the data as found in a basic configuration template and let the GUI do all the work for me.
So, below are some of the results with today’s first test.
First of all I went into the VHF/UHF side of things and targeted the local TETRA networks. These were found easily and after messing around with the GUI, I was able to get go2MONITOR set up to nicely find all the emissions within the 1.6 MHz bandwidth I’d chosen to use
From there, all I had to do was to select one of the found emissions and let the software do its thing.
Next I moved on to HF where there’s a plethora of data to choose from to test out the SDR. There was quite a large storm going through at the time and my Wellbrook loop and coax feed were getting a bit of a bashing with some considerable interference being produced with the really strong gusts, as can be seen below – the interference between the two HFDL bursts is one such gust.
I’ve frequently mentioned the Results Viewer that’s part of go2MONITOR and with things such as HFDL and TETRA, that process data quickly from lots of signals, this part of the software comes into its own.
The image below is two minutes of HFDL monitoring. All the red blocks is received data that scrolled through the Channel window too quickly to read live. In the viewer you can select any of the signals and you’ll be shown the message as sent. In this case, it is one sent by an Open Skies Treaty observation flight OSY11F.
By looking at the Lat/Long and comparing it to the flight history from FlightAware and its location at 1313z it ties in nicely. This flight was carried out by the German Air Force A319 1503 specially kitted out to make these flights.
go2MONITOR has a basic map function within the Result Viewer function so if there’s any Lat/Long position within any message it will plot it – as shown below for OSY11F at 1313z.
Within the General tab of Result Viewer you can get all the parameters of the signal.
One final test that I carried out was how well everything coped with a bigger bandwidth. In HF I can use up to 3 MHz of bandwidth with the licence I have – going up to 10 MHz once into VHF/UHF. In HF then, I selected 3 MHz in the GUI and then ran an emissions search.
My PC is nearing the end of its life but it coped easily with the amount of data found despite only having 4 GB of RAM with a 3.6 GHz AMD processor – a new PC is in the pipeline that is going to give me much better processing power.
Despite having 3 MHz available, not everything was identified. Most of this was at the fringes of the bandwidth, but some of the weaker signals also failed. That doesn’t mean you can’t then process them further, you can, it’s just the Emissions scan hasn’t quite been able to ID them. Saying that, the software managed to ID things within 2.2 MHz of the 3 MHz bandwidth.
I picked one of the weaker signals to see how both the RSPdx and software coped and they did very well, pretty much decoding all of the CIS-50-50 messages that were coming through on 8678 kHz.
So, overall, pretty pleased with how the RSPdx works with go2MONITOR.
Once I get a better PC I’ll be able to test at bigger bandwidths but even with 3 MHz here I was able to achieve the same, if not better, results than I have with the considerably more expensive WinRadio G31 Excalibur I have been using previously (running with the G33 hack software).
Not that I’m likely to really use go2MONITOR at big bandwidths – 1.6 MHz is probably fine for me – but for Pro’s there’s no doubt that having these “cheaper” SDRs would make absolutely no difference over using an expensive one such as those in the WinRadio range. In all honesty, I don’t think I’ll be holding on to the WinRadio for much longer – I’m more likely to get another RSPdx to cover this area of my monitoring.
On its own, as an SDR, the RSPdx is worth the money I’d say. I like it just as much as I do the AirSpy HF+ Discovery – the only real difference I can see between these two SDRs is the max bandwidth available.
If you follow me on Twitter you’ll see that in the last month or so I’ve been sending out images of classification and decoder software go2MONITOR working with a number of my SDR’s.
go2MONITOR is part of the go2SIGNALS range of software solutions created by PROCITEC GmbH operating from Pforzheim in Germany, themselves part of the PLATH group. PLATH Group is the leading European-based solution provider for communication intelligence and electronic warfare (EW) with worldwide government customers. The group covers all aspects of signal interception and analysis split between a number of companies such as PROCITEC. EW, COMINT/SIGINT, Jamming and Decoding are just a small part of what the group specialises in.
go2MONITOR is advanced high-performance, automatic HF, VHF and UHF monitoring software capable of recording, SDR control, wideband and narrowband classification and multichannel signal decoding.
It isn’t for the faint hearted, but once you get used to using it, it really does make gathering information on networks extremely easy. And it decodes many modes other software can’t.
In a series of blogs I’m going to show you the capabilities of this amazing software, though I must stress now, it is aimed at Professional SIGINT gathering and it comes with a Professional price tag.
Saying that, it doesn’t mean it isn’t available to the non-professional. It is open to all and to cover this it comes in various versions starting with the Standard package progressing to a full Military package – which gives you the full range of HF, VHF and UHF classification and modem recognition decoders available, including PMR and SAT (Inmarsat AERO). The Standard version isn’t to be sniffed at, it still gives you an amazing range of decoders, though you could easily argue that many of these are available in other free – or near to free – decoding software like MultiPSK or Sorcerer. A full list of decoders available can be found here. Note, this list is broken down into the various packages and not all are available with the Standard option. Confirm what belongs to what if you’re thinking of purchasing.
So what’s the difference in what go2MONITOR can do with other software available? That’s the idea of these blogs, to answer just that question. It will take quite a few blogs – mainly because there isn’t just one answer.
Here then, is a brief overview of what can be done, what SDR’s it works with – in fact, not just SDR’s but all receivers that can produce a recording – and any other things I can think of.
As, I’ve said then, it can decode pretty much any data signal out there. Obviously, some signals are encrypted so it wouldn’t fully decode unless you had the key, but you can get the encrypted messages. It can also classify voice signals, not just data. So, if you wanted to hunt out various voice networks, go2MONITOR can assist you in doing this.
Here is where it excels. Classification – and doing it very quickly.
Imagine being on your SDR (SDR1) and you can see a whole load of data signals on the waterfall/spectrum and you quickly want to know what they all are. With go2MONITOR operating another SDR (SDR2) you can dial in the centre frequency of the bandwidth shown on SDR1 into the go2MONITOR/SDR2 combo, click one button – Find Emissions – and within seconds the whole bandwidth has been analysed and every signal classified.
I’ll go back a step though here. You don’t need two SDR’s. One will do. SDR1 – as long as it is a compatible SDR – can be controlled through a GUI by go2MONITOR. The software includes a waterfall/spectrum display. Like all SDR software, these displays are fully adaptable to how you like to see the signals.
Either way, you now have a list of every emission that go2MONITOR has received within that bandwidth. This list includes Modulation type, Frequency, Bandwidth, Symbol (Baud) rate and SNR. It also shows which SDR you have used for interception (useful if you’re using go2MONITOR with more than SDR at the same time, but also with other advanced features such as network control), and it also shows if the frequency is already stored within the frequency database – yes, you can create this too; or import ready made databases in a CSV format.
Already then, you have built up a picture of what these signals are. One thing to note. If the signal type is not one of those included within the package you have, it will be classed as unknown. Example – a STANAG 4285 will show as unknown in the Standard and PMR/SAT package, but will be classified correctly in the MIL package.
OK, those of us that are looking at SDR’s all the time can pretty much tell what the signals are just by looking at them, so there’s no great advantage here is there? Except, now go2MONITOR has logged these in its database which can be searched through at a later date – handy if you’re looking for potential schedules for example.
However, the next step is where things get interesting. By putting one of these emissions into a “Channel” you can carry out an advanced classification, recognition and decode. You have multiple choices here, but I generally start off with a Classification. Whilst the software has already decided what the emission type is, by doing this it double checks just this one channel and produces a choice of decoders that it is likely to be.
By using STANAG 4285 as an example, it will put this into the list of choices, but it may put other PSK signals there too. By clicking on another button, this puts the channel into Recognition mode and it reduces the hundreds of decoders down to just those in the classification list produced. The software then calculates which is the best decoder and starts to decode the signal.
If you think about STANAG 4285 in other software, you generally have to try all the various potential Baud rates – is it Long Interleaving? is it Short? etc etc. Well go2MONITOR does this automatically. It checks the alphabet and protocol and will decode it if known. More often than not it can’t calculate the alphabet, but every now and again it does and it will produce encrypted data – don’t forget, if it’s encrypted it won’t decrypt it without the correct key.
This further Recognition and Decoding is also stored in the database for later analysis, along with a recorded wav file for playback and deeper signal analysis.
Seriously, it is harder describing it in text than it is doing it so I’ve created a video that’s at the end of this blog.
I mentioned previously that the software works with receivers that aren’t SDR’s. That’s because, as long as you can create a wav file recording – Narrowband as it’s known in go2MONITOR – it can be analysed. There are things missing, the actual frequency for instance (though this can be typed into a text box so that you can then have the right information – this i’ll show in a later blog). Time stamps aren’t naturally there but again you can add these by telling the software to use the time the recording was started.
I’ve used recordings made on my Icom IC-R8500 as an example of this but it is literally the bandwidth of the mode used by the receiver that is shown on the go2MONITOR spectrogram.
You don’t actually need to own a receiver of your own. Use an online SDR such as a KiwiSDR, record the IQ as a wav file and play it back through go2MONITOR for analysis. I’m doing just that for a Jane’s Intelligence Review magazine article.
If you use SDRConsole, then you may have also tried the File Analyser function that I blogged about in August last year. The File Analyser in SDRC is excellent, there’s no doubt about it, but it has one drawback. Once you’ve carried out your recording you have to create a run through of the recording, making an XML file that effectively joins all the wav files up. If you’ve made a wide and long IQ recording this can take quite some time. With most of my overnight recordings – normally 7 hours long, with a 768 kHz bandwidth – this takes around 45 minutes to complete.
With go2MONITOR you can also record the bandwidth IQ data. With this you can do two things. Firstly you can run it through as a normal playback, classifying and decoding as you go. Secondly though, you can open the Results window which gives you a time based view of the whole recording allowing you to immediately see any transmissions. Unlike SDRC Analyser, the signals have already been classified, and more importantly, this is done straight away without any need to create an XML file first. The Results window will be covered in greater detail in a blog of its own.
However, there are no decodings here. With just an IQ recording you need to play it back and run an emission search etc. There are some basic automation tasks available, such as setting up an emissions search every 10 seconds.
But, if you have the Automated Monitoring and Tasking package, you can also have the software automatically record, recognise and decode a single emission type – or all emissions types within the bandwidth, a set frequency, between two frequencies or any other parameters you may wish to set up.
The list of SDR’s that can be used with go2MONITOR is pretty good, though due to the target audience, many of them are high end, “government/military” receivers. But, it does work with Perseus, SDRplay RSP1 & RSP2, RFSpace NetSDR and SDR-14, and of course AirSpy R2 – and now the AirSpy HF+ and AirSpy HF+ Discovery.
Supported receiver list:
Max. Rx bandwidth
Grintek GRX Lan
IZT R3xxx series
Up to 3 channels spectrum
IZT R4000 (SignalSuite)
1 channel only
Limited USB 3.0 compatibility
narda® NRA-3000 RX
narda® NRA-6000 RX
narda® IDA 2
VITA 49 support. Only 1 MHz and no receiver control at LINUX
PLATH SIR 2110
LINUX recommended. External receiver control only
PLATH SIR 2115
External receiver control only
PLATH SIR 5110
16×768 kHz subbands External receiver control only
PLATH SIR 5115
40×768 kHz subbands External receiver control only
No gain control available
R&S EM100 / PR100
External receiver control only
Experimental support. Continuous signal up to 2.4 MHz
SDRplay RSP1 & RSP2
Up to 2 channels + spectrum
Generic VITA 49 receiver support
Max. receiver bandwidth
Can be configured in a wide range for different receiver types
Other generic “Winrad ExtIO” supported receivers
Max. receiver bandwidth
As you can see, there is a huge difference in bandwidth capabilities for each receiver. I use my WinRadio G31DDC quite often with go2MONITOR, but the AirSpy HF+ Discovery (not listed as i’ve only just got it working) isn’t much worse with it’s full 610 kHz bandwidth.
When you think that the G31 has a much better operational bandwidth than 800 kHz when you use it on its own, it’s obvious which is better value if you were buying an SDR solely for using it with go2MONITOR. It is this kind of thing that many Government agencies are looking at when it comes to funding operations aimed at large scale monitoring.
That then is a very basic overview of go2MONITOR. The quick video and images have hopefully shown you a little of what is possible.
Outside of a Professional SIGINT operation, why would an amateur radio monitor need something like go2MONITOR? And would they pay the price?
I think they would. After all, most of us have spent a fair amount on radio monitoring over the years, so why not on software that would make their monitoring not only quicker and easier, but potentially open up new areas of monitoring.
Many of us specialise in certain monitoring areas – Russian military, particular the Navy and Strategic aviation for me for example. With go2MONITOR I have already used it to hunt out potential Russian Northern Fleet frequencies by running an automated 10 second CW emission scan overnight within a bandwidth block. By doing this, and then analysing data found in the results window, I was able to target certain frequencies to see what activity there was on subsequent nights.
Whilst there are other decoders available – some of which are plugins in software such as SDR#; some of which are free – it is the quickness and ease with which it can be done that makes go2MONITOR attractive. The big question is, would you pay for this?
The shack, finally operational after a few months off.
With the rebuild of my shack complete I’ve been able to start testing out all my radios, new connections etc.
The Mini-Circuits components all come well packaged in anti-static bags
A whole bundle of new cables from Mini-Circuits arrived last of all and have helped tidy up the back of the radio 19″ rack considerably. I’ve previously installed quite a few Mini-Circuits components, including 0.141″ diameter Hand-Flex interconnect cables, and so it was more of these that I opted for. The bonus with these cables is that they are hand formable meaning you can shape and bend them into pretty much any area that you want to. The 141 series (which I use) are capable of a 8mm bend radius, whilst the thinner 086 series can be bent to 6mm.
Being able to manipulate the cables certainly helps in tight spaces, and when you don’t want them to hang down
Previously I used hand-made cables with RG58U coax, but in order to have a 19″ rack that can slide out from under the desk, the cables needed to be longer than actually required. Because of this the cables would drop down into all the others attached to the PC and in some cases cause a little interference. With the Hand-Flex cables I’ve been able to use the same length of coax to allow me to move out the rack, but be able to bend them up and out of the way of the PC cables.
They’re also very good for the radios on the rack, being able to bend them and hold in place around the radios and other cables. They are near lossless too with a quoted insertion loss of 0.01 dB in the HF band to 0.55 dB at 18GHz. I normally run tests of the Mini-Circuit components when I receive them and find that the figures quoted are near spot on. I highly recommend these cables if you’re looking to upgrade your systems, and are available from the Mini-Circuits website, along with lots of other goodies that will tempt you.
Measurement of insertion loss of the Mini-Circuits ZF3RSC-542B-S+ Power Splitter/Combiner I also purchased as part of my plans for satellite communication monitoring. This is connected to the AirSpy SDR and takes feeds from two SatCom connections (currently deactivated) and a WinRadio AX-71C Discone Antenna. Mini-Circuits quote an insertion loss of around 19.5dB at 130 MHz which is confirmed here with a signal generated at -20dB being less than 1dB out at -40.48dB when passed through the combiner.
This image shows how the cables can be held in place without cable ties
The radio setup now includes two new SDR’s – an AirSpy HF+ and a standard AirSpy with the HF+ replacing the Enablia TitanPro. I’ve also reinstated my WinRadio G31DDC which had been in storage for a year or so. I really do like the TitanPro, and have put it into storage for the time being. The recording capabilities in particular are great with it being able to select 40 frequencies at once spread over numerous bandwidths, but I have had issues with the power supply – one being it caused interference. I attempted to make one of my own but it has a 6v(+/-1v)/2.5 Amp current requirement and no matter how many different methods of building my own supply using a 12v feed downgrading to 5, 6 or 7 volts, it just wouldn’t work in a stable manner. In the end it was easier to remove it and slot the G31DDC back in its place.
As it is, I’d forgotten how good the G31DDC is and I don’t really feel like I’m missing much thanks to the ability to use the other SDR’s with SDR Console V3 and it’s SDR Analyser.
The three 19″ racking units from Penn Elcom, along with all the shelves, have been very useful and certainly makes things easier when it comes to changing radios and connections over. I can just disconnect a few things and slide the whole unit out. I also obtained a 19″ Project box from them which I used as my main 12v switch unit. This is connected to two regulated desktop power supplies that act as master switches.
Although the SDR Console website page for the Analyser states it isn’t available yet, this is incorrect and it is downloaded with the latest version of the main programme.
If you’re a current user of V2 or have been in the past then you won’t notice much difference. You can have up to 24 parallel demodulators operating within the SDR’s bandwidth that you have chosen, all of which can run independent of each other in receive and record. You can also run each demodulator through a decoder such as MultiPSK independently and decode these in parallel with each other. This capability has taken that step towards those of the TitanPro, especially when being used with the Elad FDM-S2 that can provide a Maximum DDC bandwidth of 6144kHz’s.
Unfortunately, whilst you can schedule recordings of IQ data, you still can’t do this for individual channel recordings. This is a real shame as it would be a fantastic addition to the capabilities of SDR Console.
Getting back to the analyser though this does, in theory, cancel out the lack of channel recording scheduling.
When you record IQ data it is saved as WAV files, split into multiple ones depending on how long a recording you make . All of these files can be individually played back through the incorporated SDR Console player but even better is the use of the File Analyser.
With this you get a visual “image” of the complete recording, whereby after opening the analyser you get it to combine all the files into one XML file. For the image below I used the FDM-S2 with a selected bandwith of 768kHz centred on 4425kHz, hoping to catch calls to Russian Naval base Severomorsk in CW(RJD99) from ships operating in the region. I set the scheduler up to record from 0000z to 0700z which worked perfectly, giving me 78 files totalling 78GB – obviously, the bigger the bandwidth, the larger the total file size.
After clicking on New in the analyser and browsing to the relevant folder the WAV files are saved in, the analyser finds the first one and gives this as an option to open – it automatically adds the remaining WAV files and starts the process. This can take quite some time to extract, around 45 minutes for the example shown. But you only need to do this once because once it has finished you can save it as an XML file and open it at any time – in this case it was a 28MB XML file.
A note here – do not then delete the WAV files as the analyser still needs them.
As you can see, I was successful in locating calls to RJD99, and I have highlighted some of the others that I took a look at – this is just a screenshot of two hours out of the seven recorded.
All you then need to do is find any signal of interest, and after clicking on select and start in the top ribbon, click on the signal. This will then start playing the file from that location in the main SDR Console window. You don’t need to stay on that frequency, you can use the Console as if you were listening live and move around the frequency range you dictated in the bandwidth of the recording.
And, as it is basically a live screen you can do additional things such as record and use decoding software.
RJI92 calling RJD99 on 4416 kHz during playback of the Analyser
When using the Analyser I run this through a separate PC meaning SDR Console itself can carry on working on the main radio control PC. This is also handy if you’re away but have time to go through the IQ data using a laptop. Just copy over the original WAV files to a portable hard drive/memory stick and carry on as described above.
There are numerous other functions available for you to use with the main part of SDR Console, some I still haven’t had the chance to play with completely. I’m still exploring things such as the Signal History function which can store up to 48 hours of data. Here you can export data in CSV format to third-party programs such as QtiPlot. Signal history can also be used within the Analyser
This is useful as it can give you a quick overview into single frequency use, signal strengths, fading and such like. Definitely something I need to spend more time on.
It’s been a long time coming, but Version 3 of SDR Console has been well worth the wait.
Roland Proesch has announced that his latest books on Radio monitoring are now available at his website
Whilst Signal Analysis for Radio Monitoring remains a 2015 edition, the other three – Technical Handbook for Radio Monitoring HF, Technical Handbook for Radio Monitoring VHF/UHF and Frequency Handbook for Radio Monitoring HF – have all been updated to 2017.
There is also a new title – Technical Handbook for Satellite Monitoring – which is over 400 pages long and is aimed at those that are interested in satellite communication. The book is the usual high standard with figures and tables on satellite systems and the waveforms they use.
Because of the new title, all satellite information (nearly 100 pages) has been removed from the VHF/UHF book, but these have been replaced by new modes such as Radar, C4FM, DVB-T etc.
At the moment, there are no PDF examples available, but going to my previous blog at the last release can provide that information for now. I’ll update when they do become available.
I highly recommend these books and they are very well priced at 49Euros each plus postage. There’s also the usual bundle price discount if you want more than one – further information on the website.
But, if you don’t want to pay the postage and are heading to the HAM RADIO 2017 exhibition in Friedrichshafen, Germany on the 14 – 16th July, then Roland will have a stand there (A1-213). I’m sure he’ll be pleased to see you there – I wish I could attend, but I’ll probably have to wait the 5 years or so until I move to Bavaria myself.
The Russian Navy has started to get active again after the usual period of rest over the winter months. The main reason for this is because most of the areas the Navy operate from in the North are frozen over, and are only just now starting to thaw out. There are three busy areas that produce the most traffic in the summer, but one of those practically disappears over the winter; and that is the area that falls under the command of the Northern Fleet, and in particular the White Sea. I intend to cover the Northern Fleet in much greater soon.
One thing that is noticeable is that the fleets seem to have moved to a more regional network of frequencies. They used them anyway before, but in general they tended to stick to 8345 kHz at night and 12464 kHz during the day as the main ship frequencies. I suspect that with the large increase of ships becoming active these frequencies were getting saturated with calls – something that was becoming noticeable as ships were “stepping” on each other. I mentioned last time that these main frequencies were quiet, and it now looks like this it was the reason.
As I say, I’ll go into regional stuff through the rest of the year so I’ll concentrate on a couple of interesting things that have happened over the last few months.
One of my favourite ships is Admiral Vladimirskiy, a Akademik Krylov Class Survey/Research Ship that uses the CW callsign RHO62. From late August 2014 this ship carried out a round the world trip, starting from the Baltic Sea headquarters at Kronshtadt, routing around the north coast of Russia through the Barents Sea, Kara Sea, Laptev Sea, East Siberian Sea and through the Bering Straits. From there it head south down to Taiwan and then across the Pacific to Corinto in Nicaragua, down through the Panama Canal, across the Atlantic to Brest, through the English Channel and home to Kronshtadt. It returned home on the 18th of January 2015 – a huge trip and one that our small group of monitors was able to track the whole way round, probably getting around 95% of all weather/TESAC reports that it sent. After that, it needed a good rest, and that it had until November last year when it set sail for the Antarctic.
Again, we have been able to follow its travels all the way down to the Northern edge of the Antarctic Ice belt, where it operated for some time near Davis Station, part of the Australian Antarctic program. They have a great website which provides various webcams, but unfortunately Vlad didn’t get within their sights. It’s worth checking out their website, just so that you can watch the fascinating time-lapse videos that are produced from the webcams. Vlads route took it this time through the Med, through the Suez Canal, the Gulf of Aden, along the East coast of Africa, stopping off at Madagascar for Christmas. Then it was down to Port Elizabeth in South Africa, before its final push to the Antarctic, getting there mid-January. For its time down to around Madagascar it stuck to 8345 or 12464 for its reports, but later on it transferred to 8460 kHz where it then spent most of its time. It would try the other frequencies should it not get through of course, there’s a huge selection that it could choose from.
8460 kHz is noted as being used by RMP (Baltic Fleet HQ at Kaliningrad) but in fact Vlad was calling RJH25 to pass on its messages. RJH25 is a RX/TX site in Kyrgyzstan and in this case is used in simplex instead of the normal duplex. This was good because it meant we were able to get both sides of the conversation easier than having to monitor lots of frequencies in duplex mode. A link to Google maps is in my callsign list which shows the RJH25 antenna site.
Here is one of my receptions of a FM-13 weather report from the 15th February on 8345 kHz:
0010z RHO62 586 20 15 0301 586 = SML FOR RJH45 RJH48 RJH74 RJD38 =
15001 99655 30900 22233
Distance from RHO62 to my Wellbrook Loop antenna using Google Earth
I’ve missed out most of the weather information to show the relevant data for positioning. The data equates to RHO62 being at 65.5S 90.0E heading SE @ 11-15kts. This is approximately 9670 miles from ship to my Wellbrook Loop antenna!! I must say, I am very pleased with that achievement.
So, what are the Hydrographic ships of the Russian Navy doing? Their main task is to carry out data acquisition of the waters that the Russian navy operate in, which is why the TESAC is very important to them. The checking of sea temperatures against salinity levels helps them in various ways, but there are two particular reasons for this data. One, is that temperature and salinity actually affect how torpedoes and missiles from underwater launches travel through the water – the higher the salinity and colder the sea water is, the more it can cause drag. The second is for much the same reason, but in this case it is for Submarines. Not so important for the Nuclear powered ones, but a little more so for the SSK’s as this can affect the time they can stay underwater before requiring to surface to “snort” and power up their batteries.
The TESAC data also provides the depth of the sea though most of the Hydrographic ships will have equipment that fully maps the sea beds. Again, depths are important, especially for the Submarine fleets, and I suspect they use these ships to map potential routes to strike areas for the SSBN’s. You see a good amount of Hydrographic ship activity in the Northern waters of the Arctic for instance, as with the higher sea temperatures, and the receding Ice cap, more routes are becoming available there – and this is useful for the ships too.
And finally, of course, the Hydrographic ships will be providing information to the Russian Government, not only on things like climate change but also in the search for oil and minerals. The Russians have a civilian Hydrographic fleet for this, but it is not large and so they will use data acquired from the navy too.
The navy fleet consists of around 80 ships that are potentially capable of providing Hydrographic readings, though it is hard to find out exactly whether each one can or cannot. There’s certainly quite a few in the Baltic, where they test the SSK’s and torpedoes. And there’s also plenty in the Northern fleet which has a huge areas in the Barents Sea and White Sea for the testing of missiles launched from SSBN’s. They will use the Hydrographic ships to analyse the water before and after any trials of the submarines or weapons.
Monitoring 8460 Khz for RHO62 also brought us some luck with another callsign, RMGZ, a Prut Class Submarine Rescue Ship named Epron. This had in late summer 2015 travelled east from its home at Sevastopol in the Black Sea, again via the Med and Suez Canal where it was eventually lost from our radios off the east coast of Sri Lanka. It had been erratic on 8345 up until then anyway, and this was probably because it looks like it was using 8460 as its primary frequency. Of course, we didn’t know this as we weren’t monitoring it. Epron was heading towards Visakhapatnam in India to take part in exercises and later on in a Navy exhibition. My furthest east report from it was at 16.3N 82.5E, about 50km SW of Visakhapatnam. Epron is now at home in Sevastopol after its long journey.
Prut-class Submarine Rescue ship “Epron” transits the Bosporus on its journey home to the Black Sea – Photo by Yörük Işik
I mentioned last time Project 550 Large Dry Cargo and Passenger ship Yauza which uses the callsign RHM80. Yauza has been a very busy ship over the last few months as part of the Russian ferrying of equipment and troops to Syria – named by many as the “Syrian Express”.
In all, our tracking of RHM80 shows it made five trips to Tartus from either Sevastopol or Novorossiysk , both being Russian Navy bases in the Black Sea. The last trip to Tartus has ended, and instead of heading round towards the Bosporus, it headed towards Malta, arriving there on the 4th of April; it will probably travel onwards to its Northern Fleet base of Murmansk after picking up some supplies for the journey from Valletta. The Russian navy quite often uses Valletta as a stop off point and with plenty of ship photographers there, it is a useful port for tying up callsigns to ships.
Of course we will be tracking it all the way home on 8345 and 12464 as it is very good at sending FM-13’s every six hours as required. It also sends lots of “11111” messages – so called because of the first five figure group in messages to Moscow (RIW), Sevastopol (RCV) and Severomorsk (RIT). These are status messages I believe and of low priority, and are very common. But, you don’t need to be listening out on the Russian frequencies to track Yauza, you can just use MarineTraffic to track it. Just enter its name into the search area.
Yauza wasn’t the only ship involved in the “Syrian Express” so there was plenty of traffic from other ships. Some of the callsigns we know and some of them we don’t. There’s still a couple of Large Landing Ships that are avoiding us, but it looks like I have been able to tie-up at least one ship that is currently involved in Syria – and this is RKA80. This I believe is Slava Class Missile Cruiser Varyag, and it’s given itself away by sending messages via RCV for RJS, the callsign for Pacific Fleet HQ, Vladivostok. The messages started around the time that Varyag arrived in the Mediterranean Sea so time will tell if it disappears from the frequencies once it departs the operational area. It has recently stopped sending messages with the extra section for RJS so I wonder if it’s realised it was giving itself away? An example of their messages is here:
I removed most of the message for ease as this one was 106 groups long, but this was part of what looks like a standard schedule of three priority messages, each well into the hundreds of groups (normally around the 150 mark)
Well, I hope I haven’t gone on too much. Not much frequency information for you this time but I that I plan to change when I start with the Fleet information articles in the future. 8460 kHz monitoring has also bought us some other interesting things which wasn’t known before – but that would fill one article on its own.
As I say, keep an ear out on 8345 Khz and 12464 kHz. And if you’re on the West Coast of North America then try 8348 kHz which seems to be the Pacific Fleet primary CW frequency. If you do decide to give it a try then if you do manage to get anything, in particular from North America, then please do contact me either using my contact info in my blog, or via the TSM editor. I’m very keen to see what coverage there is elsewhere in the world.
Since the time that I wrote the article I have confirmed that RKA80 is Varyag
Project 21631 Buyan-M class Patrol ship Zelenyy Dol transits the Bosporus, heading for its first ever patrol. It was heading for the port of Tartus as part of the Russian Syrian crisis fleet. Since this image was taken, sister ship Sepukov also deployed to the Med, and after further deployments both have transferred to the Baltic. Both of these ships will be two of the unknown callsigns we’ve picked up recently – photo by Yörük Işik
After a couple of days of teasing us with the standard “W” markers in CW, on the 17th February the Russian Air Force (Военно-воздушные cилы России [BBC России]) carried out a Long Range Aviation mission using two Tu-160 Blackjacks.
I was able to monitor nearly the whole mission on HF (both in CW and Voice USB), with a small amount on UHF (though no Russian Air to Air voice comms were received on VHF/UHF) and following some investigation into my data along with other logs and reports from the internet and friends, I can now compile a rough idea of the routing they took on their journey to the English Channel and back again.
The first reception I had that showed a mission was taking place was at around 0830z when a standard 3 figure group message was sent by IWV4 but unfortunately I was just setting up my gear and so missed it to write down. Further “W” markers took place at the usual every 20 minute schedule of 0840z and 0900z, with IWV4 sending another message at 0903z to the aircraft. This call gave us the CW callsign for the aircraft, probably the IL-78 Midas – 4YMA
As is standard, the early part of the mission was relatively quiet on CW with markers only, though there was one unusual thing that took place around 0920z. Firstly there was no 0920z “W” (this only happened one other time for the whole day at 1600z – the 20 mins schedule was kept going solidly otherwise) and secondly, at 0922z, there was a sending of data on the frequency. The first eight minutes was a carrier tone centred exactly on 8112; with the full data commencing at 0930z continuing until 0943z. Unfortunately, the CW recording I had for the day got corrupted so I wasn’t able to analyse the signal to at least try and determine what type it may have been. Of course, it could have been coincidence as we all know that many of the frequencies used by the Russians are shared, but this does seem almost too good a coincidence. One thing is noteworthy in recent missions, and that is the big reduction in CW messages over the large increase of voice messages – are the Russians trying out a new data messaging system for their Long Range Aviation fleet?
8112 continued in the usual manner for most of the morning, with the occasional message or “radio check” [QSA] but there wasn’t much else. The Winter CW frequency for the aircraft side of the “Bear Net” had always alluded us and was in fact the only missing frequency we had for the whole net, so it was just the ground side of the duplex network that I was receiving. I had 8990 down as a back-up frequency for their voice comms and I was monitoring this frequency on my Icom IC-R8500 in USB mode, with all the remaining Winter frequencies on the Titan SDR Pro. I was also using the Titan to monitor most of the Oceanic frequencies in case they were coming this way, something useful to do as this can sometimes give away the rough position of the Russians. Because of this set-up I had the SDR monitoring the Oceanic frequencies in the 8MHz range. The bandwidth I’d allocated also incorporated 8990 and it was during a QSA check at 1205z from IWV4 on 8112 that I noticed a faint trace of CW on the frequency! I quickly changed the mode on the Icom to CW and caught the end – “QSA3” – nothing else followed, but it looked like I had found the Winter CW airborne frequency for the “Bear Net”. But, I had to be sure.
Up until now there had been zero voice comms on 8131, the primary Winter voice frequency, but not too long after the 1205z QSA check on CW the first call came with 44732 calling KATOLIK followed by a call to BALANS after not much luck with KATOLIK. There was one more call after this on 8112 before this frequency went to markers only, but there was a reply on 8990 confirming that this was the Winter CW frequency for the aircraft. The complete 8112/8990 transcript can be found in PDF format in my full CW log
Going from various reports, the Northern QRA had not launched so this led me to believe that the Russian aircraft were not coming in the direction of the UK, but when I noticed on my SBS that the Tanker was travelling north from Brize Norton, then I wondered if they were. The only comms I had was from the Tanker with Swanwick Mil so I presume (and with no logs showing anything from Lossiemouth) that a long range track of the Blackjacks was taking place.
Certainly, on Oceanic warnings were being passed about the “unknown” traffic heading south and it’s from this information that I’ve been able to roughly guess their initial routing, down through the Shetland Island and Faeroe Island gap to near ERAKA, before tracking south along the 10W line – like I say, a rough guess, but going on previous routes this won’t be far out. They probably got to around the NIBOG area before tracking SW to go around Ireland, before heading in again towards Lands End and the English Channel.
Voice comms on HF with BALANS was pretty continuous by this stage, with three potential callsigns heard. Two would have been the Blackjacks, 44731 and 44732, with a third more than likely the support IL-78 Midas tanker that remained clear up to the north and so was much weaker with me – I think it was 60991 but was too weak to tell, with only the readback from BALANS copied.
At about 1505z it was reported that two Typhoons from Coningsby that had launched about an hour before, and had been holding in ARA10W, had joined up with the “unknowns” and these were identified as Tu-160 Blackjacks. The comms were again picked up by Kyle, and the Typhoons gave full details including the tailcodes, with the lead aircraft being RF-94101, the second RF-94104. The Russians name their Tu-160’s and these are given “Paval Taran” and “Alexander Golovanov” respectively.
By coincidence, at 1510z, 44732 calls BALANS with a message starting 502. I always suspect that they send messages out when they’re intercepted and I expect this was one of those messages. It could well have been that they were entering the Channel though, it’s hard to tell, but certainly for the whole time they were in that area, the messages sent began with 502. Around 1600z the French QRA also joined up and from images produced by the MOD, these were shown to be a single Rafale and a single Mirage 2000C – callsigns noted on Fighter Control as MASTIFF01 and MARAUD03.
From there the Blackjacks turned around and I expect pretty much followed the same route back. I could certainly tell that they were near to me later on, they were ridiculously loud on HF.
Below then is a copy of my voice logs, along with the recordings I made. A good test of my recently installed Wellbrook Loop that I’d finally been able to put up on the mast just the week before, after having it for nearly three months! Scottish weather!!
NOTE – These recordings are copyrighted to me. It has been noted that other recordings have ended up on YouTube, uploaded by a third party. Should this happen with my recordings, further action will be taken
1216z 44732 calls KATOLIK
1217z 44732 calls KATOLIK [KATOLIK very faint]
1218z 44732 calls KATOLIK, BALANS replies
1220z BALANS passes message 130 525
1222z BALANS calls 44731 numerous times
– Note, contains all of the above
One final thing to note – on exactly the same day in 2015 (day of the year, not actual date, so the third Wednesday in February) the Russians carried out almost the same flight, going down the West coast of Ireland. Further information on that mission, including HF recordings, can be found in Bear Hunting – part two
Bet you a few quid they’ll be back same day next year 😉
Roland Proesch has recently updated his books on Radio monitoring.
Published in the last month or so, the four books are great additions to your bookshelves and priced at 49Euros each plus postage. He does do bundle offers if you’re thinking of buying more than one of the titles.
The titles are:
Technical Handbook for Radio Monitoring HF
Technical Handbook for Radio Monitoring VHF/UHF
Signal Analysis for Radio Monitoring
Frequency Handbook for Radio Monitoring HF
I reviewed the 2013 edition of Radio Monitoring HF in March 2014.
For more information on prices and examples from the books head over to Roland’s website
I will hopefully be reviewing three other radio monitoring books by three different authors in the next month:
Professioneller Kurzwellenfunk by Nils Schiffhauer
Spezial-Frequenzliste 2015/16 by Michael Marten
International Call Sign Handbook by Larry Van Horn
Well it appears I may have been wrong about the previous mission in January by the Russian Bears and their routing down the English Channel – though there is still no hard evidence this did happen. But, for now then I will accept that it did unless proven otherwise.
On February the 18th the Russians carried out another flight down the west coast of Ireland, outside any sovereign airspace and this time causing less disruption than in January. That isn’t to say there wasn’t some traffic information given by Shanwick and Shannon about unknown traffic.
Kyle, aged 15, a member of a closed forum I’m in, was able to pick up some good comms from the Typhoons, including confirmation of the tail numbers of the two Bears:
Lead aircraft = RF-94130 (24 Red)
Second aircraft = RF-94116 (28 [Red])
Personally I didn’t get much but what I do have is available here:
NOTE – These recordings are copyrighted to me. It has been noticed that other recordings have ended up on YouTube, uploaded by a third party. Should this happen with my recordings, further action will be taken
It is known that the Bears flew approximately 10 to 15 miles off the coast of Ireland and this does tie in quite nicely with that. However, this doesn’t run with other messages received unfortunately. But, I’ll keep plugging away any further messages to see if there is a crack for some of them.
On to the second update.
I must have put my Excalibur on to record when I got back from work on the 19th but then forgot about it. Whilst deleting the backlog of recordings I noticed there was one I hadn’t listened to and quickly discovered I’d captured some further messages on this day too. Here’s the recording, with a transcription below (thanks to Ron for checking (and correcting) my Russian translation):
After this weeks flight of two Tu-95MSM “Bears” off the South West coast of the UK, I thought it would be a good time to release the article I produced for The Spectrum Monitor in October 2014. The article covers not only information on the Tu-95 and Tu-160 “Blackjack” but also on how to monitor these flights. There’s also some additional information that I’ve discovered I’d left out of the article plus some recordings from this weeks mission.
With regards to the flight this week, it certainly caused quite a stir, making it onto the major national news channels. There was lots of speculation that they flew all the way along the English Channel causing lots of disruption to Civil flights into and out of the UK; also lots of rubbish spoken about what ATC can and can’t see. Though I can’t comment much, I will say I don’t believe the Bears flew all the way along the channel, instead I think they went no further than to the SW of the UK. From the playbacks I’ve seen on FR24, it looks like most of the disruption was caused by the tanking of the Typhoons by the A.330 – this area has been available for tanking for many years.
To answer the question about whether the aircraft can be seen on radar because they are not using transponders – well yes of course they can. It’s just there’s no associated height information, (which isn’t always there even if aircraft do use transponders)and of course it makes it harder to track. But, there are primary radar returns that’s for sure. Where I think people are getting confused is when the Bears are flying north/south across the Atlantic tracks in Shanwick’s airspace. Here they can not be seen as they are outside the range of radar, but by this time they would have been met up by Typhoons which gives all the relevant information about height etc over the radio . I hope this clears that up.
Anyway, on to the article
When I say Bear hunting, I’m not referring to tracking furry creatures around the countryside using sophisticated radio devices as aides, finally getting into the position for a kill or photograph. No, I’m referring to the monitoring of the Russian Air Force Strategic Bomber networks on HF.
Although in general the monitoring is referred to as “Bear hunting” and the frequencies monitored are in the widely used term, “Bear Net”, this is an incorrect name as it is not always Tupolev Tu-95 “Bears” that we are hearing.
The Russian Strategic Air Force is officially known as the Long-range Aviation Command and is made up of two heavy bomber divisions. The aircraft types used are Tupolev Tu-95MS “Bear H” and Tupolev Tu-160 “Blackjack” along with the non-Nuclear bomber, Tupolev Tu-22M3 “Backfire C” which is split into four divisions. As well as the bombers themselves, there’s also other types of aircraft used to help support the missions; these being Ilyushin IL-78M “Midas” air to air refuelling tankers, and Beriev A-50 or A-50U “Mainstay” AWACS – these types being based on Ilyushin IL-76 transport airframes.
It is also presumed that other types are used in the missions, such as Ilyushin IL-76VKP and Ilyushin Il-86VKP “Maxdome” Command Posts (much like the role carried out by E-4Bs National Airborne Operations Centre aircraft used by the USAF) and even Ilyushin IL-38 “May” maritime patrol aircraft used by the Russian Navy (the USN P-3 equivalent). In general though, these types aren’t heard by those that monitor the frequencies regularly, especially the IL-76VKPs and IL-86VKPs as their statuses are not widely known, and their believed running costs make them almost too expensive to fly. The Russian Navy participation in exercises must take place, much like the combined exercises that the US Forces carry out – bombing missions/exercises supported by USN E-6Bs for instance.
There are other variants of the “Bears”, these being Tu-142MK’s and Tu-142MR’s (“Bear F/Bear J” respectively) but these are operated by the Russian Navy with Bear F’s used for Anti-Submarine Warfare, equipped with different radar fits and weapons systems designed specifically for Sub hunting; whilst Bear J’s are VLF communication airframes much like USN E-6B’s. There’s every possibility these do take part in some of the exercises we hear.
Getting back to the Air Force Bombers themselves, as previously mentioned above, there are two Strategic Divisions. These are the 6950th Guards Air Base at Engels Air Force base in the Saratov Oblast region of Russia; and the 6952nd Air Base at Ukrainka in the Amurskaya Oblast region. If you have Google Earth I’ve uploaded a kmz file showing their locations.
The bases are then divided into Regiments with the Engels base containing the 121st Guards regiment flying Tu-160s and the 184th regiment flying Tu-95MS’s. Ukrainka is made up of the 79th and 182nd regiments, both flying the Tu-95MS. Because of START, the numbers of each type flying are known, with 55 Tu-95MS’s and 11 Tu-160’s available to the Russian Air Force, but again, the full status of each airframe is somewhat hazy, even in the modern world of information technology available on the internet – there’s certainly many more photos of these types available to view online than there ever was available before the invention of the internet. The split of numbers between each regiment is again unknown, but Satellite images show up to 18 Tu-95’s at Ukrainka on the bombers apron.
Engels is almost certainly supported by IL-78 tankers either based at Engels itself, or from the Ryazan Air Force base which has the 203rd regiment based there. Ryazan is also a training and maintenance facility for the bombers. Ukrainka possibly has its own regiment of IL-78’s, but details on these are unknown at this time, it could even be another deployment of Ryazan tankers.
The Tu-95MS’s have a crew of seven, and can carry up to 16 Air Launched Cruise Missiles (ALCM), both Nuclear and conventional. Crew members comprise of:
Two pilots, radio operator, nav/defensive operator, flight engineer, bomber/nav and rear tail gunner. There’s also a spare seat for observers. The aircraft operate between 25,000ft and 38,000ft and can fly at speeds of 500kts (Mach 0.83) at the lower level. Unrefuelled they have a range of 3,455 miles, increasing to 4,480 miles with one refuel. They have however carried out multiple refuels extending this range even further. The most unique feature of the aircraft has to be the four Samara Kuznetsov NK-12MP turboprops each with eight-blade contra-rotating propellers – they make a very distinct sound
The aircraft themselves are split into three variants:
Tu-95MS-H6 and Tu-95MS-H16, referring to the number of cruise missiles the aircraft can carry. The main six missiles are on a rotary launcher inside the aircraft, with the H16 types having the ability to hold a further 10 missiles on pylons on the wings. For START purposes though, the H16’s are to be converted down to H6 standard only, if they haven’t been so already. The third variant is the Tu-95MSM which is an upgraded version designed to carry new type of ALCM.
The number of each variant is, as usual as its Russia, not fully known, but it is presumed most, if not all, are now of the Tu-95MSM designation, probably going from the H16 variant to this directly instead of downgrading to the H6 and then up again. The Tu-95MSM can be distinguished by the fact it is carrying eight of a new type of ALCM on pylons under the wings as these missiles are too long to fit in the internal weapons bay. Of course, they still have the option of using the internal rotary launcher and older ALCM’s if required.
The Tu-160’s have a crew of four comprising of two pilots, and one bomber/nav and a comms/nav operator. They have variable geometry wings that can be manually swept back as speed increases, the maximum speed being Mach 2.05 at 40,000ft. They normally cruise at about Mach 0.9 or 518kts at high altitude but they are fully capable of flying low level down to 250ft. The Tu-160 carries its weapons in two separate internal weapons bays, each with six missiles on rotary launchers
Weapons wise, both aircraft types are primarily intended to carry ALCM’s. A recently new ALCM has been designated the Kh-101/Kh-102, the latter having a nuclear warhead. The Kh-101 has a 400kg HE warhead designed to penetrate hardened shelters and has a range of around 5,000km at a speed of about 700kmh. They are reported to be accurate to 12 – 20m from this range. It is believed that an upgrade to the Tu-160s started in 2006 gave them the ability to use Kh-101/Kh-102’s.
By far the greatest number of ALCMs available for both aircraft types are Kh-55/Kh-555 (NATO AS-15 “Kent”). There are a few sub types available but for simplicity, the Kh-55 (AS-15A and B) types have nuclear warheads, whilst the Kh-555 (AS-15C) is a conventional weapon with a 410kg HE warhead. Ranges vary from 2,000km to 3,500km. There are over 700 Kh-55 ALCM’s still in existence according to reports. The long term plan was reportedly to be 500 nuclear armed ALCM’s in the inventory made up from both Kh-55 “Kent B” and Kh-102 types.
Monitoring the “Bears”
In all references to “Bears” it could actually mean either the Tu-95s or Tu-160s but it’s just easier to generalise the term to save space. More often than not they are Tu-95s though as there’s a greater number of these aircraft in the fleet.
The Bear networks use both CW and USB for communication; CW is Duplex with ground stations on one frequency and the aircraft on another; whilst in USB mode the networks are simplex. The frequencies are contained in the table provided, but as you’ll see there’s still one missing; in fact it was only recently that I discovered the summer air frequency used – until this time it was not known by the many that monitor the Bears (well no-one else had published it anyway). No doubt there are more frequencies used as, as you can see, there are secondary ground frequencies in other seasons.
The Russian Military in general use a seasonal system for selecting their frequencies and for the Bear net these haven’t changed over the last few years.
Spring 1/3 – 5/5
8029 kHz Primary
Navy Bear Net
Summer 6/5 – 31/8
8895 kHz Primary
8909 kHz Primary
Navy Bear Net
Autumn 1/9 – 31/10
8162 kHz Primary
8033 kHz Primary
Navy Bear Net
Winter 1/11 – 28/2
8112 kHz Primary
8131 kHz Primary
Navy Bear Net
I also have VHF/UHF Air to Air frequencies that the Bears have used in the past that I forgot to put in the article:
As well as HF, they also use VHF/UHF for normal transmissions to ATC, Air to Air etc. These HF networks are solely for communicating with presumably HQ Moscow and other strategic agencies, their homebase for instance. It’s even possibly transmissions to radar sites or an equivalent to the Mainsail or “Skymaster” calls made by USAF bombers.
Usually the first sign that the Bears are up is the activation of Marker Beacons on the CW networks. Every 20 minutes, lasting for two minutes, a single letter will be repeated by CW. It is always on the H+00, H+20 and H+40 and normally hand sent. The marker most commonly heard is “W” and this is almost certainly Moscow and the Strategic (or Long-Range Aviation) headquarters. Another is “G” which is believed to be Ukrainka. Engels probably has a marker but it is unknown, but various other markers noted include “Q”, “R” and “Z”.
The Naval Bears also use a Marker system, with Moscow using “C” and Arkhangelsk/Severomorsk using “S” , but it’s just as possible they also use the very same network here. Without visual identification of the aircraft you just don’t know who you’re listening too, but more on that later.
The purpose of the markers is so that the aircrew can check their radio equipment, and also confirm they are able to receive the appropriate unit they need to communicate with. If there are two markers on the go at the same time, as recently with both G and W, the one that isn’t Moscow seems to start about a minute earlier so that there’s a slight overlap. On USB there are no markers. I always wonder which is the primary method of communication here, as CW from the ground certainly has a better range, well for me anyway. Moscow “W” is normally very loud, though as usual propagation plays its part sometimes.
The Bears normally start the communications with Moscow, and I would say it’s likely to be an airborne or status message. But there is no way of telling as the messages are coded. Be it using CW or USB the aircraft always send messages containing groups of three numbers. Ordinarily there doesn’t appear to be a pattern to the numbers as such but they obviously have a meaning, examples of CW messages are:
These messages are from an excursion to the edge of UK airspace on the 19th August this year. Interestingly, I also picked them up on the 20th August 2013, also the third Tuesday of August – coincidence? To breakdown the message above, KFE4 is the ground station, KL3U is the Bear flight. There’s a possibility that the ground station callsign “travels” along with the flight, with a different ground station taking over the callsign to give complete radio coverage. This is just another theory though.
Now we all have our own ideas about the numbers and to be honest I just don’t know the true answer as to what they could possibly mean. I would expect them to be position or progress reports, status reports even. Interestingly, in this mission there were multiple messages starting with 728 or 871, and every time a message began with these numbers the second number group matched:
You may also notice that comparing the message examples, the third group is the same with regards to the first group; 728 is 046, 871 is 990. This repeats throughout the messages of this mission.
To confuse things slightly though, there is a third first group involved with KL3U, this is 558:
1301z KFE4 DE KL3U QTC = 558 130 422 295 396 246
558 messages never matched any of the second group numbers to 728 and 871, and the third group is never the same.
The messages starting 558 are more in line with the other missions I’ve logged which look totally random. There also messages that are short from an aircraft which are then an hour later at the beginning of a longer message from the ground station, such as these sent in March this year:
1612z P9DL = 710 282 073 633
1728z TRL5 = 710 282 073 633 276 040 795 197 136 802 777 539 643 709
It wasn’t until writing this article that I noticed there’s actually a forth first group in the recent mission, 732, which matches the same format as 558. So, as you can see, there’s random and there’s fixed message types. I do enjoy trying to crack these codes, something I managed to achieve in January when I analysed messages from IL-76 transporters ferrying equipment to Syria as part of the Chemical weapons removal. This can be read in my blog from that time.
Part of me thinks that each first group is a separate aircraft within the formation but there are a couple of things that cancel that theory out. Firstly, this pattern doesn’t follow in previous missions and secondly, the keying was almost certainly done by the same person due to the “fingerprint” of the CW. However, as with most formation flights of any Air Force, it could well be that only one aircraft is sending messages for all aircraft in the formation, the lead aircraft for example. The Russian Navy does this when there is a group of ships travelling together, with quite often one ship sending messages for all. It is generally believed that the air callsigns are individual aircraft as there have definitely been other missions were more than one callsign has been in contact with the ground – but were these in fact other airborne assets and not the bomber flight?
The aircraft callsigns seem to be tactical and change every time whilst the ground callsigns appear to be fixed with the same ones being used each season, examples being:
TRL5 – spring
TV6P, IZ2J and KFE4 – summer
4ASU, QZ6Y and PUO7 – autumn
IWV4 – winter
It is always a better monitoring experience if you can pick up both CW Air and Ground so that you can get both sides of the “conversation”, but this isn’t always the case, with just the ground audible. The transmitters on the aircraft are not big, and they are not powerful so it is hard to pick them up. Of course, if they happen to head over towards the UK then they do get very clear indeed, as happened recently when at least two Bears flew close to the Shetland Islands off the NE coast of Scotland.
Hearing both sides of the R/T isn’t a problem on USB as it’s a simplex network, but range of aircraft from the reception point and propagation will of course play a part in this. Your knowledge of the Russian language though is going to be main hindrance in any monitoring. Usually the ground station is very much stronger, much like the CW network.
Russian is hard enough as it is, but when you’re listening in on HF to something where the crew themselves have to wear headsets with additional noise defence fitted to the earpieces, you can just imagine what it sounds like. To put it another way, you can normally tell you are listening to a Tu-95 and not a Tu-160 because you can actually hear the turbine engines in the background! And the crew are normally shouting down the mic. To add to the difficulty of working out the messages there’s the way the numbers are said. Some say them in singles – Dva Vosem Dva (282); but then other crew members will say them as long numbers, two hundred and eighty two for example which in Russian is “dvesti vosem’desyat dva”. Luckily, you’ll normally get a second chance at the numbers as the ground controllers will read them back, often in both methods as described. I know numbers in Russian, and I really struggle, especially in the non-singular method. A recording is normally necessary to get it right – if possible.
As I’ve already stated, the message formats are the same, three figure groups. But there is a difference in callsigns. For starters the aircraft use a different call to the CW one, comprising of five numbers, 50271 for example. These numbers are logged differently by some people, 50-271 for the previous example. This is because of the way the callsigns are sent: “Fifty, two hundred and seventy one”. But I think this is wrong, and there’s possible photographic evidence that points towards the numbers being a five figure group. There’s a link to the photo evidence at the end of this report.
The ground stations also have voice callsigns as opposed to the four digit call in CW. In a way this is understandable as some of the callsigns are long and would be hard to do quickly in CW. Again though, the ground callsigns are fixed and never change, they’re not even seasonally split as far we can tell. Callsigns heard include:
ADRIS – new callsign for the recent flight
SHPORA – believed to be Rostov-na-Donu though not proven
The location of the other callsigns is unknown, but BALANS and NABOR are called the most and it seems likely one of them is Moscow or Long Range HQ.
Now here’s the strange thing. The actual message format is the same as I’ve already said, and yet when CW and USB have been sent at the same time, no doubt from the same aircraft formation, the actual message is different. As an example here’s two messages sent at exactly the same time, 0212z on the 20th August 2013:
CW: TV6P = 161 179 985 027 614 591 089 C = (this is a read back from the ground station TV6P)
USB: 30977 calls Medyanka – 527 268 987 627 805 893 206 591 093
Except for the penultimate group (591), no other number is the same, but there are similarities. At the end of the day though, these messages are being sent by Strategic Nuclear bombers, they are probably exactly what would be sent should the unthinkable happen and the aircraft are dispatched for real. The messages are not supposed to be decoded, and if I was able to I’d be a very rich man thanks to NATO. Liken them to the equally unbreakable EAM messages sent by the HF-GCS network if you like.
Of note in USB mode is that there are a lot of relay messages from one aircraft to another, something that I haven’t found in CW mode. This is probably down to CW having a better chance of getting through noise and propagation than voice transmissions. Sometimes, though, CW messages are sent blind.
More often than not the aircraft actually head east these days, especially those from Ukrainka. In the Cold War this wasn’t the case and the Bears made regular trips to Europe skirting around the northern parts, not entering any sovereign airspace, and even heading into the North Atlantic region. If they did this, it would cause all sorts of trouble as they don’t declare themselves to Shanwick Oceanic and normally just cut south across all the Oceanic tracks. The only method of knowing where they are here is via long range radar (which as you can imagine aren’t pointing out over the Atlantic as there’s not much threat to the UK from that direction) or via an “escort” of RAF fighter aircraft. These flights to the Atlantic are increasing again, sometimes going as far south as Portugal and beyond.
Most nations have a QRA (Quick Reaction/Alert) capability and in Northern Europe they used to get launched regularly but this died down when the Soviet Union fell. Russia had a lack of funds for a very long time and its military fell by the wayside; until Putin’s recent reprisal of it all. In the last few years, Bear missions have increased from practically none a year to two a month, especially recently. Sometimes it’s two a week to Europe or Pacific regions, or maybe one to Europe and one to the Pacific at the same time. Either way, they are getting more and more frequent again.
QRA aircraft will launch from the various countries along the route and intercept the Bears in “free” airspace, take some pictures, note down the aircraft identities (reporting this back directly to the Air Defence Controllers), wave and generally ensure the aircraft do not enter sovereign airspace. If the Bears continue skirting the edges of various other countries, then the current escorting QRA will hand over to the next country along the way. It takes a lot of resources to carry out the QRA task, with fighter crews being on immediate standby at their bases, 24/7, along with at least one air-refuelling tanker required to sustain the flights here in the UK. Should it be a long task, another flight of fighters will get airborne to take over whilst the first pair get a refuel. There is no messing around here though, the fighters that go up to meet the Bears are fully armed and make sure the Russian crews are aware of this fact by showing them.
Obviously, the intercepts are also monitored here in the UK and Europe but I’m not at liberty to say frequencies used due to the very nature of the missions. One thing this monitoring does provide though is the identity of the Russian aircraft, because as I mentioned earlier, the intercept aircraft report back the type and tail numbers of the Bears.
Of note from a recent intercept by RAF fighters, at the time the lead Typhoon reported flying in formation with the lead Bear, a message was sent on CW. Was this a message being sent back home that they had met up with the UK Air Defence?
For those of you that like to follow any QRA action using ADSB data, you must realise that there is a flaw in doing this, especially when reporting live on Twitter.
Whilst occasionally the fighters can be tracked, normally it is the tanker that is providing ADSB data. Without going into any specific details here, the tanker could be anything from 30 to 100 nm away from the Bears!! So, posting continuous Tweets that “the Bears are here” is completely misleading and quite often leads to huge speculation and, to be honest, complete rubbish from media outlets that state “our airspace was entered by Russian Bombers” after reading these bulls**t Tweets. Think about what you are Tweeting and the consequences of your actions – most of the time you are complete wrong and you haven’t a clue where they are!
Finally, it is also worth noting that CW isn’t always received even though there’s plenty of traffic on USB. The markers will still be being sent every 20 minutes, but there’ll be no actual traffic. I’ve not known it to be the other way round with CW only and no USB.
Recordings from the flights on the 28th January 2015
NOTE – These recordings are copyrighted to me. It has been noticed that other recordings have ended up on YouTube, uploaded by a third party. Should this happen with my recordings, further action will be taken
8131kHz 1058z – Callsigns believed to be 72181 and 72182 calling BALANS, ADRIS, KATOLIK and GEOLOG. Aircraft types are still unknown at this time but possibly the IL-78 refuellers. They call each other and chat about not getting through to any station.
8131kHz 1130z – Callsign 72186 makes calls initially with no luck, then calls 72182 and asks them to try the ground stations, which they do, also with no joy
8131kHz 1224z – Callsign 72181 calls initially followed by 72182 calling 72181. After a brief conversation 72182 tries BALANS getting through (very faint on this recording).72181 then tries BALANS again and gets through with following coded message 949 867 069 473 250 197 518. BALANS doesn’t get the message and 72181 tries two more times but BALANS doesn’t get the message clearly. Note – to cut down the length of the recording the faint BALANS transmissions are cut out
The WordPress.com stats team created a 2014 annual report for my blog. It’s amazing just how many views I had, around 11,000 in total
Here's an excerpt:
The concert hall at the Sydney Opera House holds 2,700 people. This blog was viewed about 11,000 times in 2014. If it were a concert at Sydney Opera House, it would take about 4 sold-out performances for that many people to see it.