Parade Interrupted

Diesel submarine Kolpino moored on Neva River (May 3, 2017)

[credit: Sergey Kharitonov]

What should have been a traditional event marking Victory Day in St. Petersburg has ended in a mystery. Every ship that had already arrived in St. Petersburg has suddenly left, and those that were on their way have reversed course.

Patrol combatant Serpukhov underway near Kronshtadt (May 5, 2017)

[credit: Aleksey Akentyev]

In previous years, residents of St. Petersburg could walk along the Neva River on Victory Day and Navy Day and see several ships and even a submarine anchored on the river or moored at quays or floating piers on both sides of the river. And that's how this year's Victory Day preparations began on May 2 with the arrival of a new diesel submarine (Kolpino) and two light frigates (Urengoy and Zelenodolsk). On May 3, they were joined by two mine warfare ships (Aleksandr Obukhov and RT-57). On May 5, three Baltiysk-based warships (Liven, Morshansk, and Serpukhov) arrived in the St. Petersburg area and were expected to take their places on the Neva River over the next few hours.

But that's when the mystery began. Minutes after arriving near Northern Shipyard, all three warships reversed course and headed to Kronshtadt. The fleet commander's launch (Burevestnik), which was moored at a Neva River quay, also left port en route to Kronshtadt.

Today, all the remaining naval ships departed St. Petersburg heading to Kronshtadt. And Liven, Morshansk, and Serpukhov, which never got the chance to moor on the Neva River, departed Kronshtadt heading back to sea, presumably to Baltiysk.

As defense officials have provided no explanation as to the sudden departure of all scheduled Victory Day participants, everyone is left scratching their heads.

Weather forecast for St. Petersburg, May 7-9

One popular theory is that the weather in the St. Petersburg will be extremely poor over the next few days. Yes, it will be rainy or overcast most of the time. And the winds will kick up to 7 meters per second (15.7 miles per hour or 13.6 knots) on May 8. But is that too high for ships to be moored on the Neva River?

Another theory is that the Baltic Fleet may be subjected to a surprise inspection in the next few days, and the ships are returning to their respective bases to prepare.

Of course, it's not a surprise if you already know about it.

Expansion of RF Navy Logistics Facility in Tartus

Tartus, Syria (October 25, 2014)
(credit: Google Earth)

On October 10 of last year, RF Deputy Minister of Defense Nikolay Pankov stated that documents had been prepared for establishing a "naval base, on a permanent basis, in Tartus." On December 23, RF President Putin signed Directive 424-rp, ordering the Ministry of Defense to work with the Ministry of Foreign Affairs in coordinating and signing an agreement with Syria on expanding the existing RF naval logistics support facility in Tartus. That agreement, which was signed in Damascus on January 18, allows Russia to expand the facility and remain there until at least 2066. But missing from Putin's directive and the final agreement is the term "naval base."

"The Agreement between the Russian Federation and the Syrian Arab Republic on Expansion of the Territory of the Russian Federation Navy Logistics Support Facility in the Port of Tartus and Entry of Russian Federation Military Ships into the Territorial Sea, Internal Waters and Ports of the Syrian Arab Republic" has several interesting provisions:

• Article 2 states that Syria concurs with Russia with regards to the "development and modernization of [the facility's] infrastructure for conducting repairs, resupply, and crew rest."
• Article 5 permits "the simultaneous presence of 11 ships, including ships with nuclear power plants, at the facility."
• Article 6 covers the port entry/departure notification process. At least 12 hours notice is required for ships to enter Tartus; if operationally necessary, 6 hours notice is authorized. For departures, 3 hours notice (1 hour if operationally necessary) is required.
• Article 7 specifies some of the work RF can undertake (using its own funds) at the facility: capital repairs; installation of floating piers; dredging work; the catch-all "placement of necessary equipment to support the operations of RF military ships within the territory and water space of the logistics support facility"; use of required communications resources; conducting underwater work and permitting divers to dive from RF military ships.
• Article 16 states that contents of annexes to this agreement may not be shared with a third party without prior written concurrence. Additionally, both sides "will refrain from official publication of annexes to this Agreement."
• Article 17 indicates that if Syria requests, RF may (a) provide "maritime surface and underwater, airborne, and weather status reports for the Mediterranean Sea"; (b) "provide hydrographic support in the territorial sea, internal waters and ports of the Syrian Arab Republic"; (c) "provide support in organizing and conducting anti-swimmer support in the water space of the port of Tartus"; (d) "provide support in organizing and conducting search and rescue support in the territorial sea and internal waters of the Syrian Arab Republic"; (e) "provide support in organizing and conducting air defense of the port of Tartus"; (f) send RF representatives to provide support in restoring the technical readiness of Syria's military ships.
• Article 25 specifies that this agreement is valid for 49 years and will automatically extend for 25-year periods unless one of the parties - within one year of the agreement's expiration - informs the other party of its intention to withdraw from the agreement.

As any annexes to the agreement will remain confidential (Article 16), it is difficult to fully assess the extent to which the facility will be expanded. For example, the specifics of infrastructure upgrades supporting ship repairs (Article 2) are not stated, but could include a number of options, such as the basing of a floating dry dock at the facility. Such a move would require additional waterfront space and/or upgrades to the existing territory.

But why there is no mention of a naval base in the agreement?

According to Nezavisimaya Gazeta reporter Vladimir Mukhin, Iran has expressed concerns about the increased role of Russia in the Middle East, Russia and Turkey teaming up to settle the Syrian conflict, and Russia's intent to work with the U.S. and other countries as part of a coalition. Reading between the lines, Iran's concerns could have led to a change in the wording of the agreement - from the establishment of a naval base to a simpler, friendlier expansion of the existing logistics support facility.

XLT: Rubin Designing Submarine Imitator for RF Navy

Surrogat submarine imitator
[credit: Rubin Central Design Bureau]

                                                      [Translation of TASS news article]

ROBOT CAPABLE OF IMMITATING ANY SUB BEING CREATED FOR RF NAVY
TASS
December 6, 2016

According to designer, vehicle will be notable for is simplicity of use and low maintenance and upgrade costs

MOSCOW, December 6. /TASS/. Specialists at Rubin Central Design Bureau have developed a draft concept of the Surrogat robotic complex to be used in RF Navy training. According to the design bureau, talks with the Navy about this project are in progress.

"Surrogat is equipped with a lithium-ion battery. The submarine imitator is capable of supporting training for up to 15-16 hours and will simulate a foreign submarine's maneuvers the entire time, to include at high speeds. Comparatively large dimensions (approximate 17-meter length) and an ability to employ various towed antennas will allow the vehicle to realistically simulate an enemy submarine's physical fields - acoustic and magnetic," says the Rubin Central Design Bureau.

The imitator vehicle's modular design allows for its functionality to be altered: Surrogat can imitate both a non-nuclear and nuclear submarine, as well as conduct mapping and survey missions.

Surrogat submarine imitator
[credit: Rubin Central Design Bureau]

"Today combat submarines must be used in exercises or testing, which takes them away from executing their primary missions. Using an unmanned imitator will help avoid this and lower the cost of training. Additionally, an unmanned submarine reduces risks while preserving a level of realism. This vehicle will be notable for its simplicity of use and low maintenance and upgrade costs. We are now consulting with RF Navy representatives to ensure the imitator fully satisfies the Navy's requirements," Rubin Central Design Bureau general director Igor Vilnit explained.

Rubin is not ruling out interest in Surrogat by foreign customers.

The Surrogat autonomous unmanned submarine displaces about 40 tons, has a range of about 600 miles at a speed of 5 knots, a maximum speed of more than 24 knots, and a maximum diving depth of 600 meters.

"Admiral Kuznetsov" & Friends to Deploy Soon

