9K33 Osa in Vladivostok

Due to the increased tension on the Korean peninsula, a short video clip showing a convoy of seven [see Edit below] vehicles travelling through a city has caused some raised eye brows.

The vehicles in question are 9K33 Osa (NATO designation SA-8 GECKO) surface-to-air missile TELARs, meaning that a single vehicle transports the missiles in their launch containers and is equipped with a radar allowing it to acquire and fire upon any targets without outside assistance. At least six of the vehicles in the convoy are Osas, the lead vehicle is too blurry for an accurate identification, and could be a command vehicle.

9K33 Osa-AKM. Source: Wikimedia Commons/DonSimon

The video is indeed shot in Vladivostok, at the western end of Russkaya Ulitsa, at a relatively recent date. The geolocation is based on the building to the left, visible at the very beginning of the clip, which holds a V-Laser store, as well as the small kiosk in front of it.

The Google Street-view image above is from 2013, and it seems some changes has been made to the area between the road lanes.

To the right, a large building with a slightly smaller one behind it is briefly visible. This is not found on Google Street-view, but Yandex somewhat newer imagery shows it under construction. The building in question houses the Mall Druzba Center.

All in all, the location seems quite certain, and while it is hard to say for certain how old the clip is, the inclusion of Mall Druzba Center means that really old footage can be ruled out.

The location is intriguing. As mentioned, this is at the very end of Russkaya, and there does not seem to be any logical place from where the vehicles would have come, unless they have been transported to Vladivostok by rail or sea, and are now choosing this somewhat low-key road to get out from the city.

As for the presence of Osas in Vladivostok, that in itself is no reason to worry. The movement of a handful of medium-ranged SAMs is well within normal routines. However, this does constitute a small piece of a pattern of current events and troop movements on and around the Korean peninsula which on the whole do give reason for concern.

Edit 15 April 09:40 (GMT +2):

Zvezda state that three motorized infantry brigades in the Far East has moved out. The Osas could very well be related to this.

Edit 15 April 10:50 (GMT +2):

A second video clip shows the forward part of the convoy, and together the clips seem to indicate that a total 13 vehicles are included in the convoy. Eight of these are 9K33 Osa TELARs, with a further two being the 9T217 missile transporter and loader, which carries reloads for the TELARs. The last three are then some kind of unidentified BTR armored vehicles, likely being PU-12M command vehicles. This setup does make sense, as it would mean that the convoy is made up of two batteries with four TELARs and command vehicles each, though the number of 9T217 does seem a bit on the low side.

9T217 missile transporter and loader. Source: Wikimedia Commons/Wistula

The Finnish Investigation

One of last week’s major stories was the Joint Investigation Team (JIT) presenting their ‘interim results’, again confirming what has been seen as the most likely explanation since the immediate aftermath of the 2014 tragedy: that MH17 was brought down by a Russian-supplied Buk-M1 surface-to-air missile. I won’t discuss the details here, as they have been given in a number of different forums, including by Bellingcat as well the earlier investigative report and now the JIT. Suffice to say, the amount of evidence found in both open and non-open source has reached such levels that the question of whether a Russian supplied Buk shot down MH17 can now be considered a litmus test for whether you are under the influence of Russian propaganda or not.

