Did Egypt Take Possession of a Russian Tarantul?

Egyptian President el-Sisi and Russian President Putin meet in Moscow - May 9, 2015

Ten months after Russian Air Force tankers deployed to Egypt to support Russian strategic bomber flights...

...six months after Russian President Vladimir Putin visited Egypt...

...five months after Egyptian defense minister General Sedki Sobhi visited his Russian counterpart (General Sergey Shoygu) in Moscow...

...three months after Egyptian President Abdel Fattah el-Sisi visited Moscow on one of Russia's holiest of holidays (Victory Day)...

Exercise Bridge of Friendship-2015

...two months after Egypt and Russia held their first joint naval exercise (Bridge of Friendship-2015)...

...and one week after a Russian Navy patrol ship took part in celebrations marking the opening of the new Suez Canal (attended by Russian Prime Minister Dmitriy Medvedev)...

...it appears Egypt may have just acquired that same missile-armed patrol ship from Russia.

According to unofficial reporting, the Russian Baltic Fleet's Tarantul-class patrol ship "R-32" was officially handed over to Egypt in a ceremony held in Alexandria, Egypt, on August 10.

[UPDATE: Egyptian officials have now disclosed that "R-32" was transferred from the Russian Navy to the Egyptian Navy.]

"R-32" in Baltiysk -- May 28, 2015

"R-32" is the little ship that no one wanted:

• laid down at Vympel Shipyard in 1994, launched in 1999, then transferred to the Black Sea for fitting out and sea trials;
• after being mothballed for several years, "R-32" was transferred back to Vympel Shipyard in 2007 for repairs;
• transferred to Caspian Flotilla in October-November 2008, then to Makhachkala in the spring of 2009 to prepare it for transfer to Turkmenistan;
• after Turkmenistan backed out the contract to acquire "R-32", the unit was commissioned into the Russian Navy in June 2010;
• beyond its participation in annual Navy Day parades in 2010-2013, the unit remained inactive;
• transferred to Baltic Fleet in October-November 2013;
• transferred from St. Petersburg to Baltiysk in January 2014;
• several of the ship's onboard components were inspected and/or repaired earlier this year: M-15E.1 main gas turbine, refrigerator units, Afalina emergency communications radio-buoy, and emergency lighting equipment.

Oddly, there has been no official announcement yet by either country regarding this possible transfer.

Russian Combatant Participates in Suez Canal Opening Ceremony

If you were watching coverage of today's opening of the new Suez Canal, you were probably surprised to see that the Russian Navy was quietly represented in the ceremony by the Baltic Fleet's Tarantul-class patrol combatant "R-32" (visible at 1:47:55, 1:49:11, 1:52:09, 1:55:47, and 1:56:11; see screenshots at the bottom of this post). Neither the RF Ministry of Defense nor the Baltic Fleet made any prior announcements that the patrol ship would be visiting Egypt or participating in the celebrations.

So, when did "R-32" arrive in Egypt? Polish amateur radio operator Tomasz Golojuch may have provided the only clue in this July 28 tweet:

While Tomasz provided no other data, the presence of "SB-921" (a Baltic Fleet Sliva-class tug) in Egypt last week suggests the possibility that "SB-921" is supporting "R-32" during its unannounced deployment.

"R-32" spotted in Baltiysk in early July 2015
(credit: Lex Kitaev)

The participation of a Russian combatant in today's was surely arranged to coincide with Russian Prime Minister Dmitriy Medvedev's visit to Egypt and attendance at today's ceremony.

Where will "SB-921" and "R-32" head to next?

"Bryansk" Officer Dies in Submarine's Sail

"Bryansk" surfaces through the ice -- August 21, 2007

One week ago, July 25 - the day before Russian Navy Day, a 45-year-old warrant officer (Vitaliy Shimanskiy) died on board Delta IV-class nuclear-powered ballistic missile submarine "Bryansk". Investigators remain tight-lipped while they continue questioning crew members, as well as relatives and friends of the officer. The only details to emerge so far are that he was found dead in the submarine sail after the submarine surfaced and that he was tied to something inside the sail.

The first clue that something had gone wrong came in the form of an urgent plea via social media for Shimanskiy's contact information during the early afternoon hours on July 25. And then silence... until Komsomolskaya Pravda published the first article about the incident two days after Navy Day. The item quickly spread through social media and was republished by regional and national media outlets.