SU-33 Flanker and MIG-29K Fulcrum on board "Admiral Kuznetsov" -- August 2016

It now appears certain that the Russian Navy's sole aircraft carrier, "Admiral Kuznetsov", along with the nuclear-powered cruiser "Petr Velikiy" and destroyer "Severomorsk", are preparing to deploy within the next week.

"Petr Velikiy" -- May 2016

According to social media, "Petr Velikiy" was scheduled to transfer to a mooring position near Severomorsk today and depart from there on October 15 for a six- to eight-month deployment.

"Admiral Kuznetsov" performing final preparations -- October 8, 2016

"Admiral Kuznetsov" will arrive at a similar mooring position near Severomorsk on October 11. Interfax, citing an anonymous source, earlier reported the aircraft carrier would depart on October 15-20.

"Severomorsk" at 35th Shipyard -- July 8, 2016

"Severomorsk" is also scheduled to depart on October 15, based on social media.

Auxiliary support for the deployment will likely include salvage tug "Nikolay Chiker" and oiler "Sergey Osipov". "Nikolay Chiker" is currently moored near Severomorsk Naval Base. "Sergey Osipov" was noted underway near Severomorsk Naval Base on October 8.

KA-52 Hokum on board "Admiral Kuznetsov" -- August 29, 2016

The aircraft carrier is expected to deploy with a mixed inventory of KA-27/KA-29 Helix and KA-52 Hokum helicopters, as well as SU-33 Flanker and MIG-29K Fulcrum fighters.

Repairs of "Admiral Kuznetsov" began last spring, and it appeared they would continue until the end of this year; however, the repairs were completed earlier than scheduled. Following a number of underway combat drills and carrier flight operations, "Admiral Kuznetsov" returned to Rosta for final preparations before it transfers to its Severomorsk mooring position this week.

"Admiral Kuznetsov" & Friends to Deploy Soon

SU-33 Flanker and MIG-29K Fulcrum on board "Admiral Kuznetsov" -- August 2016

It now appears certain that the Russian Navy's sole aircraft carrier, "Admiral Kuznetsov", along with the nuclear-powered cruiser "Petr Velikiy" and destroyer "Severomorsk", are preparing to deploy within the next week.

"Petr Velikiy" -- May 2016

According to social media, "Petr Velikiy" will transfer to a mooring position near Severomorsk on October 9 and depart from there on October 15 for a six- to eight-month deployment.

"Admiral Kuznetsov" performing final preparations -- October 8, 2016

"Admiral Kuznetsov" will arrive at a similar mooring position near Severomorsk on October 11. Interfax, citing an anonymous source, earlier reported the aircraft carrier would depart on October 15-20.

"Severomorsk" at 35th Shipyard -- July 8, 2016

"Severomorsk" is also scheduled to depart on October 15, based on social media.

Auxiliary support for the deployment will likely include salvage tug "Nikolay Chiker" and oiler "Sergey Osipov". "Nikolay Chiker" is currently moored near Severomorsk Naval Base. "Sergey Osipov" was noted underway near Severomorsk Naval Base on October 8.

KA-52 Hokum on board "Admiral Kuznetsov" -- August 29, 2016

The aircraft carrier is expected to deploy with a mixed inventory of KA-27/KA-29 Helix and KA-52 Hokum helicopters, as well as SU-33 Flanker and MIG-29K Fulcrum fighters.

Repairs of "Admiral Kuznetsov" began last spring, and it appeared they would continue until the end of this year; however, the repairs were completed earlier than scheduled. Following a number of underway combat drills and carrier flight operations, "Admiral Kuznetsov" returned to Rosta for final preparations before it transfers to its Severomorsk mooring position this week.

Are Kalibr Ships Transferring to the Baltic Fleet?

"Zelenyy Dol" -- February 14, 2016

(credit: Yörük Işık)

