More Konteyner

March 19th 2020 produced an interesting news story from TASS regarding a new Konteyner 29B6 OTHR system that is to be deployed in the Kaliningrad Oblast.

The full story can be read here in Russian.

Now, I still have my doubts about it being deployed here, and my first impressions were that it was just propaganda, but it still needs analysing to see what it could produce.

The article, sourcing a “Military-industrial complex”, mentions that the system is to cover the whole of Europe, including Great Britain.

This is, in itself, interesting as most of Europe is actually already covered by the system at Kovylkino. The mention of Great Britain specifically also is interesting as another Konteyner OTHR to cover this country would really only give an extra few seconds of warning that anything was coming from this direction. Moreover, I suspect that the Kovylkino system does actually cover Great Britain anyway, especially with the pulse rates of the system that I’ve analysed myself.

Looking at the image below you can see that if a system was placed at the rough centre of the Oblast, then only France, Spain and Iceland – along with GB – would be the extra countries that would be covered. The east of France is already covered as it is.

Personally, I wonder if – whilst GB might get extra coverage – the true targeting of the system would be to the North.

The Russian military have long been saying that they want to cover the Barents Sea and up to the North Pole with an early warning radar – specifically Konteyner – so this could be it.

If we adjust the predicted coverage to the North in an image then you get the following.

So, depending on the azimuths of the arrays used, we can see that GB, Iceland, East Greenland, North Sea, Norwegian Sea, Barents Sea, Norway, Sweden, Finland, Svalbard archipelago and the Noveya Zemlya archipelago (Severny Island and Yuzhny Island) could be covered by a four array system.Norway and Sweden are already partially covered by Kovylkino.

To me, this is the more likely coverage that will be created SHOULD a Konteyner system be placed in the Kaliningrad Oblast. And it is a should!

The TASS article states that multiple sites are being considered. The system at a minimum requires two sites. And the Oblast is not very big.

In all reality, the city of Kaliningrad itself is just 30 km from the Polish border. It would not take very long for a strike from a foreign land based missile site to reach a Konteyner site in the centre of the Oblast. It is because of this fact that I have my doubts about one being sited here, but who knows?

But say they do choose the Oblast for system two, where’s the likely spot?

If anything is to go by, with their previous sites, near an airfield seems to be a good choice, be it one in service, or one that could be quickly reinstated.

There’s a number of abandoned sites, including:

• Chernyakhovsk at 54°36’7.12″N 21°47’29.07″E
• Nivenskoye at 54°33’48.13″N 20°36’13.02″E
• Marienkhof at 54°51’57.25″N 20°11’0.92″E

Chernyakhovsk has a large military presence – as does the whole of the Oblast to be honest! – and some work has been started at 54°39’1.12″N 21°48’24.77″E that I’ve been monitoring since mid 2019. Here there have been a number of small buildings about 3 metres wide since at least 2005 but I think these are something to do with oil or gas extraction – as is the new development. Moreover, the shape isn’t right for Konteyner as can be seen below.

Marienkhof (Dunayevka) is the location of a Voronezh-DM Early Warning radar that is situated to the SE of the old airfield. There is plenty of land around here for extra development. Moreover, out to the west coast is Yantarny which is home to the 841st Independent EW centre, and to the north is a SIGINT site at Pionersky that houses one of the new Sledopyt satellite signal interception systems amongst others.

Voronezh-DM Early Warning radar site near old Marienkhof airfield

Nivenskoye certainly has a lot of land available, but it is the nearest site to the Polish border and certainly not top of my list.

My favourite area would have to be near to Marienkhof due to the location of other Russian systems of this “type” – radio/radar/SIGINT based systems. The area is almost as far as you can get from any land based threats, though of course anything from the sea would not be that far.

I guess we’ll just have to wait and see what develops. One thing is for sure, the system stands out once you have an area of interest and this area is not that big to continually monitor.

For a while, sites like these in the Kaliningrad Oblast took my interest as they were developed a few years ago – this one situated at 54°28’10.14″N 21°39’4.07″E – as they looked liked potential radar or antenna sites. But it soon became obvious they were actually something to do with cattle farming

SDR Console V3 analyser

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.

A quick update & Roland Proesch Radio Monitoring books 2018

Firstly, a quick update on what’s been going on with me.

In the world of radios, ships, photos and Russians – not a lot!! No blog since September 2017 wasn’t what I had planned that’s for sure. Much of my writing time has gone to Jane’s, which has been great. This has meant I had to prioritise any free time available to them, having to put my blog on the back burner. Overall I’ve written or carried out analysis for around 10 Jane’s magazine articles since September 2017, as well as my continual fleet analysis on the Russian navy for Fighting Ships.

