Saturday, July 11, 2015

Tracking "Ametist"

Tracking "Ametist" along the inland waterway system, May-June 2015
In 2012, Almaz Shipyard (St Petersburg) was awarded a contract for the construction of the shipyard's fifth Rubin-class (Project 22460) patrol ship "Ametist". The unit rolled out of the shipyard in March 2014, and began sea trials in August. The ship was officially handed over the Russian Coast Guard in October and transferred to Kronshtadt, where it remained until May of this year.

"Ametist" could not transfer to the Black Sea in late 2014 as the inland waterway system would close during its transit, forcing it to winter somewhere along its journey. This is exactly what happened to "Izumrud" the year before: it departed St. Petersburg on October 4, 2014, arrived in Volgograd on December 1, and eventually transferred to the Caspian Sea to winter over. It remained there until resuming its transit on April 7 and arriving in Balaklava on May 1, making this a 210-day transfer.

So, how long does it take to transfer from St. Petersburg to Balaklava during the summer? The below chart and Google Earth plots depict the ship's transit along the Neva, Volga, and Don Rivers during its May 12-June 30 (50-day) transit.

May 12 Day 1 St. Petersburg
May 13 Day 2 Svir River Entrance Buoy
May 14 Day 3 Upper Svir River Lock
May 15 Day 4 Vytegra Lock
May 16 Day 5 Kovzha River Estuary
May 21 Day 10 Yaroslavl
May 22 Day 11 Gorodets
May 23 Day 12 Nizhniy Novgorod
May 25 Day 14 Novocheboksarsk
May 26 Day 15 Kazan
May 28 Day 17 Tolyatti
May 30 Day 19 Balakovo
June 7 Day 27 Saratov
June 11 Day 31 Volga-Don Canal Lock 1
June 12 Day 32 Volga-Don Canal Lock 11
June 14 Day 34 Nikolayevskaya Hydroelectric Plant
June 16 Day 36 Koluzayevo
June 30 Day 50 Balaklava

"Ametist" arriving in Balaklava - June 30, 2015

Thursday, July 2, 2015

Cruise Missiles Launched in Sea of Okhotsk

Area closures (red), flight ban (yellow), and flight route restrictions (green) for anti-ship cruise missile launches

According to the Russian Ministry of Defense, two naval anti-ship cruise missiles were launched from the Sea of Okhotsk on July 1. At least one of them overflew the Kamchatka Peninsula to strike a target east of the peninsula.

Area closures, a flight ban, and flight route restrictions were declared over the affected areas for June 29 through July 2:

PRIP PETROPAVLOVSK 78/15 CHART 61025
SEA OF OKHOTSK
1. MISSILE FIRINGS 29 JUNE THRU 01 JULY 2300 DURATION 6 HOURS
AREA 58-39-12N 155-39-06E 59-12-12N 156-10-00E 58-40-00N 159-25-12E
SHORE 57-52-48S 157-34-48E
2. CANCEL THIS MESSAGE 020600 JULY

PRIP PETROPAVLOVSK 79/15 CHART 60103
BERING SEA
1. MISSILE FIRINGS 29 JUNE THRU 01 JULY 2300 DURATION 6 HOURS
AREA 54-42-12N 165-34-12E 56-06-18N 162-08-00E SHORE
58-13-30N 162-04-12E 57-16-18N 167-38-12E 55-38-00N 167-45-48E
2. CANCEL THIS MESSAGE 020600 JULY

P4325/15 NOTAMN
Q) UHPP/QRTCA/IV/BO/W/000/330/5620N16440E115
A) UHPP B) 1506292300 C) 1507020500
D) DAILY 2300-0100 0300-0500
E) TEMPO DANGER AREA ACT WI COORDINATES:
 575700N 1634036E-571618N 1673812E-553800N 1674548E-
 544212N 1653412E-554412N 1630430E-575700N 1634036E.
F) SFC  G) FL330

P4324/15 NOTAMN
Q) UUXX/QARLC/IV/NBO/E/000/330/5746N16321E320
A) UHPP UHMM B) 1506292300 C) 1507020500
D) DAILY 2300-0100 0300-0500
E) ATS RTE SEGMENTS CLSD:
 B237 DIVIN - AMETO,
 B240 TILICHIKI NDB (TK) - OKLED,
 B241 BERUD - GITRU,
 B242 DIPNA - NIKOLSKOYE NDB (NK),
 B244 APTIK - RITAR,
 B327 BAMOK - IRKAN,
 B484 DIVIN - MUROL,
 B804 BALUB - OSMOR,
 B962 RAMKA - OTLIM,
 G583 NILAR - IRKAN.
F) SFC  G) FL330

According to the first report, an SS-N-19 Shipwreck anti-ship cruise missile was fired by a simulated enemy nuclear-powered submarine [the report did not indicate which Oscar II-class nuclear-powered submarine - "Omsk", "Tomsk", or "Tver" - played this role]. MIG-31 Foxhound fighters were scrambled "at supersonic speeds" to the "lower levels of the stratosphere" to search for, intercept, and shoot down the missile. The fighters were aided by an A-50 Mainstay airborne early warning and control aircraft.

