April 11, 2020

THOSE COVID DAYS OLD FRIEND by Pete

In response to some offline requests for another poem, here is:

THOSE COVID DAYS OLD FRIEND

First is the standard, pre-COVID version, sung by Bonnie Tyler http://youtu.be/gnjusvjK5Qk

and here is my version:

Yesterday I wiled away the hours
Dreams of young fresh lazy days with you
Once we had our sunny lives in Dapto
Then red smoky days left us feeling blue

These lonely days my friend
I hope they quickly end
No song and dance
Forever and a day
Can't live the life we choose
Survive on chips and booze

These lonely days, oh squalid COVID days

La la la la la la ...

Then the dizzy years went rushing by us
We lost our toned bodies on the way
And when at last I see you at the Bowlo
You technicolour yawn and run away

These lonely days my friend
I hope they quickly end
No song and dance
Forever and a day
So tragicly like yobs
Dentures in our gobs

These lonely days, oh misspent COVID days

La la la la la la

Just tonight I stood before the mirror
Nothing fits the way it used to be
In the glass I saw my fat reflection
The product of too much Easter choclatee

These lonely days my friend
I hope they quickly end
No song and dance
Forever and a day
Can't live the life we choose
Orthotics in our shoes
Those lonely days, oh bl--dy COVID days

La la la la la la

To the door I hobbled in my slippers
I heard your voice familiar through the years
Through the grill I smell the reek of kippers
And now I see you Botoxed to the ears

These lonely days my friend
I hope they quickly end
No song and dance
Forever and a day
Can't live the life we choose
Survive on chips and booze

These lonely days, oh effing COVID days

Cry cry cry cry cry cry

Pete
(Some words courtesy http://www.amiright.com/parody/60s/maryhopkins3.shtml  )

April 9, 2020

A COVID Poem by Pete

With apologies to a pretty good band :) *

When we find ourselves in times of COVID
Months of hopefulness decree
There will be a vaccine
Let it be.

And in lonely hours of darkness typing
Listening to the crash of sea
Good Friday comes tomorrow
Let it be

Let it be, let it be.
Let it be, yeah let it be.
Whisper joys pre-COVID
Let it be


* Very much inspired by the Beatles – performed here https://youtu.be/7P6X3IWLECY and below.

A COVID variation Paul McCartney didn’t anticipate when he created Let It Be in 1968-70.




April 8, 2020

Captain Crozier COVID-19 Affair - Sacking Admirals?

With Captain Crozier of USS Theodore Roosevelt being relieved of command, April 2, for  publically demanding his COVID hit crew be allowed to disembark in Guam - new questions are being asked about which Admiral heads should roll. If any. 

This is following the resignation of a high civilian, acting Secretary of the Navy Modly, over the affair. All this is to do with sometime conflicting needs of honouring chain of command against responsibility for the welfare of your crew. 

This is a complex issue involving the USN's octopus like chain of command.

Looks like Croziers's immediate boss is Rear Admiral Stewart P. Baker, Commander Carrier Strike Group 9 which includes USS Theodore Roosevelt. Should Baker's head roll? 

Here's a major part of a Washington Examinerarticle, April 7, 2020, focusing on Admiral Baker:

"Baker was Crozier's direct commanding officer in his role as commander of Carrier Strike Group 9. While aircraft carrier captains such as Crozier are in charge of their particular vessels, an admiral commands the deployed strike group, [including the carrier, and associated destroyers, cruisers, submarines and supply ships].

So far, however, we don't know what Baker was or was not doing about Crozier's concerns in the days that preceded the latter's email. And that matters very greatly because learning more will help us get to the bottom of whether Crozier's chain of command failed him or he failed it.

For a start, note that the New York Times has reported "that tensions between Captain Crozier and his immediate boss, Rear Adm. Stuart P. Baker, the commander of a multiship task force including the Roosevelt, most likely complicated the Navy’s response to the viral outbreak and prompted the captain to send a four-page [email] pleading for help."

As Defense One's timeline points out, we know that these tensions were bubbling two days before Crozier's email hit the San Francisco Chronicle. Now, note some reporting on why Crozier sent his email without first informing Baker of his intent to do so. As the very well-sourced David Ignatius explains, Baker told Modly that he had asked Crozier why he hadn’t sought advance clearance for the message or large distribution and, "According to Modly, Crozier answered that 'he worried Baker would not let him send it to that broad a group.' Baker affirmed to Modly: 'He was right. I wouldn’t.'"

