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.

Baltic Fleet Tries to Forget the "Steregushchiy" Fire

"Steregushchiy" undergoing routine dock repairs, early 2015
credit: RF Baltic Fleet

What was supposed to be a somewhat routine exercise in mid-April turned into a real emergency for one of the Baltic Fleet's newest combatants.

Prior to the exercise, Steregushchiy-class frigate "Steregushchiy" had completed a routine 59-day out-of-water repair period at the Yantar Baltic Shipyard in Kaliningrad before returning to Baltiysk Naval Base on March 21. According to the March 21 edition of the fleet's newspaper, Strazh Baltiki (released the same day as the frigate's return to Baltiysk), shipyard work included repairs to hull fittings, propellers, the main engine, and diesel engines, as well as a fresh coat of paint. The ship's commanding officer, Captain 3rd Rank Aleskey Suslov, told the newspaper that "Steregushchiy" was to complete all combat certifications by the end of April.

On April 17, 2015, the Western Military District press service issued a press statement regarding a recently held anti-air and antisubmarine warfare exercise involving all four of the Baltic Fleet's Steregushchiy-class frigates: "Boykiy", Soobrazitelnyy", "Stoykiy", and "Steregushchiy". Also included in the list of participants were two firefighting vessels, an AN-26 Curl fixed-wing transport, and a KA-27 Helix helicopter. The inclusion of firefighting vessels in live-fire exercises seemed odd until you reached the end of the article in which the press release stated that the ships also practiced "rendering assistance to one of the ships, which was simulating a casualty."

It should be no surprise that even before the press release was broadcast by the major Russian news outlets, hints of a true emergency on board "Steregushchiy" began to leak out. According to one source, "Steregushchiy" was supposed to be underway for four days, but the frigate was forced to return within six hours of getting underway due to a fire. Two weeks later, a different source indicated the fire may have started after fuel somehow entered the frigate's exhaust funnel. That source also indicated there were some injuries, although the exact nature of the injuries and the number of injured personnel were not provided.

It is not known whether the AN-26 and KA-27 were part of the exercise, part of the response to the fire on "Steregushchiy", or both.

Thus, the Western Military District's inclusion of firefighting vessels and the rescue drill in its press release appears to be an attempt to cover up a response to an actual at-sea emergency. With NATO's Baltic partners keeping a vigilant eye on Russian military activity in the region, the Russian military press officers have to quickly devise explanations for any unusual military activity, such as an accident. Sometimes, however, their explanations fail.

XLT+: Could Engine Fire on "Admiral Gorshkov" Impact "Admiral Kasatonov" Delivery?

Gorshkov frigate "Admiral Flota Sovetskogo Soyuza Gorshkov" at Northern Shipyard - January 23, 2015
(credit: Curious)

                                                   [translation of FlotProm news article]

ENGINE ON "ADMIRAL GORSHKOV" FRIGATE DESTROYED BY FIRE DUE TO CONTROL SYSTEM FAILURE
January 28, 2015
http://flotprom.ru/2015/181758/

The Central Naval Portal (CNP) has learned that an accident involving an engine on the new frigate "Admiral Flota Gorshkov", built at Northern Shipyard for the Russian Navy, was caused by the failure of a control system.

A CNP journalist learned from the Saturn Scientific Production Association, which is performing a survey and subsequent repairs of the engine, that the primary theory behind the failure was abnormal performance of the control system which led to the engine being flooded with fuel, after which it caught fire.

The fact that the engine on the Russian Project 22350 frigate "Admiral Gorshkov" required repairs was reported on December 29, 2014. On December 17, Northern Shipyard announced it was accepting bids for a 24-million-ruble contract for disassembling and surveying the ship's gas turbine engine.

According to a Saturn official, an assessment of the loss and inspection of the damaged engine pieces will last until March 2015 as company workers are not familiar with the engine's design. It is too early to announce when repairs will be completed and when fully operational engine pieces will be available.

The accident theory has been confirmed by another CNP source within the shipbuilding industry who has information about the accident. "The fuel pump did not shut off in time. There was a surge, and blades in the engine were damaged by the fire. The turbine has been removed and shipped to Rybinsk (location of Saturn Scientific Production Association - ed.) for repairs," the source said, noting that this occurred in September 2014.

Additionally, similar information has been reported by yet another knowledgeable shipbuilding industry source. He said that the control system failure could have been the result of a design error. "The turbine needs to undergo capital repairs; the blades were damaged by the fire. The problem was with the control system's performance. It was, most likely, a design error," he explained.