One of my articles from the November 2017 edition of Jane’s Intelligence Review

With regards to any radio monitoring, that also had to go on a back burner. When the shack was rebuilt as part of the house renovations I installed all the coaxial in temporary locations, drilled through the outer wall and coming into the shack through a large 50cm by 30cm hole in the interior plasterboard wall. This was in April 2015!! Hardly temporary!!

Due to the pretty crap weather we get here, and the fact that I needed at least 5 days of continuous good weather to be able to do all the connections outside, it has taken until the last week – 3 years later – to finally get the sunny days I needed at the same time as being off work.

Over the last year, the temporary connections had become worse and worse, with lots of noise causing interference. Nothing was earthed correctly either. Other factors such as the neighbours installing dreaded solar panels really screwed up everything, totally wiping out the main Russian navy day frequency they use for CW.

Not only that, with the hole in the interior wall being the size it is, it gets very cold in the room during the Winter – and the rest of the year for that matter – with a large draft blowing in most of the time.

Anyway, new outside connections are complete, in nice new waterproof boxes. Now the exterior part is done, I’m not weather dependant on the rest of it and hopefully I’ll be back up and running in the next month or so. I’ll do a full blog on the new setup once it’s complete.

Roland Proesch Radio Monitoring books 2018

For 2018, Roland Proesch has updated two of the five books he creates in his Technical handbook range.

The first is Signal Analysis for Radio Monitoring Edition 2018. This has nearly 60 new pages of information on how to analyse various waveforms, including a new section on Satellite signals – useful if you’ve already purchased his Technical handbook for satellite monitoring 2017. There’s also a section on describing how to analyse RADAR signals. Other things such as useful software tools and PC calibration is also included. Here’s a PDF of the contents with new information highlighted in yellow.

The other book is Frequency Handbook for Radio Monitoring Edition 2018. Whilst many people would say a book containing information on frequencies used by various utility stations, armed forces and other agencies is dated and old school, I tend to disagree. There is so much useless information out there online, I prefer using a book for looking things up that I may have found on the HF bands. Granted, a book does go out of date – normally as it’s being printed – but you can quite easily add your own entries in the right places if needed.

This update has several hundred changes of new, deleted and updated frequencies ranging from 0Hz to 30000kHz, and contains a section dedicated to ALE frequencies and idents.

Both books, along with the ones released last year in one of my previous blogs, are available from his website. As usual, he has his bundle offers which makes the books cheaper if you buy two or more at the same time.

I’ve used his books for years and highly recommend them.

Liman follow-up

Well, it’s a couple of days now since my blog on the Liman incident went live. I’ve had some great feed back on my coverage.

There has however been one individual that has not liked it so much. This is Steffan Watkins, owner of the blog Vessel of Interest. Mr Watkins was one of the unnamed characters I referred to in the Liman blog. He is widely regarded as a conspiracy theorist, and even has to go to the extent of denying it on his own blog. Whether he is or isn’t is irrelevant really.

Interestingly, a recent piece of work I was asked to do for Jane’s Intelligence Review magazine was to analyse an image of Russian navy Vishnya-class AGI Viktor Leonov to try and work out the various intelligence gathering systems that may be on board via all the different antennas visible. The actual article was written by Mr Watkins.

Now, up until this stage I really didn’t pay much attention to anything Mr Watkins wrote, mainly because what he wrote was aiming towards being the aforementioned conspiracy theories. But, he kind of came through with an interesting article – though it was nothing I didn’t know, as a group of us have been following Viktor Leonov for a few years now.

So, why hasn’t he enjoyed my blog? Well, I suggest you read it and see what he has come up with, and then come back here where I’ll answer his “questions”.

Hopefully, then you have read his blog on Liman now.

Firstly, lets talk about the “expert” part. He seems to think that I am condescending towards others from my comments. I am fully open to ideas and theories if there is evidence to back these ideas up and people also listen to what is being presented to them. In this case he did neither. And my references to things such as the Heather Sea evidence is clear – the ship wasn’t involved, it never was and yet people were still saying it was (not Mr Watkins I hasten to add, he hadn’t looked into anything outside the bubble of Liman). It was a quick and easy search through AIS history to see that it wasn’t, and yet people weren’t doing this. My reference to not being an expert is correct. I have no qualifications in the field of Radio Communications, I do not have an amateur radio licence and such like. I do not have a degree or a masters or any other diploma in the theories of radio – therefore I am not an expert. In ATC we have engineers that are experts in that – I wouldn’t dare tell them their job, just like they wouldn’t tell me how to keep aircraft apart. This is the reference I am making to being an expert.

