Sunday, June 09, 2019

Making a Better Army Staff Officer, with COL Kirk Dorr, USA - on Midrats



How does our Army help officers understand military doctrine, history, and theory? How do we ensure that our staffs have leaders capable of generating options for commanders engaged with our most complex operational and strategic problem sets?

It doesn't happen by accident.

To address these questions and related topics, our guest this Sunday from 5-6pm Eastern will be Colonel Kirk Dorr, USA the Director of the U.S. Army’s School of Advanced Military Studies (commonly known as “SAMS”) at Fort Leavenworth, Kansas.

COL Dorr is a career Armor Officer, has commanded formations from the company to brigade-levels, and served in staff officer assignments up to the Army Staff and Joint Staff-levels.

COL Dorr’s military education includes attendance at both Harvard University and the Massachusetts Institute of Technology as a resident Fellow studying international affairs and security studies. He is also a graduate of the School of Advanced Military Studies, Joint and Combined Warfighting School, and the Army Command and General Staff College.

Join us live if you can, but if you miss the show you can always listen to the archive at Spreaker

If you use iTunes, you can add Midrats to your podcast list simply by clicking the iTunes button at the main showpage - or you can just click here.


Friday, June 07, 2019

Fullbore Friday

With this being the week of the 75th anniversary of the Normandy Invasion, the Battle of Midway has taken a back seat, rightfully.

At the end of April, I came across one of the best presentations about the Battle of Midway I have ever seen. What makes it so good is its presentation: from the Japanese perspective. The author has only published Part-1 of a two part series, but you need to see it now.

Not just that, it brings in to the light some of the lesser known stories from the American effort - specifically the heroic attacks from the land-based aircraft from Midway after the discovery of the Japanese fleet by a PBY just in time. They may not have directly done much, but they set the table for the carrier aircraft to catch lightning in a jar - as you'll see below.

I recommend that you watch the whole thing, but if you are running short of time, I ask you go to the 11:50 timestamp of the first video.

What especially hit me were the attacks of the Vindicator squadron. Even more obsolete than the Devastators - and their pilots knew this - they still pressed on.

First there was the defense of Midway by the fighters as the attack aircraft went to attack the approaching Japanese force:
- 13 of 18 Buffalo shot down.
- 2 of 6 Wildcats shot down.

The first Midway based attack: 0710:
- 5 of 6 USN Avenger torpedo bombers shot down.
- 2 of 4 USAAC Marauders shot down.
- No hits.
- 2 Japanese Zeros lost.

2nd at 0753:
- 8 of 16 USMC Dauntless dive bombers shot down.
- No hits.
- 1 Japanese Zero lost.

3rd at 0810:
- 15 USAAC B-17 at high altitude.
- No hits. No losses

4th at 0847:
- 11 USMC Vindicator dive bombers.
- 2 of 11 shot down.
- No hits.
- Avoided Japanese carriers and attacked IJN BB Haruna.

Watch 'em all. Next time people tell you how unrealistic the "Last Charge of the Dothraki" was in Game of Thrones ... think of the land based aircraft at Midway (including my Buffalos) - they did the same with the same foreknowledge of the odds.

You do it because it must be done.

Duty. Mission.




Thursday, June 06, 2019

75-years on: D-Day

Sadly, this anniversary of a great moment in western civilization is being smeared by petty contemporary politics by an ungrateful, mal-educated, and narcissistic modern culture.

I am not interested in sharing anything being done or being said for or by modern politicians.

Today, let's just watch what they watched. See what they saw.

These things are always meaningful, especially if you have had the chance to live in or visit these same places.


Wednesday, June 05, 2019

Not Just an Australian Own Goal - They Just Gave the Field to China

Sure, the USN can make a mess of port visits with Fat Leonard ... but on the receiving end, Australia just ... well ... give China the "W."

Details at USNIBlog.

Come by and facepalm with me.

Tuesday, June 04, 2019

Bureaucratic Self-Harm and the Seawolves

One of the great tragedies of the obsession with Joint, Goldwater-Nichols - and to no small measure petty budgetary parochialism - was the loss of the Navy's ability to quickly create inside its own lifelines capabilities to meet the requirements to support combat operations as we encountered them.

We saw it in Iraq, we saw it in Afghanistan, we continue to see it today. Heck, not just USN, but USAF has the same problem. Just look at the bureaucratic slow roll of a capability I heard people screaming for in C5F as we clawed our way up the Kandahar Valley in late 2001 - the Light Attack Aircraft.