The blue circle indicates a 300nm range for an SS-N-12 launched at the far western edge of the Sea of Okhotsk area closure

The MOD's second report indicated that Slava-class cruiser "Varyag" launched an SS-N-12 Sandbox anti-ship cruise missile "at maximum range" against a sea target. According to a post-launch damage assessment, the sea target was "successfully damaged." Given that the maximum operational range of the SS-N-12 is 300 nautical miles, the only way this would be true is if the missile flew over the Kamchatka Peninsula. Considering the layout and geometry of the area closures and flight ban, the missile would have had to travel southeasterly from the Sea of Okhotsk.

The events, which are most likely part of the ongoing "exercise" that began in early June, occurred on the eve of the Pacific Fleet Submarine Forces' 77th anniversary, which was celebrated today.

Wednesday, June 24, 2015

Cam Ranh Bay Submarine Base

Location of Cam Ranh Bay Submarine Base
Below are some photos taken this year of the Cam Ranh Bay Submarine Base, which was established to support the six Kilo submarines built by Russia between 2010 and 2016.

View from HQ building towards barracks, club, and sports center
View from HQ building towards administrative buildings and barracks
View from HQ building towards club and training center
HQ building
Submarine piers
Floating dry dock
Parade grounds
Barracks

Below are snapshots of Google Earth showing the timeline of construction of the new submarine base.

August 24, 2009
June 27, 2011
July 13, 2012
January 10, 2013
March 25, 2013
March 2, 2014

Friday, June 19, 2015

Update: Pacific Fleet Preparing for Large-Scale Exercise

Kilo submarine spotted near La Perouse Strait -- June 18
(credit: Japanese Ministry of Defense)

It took a little time, but the Eastern Military District has finally announced what was already evident: the Pacific Fleet is carrying out a large exercise. According to today's announcements:

The readiness of fleet forces (troops) to carry out actions as part of tactical groups will be inspected during the exercise, which will be under the control of combined unit commanders in the Sea of Japan, the southern part of the Sea of Okhotsk, and in Avacha Bay.

During the phased inspection, levels of combat readiness of execution of elements of combat training will be assessed for ship, submarine, naval aviation and coastal troop commands on the Kamchatka Peninsula and in the Primorye Kray. Nearly 50 ships and auxiliary vessels, 40 aircraft and helicopters, and up to 14,000 servicemen and civilian specialists will be part of the inspection.

Additionally, Kamchatka-based SSC-1 Sepal coastal defense cruise missile units have been put on alert and deployed to launch points as part of the exercise.

Not much in terms of naval ship participation has changed since this unfolding exercise was first discussed on Monday. According to social media, Sovremennyy destroyer "Bystryy" and Udaloy I destroyers "Admiral Vinogradov" and "Marshal Shaposhnikov" departed Vladivostok earlier this week after loading weapons at nearby Fokino. And Kilo submarine activity continues to be observed near the La Perouse Strait.

While the official announcements so far only point to a naval exercise, there have been some other notable training events in the Eastern Military District this week that may suggest the naval training activities could morph into a larger military district event.

  • During one training event, 300 district-level peacekeeping troops were ordered to provide security at an unspecified Primorye Kray airfield as humanitarian aid was being flown in and as refugees were being flown out of an area that had experienced some type of emergency. Nearly 300 soldiers and naval infantrymen were activated for this event.
  • On June 18, Airborne Troops, along with MI-8 Hip and MI-24 Hind helicopters, SU-25 Frogfoot close air support fighters, and IL-76 Candid transport aircraft, held a command-staff exercise at the Sosonovyy Bor training range near Ulan-Ude. One of the BMD-2 vehicles dropped during the training fell to the ground after its parachute failed to deploy. The accident may have led to a forest fire which has spread to nearly 730 hectares, although local officials are still investigating.
  • Nearly 2,000 district troops and 600 pieces of heavy equipment are deploying to the Sergeyevskiy training grounds in the Primorye area for live-fire drills.

Monday, June 15, 2015

Pacific Fleet Preparing for Large-Scale Exercise

Grisha frigate "Koreyets" conducts eastbound transit of La Perouse Strait - June 1, 2015
(credit: Japanese Ministry of Defense)
It appears that Vladivostok-based naval units are heading towards Sakhalin Island, the Kuril Islands, and the Kamchatka Peninsula for what has become an annual event: preparing for the next Eastern Military District-level exercise.

It's hard to hide their movements when they transit the La Perouse Strait, which runs between Russia (Sakhalin Island) and Japan (Hokkaido). Below are the dates and units that have conducted an eastbound transit of the La Perouse Strait so far:

June 1 Grisha frigates "Koreyets" and "Metel"
June 5 unidentified Kilo submarine
June 7 Tarantul III patrol ships R-19, R-29, and R-298
June 9 unidentified Kilo submarine
June 10 unidentified Kilo submarine