He also mentions banter on twitter. There was no such thing, certainly not in my eyes. I’ve been around banter for decades – in the forces you need to be able to take it, and give it – and it is actually worse in the world of ATC. I can recognise banter when I see it. He also mentions an exchange of ideas. Yes there were exchanges of ideas, but he really wasn’t coming up with anything of substance. Instead, from his comments, he gave a picture that there was a conspiracy behind the incident – there had to be something because of the nature of the ship involved – an Intelligence Gatherer.

He actually says this in his blog:
Any ship could have an accident while at sea, in the fog, early in the morning. But, this wasn’t “any” ship; just by being a Russian Navy AGI (a “Spy Ship”) it makes me +1 suspicious. There is no good rational basis for that suspicion, except it’s a Russian Navy AGI, it definitely has sensitive gear aboard, and having it sink leaves a gap in whatever task it was doing, on the deployment it was on.

Why does this receive an extra degree of suspicion? Oh, that’s right, there’s no rational explanation, it’s just suspicious.

I wonder what Mr Watkins reactions were to the collision between a French Navy SSBN and a Royal Navy SSBN in the middle of the Atlantic in 2009. Holy shit, the French are at it again, trying to sink our navy 🙂

He refers to the fact that surely the Youzar Sif. H must have been able to have seen the Liman on radar:
The Liman was not a “stealth” ship, and as far as I understand, should have shown up on the navigational radar of the Youzarsif H; isn’t that why navigational radar exists?
Well, if two of the most expensive vessels in the sea, with some of the most sophisticated sonar and listening equipment ever made managed to thump into each other in the wide open Atlantic, then it is perfectly feasible for two ships to hit each other in thick fog in one of the busiest shipping lanes on the planet.

And it doesn’t even have to be in thick fog or underwater – ships hit each other. His Canadian navy had such an incident in 2013 in perfectly good weather when they were approaching each other.

Or there’s the Turkish Coast guard patrol boat that was hit in broad daylight, in the middle of the Bosporus, by a 158ft long Bulk carrier in August last year

Further about the radar he stated:
They were in thick fog, only navigating by instruments, and didn’t see a ship directly in front of them on radar?
Isn’t that weird?
I don’t think it reflects well on the Youzarsif H’s crew, unless the operations of the Liman were causing issues for the radar of the Youzarsif H. Yes, that’s wild speculation, because it makes no sense how a ship doesn’t notice a giant hulk of floating steel in front of it on radar. Make up your own crazy theory! It’s better than what we have now, which is nothing.

None of us know what radar system Youzar Sif. H has in place. I’ve been on quite a few ships in my time, civil and military – and of course I work with radar all the time. You get plenty of radar returns or “primaries” which you don’t know what they are, and you do your best to avoid them if you are not sure, but you have to make an assessment as what you think is a ship/aircraft and what is just weather (or a wind farm in a lot of ATC cases these days). The image here shows just a basic ships radar image, a modern one at that, so actually could be much better than the one on Youzar Sif. H – we won’t ever know I expect. Other radars are available of course, with more detail, but if Mr Watkins can work out what is what in this image then well done.

The next statement he produces is:
There have been no reports regarding who ran into who; or if it was a mutual effort. The news media is making it sound like they were both moving and collided in the fog. I’m not sure that’s correct.
He produces a list of things that could have happened – yes all obvious – but then doesn’t actual state why he thinks the news media are incorrect?? So why do you think this Mr Watkins?

He then mentions jamming of the AIS frequencies, but thankfully seems to have realised that this wasn’t the case. At the time of the “banter” he wasn’t stating that though:
See, there you go down the rabbit hole again. I’m wondering if the AGI screwed itself by engaging in EW in the same frequency range as AIS. 161.975/162.025 MHz range, within the usual Marine VHF band, right? Might explain the sketchy AIS coverage immediately prior.
Firstly, I’m still not sure what he’s referring to with EW. Early Warning?? Electronic Warfare?? Neither of which Liman is equipped for. And, secondly I went into great depths, the best I could at the time (see later) to try to explain the likely reason for the sketchy AIS coverage – all of which he kind of brushed aside for his more extreme likelihoods. Here, again he gives the air of being a conspiracy theorist.

We now get on to my favourite part of his blog:
•The Youzarsif H’s AIS signal was being received by terrestrial based AIS receivers, which Mr Roper described in his blog post with excruciating detail. The signal was very spotty before the collision, and crystal clear after the collision. This is the thing that really draws my eye and triggers my curiosity; it is the basis for much of my suspicion regarding this event. On the day Mr. Roper and I were discussing this he specifically dismissed my speculation that the issue could be related to the sender and insisted the gap in reception must be related to the receiver, or environmental conditions.
“This totally depends on the receiver not the sender! The receiver may have been off.”
-Tony Roper, 6:29 PM EST, May 4 2017
I tried to convey that my interest was less with the gap before the collision, and more with the immediate change to the signal quality (seemingly crystal clear reception) instantaneously after the collision, which Mr Roper had no explanation for at the time. It seems after reflection, he now theorizes the sender, may have had their antenna(s) facing away (blocked by the ship’s superstructure?) from the shore-based receiver when travelling Southbound (toward the Liman) and immediately after the collision turned around and faced their AIS antenna(s) toward the shore-based AIS-T receiver. This is fantastic speculation, and would explain how the signal went from terrible, to perfect, immediately, while other ships in the area had AIS-T signal all along.