Finnish Buk-M1 TELAR with missiles mounted. Source: Wikimedia Commons/Finnish Defence Forces
For Finland, the interesting part came when Dutch newspaper Telegraaf broke the story that Finland had provided data and performed secret tests on our Buk-missiles, which are of the same M1-version as the TELAR used for downing MH17. To begin with, this ‘important contribution’ by the Finnish authorities was cheered by Finnish media (#Suomimainittu), but the party was cut short by the announcement that JIT had in fact not been allowed by Finnish authorities to see the evidence. This in turn caused a minor uproar that was rapidly shaping into a political storm when the Finnish President called a press conference on the issue.

But first, let’s rewind to how the by now infamous SAM-system ended up in Finland. By the end of the Cold War, the Soviet economy was in a very poor shape. This was also seen on the clearing accounts which formed the basis for Finnish-Soviet trade. Under this system, anything exported by Finland was ‘cleared’ from the account when items to a corresponding value were imported by Finland from the Soviet Union. When the Soviet Union disintegrated, the Soviet balance sheet was squarely in the red, i.e. the Soviets owed Finland goods. During the years since, this has gradually been paid off as goods, services, and cash payments, until the last payment was made three years ago.

One of the early payments was the Buk-system, which arrived in Finland in the mid-90’s and replaced the earlier (and outdated) Soviet-made S-125 ‘Neva’ (SA-3 GOA), local designation ItO 79. The Buk-M1 was introduced under the ItO 96-designation (now ITO 96), and served for roughly a decade until concerns over its vulnerability to countermeasures caused its gradual withdrawal in favour of the medium-ranged NASAMS II (ITO 12). The last batch of conscripts trained on the system in 2005, but the system was scheduled to remain in service at least for a further ten years.

Fast forward to 2014, when the Dutch prosecutor’s office contacted Finnish authorities and asked for technical assistance as part of the criminal investigation into the fate of the MH17. Exactly which Finnish authority received the request is unclear, but eventually a small circle of top politicians were the ones who made the decision on whether to answer the call or not. The decision was made to collaborate with the Dutch prosecutor’s office in full,  and to keep the cooperation secret from the general public. The last part was due to the Dutch authorities requesting that this would be the case, and was not seen as anything unusual given the circumstances. Evidence gathering is a tricky matter even in a ‘normal’ case, and as such it was understood that the cooperation would not be disclosed until during the eventual trial, at the earliest.

The third arrival of the bodies of MH 17 victims. The coffins were transported from Kharkov to the Eindhoven Air Base. Source: Wikimedia Commons/Hille Hillenga – defensie.nl

All this was revealed during the press conference, where the President stressed that the decision was not taken lightly. The acquisition document of the Buk, which isn’t public, forbids the disclosure of information concerning the system to third parties. This was then weighted against the UN Security Council Resolution calling upon all parties to provide any requested assistance to the investigation(s). During the investigation a number of requests have been made, with the most ‘special’ one probably being the request to detonate a warhead and collect part of the shrapnel (contrary to some reports, no missile firings seems to have taken place). This was done in an undisclosed location in Finland by the Finnish Defence Forces in the presence of Dutch officials, and the requested shrapnel was handed over to the Dutch authorities.

Key to the story is that throughout it was the Dutch prosecutor’s office that was in contact with the Finnish authorities. According to president Niinistö, Finland has handed over all information requested by the Dutch authorities, and at no single point have the investigators expressed any kind of disappointment that the data wouldn’t have been thorough enough. The current issue came about as a result of the Dutch prosecutor asking permission that the evidence be handed over to JIT. The letter which requested this did not include any time frame for when the answer was needed, and as such it was decided to send a small committee over to the Netherlands to discuss how this change had come about, and exactly which part of the evidence was needed (the president confirmed that it was preferred and legally more straightforward to cooperate with the prosecutor’s office rather than the JIT). Before the Finnish administration had had time to put their plan into action, the JIT published their interim report and the fact that Finland was involved was leaked.

President Niinistö and Foreign Minister Soini at the MH17 press conference. Source & copyright: Matti Porre/Tasavallan presidentin kanslia
The President was clearly not happy with how the Finnish actions had been portrayed in the media, or with the fact that the Dutch had leaked the info after being the ones who originally requested secrecy.

Enter the follow-up discussion on what the press conference meant, and how Finland’s reactions should be seen (especially in the light of our relations vis-a-vis Russia).

Some have been quick to argue that there are traces of Finlandisation all over the handling of the issue. The simple fact that the decision to supply the evidence was taken by the political leadership and not by the officials normally handling these kinds of requests point in this direction, as do the continued emphasise on how hard the decision was due to the acquisition document forbidding this kind of information sharing. The critics also point to the fact that Finland did inform the Russian authorities of the request for evidence and that we were going to collaborate with the Dutch investigation. ‘We told no-one, except the Kremlin’, does indeed have a somewhat bad ring to it.

On the other hand, there are also a number of issues here that point directly in the opposite direction, perhaps the main point being that Finland decided to inform Russia that we were going to disclose technical details of their SAM system to an investigation that quite likely was going to result in Russian citizens being charged. The key word here is ‘informed’, the government never asked for permission, something the president clearly stated had been decided against when asked about the issue. The investigation has also spanned over the latest set of parliamentary elections, showing that there is broad support for it to continue.

(A third point of view was the pro-Russian trolls who now argued that this shows that the JIT isn’t trustworthy and that the ‘true source’ of the bow tie-shaped fragments now has been revealed. As noted, the disinformation campaign on the MH17 has long since lost all its credibility.)

I am personally a bit torn over the issue, and felt the beginning of the presser emphasised how hard the decision was a bit too much considering the nature of the issue. On the other hand, I find it hard to be too shocked over the fact that the request for assistance wasn’t dealt with as a run-of-the-mill case. It should be noted that as the original acquisition deal for the Buk-missiles was handled through the government-to-government discussions on the clearing account, the ban on publishing the information is not a buyer-supplier NDA, but most likely part of a government-to-government agreement. Pointing to this is also the fact that it indeed was the president and the Foreign Minister who hosted the press conference, showing that this was dealt with as a matter of foreign policy and not one of a strictly legislative nature.

There has also been discussions regarding if the information handed over to the Dutch actually included such data that was covered by the ban in the first place. This is all pure speculation, as no-one in the public has seen neither the acquisition document nor the details on what information has been requested. However, my personal opinion is that if the information was indeed of such a nature that the Dutch prosecutor needed to get it from an operator of the system, it is also likely to be covered by the secrecy clauses.

In the end, while the exact pattern of decision making might or might not have followed the letter of the law to the point, the whole issue was probably best described by FIIA’s Mika Aaltola who noted that the whole issue is a “storm in a teacup”. This has been further confirmed by the Dutch Foreign Minister Koenders apologising to FM Soini for the leaks, as well as by the chair of the JIT, Gerrit Thiry, who clarified that it certainly wasn’t his intention to criticise the Finnish authorities, but that it was an unfortunate misunderstanding between the Finnish journalist and the Dutch police making the statement. Thiry is extremely satisfied with the assistance provided by the Finnish authorities, and as such everything is back to normal.

Kaliningrad and the Suwałki Gap – a look from the other side

The discussion regarding the potential of an armed conflict, or even regional war, between NATO and Russia over the Baltics have become a staple of the post-Crimean world. Most of the focus has been placed on the difficulty in reinforcing the Baltic states in the face of a Russian anti-access/area denial ‘bubble’ (A2/AD) created with Kaliningrad as the centre of the bubble, and the potential of strengthening this bubble by rapidly occupying the Swedish island of Gotland. If this was to happen, the only way of reinforcing the Baltic states would be over the Polish-Lithuanian border, a strip of land which rapidly has become known as the Suwałki gap (named after the Polish town at one end of the gap). The Suwałki gap in turn is claimed to be extremely vulnerable, as it is wedged in between the Kaliningrad enclave and the Belarusian border.

I will argue that this is, in certain aspects, an oversimplification, but that contrary to what one might expect, this does not lessen the risk of a confrontation.

The A2/AD Bubble

With regards to the A2/AD bubble set up in Kaliningrad, it is usually seen as blocking maritime and airborne forces. By using a combination of long-range high quality surface-to-air missiles and anti-shipping weapons (land based missiles as well as surface and subsurface units), Russia would be able to deny NATO forces entry into the southern parts of the Baltic Sea, and any units operating there would be under constant threat. These two features are a key part of the definition of A2/AD challenges, see e.g. [1]. As NATO is lacking both numbers and key capabilities (such as mechanized and armoured units) in the Baltic states, any NATO response to an incursion would have to include a rapid transfer of reinforcements from other NATO countries and into the Baltic states. The ability to hinder or disrupt these reinforcements would ensure that Russia can maintain superiority on the battlefield in terms of both numbers and lethality of the weapon systems employed.

This description is usually accompanied by maps featuring rings at 400 km, the stated maximum range for the longest ranged surface-to-air missile in current Russian inventory (the 40N6 missile of the S-400 Triumf system) [2], as well as at 300 km, the approximate maximum range of the K-300P Bastion-P coastal defence system’s P-800 ‘Yakhont’/’Oniks’ missiles [3].

Scale models of P-800 Yakhont/Oniks missile and vehicles from a K-300P coastal defence battery. Source: Wikimedia Commons/Vitaly Kuzmin

However, this fails to account for a number of facts. To begin with, at maximum range missiles lacks the energy to be able to chase down and hit maneuvering targets such as fighters. The very long range nature of the 40N6 also by necessity dictates that the missile is extremely large, further degrading the performance against maneuvering targets. As such the main use of the 40N6 is likely against large high-value targets such as AWACS, tankers, stand-off jammers, and transport aircraft. A more fitting maximum range when discussing fighter-sized targets would be that of the somewhat smaller and shorter-ranged 48N6E missile, which in its latest version feature ranges over 200 km [4]. This is still a highly potent weapon, but the area covered is roughly a quarter of that of the 40N6.

For anti-ship missiles, the need to maneuver isn’t as crucial, but going out to maximum range means that a measure of tactical flexibility is lost. This includes routing the missiles to attack from unexpected vectors, or simultaneous impact by missiles approaching from different directions, see e.g. video clip from Ruptly [5].

The main problem operating out at very long ranges is target acquisition. The range of radars are usually limited by the horizon, which is the reason that aircraft mounted radars are so popular. This is a problem for Kaliningrad, as the whole area is easily covered by NATO air defence networks (more on which later), and as such Russia has installed over the horizon (OTH) radar arrays in the area. In the case of Kaliningrad, it was recently disclosed that the Sunflower-E (Ru. Подсолнух-Э / Podsolnukh-E) long-range air- and surface radar will be installed in Kaliningrad [6]. Note that the picture in the source is of the anti-missile radar Voronezh-M, also found in Kaliningrad [7], and not of the Sunflower-E. The exact range of this array is unclear, but the manufacturer claims it can be used to cover the 200-mile (320 km) economic zone of coastal countries [8], while the earlier quoted Russia Today article cited ranges ‘up to 450 km’. This latter figure is likely against large airborne targets at altitude, which is also in accordance with a widely circulated but unsourced graphic [9]. The radar array is made up of a ‘forest’ of individual antennas, which means that it is likely very resistant to shock waves from bomb blasts. However, the largely immobile nature and size of the installation means that its exact location is well-known, and while the antennas might be hard to destroy and do feature a certain degree of redundancy if damaged, the system likely has other key components (power supply, transmitters, receivers, and operator centrals) which are more vulnerable.

Radars are also inherently active, which means that they can be located once they start transmitting. To avoid this both anti-ship missiles and the S-400 has the ability to be fed targeting data from passive sources such as emitter locators, which work by locating an emitting radar of the adversary. This is particularly effective if the enemy forces have used active jamming to make the use of own radars impossible, as the active jammer is a very strong source of emission, and hence easily targeted. As a general rule, these systems are however less accurate than active systems, and the difference is emphasised when operating at very long ranges. The fact that all missiles discussed here have their own active radars does remedy this to a certain extent.

In summary

  • The A2/AD bubble in Kaliningrad is made up of some of the world’s most modern anti-ship and surface-to-air missiles
  • To achieve accurate targeting data at extreme ranges, it relies on potentially vulnerable sensor systems
  • Secondary sensors are available, but offer a somewhat degraded picture
  • The bubble does not start at an absolute range (e.g. 400 km), but instead gradually increases in capability and lethality the closer one gets to Kaliningrad

Logistics and Kaliningrad as an enclave

Often overlooked in the discussion is the logistics of the A2/AD bubble and the vulnerability of Kaliningrad itself. The long range missiles of the S-400 and K-300P systems are large and bulky, with e.g. the 48N6E being 7,5 m long. The TEL firing units as well as transport units for reloads are all based on either 6×6 all-terrain trucks pulling semi-trailers or self-propelled 8×8 heavy all-terrain vehicles. The pure size means that the battery won’t have too many missiles with it in the field. Notable for Kaliningrad, if reinforcements are needed fast, only large transports are able to airlift the loaded vehicles, and only a limited number at a time.

This slideshow requires JavaScript.

Out in the field, the battery moves as a large convoy of bulky vehicles. The firing battery comprises an engagement radar and up to twelve TEL’s, each with four missiles. These are then backed up by the supporting vehicles, including missile transports (roughly similar to the TEL’s in outward appearance) and the reload vehicle with a heavy-duty crane. The firing batteries are then linked to a centralised command vehicle and a long-range acquisition radar. This means that any S-400 battery on the move will include ten to twenty oversized trucks. For the K-300P, the composition is roughly similar.

This mobility is one of the great benefits of the S-400 and K-300P systems. The whole battery can be moved around quickly, and deployed in a spread out fashion to hide from enemy units, see e.g. example of K-300P firing P-800 Yakhont from a concealed position [10]. However, as soon as the radar starts emitting, the rough position of the battery can be found out. This means that for the the systems to heighten its chance of survival, the battery will frequently need to change positions. This in turn means that there needs to be several batteries moving around in a coordinated fashion, so that at any given time there will be a firing ready battery somewhere. For the anti-ship batteries the need to operate with the battery’s radar on is smaller, and by extension they can more easily stay hidden.

Kaliningrad is roughly 200 km long (east-west) and 100 km wide (north-south). This rather small area would have to host a number of S-400 batteries, one or two of which at any given time are shifting from one firing position to another. It is clear that during the movement phase the large trucks would be vulnerable to detection, and by extension suppression and destruction. The same would be true for the large resupply vehicles bringing new missiles from warehouses out to the firing units deployed in the field.

The logistics for the missile batteries is but a small piece of the larger logistical headache concerning the Kaliningrad enclave as a whole. As mentioned, it is wedged in between NATO countries, and while it can disrupt air and seaborne reinforcements into the Baltic countries, it is in fact even more tightly besieged itself.

Artillery coverage Kaliningrad.jpg
The range covered by three artillery batteries deployed in Siluté (Lithuania), Budry, and Gorowo Ilaweckie in green. The ranges are 48 km for the battery in Siluté, based on the XM982 Excalibur guided munition in service with the German PzH 2000 (though currently not with the Lithuanian army), while the range for the Polish batteries are a more generic 40 km. In blue we have the 160 km of the US ATACMS missile fired by the M270 MLRS, with the batteries deployed to Suwałki and Elblag.
SAM coverage Kaliningrad.jpg
The range of three SAM batteries with ~100 km range (e.g. Patriot PAC-3, SAMP/T), deployed in Tauragé (Lithuania), Elblag, and Suwałki.

If we for a moment turn the table, and start drawing range rings based upon NATO weapons systems, it soon becomes clear that current medium/long range systems such as the Patriot PAC-3 or the SAMP/T could seal of the airspace of Kaliningrad. Similarly, the narrow width in the north-south direction means that large areas of Kaliningrad are covered by current Polish and Lithuanian artillery systems deployed inside their own borders. This means that the suppression of enemy air defences mission (SEAD) could in part be undertaken by artillery units equipped with modern munitions instead of risking aircrafts and pilots as would usually be the case. If long-range surface-to-surface systems such as the US ATACMS missile system are used, the whole enclave can be covered by ground based systems.


In summary

  • The small size of the Kaliningrad is problematic with regards to keeping the location of the SAM batteries concealed when shifting position
  • The whole enclave would be under siege from the onset of hostilities, as the whole airspace can be covered by a small number of units operating current surface-to-air missiles
  • The size of the enclave means that NATO ground based systems would have a large impact, including performing missions usually reserved for airborne systems (such as SEAD)

The Suwałki gap

As a consequence, the importance of the Suwałki gap to both sides becomes clear. The gap, roughly the area coloured yellow in the map below, constitute the sole land route between the Baltic countries and the core of the NATO countries found in the European mainland. Similarly, the area marks the shortest distance from the Kaliningrad enclave to Belarusian territory, and as such is the most likely place for a Russian attempt to relieve the surrounded enclave.

Suwałki gap

The gap is often described as ‘vulnerable’ from a NATO point of view, mainly due to it being only 65 km wide at its narrowest point. This means that the entire width of the gap is within range of Russian artillery, and ground units could cover the distance in a matter of days (or less if unopposed).

However, this fails to account for a number of factors. While disrupting the movement of troops on the two main roads (Suwałki-Kaunas and Augustów-Alytus-Vilnius) and  single railway that passes though the gap is possible not only with artillery as well as with e.g. special forces on foot, cutting it off completely and opening a corridor to Kaliningrad is another thing completely. The main transport arteries of the gap, as mentioned, traverse the region in the northeast-southwest direction, i.e. between Poland and Lithuania. There are a number of smaller roads going in the opposite direction, but in general it is easier to move troops and materiel between Poland and Lithuania than between Kaliningrad and Belarus. The main road going east from Kaliningrad goes north of the gap, and passes through the Lithuanian capital of Vilnius, before continuing on to Minsk. The terrain is also very varied, with especially the area bordering Belarus being heavily forested. As such, the terrain is well-suited for the kind of light infantry that makes up the majority of the Lithuanian army. Below is an example of the terrain found in this area, featuring the road from Belarus to Druskininkai, Lithuania.

Perhaps the most often overlooked factor is the Polish army. At the same time many NATO countries have shifted to lighter and smaller units, Poland has maintained a core of heavy units, lead by the formidable 11th “Lubuska” Armoured Cavalry Division [11]. The unit is a full-fledged armoured division, featuring two armoured brigades equipped with Leopard 2A4 tanks, to be upgraded to the Leopard 2PL standard [12]. Backed up by two mechanised divisions equipped with PT-91 Twardy, a locally modernised MBT based on the T-72, it could provide the core of a complete armoured corps, one of very few left in NATO.

The big difference between the Polish army and others large armoured units in NATO is that it is based close to the Baltic countries, and, crucially, that the political leadership in Poland and the Baltic states largely shares the same view of Russia and the need to counter an increasingly aggressive Kremlin. As has been noted in other scenarios, the key to countering a Russian aggression in the Baltic states would be to get qualified units on the ground as soon as possible, to boost deterrence and provide an answer to the heavily mechanised Russian ground units that otherwise would be hard to counter for the light infantry units that make up the core of the Baltic armies [13]. Importantly, if a crises were to start to unfold, the Polish units might be the only ones where there would be both the political will and a short enough transfer time that they might pass through the Suwałki gap and take up position before the gap would be under serious threat. The distance from Suwałki to e.g. Tartu is just over 600 km by road, a far cry from the logistics involved in getting a US or British armoured division deployed to Estonia.

Polish Leopard 2A4 from the 11th “Lubuska” divsion during exercise Steadfast Jazz, held in Poland and the Baltic States during 2013. Note the winged hussar emblem on the turret. Source: Wikimedia Commons/Cpl Madis Veltman, Estonian army

It is obviously not without problems to deploy these units to the Baltic states. To begin with, the eastern Polish border can hardly be left undefended. Also, there is a gauge break between the Polish and Lithuanian railway systems, meaning that, until Rail Baltica is ready, what would otherwise be the most efficient way of rapidly moving tracked vehicles from Poland to the Baltic states feature a severe bottleneck. Also, the 11th “Lubuska” division is deployed in the southwestern parts of Poland, more or less as far from Lithuania as possible. The 16th “Pomeranian” Mechanised Division is however deployed opposite Kaliningrad, and while its PT-91’s are inferior to the Leopard 2PL, they are superior to anything currently deployed in the Kaliningrad enclave.

In summary

  • The main logistical arteries of the Suwałki gap, constituting two major roads and a railway, all go in parallel from Poland to Lithuania, with only smaller roads in the gap connecting Kaliningrad and Belarus
  • While part of the Suwałki gap is open ‘tank country’, other parts are heavily forested and/or broken up by water. A mechanised force would be vulnerable to ambushes and being funneled into bottlenecks
  • The Polish army fields a considerable striking force in the form of heavy armoured and mechanised units, as well as what is likely a lower threshold to deploy these in the Baltic states in the face of a crises compared to NATO countries located further from Russia


All in all, the Kaliningrad enclave does constitute a strategic problem for NATO in times of crises, due to its location at the entrance to the Baltic states and with the long ranged systems based there interfering with any NATO operations in the southern Baltic Sea. However, it is not an absolute hinder to NATO operations in the area, and in a prolonged conflict it would effectively be under siege. Similarly, the Suwałki gap is not necessarily as vulnerable as it is sometimes portrayed. Also, while the draw down amongst the traditional major NATO countries have left gaps in the ability of NATO to rapidly project military power with heavy units, Poland still upholds a sizeable mechanised force within striking distance of the Baltic states, coupled with a more assertive political leadership compared to what is often seen in the traditional NATO countries.

However, while all this might seem to be good news for NATO in the face of increased Russian aggression and the reckless behavior displayed by the Kremlin in relation to several of their neighboring countries, I will argue that the opposite is in fact the case.

The ability of NATO to respond to a Russian aggression aimed at the Baltic states, as well as the possibility to move Polish units into the Baltic states at short notice, create a scenario where, in an unfolding crises, time would not be on Russia’s side. In fact, if Russia would conclude that a confrontation was inevitable, it would make sense to strike sooner rather than later. Through this, the capabilities of NATO and the relatively weak position of Kaliningrad might actually become catalysts for instead of deterring an open conflict.

While a regional conflict over part of the Baltic states would be bad enough, this is far from the worst scenario. St Petersburg is within 150 km from the Estonian border. If the Kremlin actually start believing their own narrative of an aggressive and expansionist NATO, even the possibility of NATO moving a mechanised division into Estonia might be the spark that ignites a larger confrontation. And a conflict in which Russia feels that its very heartland is threatened by NATO tanks is one from which it won’t back down. I am strongly of the opinion that appeasement is not the best way forward when it comes to Russian aggression. But if Putin makes a move towards the Baltic, NATO just might be out of good options.



A BK-16 and a not-so-secret marina

An interesting picture came to my attention yesterday, showing Rybinsk Shipyard’s BK-16 fast assault craft in an undisclosed small naval marina. Extremely little footage of the BK-16 in service have appeared, so finding one at what looks like a makeshift base warrants a closer study.

A number of vessels, including possibly another BK-16 and a midget submarine, are also present under covers. After some time of looking at satellite maps of Russian and Crimean shores, a picture search, and some discussions with my wife regarding the vegetation around the Black Sea, Baltic Sea, and Russian inland, we managed to locate the likely spot. It seems to be situated in Sevastopol, on the Crimean peninsula. What is interesting is that an earlier picture of the area shows it seemingly being a civilian boat workshop. Now it is clearly in military use, as evident not only by the increased number of vessels, but also by the hoisted naval ensign and the dark green trucks parked between the two buildings.

The likely location from where the picture was taken with some key identifying features marked. Satellite picture from Google Maps

That Russia has taken to using former civilian facilities in Sevastopol, long the main base of the Black Sea Fleet and by extension the main logistical hub for the operations in the Mediterranean and Syria, is perhaps the most interesting fact here. The equipment seems to point towards a smaller unit of marine infantry, possibly a reconnaissance and/or special forces unit. Either there has been such a rapid expansion of units stationed in Crimea since the Russian occupation started that units with a smaller logistical footprint has had to move out of the main facilities, or then this is an attempt to keep the operations of this unit outside of the spotlight. Note that even the rusty fence in the foreground has not been mended since the first picture, meaning that the facilities seems to have been taken over ‘as is’. This might indicate the navy’s stay being only temporary, or it is another sign of the navy trying to keep a low profile (if so, not hoisting the St Andrew’s flag might have been a good idea). Another really interesting question is obviously if there really is a midget submarine under the tarpaulin, and if so, has it been used operationally in the Black Sea?

Project 03160 ‘Raptor’ Capable of 48 kts?

Swedish blogger/twitterer Observationsplatsen yesterday posted a video published by Pella JSC of a Project 03160 ‘Raptor’ (ru. Раптор) performing trial runs. The trim of the boat during runs is rather more positive than in the case of its Swedish counterpart, something that spurred me to do some number crunching.

The nose-high running of the Raptor. Source: Pella JSC
Strb 90
The flat running profile of the CB 90. Source: Wikimedia Commons & Norwegian Defence Forces.

As said, what seemed evident from the video was that the boat traveled in a nose-high position, which generally means that the center of gravity is too far aft and/or that the boat has trouble getting through the transient phase and into the planing phase. The original CB 90 does not, meaning that something apparently went wrong for Pella. As said in my original post on the Raptor, reverse-engineering is not as easy as it seems.

A disclaimer to begin with: it is possible that Pella is simply performing their test-drives at half-power. However, I lack any idea of why they would choose to do that, and post a video of it without any notice about the restrictions imposed.

The hull form of the CB 90 is not optimized for planing, being of the semi-displacing kind. This provides better sea-keeping abilities, but it also means that there is less horizontal surface to provide the dynamic lift needed for planing. On the CB 90, this is accentuated by the very narrow chines. According to the three-view plans provided by Dockstavarvet and Pella JSC respectively, the width of the chines doesn’t seem to differ in any remarkable way. The difference in performance must thus come from something else.

The narrow chine of the CB 90. Source: Author.
The narrow chine of the CB 90. Source: Author.

According to Dockstavarvet, the CB 90 has a displacement of 18 tons, being powered by two 805 hp engines, giving a thrust to weight ratio of 89 hp/ton. The Raptor is cited by Pella as 23 tons, with two 1133 hp engines (curiously enough, the English version gives the total power as only 2 x 1000 hp). This gives the Raptor a higher thrust to weight ratio of 98 hp/ton, a 10% increase compared to the CB 90. However, this performance increase comes at a price. The original Scania DSI 14 engines of the CB 90 had a dryweight of around 1700 kg apiece. Pella has not given out their engine of choice on their homepage, but a secondary source of uncertain value gives the engines as Caterpillar C18’s. This seems logical, as several of Pella’s tugs have been fitted with Caterpillar diesels. The C18 has a dryweight of 1950 kg, or 400 kg more weight for the pair of marine diesels. Another change is in the type of waterjets employed. The Rolls-Royce FF410 of the CB 90 had a dryweight of 485 kg, and an entrained water volume of 192 liters/kg. I have not found the model or manufacturer of the waterjets of the Raptor stated anywhere. However, if one looks closely at the drawings provided by Pella, it becomes very clear.

Water jets
The stern with the water jets of the Raptor. Source: Pella JSC.

That, my dear friends, is a Rolls-Royce Kamewa A3-series water jet, most probably of the 40A3-model. Unlike the axial-flow FF-series, the A3 provides a hybrid-flow design, giving higher performance. However, another major difference is in the material. Where the FF-series is made of aluminium, the A3 is of an all-steel construction. This raises the dryweight to 850 kg apiece, with an entrained water volume of 186 litres/kg. In total, a simplified calculation of the weight of the drive package (not counting liquids, turbocharger, transmission, shaftes, …) of the Raptor gives a total weight of 5970 kg, with the corresponding value of the CB 90 being 4755 kg. This is a 25% increase in the mass of the drive train (compared to a total increase in displacement of 28%). In fact, the increase in weight of the engine and water jet accounts for roughly 24% of the total increase in displacement.

The important part, however, is the fact that the drive train is placed at the stern of the boat. This gives any increase in weight in the drive train a large impact due to the long lever. As the increase in weight of the jet and engine is in line with (in fact slightly under) the general increase in weight of the boat, this should not affect the trim of the boat if all added mass was distributed evenly.

Why then does the Raptor travel around with its nose in the air? I have no definite answer. It is possible that the added ballistic protection or an increase in engine room insulation has caused a shift in the centre of gravity aft. Another possibility is that the lengthening of the hull (the LoA of the Raptor at 16,9 m is two meter longer than the 14,9 m of the CB 90) has caused a similar shift. The fuel tank is also probably situated slightly aft of the centre of gravity, meaning that an empty vessel with full tank(s) would be trimmed more nose-high than a loaded vessel with empty tanks. The hard numbers available indicates that the boat should be able to attain the 48 knots specified. However, until Pella releases a new video, I will stand by my opinion that the Raptor does look more like a 35+ kts boat than a 48 kts.

Project 03160 “Raptor”

The Pella Shipyard of St Petersburg, mainly known for their tug boats, last week officially launched the first series produced vessel of their new Project 03160 ‘Raptor’-class (ru. “Раптор”). This boat is rather interesting, if not for anything else, then at least because it bears a striking resemblance to a 30 year old Swedish design…

Project 03160 “Raptor”. Picture from Pella Shipyard.

The internet seems to differ whether the boat is in fact a licensed version of Dockstavarvets Combat Boat 90/Stridsbåt 90, or if it just “happens” to look like one. However, what is certain is that Dockstavarvet sold a number of its Interceptor Craft 16 M, a patrol craft based on the CB 90 concept, to the Russian border guards (FSB)[1]. The Raptor, however, seems to be based on the original CB 90 instead of the IC 16 M, and it is clearly stated that this time the customer is the Russian Navy, with at least four boats slated for the Black Sea Fleet.

The armament is rather interesting, with a single remote weapons station with EO-sights and a single 14,5 mm heavy machine-gun. The “Range of target detection – 3000 m” is a value which naturally doesn’t tell us anything, as there is no mention of what kind of target and environment this corresponds to. The back-up weapons are two pintle-mounted PKP light machine guns, which is a somewhat strange choice. The PKP, or 6P41 “Pecheneg”, is a development of the PKM, and mainly differs from this in having a non-replaceable air-cooled barrel, and an integrated bipod, and as such is marketed as a dedicated squad-support weapon.

Whether the Raptor mounts the baseline version, and actually retains the bipod, or not remains to be seen, but this could be an indication that the Russian marine infantry is about to ditch the PKM completely in a relatively near future (another alternative, naturally, is that the PKP is simply listed by the yard as a marketing trick, but that in service the boats are fitted with the PK-derivative that is closest at hand when sailing). All in all, a quite solid, but not overly heavy weapons fit, which should provide ample opportunity to “intercept and arrest […] small targets”. The inclusion of ballistic protection, at the expense of weight, and thereby speed and agility, adds to the feeling that the Russians expect the boat to operate on the battlefield where small arms fire (both own and incoming) can have an effect on target. This could well be not only close to the shore, but also in riverine conditions.

The role of the boat seems to be accurately described on the home page. Key focus is on transporting an assault force, with a secondary  anti-shipping/anti-surface capability (or as a patrol vessel in peacetime).

Looking at the camo scheme, it does feel more suitable to the inland waterways of south and central Europe than to the coastlines of the Baltic Sea, but this might just be my prejudices about how a “proper” boat pattern should look if it is to fit in in the Gulf of Finland.

Is the boat then a copy of the CB 90. If it is unlicensed, I believe the answer is ‘No’. The general layout certainly seems copied, but it is hardly revolutionary. Pella might have borrowed more than is considered “fair”, but the general characteristics of the CB 90 is conventional enough. To try and reverse engineer the details of the CB 90 would probably not have been worth the hustle. To begin with, Pella would have to send a number of engineers to a boat and measure it up, down to what size the bottom stringers are and how high the masthead light is, as well as document every little detail of the equipment. After this, the engineers would have to create the whole drawing package from scratch, after which they would have to adopt it to Pella’s materials and standards. What is the size of the Swedish chairs? Does Pella’s standard choice fit? What can be used instead? How is the Russian ballistic protection attached, compared to the original?

The other possibility is naturally that Dockstavarvet indeed have licensed the production, but understandably wants to keep a low profile about it. See edit

Simply using a proven general layout, and starting an own design from there, is far faster than “true” reverse engineering. And I think speed is the issue here. Projecting boats from the keel up is a long process, even when it is a relatively small and straightforward one as the Raptor. Going through all the normal stages, with a preliminary round of tenders, choosing a winner, nailing down the details of the design, producing and testing a prototype, building a pre-production run, and then finally going into series production, usually takes at least a few years. Here it seems like the first steps have been skipped, and the project jumped straight into the detailed design phase. The result is a stop-gap vessel, built to expand on current capabilities (and numbers), rather than revolutionize them. This also fits the general trend of rapid expansion of the Russian armed forces.

Edit 22:45 (GMT +2 DST) 25062014:

When the pictures first surfaced last spring, Dockstavarvet’s CEO K-A Sundin strongly denied any involvement, and stated that Pella apparently on their own have gotten their hands on “some material” and created a clone.