Examples are legion of when Navy has needed a capability, but had to wait or get none simply because the other services' "high-demand/low-density" assets simply had more important things to do. That is an arrangement that fits an "efficiency" mindset, but fails the "effectiveness" requirement in war.

Of course, I'm talking today about the capability our Navy grew pre-Goldwater-Nichols out of whole cloth in the body of Helicopter Attack Squadron (Light)-3 and her sisters. A great article over at USNI Proceedings re-introducing their story to a new generation.
One of the principal avenues for resupplying communist Viet Cong fighters was the populous Mekong Delta. The most productive agricultural area in South Vietnam, it featured a web of waterways that were used to infiltrate the region. To stem the flow of supplies, the U.S. Navy initiated Operation Game Warden in late 1965, establishing Task Force 116—a fleet of amphibious vessels and armed river-patrol boats collectively known as the “Brown Water Navy”—that patrolled the delta’s inland rivers and search suspicious vessels. The delta soon became a hotly contested and wide-ranging arena of warfare, where Navy small craft, SEALS, and Army ground forces faced danger at nearly every turn along the jungle-lined waterways.

With the commencement of Game Warden, the Navy concurrently adopted a new designation for its rotary-wing community: the helicopter combat support squadron (HC). These units largely operated as part of the blue-water Navy, performing the utility and plane guard duties that were established missions for helicopters operating from carriers and surface ships. With the exception of search-and-rescue missions, day-to-day operations tilted more heavily toward the support part of the squadron designation and less on combat.

This changed in 1966, when Rear Admiral Norvell G. Ward, Commander Naval Forces Vietnam, offered General William C. Westmoreland, Commander, U.S. Military Assistance Command, Vietnam, much-needed air support for his riverine forces. Army helicopters had been performing those missions on a temporary basis, but Admiral Ward proposed to provide Navy crews if the Army contributed helicopter gunships, which did not exist in the Navy’s aircraft inventory.

The resulting agreement brought members of HC-1 in country to fly UH-1B Iroquois helicopters, with the first contingent arriving on Independence Day 1966. Training under Army pilots and crews included familiarization with the aircraft, armament, and the vast area of operations. On 19 September, the first HC-1 detachment arrived on board the USS Tortuga (LSD-26), one of the collection of amphibious vessels, including tank landing ships (LSTs), that served as bases of operation for HC-1 and later HA(L)-3. The Navy men also received a new nickname—the Seawolves.
Yep, this is the Navy I know.
Aviation Structural Mechanic Third Class Joe Crutcher recalls himself and a fellow maintainer borrowing black paint from an Australian unit that they mixed with green paint provided by the Army to give the HA(L)-3 UH-1Bs a different look. Commander Robert Spencer, the squadron skipper, directed them to paint “NAVY” in white letters on the tail booms, saying, “I want the Army to know the Navy is here.”

One thing not lacking was personnel willing to serve in the squadron, even knowing what they faced. “If you go to HA(L)-3,” retired Captain Brian Buzzell recalled of the squadron’s reputation among those coming out of flight school as helicopter pilots, “you are going to get shot at and maybe killed.” Those pilots joining stateside trained under the tutelage of the Army (initially at Fort Benning, Georgia, and later at Fort Rucker, Alabama), learned how to fire and clean an array of weapons, and completed the Army’s demanding SERE (survival, evasion, resistance, and escape) school.
Read it all.

Of course, in spite of the example they gave, we did not have the same spirit or ability to adjust due to the bureaucratic adhesions from DC and "other priorities" of senior leadership than supporting Sailors under fire. Navy gunships did survive on life support in the USNR, but neglected and never expanded, they finally were allowed to starve to death in 2016. What a disgrace.

There is some good news for history though, there is a documentary;
Jeff and Shannon met with the president of the HA(L)-3 Seawolf Association, Mike Dobson, in 2012 and proposed making a documentary. With Jeff traveling the world filming the World Surfing League, not until 2014 during a squadron reunion in Dallas, Texas, did the couple dedicate themselves to beginning work on the film.
You can get more details here.

Monday, June 03, 2019

History Majors vs. Math Majors: The Problem of a Coherent Fleet Architecture

We are blessed to start another week with a guest post by our friend Bryan McGrath.

Bryan explores a hard topic we have all had to deal with in our Navy - one fully meshed with the challenge of selling the effective vs. the efficient; the intangible vs the quantifiable.

Bryan, over to you;