Firstly, by excruciating detail I’m guessing Mr Watkins didn’t understand it. You must forgive me for trying to explain how something works instead of just giving less than half information on how something works. If he thinks my information was excruciating then maybe he should read the Propagation pages in the ARRL handbook which is spread over 30 pages. Or maybe he should go to websites such as:
Make more miles on VHF
HF Propagation tools
Or one of the many pages by Tomas Hood on propagation
It is obviously a fault of mine to make something interesting for the reader, that will hopefully teach them something.

I said above that at the time I did my best to try to explain to Mr Watkins what may have happened. This he seems to have thrown back in my face, alluding that I may have changed my mind on my original thoughts. I didn’t dismiss his thoughts but pointed out that there may have been a break in coverage. The interesting thing is the quote he has used, taken at 6:29PM EST. This was actually 23:59PM UK time, I was in a hotel room, 450 miles away from my computers and AIS systems. Maybe Mr Watkins has presumed that the rest of the planet is running at the same time as Canada, and that we were all glued to our PC’s? I made the best assessment at the time – and you know what, I wasn’t far wrong in the theory of coverage, as I proved in the blog.

He says I have “reflected” and changed my mind. No, I haven’t Mr Watkins. It’s a combination of both sender and receiver. I didn’t reflect. What I did was, on getting home, do some further analysis. Something Mr Watkins has quite clearly not done. He can only produce the same data on the what Youzar Sif. H did both before and after the incident. He still hasn’t come up with anything else – yet he has the nerve to criticise my analysis.

Come on Mr Watkins, show us some workings out. Do some actual analysis.

Here’s something for you. Data taken today from the same region.

The image below shows the tracks for various ships and their plots as received on AISLive

Holy crap – how do we explain all those gaps in the plots especially the ones on the rough route Youzar Sif. H took?? How the hell does the furthest ship away from any receivers have the best plot history?? Hmmmm, please do tell Mr Watkins. Maybe the Russians are jamming the area from outer space? Maybe there’s another AGI there?? Or maybe there’s just a poor area of reception.

The picture below shows the same area, at the very same time, but this time taken from MarineTraffic.

I’ve purposefully highlighted Reina as it is also highlighted in the AISLive image. The red ship to at the bottom is also on the AISLive image as the fully tracked ship. But what is that? MSC Eleonora is showing here, but isn’t on AISLive – what the hell?? How does that happen?? Please explain with all your worldly knowledge Mr Watkins.

Here’s some extra data for you, just so that you realise that AIS receivers aren’t on all the time (mine was off whilst 450 miles away for the weekend by the way). The three receiver examples that I used for the blog have the following averages for receiver availability over the last two months:
Istanbul = 93.3%
Burgas = 98.9%
Elena = 97.95%
So, not available all the time then.

He ends the large waffle with:
Can we prove this theory with the available data? Well, it’s certainly not as clear as I would like it to be. It is still crystal clear that immediately after the collision the AIS transmissions went from random times between successful transmissions to a steady stream at 3-4 minutes

The following day, still in the hotel 450 miles away from all my gear, I sent Mr Watkins roughly the same as the above showing a plot of another ship with the same loss of coverage. That obviously wasn’t enough evidence to make it “crystal clear”. I then produced my blog with further evidence – including an example of Youzar Sif. H with a loss of 14 hours of coverage – which again obviously wasn’t “crystal clear”, but was in fact excruciatingly full of too much detail for Mr Watkins. I have now produced the above which explains – yet again – that there are gaps in the coverage, yet other ships somehow have a better plot history. I suspect though, that all this will be far too foggy for Mr Watkins and he still will not be able to see anything clearly – except for a conspiracy.

Propliner Annual 2017

Just a quick post to inform you that this years Propliner Annual is now available to purchase.

Going on from last years successful year book, the 2017 edition is 108 pages of fantastic articles and photographs – many of which are in full colour (though the black and white images of days gone by are also great to see).

As well as a run down of what has been happening in the Propliner world over the last year or so, the year book contains 16 articles, including the following:

The history of the Avro 748 with VARIG in Brazil
The Barkley-Grow T8P-1 operations in Canada
A tour around Austria on Austrian Airlines Avro 748s in 1969
The aviation enterprises of John Gaul
BOAC’s fleet of early Lockheed L-049 Constellations
Flying on a Wilderness Seaplanes Grumman Goose in British Columbia
NASA’s Super Guppy
A tour of the ramp at Opa Locka
A tour of airfields in southern California and Arizona
The history of a Douglas DC-6A delivered new to Canadian Pacific Air Lines in 1958 which is still operational in Alaska with Everts Air Cargo.
Lockheed Electras flown by Cathay Pacific
Polynesian Airlines Percival Princes operations
Airlines of South Australia Douglas DC-3s operations
The early history of TACA in Central America

At just £11 in the UK including p&p this is a bargain. Prices outside of the UK are a little bit more at £13 for Europe and £15 for the rest of the World, but this is marginal for such a high quality publication.

If you’re interested in buying a copy then head over to the dedicated page on the Propliner website, where you can pay by PayPal.

Recent published work and photography processes

It’s been a busy six months or so for me with regards to having work published.

My main work has been the continuous analysis of the Russian navy to assist the editor of Fighting Ships, Stephen Saunders, to keep the data in the yearbook as accurate and up to date as possible. This information is also used in the on-line version of the yearbook. The current 2016/2017 edition is now available with plenty of my Russian navy data included, along with photos that I’ve taken.

As you know I stopped selling the yearbooks last year (apart from a large sale at the beginning of this year) and since then IHS have added older titles to their online store. Though not as cheap as I was able to get them, it may be worth taking a look to see if there’s any titles you may need in your collection. Here’s the link to the Fighting Ships page in the store.

As with all things involved with data analysis, looking into one thing generally off-shoots into another. From the OSINT work that I generally do for Fighting Ships, I normally have to take notes and data which would also fit into some of the other yearbooks. Some of this data has been sent to the various editors of the C4ISR yearbooks, which I hope will also be included in future publications. And there’s also photographs of radars, weapons and other systems that I’ve been taking over the last few years that hopefully will also be of use.

 

 

 

 

 

 

 

 

The OSINT work also brought me to the attention of one of the IHS magazines, Jane’s Intelligence Review. Since May I have worked on three articles for this magazine, two in conjunction with other writers, and one on my own. I am currently working on two more pieces for them, but at this time I can’t divulge on the subject matter.

The work has been very interesting indeed, and has brought me a couple of new acquaintances and friends from it. I’m hoping that that I can carry on with other articles for them once the two I’m working on now are complete.

 
Another magazine by IHS, Jane’s Navy International, has used a couple of my photos in recent months with hopefully more to follow. The magazines can be subscribed to from the IHS magazine online store.

It’s good work editing images for magazines, but its certainly a lot harder than it used to be – in general for less money than what you used to receive. The advent of digital photography has reduced the prices one gets for inclusion in magazines, mainly due to the fact that so many people now do it and so the editors have a plethora of images available to them. The silly thing is that in the old days you used to only take the photo, normally on slide film (Kodachrome 64), with no further editing by yourself (unless you happened to process the images in your own darkroom – I didn’t!). You’d send away the film to Kodak who would process it for you, and then you’d check over the slides after they’d been returned, deciding on which ones to send away. The only real work needed was to annotate the slide with basic information, and include a letter with further notes and where to post the cheque payment if used. Of course, you’d never see the slide again, and so if you wanted to have a copy for yourself then you’d need to take two photos – it was costly business using slide hence the payments you received being greater than they are now for far less work (one trip to the USA cost me more in Kodachrome 64 than it did in flights!!).

These days, the full photo process takes much longer.

Take the recent Joint Warrior (JW) exercise that I photographed. For this exercise I set aside two days for the actual photography. I then needed a further four days to carry out the actual editing of the photos for various publications! With current copyright laws, and the fact that most publishers are aware that photographers send away the very same image for inclusion in different magazines, the publishers now insist on exclusivity with an image (including publication online). Because of this, as a photographer you have to think ahead about who you are taking photos for. With JW I was thinking of three main possible targets – Fighting Ships, Jane’s Navy International and Warships IFR. As well as these I also had to think about the various other yearbooks by IHS (C4ISR and Weapons). So, if one ship comes along I need to take at least three images of it, maybe milliseconds apart, to cover the three main publications. Multiply that by a few hundred and you can see that there is a lot of images to go through once back home.

Back home then, I now need to process the images myself – no longer do they go away to Kodak for initial processing, and the publication no longer fine tunes the image for what ever use they may have. You need to trim it, get the exposure and colours right and make sure it’s sharp. Not only do you need to edit each image, you also have to include additional information for each one. This needs to be a title, your name, copyrights, what the subject is, when and where you took it and any other information you may think is needed for the publisher. With over 400 photos to go through for this JW it took a lot of time to carry out the whole process – 4 days as I’ve already said. From the 400 or more images that I took, I sent away around 70. How many of those will finally end up being published is unknown but I hope that it is around half of them.