Unidentified Kilo submarine conducts eastbound transit of La Perouse Strait - June 10, 2015
(credit: Japanese Ministry of Defense)
Based on social media clues, the following ships are also heading out on voyages lasting anywhere from one to two months, thus making them prime candidates for whatever events are about to occur east of the La Perouse Strait:

  • Alligator landing ship "Nikolay Vilkov"
  • Grisha frigate "Sovetskaya Gavan"
  • Slava cruiser "Varyag"
  • Sovremennyy destroyer "Bystryy"
  • Udaloy I destroyer "Admiral Vinogradov"
  • Udaloy I destroyer "Marshal Shaposhnikov"
  • Vishnya intelligence collection ship SSV-208 "Kurily"

Past Eastern Military District-level exercises have been spread out across a vast region, from Sakhalin Island to the Bering Sea. Some of these units will not transit beyond Sakhalin Island, while others will preposition to the Kamchatka area to await further orders. As a reminder, last year's workup for the "Vostok-2014" operational-strategic exercise also took place east of Kamchatka.

And another MOD "surprise inspection" before the main event should be no surprise to anyone.

Saturday, June 13, 2015

Where in the World is "Admiral Panteleyev"?

Udaloy I destroyer "Admiral Panteleyev" - undated

On February 4, a Russian Navy Pacific Fleet surface action group led by Udaloy I-class destroyer "Admiral Panteleyev" departed Vladivostok for what was supposed to be a three-month deployment. That deployment has now stretched into its fifth month, and no one knows for sure when it will return to its home port.

The group, which also includes two auxiliary vessels (Dubna tanker "Pechenga" and Goryn rescue tug "SB-522"), was reported to be conducting training in the South China Sea a week later. The group was supposed to arrive in Cam Ranh Bay, Vietnam, but that port call never happened due to changes in operational plans, according to an anonymous source.

Following a short port call in Sattahip, Thailand, in early March, a six-day port call in Langkawa, Malaysia, in mid-March, and a brief port call in Colombo, Sri Lanka, in late march, "Admiral Panteleyev" and its support vessels headed into the Indian Ocean. The official story ends when the ships departed Colombo on April 1.

The reason the Russian MOD has not released any new information on the group's whereabouts may be connected to the mission it is currently performing. On April 12, the MOD announced that Black Sea Fleet Vishnya intelligence collection ship SSV-201 "Priazovye" was involved in evacuating combat zone refuges from Yemen to Djibouti, even though the spy ship's participation began at least two weeks earlier. If the "Admiral Panteleyev" group were some how involved in an ongoing humanitary mission, one might expect the MOD to publicly tout the destroyer's efforts. But there has only been silence.

Social media, on the other hand, has provided a few clues. In early May, the destroyer was reportedly anchored near Africa, but not in a port. In early June, "Pechenga" made a port call in Salalah, Oman, to take on supplies before returning to the destroyer's location. It seems the destroyer hadn't moved from the same anchorage at which it arrived in May. While the exact whereabouts remain a mystery, according to one source, the ship is supposed to conduct a port call - somewhere - in the coming days. As for when it might return to Vladivostok, one source indicated mid-August as a likely time frame.

What is "Admiral Panteleyev" doing that is so secret?

MOD vs Zvezdochka Shipyard: Oscar II "Orel"

Oscar II submarine "Orel" undergoing dock repairs at 82nd Shipyard (Roslyakovo) - March 31, 2012
credit: avsky
On December 30, 2010, the Russian Ministry of Defense signed state contract R/1/2/0137/GK-11-DGOZ with Zvezdochka Ship Repair Center for service maintenance and repairs of Northern Fleet ships and submarines, to include Oscar II submarine "Orel", Sierra II submarine "Pskov", and Victor III submarines "Obninsk" and "Tambov". Costs included in the table of work to be performed on "Orel" totaled RUB 10,529,136. While the contract was signed in December 2010, the specific repairs for "Orel" were not approved by the MOD until May 22, 2012 - nearly 17 months after the contract was signed. According to the contract, all work under the contract was to be completed by December 31, 2012.

On December 25, 2014, the MOD filed papers with the Arbitration Court of Moscow seeking RUB 3,042,920 in compensation for the shipyard's failure to complete the agreed to work on "Orel" by the specified deadline. According to its complaint, the MOD stated that some elements of the submarine's repairs were not completed as of October 16, 2013, or 289 days after the contract deadline.

The court determined that nearly all contract line items for the "Orel" repairs were completed by the deadline. Two line items, totaling RUB 7,260,831, were completed by May 13, 2013. However, this delay was caused in part by the MOD's failure to finalize the specifics of the submarine's repairs as they related to those two line items until May 2012.

On April 2, 2015, the court issued its decision (A40-217314/2014) in which it found Zvezdochka was not authorized to unilaterally stop work under the contract, as it violated Articles 309 and 310 of the Russian State Code. The court, however, dismissed the MOD's claim that a contract having multiple line items can only be considered complete when all line items have been completed. Since the shipyard did complete all but two of the line items within the stated deadline, the court limited the shipyard's compensation to the MOD to RUB 500,000 (about 16% of what the MOD was seeking), plus another RUB 13,000 in court fees.

Within a few days, both sides filed appeals with the 9th Arbitration Appeals Court, which is scheduled to begin reviewing the case on July 7.