The key here is thus to figure out whether Modly is being entirely honest when he says that Crozier was receiving all appropriate Navy guidance and assistance before he sent out his email. Or whether Crozier, as his unauthorized email would suggest, felt that the chain of command was risking the lives of the Theodore Roosevelt's crew and air wing without compelling mission rationale to the contrary. It is worth noting here that, contrary to Modly's pushback against Crozier's email description of a nonwar footing that justified the Theodore Roosevelt's return to port, it would be a big problem for the Theodore Roosevelt to arrive in the South China Sea as an epidemic wreaked havoc across the ship. That would risk the ship being unable to face a critical enemy threat such as Chinese ballistic missile forces.

So, what about Baker?

Well, what's odd here is how quiet Baker has been since Crozier's firing. We haven't heard that he's delivered any rallying speeches to the Theodore Roosevelt's crew, for example. Instead, Baker seems to have been focused on praising his Navy leadership. Note Baker's comments on Sunday expressing how he is "extremely thankful for the overwhelming support from the government of Guam and Naval Base Guam in the fight against COVID-19, even with such short notice, they were able to assist getting our Sailors moved off ship in a short period of time. Their support has been critical to our ability to remain mission ready."

Again, perhaps Crozier was receiving Baker's ardent support and simply overreacted without justification. Perhaps the Navy had already decided to give Crozier what he needed as hundreds of crew members faced infection. But Baker's choice of words and the disagreements prior to Crozier's email over how to handle the outbreak suggest another possibility. Namely, that Baker had his eyes more tightly focused on getting one of the Navy's few vice admiral billets and ignored Crozier's concerns in fear of aggravating Navy leaders.