Saying all that, it really is good fun and I still enjoy seeing my photos in any publication, be it book or magazine. I recently bought a new gadget for my GoPro, a time-lapse timer that moves the camera, and I decided to test it out whilst editing one of the images taken at Joint Warrior. The result of that test is below:
 

 

Talking of having things published in Warships IFR, I have actually had quite a good amount put into print for this magazine recently. And I believe there is to be a good spread in the December edition with images taken from the Joint Warrior exercise that I have mentioned above. I also hope to start writing the occasional piece for the magazine.

I’ll keep you informed.

Propliner is back

Around 11 months ago I reported the sad end of Propliner magazine in my article “End of an era”.

I’m very pleased to say that due to requests to the editor that Propliner be kept in some form or other, he has decided to try out whether it could succeed in an annual format.

In his words “Within days of announcing my decision to suspend publication of Propliner as a quarterly journal, I became aware of the enormous sentiment surrounding the magazine, and that there were a large number of disappointed readers.”

He continues ” Having remained in touch with many of the regular contributors and having canvassed their opinions, I have decided to go ahead and publish a Propliner Annual in April 2016″.

A brief outline of what is intended in the first (and hopefully not last annual) was also given – 96 pages full of features and photographs, as well as news on the past years events. Further information is on the advert to the right.

Amazingly, the annual is still going to be priced very reasonably indeed. For those in the UK, it is to be priced at £11 including delivery, with Europe at £13. The rest of the World is still only £15 for air mail delivery.

The target publication date is April 17th and orders can be placed at the Propliner website

PlaneBaseNG Update

Another bit of aviation news is a new update to the PlaneBaseNG database software. I ran a review of the database just over a year ago if you’d like to look back at what I wrote. Otherwise, head over to the website for more information, screenshots etc.

If you’re looking for an aviation database then this is definitely the one to have.

Fred T. Jane

Today, the 8th March 2016, marks the centenary of the death of Fred T. Jane, the founder of Jane’s Fighting Ships and all the off-shoots of products that now exist under his name. He was 50 years old.

Fred was discovered on the morning of the 8th March 1916 “dead in bed at his residence in Clarence Parade [Portsmouth]” and “had been attended during the past week or so by Dr Cole-Baker on account of an attack of influenza, and had also complained of heart trouble, but his sudden death came as a great shock”.

He lived quite an amazing life during those 50 years, too much for me to cover here, but luckily a book was written about him by Richard Brooks, published in 1997. The book is still available today, easily found on Amazon for instance, and is titled Fred T. Jane – An eccentric Visionary (From Ironclad Ships To 21st Century Information Solutions) – and it is a great read.

Not only did Fred invent Fighting Ships and All the Worlds Aircraft, he was one of the first people to have a motor car in the UK (including racing them), he was one of the first private pilots (though not very good going by all the crashes he had), he was a member of Parliament, he was a writer of Science Fiction (at the same time as H.G. Wells was writing on the very same subjects) and a very successful artist. It was the artistry and writing that got him into creating Fighting Ships, even though there were other successful books in existence at that time covering the same subject matter. It was his line drawings and silhouettes that made Fighting Ships stand out from the rest, and it is why the books are still in existence to this day whilst the others have dwindled into the past.

As well as writing and illustrating his own Science Fiction, he created artwork for other writers, including this for the book Olga Romanoff by George Griffith in 1893.

Taken from the 1932 edition of Fighting Ships, the earliest in my collection.

The early Fighting Ships books, the first of which was printed in 1898, went into extraordinary detail. These included the same details as is found in todays editions – weapons, crew numbers, engine types, speed etc., but also down to such details of the thickness of hulls in the various areas of each ship. The details on guns and armoured hulls were given comparative identifiers to show that a certain type of gun was capable of piercing a certain type of armoured hull. It was from this that the use of the books became manuals in “WarGames”.

Four metres of Fighting Ships. Nearly every edition from 1946 to 1995, plus the earliest I have from 1932

Now, these WarGamers weren’t just “nerds” sitting around at home, these were Naval Officers who used the information for training and strategy building, although the game was available to the public too. Prices at the time ranged from 4 guineas to £40 (around £4,400 in todays money), though the top end product “contained practically all the warships in the world” and was used primarily by various navies, including the Japanese Navy. The “games” came with model ships as part of the boxed set.

The early editions were in Landscape format, with different “standards” available – the “top end” versions were leather bound.