This opinion is shared by a Northern Shipyard employee. "The control system malfunctioned even though it functioned normally prior to this," the company specialist noted.

The design of the frigate engine's control system is Avrora Scientific Production Association Concern. Avrora informed CNP that the customer has not contacted the company regarding any complaints resulting from the mishap and pointed out that talking about the causes of the mishap can only be done after an official conclusion is made by experts.

Northern Shipyard's press office claims that there have been and currently are no problems with the ship or its equipment. "Our position is very simple. 'Gorshkov' completed the first phase of testing. And that's our position," stated the press office, adding that during the sea trials, the ship demonstrated specified numbers in accordance with technical specifications.

The fire-damaged M90FR gas turbine engine was developed and built at Saturn Scientific Production Association in cooperation with the Ukrainian company Zorya-MashProyekt. The Ukrainian company's press office told CNP that it had not heard about any problem with the Russian ship's engine and that no one had consulted the company regarding repairs.

Afterwards, CNP learned that the frigate's damaged engine was replaced with a duplicate engine from another ship of the same class - "Admiral Flota Kasatonov", which is also being built at Northern Shipyard. This was done in order to not delay factory sea trials of "Gorshkov".

                                                                      - - - - - - - - - -

Gorshkov frigate "Admiral Flota Kasatonov" at Northern Shipyard - January 23, 2015
(credit: Curious)

• If the September 2014 timeframe is correct, then the incident occurred during pierside testing - before factory sea trials even began. "Admiral Flota Sovetskogo Soyuza Gorshkov" completed 30 days of factory sea trials between November 18 and December 26 last year. It has not been underway since.

• "Admiral Flota Kasatonov" was launched at Northern Shipyard on December 12 (without a gas turbine engine, if you believe the above report).

XLT+: Project 20386 Corvette and UAVs

Gorizont Air S-100 unmanned aerial vehicle on display at Interpolitekh-2013 - October 2013
(Image courtesy of dokwar.ru)

                                                     [Translation of TASS news article]

NEW GENERATION CORVETTE WITH MODULAR WEAPONRY AND SHIPBORNE UAVS TO BE LAID DOWN IN 2015
Source: TASS
Date: October 15, 2014
http://itar-tass.com/armiya-i-opk/1508847

The keel-laying of a Project 20386 new generation corvette, which will bring together a modular principle for weaponry and the capability of basing unmanned aerial vehicles, is planned for next year year. Igor Zakharov, deputy general designer of Almaz Central Naval Design Bureau, told our TASS reporter this during an interview.

A number of media outlets, citing the Almaz design bureau and United Shipbuilding Corporation, earlier reported about the impending construction of corvettes under the improved Project 20386, which has evolved from the Project 20380 and Project 20385.

"The technical design phase is currently underway; therefore, I cannot describe the new corvette's characteristics. It will be a multipurpose ship of a principally new project. The keel-laying is planned for 2015," Zakharov said.

According to him, most likely the ship will be laid down at Severnaya Verf in St. Petersburg, but the decision rests with the customer.

Zakharov noted that the future corvette will have permanent, basic weaponry and removable combat modules, which will expand the number of missions the ship can perform. Designers are also interested in the introduction of an unmanned aerial vehicle on the corvette, "but everything related to this issue is not moving forward as fast as we would like," the Almaz deputy general designer admitted. He explained that the problem is linked to operating unmanned aerial vehicles in the common airspace of Russia and relevant regulatory issues with air safety.

The Gorizont helicopter-type unmanned aerial vehicle is being looked at as a possible option for equipping the corvette. "This is the only Russian unmanned vehicle that we know of that can land on a ship," Zakharov explained.

-------------------

Beyond the translation...

Indeed, Almaz Central Naval Design Bureau is still performing research and development into the Project 20386. On September 30 of this year, the design bureau announced that it had signed a contract with the Krylov State Scientific Center for "Component of Scientific Research Work: Determination of the Seagoing and Maneuvering Qualities of the Project 20386 Ship (Project 82)." The contract, which is based on Technical Specification 20386.360030.010TZ, is effective through November 2015. The work is broken down into two stages for which Almaz will pay RUB 6,097,000 (Stage 1) and RUB 3,450,000 (Stage 2).

If realized, Project 20386 would represent the third variant in the Steregushchiy line of frigates. Four units have been built, and two more are still being built (Amur Shipyard) as Project 20380 (Steregushchiy I). Two units of the Project 20385 (Steregushchiy II) have been laid down, with at least two more reported to have been contracted for construction at Amur Shipyard.