In short, we need to know more. As far as is possible amid the coronavirus outbreak, congressional armed services committees should seek testimony from Baker, Crozier, Modly, and 7th Fleet commander Bill Merz [HQ'd in Yokosuka]The Navy has had too many senior leadership failings in the past 12 months. Let's ensure accountability."

WHAT OF OTHER ADMIRALS INVOLVED?

Baker's vulnerability includes only being a Rear Admiral. But there are more senior Admirals up the chain:

-  Baker's boss Vice Admiral Scott D. Conn Commander US Third Fleet, based in San
    Diego.

-  Conn's boss, 4 star Admiral John C. Aquilino - Commander US Pacific Fleet, based in
    Pearl Harbor, Hawaii.

-  Aquilino's boss, 4 star Admiral Philip S. Davidson, Commander Indo-Pacific Command  

-  Another Aquilino boss, 4 star Admiral Michael M Gilday, Chief of Naval Operations

-  Gilday's boss, 4 star General Mark A. Milley, Chairman, Joint Chiefs of Staff.  

PETE COMMENT 

Look's like there are sufficient 4 stars to blur the chain of command. 

The COVID-19 threat deserves quick sorting out on policy and naval-military operational response levels. 

Pete

April 7, 2020

Australia to Delay Payments on Major Defence Projects

Due to announced future spending of more A$200 Billion on COVID-19 the Australian Government will eventually announce severe payment delays in big ticket naval defence projects. This especially impacts the specific vessels or aircraft, Australia is buying, that have not yet actually “cut steel” including the:

- 12 x Attack class future submarines to cost more than A$100 Billion (life of project) for the RAN

- 9 x Hunter class future frigates to cost more than A$35 Billion for the RAN, and

- 6 x MQ-4C Triton marine reconnaissance UAVs to cost more than A$7 Billion for the RAAF.

Major contractors, including Naval Group (Attack class) and BAE Systems (Hunter class), will find their projects may be delayed 2 to 5 years. 

This is given the A$200+ Billion in medical and fiscal stimulus anti-COVID-19 costs that the Australian Government announced in March 2019

Pete  

April 2, 2020

Extra Pressure on Submariners Social Distancing Onshore

A reply by Anonymous has prompted me to look further at the COVID-19 social distancing pressures on submariners, their families and other loved ones.

Hi Anonymous

Yes, no doubt, colds and maybe flu (?) may impact crews on missions doubly.

But COVID-19 is a greater order of risk. I hear submarine crews are now required to go into individual quarantine for 2 weeks Before the 2 to 3 month SSK mission.

2 weeks quarantine on top of the usual hardship of separation from families (and other loved ones) couldn't be fun.

Also even the downtime R & R onshore is compromised by the Western Australian government's understandable COVID-19 restrictions. Hitting the town is severely limited.

Onshore families are likely feeling the pressure of social distancing restrictions. Maybe ones spouse has lost her job in Perth. The freedom of kids going off to school may now change to stay-at-home learning. The extra money (pay for hardship) submariners generate now cannot be spent in the usual way. Restrictions extend from Australia's main submarine base, at Fleet Base West, aka HMAS Stirling (below) to Australia's secondary submarine base in Sydney Harbour and forward base in Darwin. 

I imagine all these submariner restrictions, when onshore, and worry about family on COVID restrictions are playing on submariners' minds as they go on their next mission.



Pete

April 1, 2020

Indian SSBN Arihant's Deterrence Shortcomings

On January 14, 2019 Yogesh Joshi published an excellent article at Texas National Security Review's website War On The Rocks, titled “ANGLES AND DANGLES: ARIHANT AND THE DILEMMA OF INDIA’S UNDERSEA NUCLEAR WEAPONS” The following is just a portion of  Joshi's article, with the link https://warontherocks.com/2019/01/angles-and-dangles-arihant-and-the-dilemma-of-indias-undersea-nuclear-weapons/

"...Project Samudra and the Burden of History
The peculiar history of India’s long quest for a nuclear submarine leaves a long shadow over Arihant’s [Wiki link] capabilities.
India’s nuclear submarine program began in 1966 with feasibility studies on marine nuclear propulsion. Rather than being driven by any military necessity, the program was influenced by considerations of the nuclear establishment’s organizational prestige. As Homi Bhabha, father of India’s nuclear energy program, argued at the time, maritime reactors “could demonstrate India’s impressive capabilities in the field of nuclear energy.” Military justification for the program came much later when, during the 1971 Bangladesh war, the United States sent the aircraft carrier USS Enterprise into the Bay of Bengal to support Pakistan. Thereupon, as a conventional fighting platform, nuclear attack submarines attracted the attention of the Indian Navy because they could raise the threshold of superpower intervention in the region. However, the nuclear scientists could not produce a viable marine reactor. In the early 1980s, therefore, the Indian Navy turned to the Soviets for assistance.
In April 1982, the Soviet Union agreed to lease an attack nuclear submarine (SSN) to the Indian Navy and provide technical assistance to India in building its own submarines. This was the beginning of Project Samudra (Project Ocean), which was to include two vessels codenamed S-1 and S-2.
The stated intent was to produce a “cost-effective deterrent against Pakistan’s enlarging military machine,” according to a top-secret report explaining the program that I obtained from a former government official. The larger objective of these acquisitions, however, had little to do with nuclear deterrence — it was directed towards the growing naval presence of the great powers in the Indian Ocean, more focused on conventional operations than nuclear issues. The report stated, “more significantly, such acquisitions would enhance India’s credibility particularly in view of the increasing presence of the outside powers in the Indian Ocean.”
Project S-1 culminated with the loan of a Soviet Charlie-class SSN in 1988. Project S-2 paved the way for the establishment of the Advanced Technology Vessel (ATV) Directorate, a dedicated research and development agency responsible solely for building an indigenous SSN. The project suffered major delays as India’s nuclear establishment continued to face technological hurdles in producing a viable reactor design. Still, the path was set: India was designing and developing a nuclear attack submarine.
The Indian and Pakistani nuclear weapons tests of 1998 changed the nature of India’s nuclear submarine program. Indian decision-makers were keen to explore avenues that could render their nuclear forces more survivable, including placing nuclear weapons at sea. The first step towards building a sea-based deterrent was to place modified Prithvi missiles on board two Sukanya-class missile boats. The ATV Directorate, however, soon proposed modifying the nuclear attack submarine into a strategic weapon system. The navy was also keen to have its share of the nuclear pie. Thus, soon after the 1998 nuclear tests, India decided to convert what was originally designed as a nuclear attack submarine armed with cruise missiles for conventional naval operations into a strategic weapon system for nuclear delivery. Project S-2 became the first of India’s SSBNs.
Yet this revised mission left the program highly limited in its capabilities. India had started developing a 300-km earth-skimming cruise missile called Sagarika with Russian help in 1991. When India decided to convert the attack submarine into an SSBN, the size of the boat and its missile block was fixed based on the earlier SSN design — meaning only a modest missile with limited range could be retrofitted in. The only option was to replace the Sagarika cruise missiles with ballistic missiles that could carry a one-ton nuclear warhead. Today, the limited range of the K-15, the primary weapon system on Arihant, is the result of these post-hoc technological fixes. Arihant can carry 12 of these 750–1,000-kilometer range missiles, barely sufficient to hit a few major cities in retaliatory strikes against Pakistan, let alone Chinese targets. Its small reactor size also restricts its endurance at sea. In fact, the nuclear reactor onboard Arihant is of vintage Soviet design. Arihant is not Pakistan-specific by design but only by default: Its technological evolution rendered it incapable of anything else.
The burden of history continued to inform the trajectory of India’s SSBN program. To achieve meaningful deterrence vis-à-vis China, India not only needed more SSBNs, but also longer-range missiles that could strike deep inside Chinese territory. In the early 2000s, the Indian government, therefore, sanctioned the ATV Directorate to produce two more SSBNs of the S-1 type and to increase the range of the missiles to 3,500 kilometers. The increase in range entailed a consequent decrease in the number of missiles. The problem, again, was the fixed size of the submarine: Given the immutability of the S-1 design, the long-range missile could only be accommodated by increasing the missile diameter and reducing the total payload. But reduction in nuclear payload meant lesser bang for India’s buck, since it reduced the number of nuclear weapons it could deploy at any given time against China.
When the cabinet of ministers pointed out this problem in 2004, the ATV Directorate decided to include another missile block by increasing the length of the next two boats. Yet in 2006, a major technical review of the program concluded that all five boats proposed so far fell short of a true SSBN force capable of deploying intercontinental ballistic missiles (ICBMs) that could reach all parts of China. It also required a nuclear reactor double the size of previous boats that could endure longer operations at sea. The review committee recommended a new class of boomers with a reactor double the size of previous S-Class boats and capable of launching ballistic missiles in excess of 6,000 kilometers. S-5, as the boat is officially designated, was approved in 2015. This evolution of Project S is symptomatic of mission creep in India’s deterrent requirements, especially as it attempts to achieve deterrence parity with China. The piecemeal expansion of India’s nuclear submarine program severely undermines its deterrent capability. Until India fields an SSBN fleet with ICBM capabilities and improves upon the designs of its nuclear propulsion package, its sea-based deterrent will remain a paper tiger. As Admiral Arun Prakash estimates, it will take India “50-60 years” to field a credible SSBN force.
Arihant’s historical evolution also leaves doubts about its robustness and reliability. There are more than a few rumblings within Indian Navy circles regarding reactor designs based on second-generation Soviet submarines. Arihant’s first deterrent patrol lasted merely 20 days, suggesting endurance issues with its nuclear propulsion package. Finally, the Indian Navy would have to develop very robust infrastructure for training, maintenance, and repair of its SSBN fleet before the sea-based deterrent could be realized. In fact, the fleet has recently suffered from a series of accidents, including the 2017 mishap onboard Arihant. Only extensive operational experience will build the required confidence both in the men and the machine.
Given the twists and turns of its nuclear submarine program, the resulting technological limits, and the underlying problems with Soviet legacy platforms, Arihant’s first deterrent patrol is just a modest beginning in India’s effort to deploy a credible nuclear triad. For the prospective future, its nuclear deterrent will continue to rely on the land- and air-based legs. Indian decision-makers must accept the reality of this modest enterprise. Rather than engaging in premature triumphalism over Arihant, India should take a page from the Chinese playbook to hide its capacities and bide its time.
Operationalizing Deterrence at Sea
Even though Arihant, in its current form, has limited utility against China, its operationalization has nonetheless raised serious questions about how India would deploy its nuclear submarine force, whether this will entail a “ready-to-use” arsenal, and whether India has developed a sufficiently elaborate command and control mechanism to avoid unauthorized use of nuclear weapons. Such alarmist reactions, however, do not fully capture the efforts India’s Strategic Forces Command has made in establishing operational protocols for its SSBNs. The command’s standard operating procedures for the nuclear triad alleviate three major concerns. First, a sea-based deterrent would not engage in conventional operations, nor does it automatically translate into a “ready-to-use” arsenal. Second, custody of India’s nuclear weapons has not necessarily been delegated to the military. Last, India’s political leadership will maintain firm control over nuclear assets.
First, as far as deployment is concerned, India is most likely to follow a bastion strategy rather than putting its SSBNs on constant patrol in open seas. A “bastion” or a “citadel” model entails operating submarines in waters close to home and away from hostile forces. In India’s case, the most suitable geography is in the Bay of Bengal, the Andaman Sea, and in the Northern Indian Ocean. The Pakistani Navy has very limited capability to operate in these waters, while India’s overwhelming naval presence through its conventional fleet and anti-submarine warfare operations will be able to create a cordon sanitaire against Chinese submarine activity.
While some fear the nuclear submarines will have a dual (nuclear and conventional) role, my interviews with Indian Strategic Forces Command officials suggest otherwise. The nuclear submarines will remain solely under the operational command of the Strategic Forces Command, which handles nuclear forces, rather than the Navy, (which handles conventional naval forces). A clear division of labor between the two has been codified, reducing the risk that Indian nuclear forces at sea could get entangled in conventional operations.
In fact, Indian SSBNs would not operate alongside the Navy’s conventional fleet as any coordination could lead to the nuclear submarines’ exposure by enemy intercepts of fleet communications.
Relatedly, the operationalization of Arihant does not mean India’s nuclear weapons are now on hair-trigger alert. It is highly unlikely that the submarines will carry a nuclear payload during peacetime. In fact, insofar as India’s SSBN force will not perform constant patrols armed with nuclear weapons at all times, it does not entirely fit the definition of a true triad. India’s operational plans for its nuclear submarines consist of a three-stage process. The first is nuclear alerting, or mechanically mating missile launch tubes with missile canisters armed with nuclear weapons at specialized naval facilities. This would start at the first indications of a crisis situation (Strategic Forces Command defines a crisis not as the start of actual conflict, but any scenario where Indian decision-makers foresee a possibility of military escalation with Pakistan or China). The second stage involves dispersing the submarines on deterrence patrol. It is only after the boats receive political authorization that they will maneuver to predetermined positions to prepare for the eventual launch of nuclear weapons. This strategy does entail a risk of a “bolt from the blue” nuclear strike against India’s major naval bases, but decision-makers are willing to run this risk given the other legs of the nuclear triad and the inherent uncertainty that any first strike would eliminate all its nuclear assets. Since at least 2008, Strategic Forces Command has consistently strived to develop and put into practice such operational plans for India’s SSBN force.
Lastly, India has developed an elaborate command and control apparatus to maintain firm political control over its sea-based nuclear assets. When the submarines encounter a crisis situation, nuclear weapons will be physically mated with ballistic missiles, per the first of the three steps described above. For this reason, India needed positive command-and-control mechanisms to ensure that when authorized a launch will always occur and that unauthorized or accidental launches never occur. Former Strategic Forces Command personnel have told me in interviews that India has developed such mechanisms: Even after nuclear weapons have been mated with missile tubes, the military will not be in command of nuclear weapons. Any ballistic missile launch requires a two-step authorization, in which civilian authority plays a key role. Even in situations where an imminent enemy strike may be about to take out the submarine’s ballistic missiles, civilian authority will remain the sole custodian of India’s sea-based nuclear forces.
These operational procedures would require extensive testing and training, and a robust communications network. Strategic Forces Command has to establish beyond doubt that the controls will work under the fog of war and that decisions will be securely communicated to the submarines’ battle stations. The infrastructure for these communications has grown alongside the SSBN program, but will still take a lot of time to mature and attain operational effectiveness and reliability. These concerns will continue to cloud the readiness of India’s SSBN force.
Thus, Arihant’s operationalization should not lead to a conclusion that its nuclear weapons are now fully mated with delivery systems and that control has shifted to the military, as many alarmists seem to fear. India has strived to ensure complete political control of its nuclear assets at sea, ruling out any unauthorized use.
Indeed, Arihant’s problem is not that it has nuclear weapons on hair-trigger alert, that it suffers from loose command and control, or that it increases the risks of accidental nuclear use. Rather, Arihant is yet another manifestation of India’s deterrent dilemma between China and Pakistan. As Pakistan responds to India’s sea-based deterrent, it will exacerbate the subcontinent’s nuclear tensions while providing no meaningful change in India’s nuclear deterrent vis-à-vis Beijing in the foreseeable future..."
Yogesh Joshi is a Stanton Nuclear Security Postdoctoral Fellow at the Center for International Security and Cooperation, Stanford University. He is the coauthor of India and Nuclear Asia: Forces, Doctrine and Dangers (Georgetown University Press, 2018).

See Yogesh Joshi's whole excellent article at War On The Rocks