Though the Royal Navy was very slow in taking up the game, the Russian Navy were extremely interested in it and invited Fred to St. Petersburg in 1899 where he met Tsar Nicholas II. Grand Duke Alexander Mikhailovich even wrote the preface to the 1899 edition of Fighting Ships, the Duke being the Tsars brother-in-law. Fighting Ships isn’t even officially sold to anyone in Russia anymore.

The British Battle Fleet first edition from 1912

Thanks to this trip, Fred was able to publish an off-shoot book titled The Imperial Russian Navy which led further to The British Battle Fleet – a book I have in my possession in its first edition format. It is thought that to this day, no one else outside of Russia has had such access to their fleets. Fred became good friends with members of both the Russian and Japanese Navies, something that caused him grief later on during the Russo-Japanese War of 1904-05 where he lost friends on both sides.

Fred died on his own, though he had an estranged wife and a daughter, but his legacy still lives on today. Ironically, the house he died in was bombed by the Germans in the Second World War, but flats that were built there in its place has a plaque commemorating his name.

I’m very proud to have had my photographs printed in recent editions of Fighting Ships and I enjoy very much the research I do on the Russian Navy that I then forward on to the yearbooks current editor, Commodore Stephen Saunders RN. He is just the eighth editor in the 118 years of publication.

For more information on Fred T. Jane, please look up the previously mentioned book by Richard Brooks – you won’t be disappointed.

TitanSDR Pro demonstration

After receiving quite a few requests on information about the Enablia TitanSDR and it’s capabilities, I decided it would be good a good idea to create a demonstration video that would hopefully show just how good an SDR it is. The video is at the end of this blog.

I think that a lot of people can’t understand just why the two versions are the price they are, especially when it seems that a new dongle SDR is being evolved every day at a ridiculously cheap price. Yes, they are expensive but when you compare the price of these SDR’s to a top end desktop receiver, such as the Icom IC-R8500 for example, then it is fairly comparable.

But you must consider the fact that the Titan is really more than one receiver. The Pro version is 40 receivers, the standard is eight. You can’t record independently using the Icom, you need some additional software or a digital voice recorder plugged in to the receiver; and even then you can only record the one frequency – the Pro can record 40 frequencies, the standard can record eight.

The TitanSDR Pro can monitor up to 40 frequencies at the same time. Here, 10 frequencies are being monitored, mainly Oceanic ones.

Then, you can’t really record any bandwidth to play back using the Icom, but both versions of the Titan can record up to three separate bandwidths. These can then be played back, either through the SDR itself, or on another PC using the supplied USB dongle that carries a second version of the software – and if you did this you could be listening to, or recording, further frequencies or bandwidths. And all these separate bandwidth recordings can, of course, be played back multiple times, with multiple recordings being made within them; or data can be decoded; or signals analysed – what ever you require from an SDR.

This image shows the Titan monitoring 12 frequencies, 6 of which are decoding ALE using PC-ALE. This can take place in the background, while listening to the other frequencies on the SDR.

But, of course, this is just standard for any SDR isn’t it?? But is it?? Can you think of another SDR that has the capability to monitor/record 40 frequencies at once? I can’t.

The nearest SDR I found to the Titan in quality of not only recording capabilities but in quality of filters etc. meant that I would need to buy around 13 SDR’s of this model and spend over €30,000. Yet, just one of this model costs pretty much the same price as the Titan. Now, with that knowledge, the price of the TitanSDR’s really doesn’t seem that bad after all.

Don’t forget, the TitanSDR is a Military spec. SDR, designed originally for agencies to monitor multiple frequencies for analysis and data collecting. It already has top specifications but Enablia are still willing to listen to the users and add requested features if they can. They have already done this with quite a few ideas that myself and other users have suggested.

You’d think that the Titan would be a CPU guzzler wouldn’t you? Well it isn’t. Here the SDR is running 31 frequencies, whilst making multiple decodings using MultiPSK and PC-ALE. The CPU is running at only 27%, and that was it’s max reading.

 

PlaneBaseNG

I promised the owners of PlaneBaseNG that I’d add something about their aviation database to my blog about a year and a half ago, but due to personal issues and renovating my house I never got round to it. As it is though, I’m glad I didn’t because the database has changed so much since then I’d have had to have done blog updates practically every month since.

But, as it’s nearing the two year anniversary of it’s conception I thought now would be the right time.

So what is PlaneBaseNG? In the words of its owners “PlaneBaseNG is a fully featured product that manages all your aircraft sighting logging and reporting needs” and I’m not going to say otherwise. It is a great aircraft database, much better than any others around at the moment. It is simple to use, the search features are great and it has the easiest logging features I’ve seen. And most importantly it’s free – though you can donate money to help with its development if you wish, it’s totally optional.