Let’s get this out of the way early. I have a BA in History and an MA in Political Science. My budding career as a submariner (I loved the 70 days I spent on an attack boat the summer before my fourth year in NROTC and wanted to go submarines) was snuffed out by modest calculus and physics grades (ok, less than modest) resulting in my not even being asked to make the trip to DC for a nuclear power interview. I have nothing against math majors (or technically proficient people), I have just never been counted among them.

My time in and around the Navy has been as a man of words and ideas. Strategy and policy have been my game, and throughout my career, I have found myself across the table from an archetype in which the Navy specializes: the Operations Research/Operations Analysis (OR/OA) expert. The Navy mass produces these folks. There may even be a classified laboratory that digitally prints them. They are unflinchingly professional, incredibly intelligent, and mathematically adroit. I and others like me have been reduced to befuddled silence in their presence when they pull out their spreadsheets and spider charts and multi-variate analyses to utterly destroy a thought, concept, or initiative. You know I’m right. You’ve been there too.

Ultimately, it is these people who run the Navy, and generally speaking, this is a good thing. As the Chief of Naval Operations does not actually operate a navy, he and his staff are optimized to do one and only one thing well—and that is to build budgets. The building of budgets requires hard choices from among many seemingly critical options. Having math whizzes around to order and prioritize these choices employing elaborate computer models and intricate campaign analyses is very helpful in this pursuit. No, it is essential. And this is why I have always admired these folks.

Truth be told, I have also had my problems with them, and it wasn’t until I began thinking about this piece that the nature of those problems began to crystalize. The proximate cause of this focus was the recent DoD budget submission in which the aircraft carrier USS Harry S. Truman (CVN 75) was slated for decommissioning decades early, as a result of a decision to cut its mid-life refueling and overhaul from future budget consideration. This decision would presumably free up resources within the Navy budget for other purposes. The fact that the FY20 Budget submission also included a nearly $500 million line item for two Large Unmanned Surface Vehicles (LUSV) (which did not appear in the previous budget submission) fueled the widely held perception that the Truman was being harvested in order to devote resources to other priorities, including unmanned surface vessels. This perception was further advanced when CNO nominee ADM William Moran said as much in his confirmation hearing. Fortunately or unfortunately—depending on how you view the importance of aircraft carriers—while ADM Moran was making his statement before Congress, the Vice President was preparing to tell the Sailors of the Truman that the President had reversed his decision and that the Truman refueling would be funded.

Putting aside the unfortunate timing of the announcement and the questionable state of alignment within the administration’s national security-making apparatus, the decision to drop the carrier force from its congressionally mandated number of 11 to 10 (eventually) bears scrutiny. Here’s where the history major vs. math major thing comes in.

Make no mistake about it—a decision of the magnitude of the Truman cut would have been accompanied by reams and reams of data. Exhaustive campaign analysis and force on force excursions would have been run literally thousands of times within sophisticated computer models. Devising and implementing these models are the math majors, the OR/OA folks. Give them a set of assumptions and they will give you an answer. Sometimes you like the answer, sometimes you don’t, sometimes you question their assumptions (although you shouldn’t, because they don’t make up their own assumptions, they are given to them by leadership).

That the analytical community would conclude that within an acceptable level of risk given the existing major war plans, the Navy could get by with 10 carriers does not surprise me in the least. I have enormous confidence in their ability to conduct these types of analyses. When it comes to making these recommendations based on cold hard data obtained as the result of sophisticated models of naval warfare in which the capabilities and capacities of the combatants are known and assumed, the math majors are unbeatable.

You know where they aren’t unbeatable? They aren’t unbeatable when it comes to thinking about the force that does the job the nation asks it to do 99% of the time, and that is to regulate the security environment in areas of the world that matter to the United States. Just those words…. “regulate the security environment” …will drive a math major nuts. What does this mean? How do you measure it? How much does one unit of it cost? This lack of clarity is the root cause of the real weakness the math majors have when attempting to analyze the peacetime security environment, and that is they don’t have good models of it. Put another way, devising a mathematically coherent and defensible force structure to account for concepts like “presence” and “conventional deterrence” is simply harder than devising the force structure one needs to fight and win war. And because they cannot do it, they don’t, or at least they don’t like trying.

You know who IS comfortable thinking about force structure and fleet architecture in the context of regulating the peacetime security environment? History majors. That’s right. History majors. Because we can’t (and shouldn’t) do advanced math, we don’t. Now of course, the answers we give are always far more subjective than the answers the math majors arrive at, but at least we try. We know that we can’t model the peacetime security environment to the degree that we can the war plans…so we don’t try. We look at the world as it is, and we think it wise to have major naval power available in and around Europe, in and around the Indian Ocean and the Arabian Gulf, and in the Western Pacific. We know that having that power “present” demands some combination of a rotation base of ships and forward stationed units. We know that it takes a long time to get a ship from Norfolk or San Diego to Bahrain, and since the earth isn’t getting any smaller and ships aren’t getting any faster, the force is sized to account for these distances.