While there are few other clues about Shimanskiy (he was a member of the submarine's Second Crew), a quick internet search revealed that a Senior Warrant Officer Vitaliy Vitoldovich Shimanskiy had appealed to the Gadzhiyevo Garrison Military Court in February 2014 to force defense officials to pay him money owed following decrees by the Western Military District that had increased his salary. The description of Shimanskiy's job title matches that of a technician working on a nuclear-powered submarine.

Many questioned why Shimanskiy remained in the sail as the submarine was submerging (no one knew he was missing? possible suicide?) and why he was tied to the sail (so his body would be found?). Several current and former servicemen from the submarine's home port of Gadzhiyevo did admit that there was at least one other similar situation, although the submariner(s) in that instance survived.

Warrant Officer Shimanskiy is survived by his wife and daughter. A memorial service was held on July 30; the burial will take place in St. Petersburg.

Pacific Fleet Launches Another SSC-6

SSC-6 Sennight area closure -- July 27-August 1, 2015

According to a spokesman for Russia's Eastern Military District, a Pacific Fleet missile unit recently launched an SSC-6 Sennight (Russian name: 3K60 Bal) anti-ship cruise missile from a position near Cape Povorotnyy. The target was stricken auxiliary vessel located 50 kilometers from shore. The target was reportedly "destroyed", earning the missile unit a score of "outstanding."

The missile launch occurred within an announced area closure:

HYDROPAC 2421/15

SEA OF JAPAN.
RUSSIA.
MISSILES.
DNC 23, DNC 24.
1. HAZARDOUS OPERATIONS 2200Z TO 1000Z
COMMENCING DAILY 27 THRU 30 JUL
IN AREA BOUND BY
41-13-00N 133-36-00E, 42-05-30N 133-04-42E,
42-17-30N 133-03-00E, 42-37-00N 133-01-18E,
42-41-30N 133-03-12E, 42-42-00N 133-10-00E,
42-41-48N 133-10-18E, 42-33-30E 133-34-30E,
42-28-00N 133-49-12E, 41-48-12N 134-43-00E,
41-36-30N 134-26-18E, 41-28-00N 134-12-42E,
41-21-00N 133-56-12E.
2. CANCEL HYDROPAC 2414/15.
3. CANCEL THIS MSG 311100Z JUL 15.//

Authority: NAVAREA XIII 85/15 240902Z JUL 15.

Date: 240945Z Jul 15
Cancel: 31110000 Jul 15

This is at least the second SSC-6 launch in the Pacific Fleet this year; the first occurred on April 28.

All Aboard the Bulava Production Retooling Train!

Between 2013 and 2015, at least a dozen Russian enterprises have announced retooling plans connected with the production and assembly of 3K-30 Bulava [SS-N-32] missile components. The names of known companies and retooling costs are listed below:

Name of Enterprise	Retooling Costs
Central Scientific Research Institute of Automatics and Hydraulics	RUB 14,000,000
Elektron Central Scientific Research Institute	RUB 4,918,000
Geofizika-Kosmos Scientific Production Enterprise	not specified
Iskra Factory	RUB 3,850,000
Lebedev Scientific Research Institute of Synthetic Rubber	RUB 52,680,500
Moscow Institute of Thermal Technologies	RUB 76,897,249
Pulsar State Factory	RUB 6,870,000
Scientific Research Institute of Applied Chemistry	RUB 3,100,000
Scientific Research Institute of Physical Measurements	RUB 197,980
Scientific Research Institute of Semiconductor Devices	RUB 3,646,180
Soyuz Federal Center for Dual-Purpose Technologies	RUB 199,871
Votkinsk Factory	RUB 3,943,971
Zvezda Factory	RUB 30,628,260

The above costs (totaling RUB 200,932,011) cover everything from design documentation for retooling of fabrication facilities to the delivery of  specific machinery required in the production of missile parts.

Follow-Up 1: Towing Service Contracts for "Sovershennyy" Frigate

Since my July 12 blog post, Amur Shipyard has still been unable to secure contractors to tow the Steregushchiy-class frigate "Sovershennyy" in the shipyard's transport dock "Zeya" all the way from the shipyard to its outfitting subsidiary in Bolshoy Kamen. And it now seems impossible that the frigate will begin its transfer on August 5, as previously scheduled.

"Aldar Tsydenzhapov" keel authentication plaque -- July 22, 2015
(credit: Amur Shipyard)

On July 22, a new Steregushchiy-class frigate ("Aldar Tsydenzhapov") was laid down at Amur Shipyard. The very next day, the shipyard's contract bid review committee selected Khabarovsk-based Amur Shipping Company as the winner of the contract covering the Amur Shipyard > Buoy 18 > Amur Shipyard portion of the transfer. On the same day, however, the committee rejected the only two bids that had been submitted for the contract covering the longer Buoy 18 > Bolshoy Kamen > Buoy 18 portion of the transfer. One company, Far East Maritime Freight, may have submitted a bid that exceeded the contract's maximum costs. The bid by the second company, Shore of Good Fortune, apparently did not have tugs that met the minimum tow capacity specified in the contract.


Amur Shipyard's emergence from bankruptcy has had its hiccups. Just this week it was announced that the Khabarovsk Heating Company shut off steam and heat supplies to the shipyard, which owes the company RUB 27.5 million. And the small fire that broke out today could have been worse.

As I stated earlier, if the "Sovershennyy" transfer doesn't begin soon, the transfer of the overhauled Kilo-class submarine "Komsomolsk-na-Amure" (formerly "B-187") from the shipyard to Bolshoy Kamen will be in jeopardy of not happening this year.

Towing Service Contracts for "Sovershennyy" Frigate

Steregushchiy frigate "Sovershennyy" -- May 22, 2015

A year after emerging from bankruptcy, Amur Shipyard finds itself in a bind partly due to a miscalculation of contract costs. And if the contracts aren't signed soon, the delivery of a repaired Kilo-class diesel submarine could be delayed until 2016.

In January 2006, the Russian Ministry of Defense signed a contract (253/05/2/K/0038-06) with Amur Shipyard for the construction of Steregushchiy-class frigate "Sovershennyy". The ship was laid down on June 30 the same year. The two parties signed a supplementary agreement (704/27/2/ONK/DN6/0105-10) in February 2010, four years after the original contract was signed. In November 2011, a second supplementary agreement (Z/1/1/0635/D10-11-DGOZ) was signed to continue the contract after the shipyard was declared bankrupt. In February 2014, following a visit by defense minister Sergey Shoygu, a new contract (Z/1/1/0047/D17-14-DGOZ) was signed to establish new costs for the construction of both "Sovershennyy" and "Gromkiy" (a second Steregushchiy frigate laid down in February 2012). The new contract was signed four months before Amur Shipyard officially emerged from bankruptcy. On May 22, 2015 - nine years after being laid down, "Sovershennyy" was finally rolled out.

On May 26, Amur Shipyard approved a purchase package (RUB 81,900,000) for towing "Sovershennyy" in the shipyard's transport dock "Zeya" from Amur Shipyard to its outfitting subsidiary in Bolshoy Kamen and then back to Amur Shipyard. The towing operation was scheduled to begin no later than August 19 and involve two 600hp (or greater) tugs and one 1,800hp (or greater) tug. A month later, however, the package was withdrawn in order to modify the technical specifications of the work package.

Last week, Amur Shipyard approved two new purchase packages for the operation. The first package (RUB 49,600,000) only covers the tow route from the shipyard to Buoy 18 on the Amur Estuary and (after returning from Bolshoy Kamen) back to the shipyard. The second package (RUB 88,560,000) covers the route from Buoy 18 to Bolshoy Kamen and then back to Buoy 18. The tug requirements and start dates were also modified for both routes. Comparisons of the 2014 and 2015 contract packages are shown below.

Amount	Route	Start	Towing Requirements
RUB 25,000,000	Buoy 18 >  Amur Shipyard	July 5, 2014	1 tug (1,800hp) +         2 tugs (600hp)
RUB 81,900,000	Amur Shipyard > Bolshoy Kamen >  Amur Shipyard	August 19, 2015	1 tug (1,800hp) +         2 tugs (600hp)
RUB 49,600,000	Amur Shipyard > Buoy 18 > Amur Shipyard	August 5, 2015	2 tugs (1,800hp)
RUB 88,560,000	Buoy 18 > Bolshoy Kamen > Buoy 18	August 10, 2015	1 tug (7,800hp) +         1 tug (3,000hp)

Comparing the cost differences between the May package and the July packages indicates the original cost calculations were off by RUB 56,260,000. Amur Shipyard signed a similar contract (RUB 25,000,000) in 2014 for towing "Zeya" one way between Buoy 18 and the shipyard. If you double the amount, it matches nicely with the RUB 49,600,000 in the July 2015 purchase package that includes two-way towing services.

Miscalculations aside, it's amazing that Amur Shipyard has not yet signed towing service contracts for this transfer. The new contracts specify that the towing operation should commence no later than August 5 and that "Zeya" should be returned to the shipyard no later than September 1. 
The dates are important because Amur Shipyard also plans to roll-out Kilo-class diesel submarine "B-187" and transfer it to Bolshoy Kamen this year. The transfer has to be completed before Amur River becomes unnavigable due to the onset of ice conditions in late October. Any delay in transferring "Sovershennyy" could jeopardize the transfer of "B-187" this year.