PlaneBaseNG (or PB from now on) was developed after a few people got fed up with other databases out there. In particular, there was one that hadn’t changed for quite some time. I used this (unnamed) database and can vouch that it was good at first but very quickly went out of date in its development and style. Not only that, despite saying they would listen to their customers and add features where possible, this just never happened. In my opinion, though not proven, I think that the owners of the (unnamed) database used the funds from the subscribers to travel the world planespotting. The initial purchase wasn’t cheap (currently £130), and there were yearly subscription fees for the weekly updates – I mean, they even charged the poor data inputters the yearly subscription fees despite having to spend hours updating the data. Yep, I know this because I was a data inputter for them for a (very) short while. Handily enough all the fixed “books” for trips, created from search features, happened to be of the favourite trip locations of the owners. Requests for user created “books” fell on deaf ears.

I soon realised they weren’t for listening to anyone when I gave them some advice on making the data input easier. There were countless errors in Operator names, or should I say countless different versions of names for the same Operator – Delta Airlines/Delta Air Lines etc. This was because each editor had a crib sheet instead of having a much more useful sub-database containing the definitive list of Operators that could be chosen from a drop down list. It was easy to implement but it wasn’t and I got frustrated – as a user, searches were a nightmare as the data was quite often wrong. So I left editing but carried on with the database as there were no other options out there – except creating your own (which I had done and it was much better than this (unnamed) database, but as a single data-inputter going through Aviation Letter each month was very time consuming and so I had had to give up).

I was pleased to hear, about two years ago, that there was a new database coming out; and I was lucky enough to be one of the early users as I knew a few of the guys involved, some of which had also left the other database. PB changed very quickly in the early days, with almost daily updates to the actual software and features. This has slowed down now but that is because it is features packed, and I don’t know if there’s anything else PB can produce or think of that’s needed. Just some of the features included are:
Search facilities for Reg, Manufacturer, Type, Operator, Mode-S hexcodes, SelCal, Base, ICAO Operator codes
Multiple User creatable Reports
Wordbook (to create a handy needlist when travelling)
Adding photos to records
Flight logs

And much more – full information of all the features are on their website and in the extensive manual (something else the (unnamed) database fell short with, being four to five years out of date when I last saw it).

The database isn’t just for “spotters”, it can be used by anyone that is interested in aviation. For instance the SelCal search is useful to those that listen to HF regularly and need to check on what they’ve possibly heard. The same goes for checking details on Operators or Squadron details – the searches are endless really. Updates to the database occur twice a week, with a full update on a Tuesday and an additional Airliner/Execs update on Fridays. The database itself contains well over a million entries in categories of Airliners, Executive Jets and Propliners, Military (fighter/transports/Helis etc), Helicopters, Russians and GA types – you name it, they’re in there – even gliders. And if there’s something that’s not in there, a quick email and I’m sure it wouldn’t be long before it was.

Now on to PB’s sidekick – PBLink. This feature is for those that use either SBS or PlanePlotter virtual radars. It is a separate download that adds a background link to PB so that when you get an unknown Hexcode appearing on your radar a check is made with the main database and the details filled out in the SQB file for the radar. Before hand I had to use the Gatwick Aviation Societies (GAS) data, but that required access to the internet. The great thing about PBLink is that an on-line connection isn’t needed, making it possible to go fully mobile with your SBS. I tried it out last year at LAX, from the back of my hire-car and it worked perfectly, along with being able to log what I saw. There’s even the possibility to download a fully populated SQB file (overwriting your current one) which means you don’t need PB installed at all. I don’t bother with that as there’s no real point if you use PB as well (plus I use specific flags and file names for these which would get wiped out I think). As it’s linked to your database it also shows whether you’ve seen the aircraft before and if so, where and when.

Again, there’s plenty more details on the website and in the PBLink manual. It’s pointless me saying anymore, I’d only repeat what is in it and probably in not as much detail.

Finally, the last manifestation of PB is PBLite. This is designed for Windows based tablets and is an almost exact copy of the full PB database. One thing that’s great about this software is that if you use the full version on your PC or laptop, you can copy across your logs/sightings to the tablet. And just to add, this also possible if you have a desktop and a laptop – your loggings can be copied between the two as and when.

I like PlaneBaseNG a lot, I use it daily and not just for the spotting side of things. I use it for radio monitoring, and I use it to confirm information when I’m writing my blogs and magazine articles. With over 1000 users already, I’m obviously not the only one that thinks it is a great product.

All I’ll say is, go and take a look at the website for PlaneBaseNG and you’ll see many more features – some I haven’t even tried yet. Meanwhile, over at the (unnamed) database, despite a nice new glitzy website – it’s still the same old database by the look of the screenshots.