The other thing history majors do is—well, you know, read history. We have read that time and time again since World War II, adversaries have devised “carrier-killer” weapons that have rendered the carrier obsolete. And time and time again, circumstances arose that reminded us of the utility of the carrier in both peace and war. We are of late, engaged in one of these debates, and the certainty with which carrier critics contend that this time is different, that these threats are unanswerable, is notable. Their models show that the aircraft carrier is suddenly uniquely vulnerable, or more to the point, most everything floating is vulnerable. I take no issue with these facts. I understand the state of modern ISR, and I realize that EVERYTHING on the modern battlefield is vulnerable.

What I take issue with is their conclusions. Or at least some of their conclusions. We are told that because large is bad, we need many, small and cheap. Why? Because large is vulnerable in the models that have their confidence. And the models that have their confidence are models that replicate conflict. They do not have models that replicate the peacetime security environment, and so we are unable to assess how the shift from large, expensive, and few, to small, cheap and many perturbs that environment. Put another way, we haven’t a clue how our growing fascination with the conduct of high-end war impacts our ability to deter it.

We do know that the movement of fleets continues to be a powerful signal of national interest and intent. Have the Iranians been less aggressive as a result of our moving a carrier from the Mediterranean to the Arabian Sea? I really don’t know. Without insight into the minds of Iranian decision-makers, I cannot know (the modeling problem, explained). What I do know is that a large, powerful, chunk of U.S. naval power was re-routed in order to influence that leadership. I think that it did so—although of course, I cannot know. I think the President’s national security team thinks so, although I cannot know. I prefer to think that the strategic value of billions of dollars of national treasure and thousands of American lives moving into harm’s way as a signal of intent represents a considerable inducement to potential adversaries not to act. I am less sure of the influence of some of the platforms and systems that are considered beneficiaries of the demise of the carrier in doing so. Someday, my luxury of thinking this way may prove unwise. I see no evidence that this is so.

Which brings us back to the history major vs. math major issue. The plain truth is we need both to consider the inputs into the fleet architecture problem. We must have a fleet that is useful in peace AND war, and I’m not sure that the capabilities that matter in these pursuits are the same. I think it is horribly unfortunate that the narrative around the FY20 Budget became one of “carriers vs unmanned surface vessels”, because we need both. We need the unmatched power and flexibility of the CVN/Air Wing/Strike group as a means of regulating the peacetime security environment and for a number of critical war-fighting functions.

We need Large Unmanned Surface Vessels (LUSV) to distribute and increase the firepower available to what appears to be a fleet topping out around its current size. We need a war-fighting and a war-deterring Navy. We need cold, hard, analytical facts, and we need experience and judgment to fill in where the facts aren’t available. We need history majors, and we need math majors.
Finally, we need to unabashedly embrace the notion that seapower is different than land and air power. Seapower serves a peacetime regulatory function in guaranteeing freedom of the seas that underpins both our security AND our prosperity. Air and land power are incredibly important aspects of national power, but they have little to do with peacetime prosperity and regulation of the security environment. One of the reasons history majors and math majors clash when devising fleet architectures is that we have ceased to make the strategic argument for seapower, and so seapower is treated within the Joint context solely as an instrument of war—and as an instrument of war, it can comfortably be considered within existing (and incomplete) analytical models. Seapower to a maritime nation is also strategy, national strategy, and we should not shy away from this.

Bryan McGrath is the Managing Director of The FerryBridge Group LLC and the Deputy Director of Hudson Institute’s Center for American Seapower. He counts several math majors among his closest friends.

Saturday, June 01, 2019

Midrats Early Summer Melee


He’s back! EagleOne is back in the studio to help us kick of summer with a Midrats early-summer melee!

With most schools out, what you need right now is a good maritime hour to refocus the brain.

For the full hour from 5-6pm Eastern we’ll try to cover it all from the latest McCain kerfuffle to WESTPAC to NATO to the FFG(X) dropouts and more, we’ll cover the waterfront.

As always, the phones and chatroom will be open if you want to join the show.

See you Sunday!

Join us live if you can, but if you miss the show you can always listen to the archive at Spreaker

If you use iTunes, you can add Midrats to your podcast list simply by clicking the iTunes button at the main showpage - or you can just click here.