This morning, shipspotters Alper Böler, Devrim Yaylali, and Yörük Işık photographed Russian Navy patrol combatants "Serpukhov" and "Zelenyy Dol" as they headed south through the Turkish Straits. The two ships earlier returned to Sevastopol on September 17 following a 38-day deployment to the eastern Mediterranean Sea. During that deployment, both ships launched 3M-14 Kalibr land-attack cruise missiles into Syria.

After a three-week break, "Serpukhov" and "Zelenyy Dol" are headed back to the Mediterranean Sea - possibly with a final destination in the Baltic Sea.

(credit: Main Intelligence Directorate - Ukrainian Ministry of Defense)

On September 16, the Main Intelligence Directorate of Ukraine's Ministry of Defense reported on its website that the two patrol combatants were scheduled to begin a transfer to the Baltic Fleet on September 24 using Russia's inland waterway system. Such a transfer would have required sufficient lead time to remove a portion of the ships' superstructures. With such a tight timeline (September 17-24), this option seemed unlikely. And the ships remained idle until they departed port yesterday.

"Serpukhov" and "Zelenyy Dol" could temporarily increase the Russian Navy's presence in the eastern Mediterranean; however, the Malta Ship & Actions Photos website claims the two ships will call in Valletta, Malta, in mid-October. According to the website, the ships will be supported by salvage tug "SB-36", which has been deployed to the Mediterranean Sea since last month. It should be noted that Malta Ship & Actions Photos reported last month that "Serpukhov" and "Zelenyy Dol" would visit Valletta on September 29-October 2, which did not occur. As the website has a good record of reporting on future Valletta port calls, the discrepancy in the Russian ships' port call dates is likely related to a scheduling change.

Having traveled that far west with a tug, it seems even more likely that "Serpukhov" and "Zelenyy Dol" will continue to the Baltic Sea. But the small patrol combatants will require several port calls (Ceuta? Lisbon?) and/or logistical support by a naval tanker.

The Baltic Fleet would benefit greatly from the introduction of Kalibr-armed warships. While Kalibr-capable ships and submarines are tested in the Baltic Sea before being transferred to the Black Sea Fleet, the Baltic Fleet currently has no Kalibr-capable ships or submarines in its own permanent inventory.

Klavesin-2R-PM to be Tested in Black Sea

Klavesin-2R-PM autonomous unmanned undersea vehicle
[courtesy: TASS]

Rubin Central Design Bureau of Marine Technology recently secured an insurance policy with SOGAZ (Gas Industry Insurance Company) to cover the loss of or damage to two Klavesin-2R-PM autonomous unmanned undersea vehicles, each worth RUB 300 million.

The first attempt to secure insurance began on February 10. Rubin announced it was accepting bids to insure the two vehicles during testing in St. Petersburg, in Crimea, and in the Black Sea, as well as for transportation between the locations. The insurance premiums (RUB 48 million) were unequally divided between the two vehicles: RUB 27 million for one (in 2016), RUB 21 million for the other (in 2017). Each vehicle being covered includes a load-bearing frame, propulsion system, containers with equipment and batteries, and other related components. The technical specifications provided for the Klavesin-2R-PM were:

• length: approximately 6,500 mm
• diameter: approximately 1,000 mm
• weight: approximately 3,700 kg
• maximum range: approximately 50 km
• diving depth: approximately 2,000 m (due to the depth in the Black Sea test range, the diving depth will be 500 m)

Despite the fact that two companies bid on the contract (Ingosstrakh and SOGAZ), the competitive process was unexplainably stopped on March 4.

A second attempt began March 23. In the version of the documents published for this round, the vehicle's technical specifications were moved from the main contract document to an annex, which was not published. On April 6, the contract selection committee announced that the competitive process was nullified as only a single company (SOGAZ) had bid on the contract.

The third and final attempt began on April 6 with no changes made to the contract documentation. On April 21, after reviewing bids from two companies (MAKS and SOGAZ), the contract selection committee chose SOGAZ; the contract was signed on May 4. A few weeks later, SOGAZ released a statement on its website confirming that it had won the contract.