Wednesday, August 16, 2017

MV-22 Assault

The Marine Corps has been rapidly moving away from the traditional over-the-beach amphbious assault using landing craft to an aviation based assault concept using helos and MV-22’s.  ComNavOps has questioned the feasibility of this approach in numerous posts.  Let’s continue to examine the issue.

Defense Update website has a fascinating article describing numerous helo shootdowns.  Here are some numbers to get a feel for the magnitude of the problem.

“The U.S. Army has lost more than 120 helicopters in the war on terror, about 25 percent of them due to enemy engagements. According to recent official statistics, some 57 U.S. helicopters had been downed in Iraq until Feb. 4, resulting in 172 deaths, or about 5.5 percent of total American deaths since the conflict began in March 2003. According to U.S. Army General Simmons, the U.S. Army has lost 29 helicopters to enemy fire since March 2003.” (1)

How have these losses occurred?

“The majority of the firefights involve machine-gun and heavy-machine-gun fire, categorized as up to 23 mm, Simmons said. But, he added, some surface-to-air missiles, such as SA-7s, SA-14s and SA-16s, have been used to shoot down Army helicopters.“ (1)

While that may seem like a lot of losses for a semi-war, we have to recognize that helos have heavy workloads and fly a lot of hours and missions.  It is simple statistical probability that some will be shot down or damaged.

“Army helicopters average 100 enemy firefights monthly and are hit about 17 times a month. Most times the helicopters are able to fly back to base. Simmons said that is a testament to the quality of pilots, crews and equipment. The number of flight hours for the Army has nearly doubled in the past two years. In 2005, pilots logged about 240,000 hours. This year, Simmons said, he expects that number to reach nearly 400,000 hours. In 2006, pilots and crews flew 334,000 hours.” (1)

On the other hand, highly sophisticated helos should be quite successful against ill-equipped and ill-trained terrorists so any losses should be viewed with a degree of alarm.

What about countermeasures and defensive tactics?

“As result [of losses due to SA-18 type missiles], U.S. military helicopter pilots in Iraq tried flying low and fast, hoping to elude heat-seeking missiles fired by insurgents. But the insurgents responded with heavy weapons such as machine guns and rocket-propelled grenades, and the loss rate of American helicopters soared. So the pilots went high again and insurgents replied with lethal surface-to-air missiles. The vicious circle continued.” (1)

It’s not just newer surface-to-air (SAM) missiles that threaten helos.

“What is still more vexing to Helicopter pilots flying combat missions in Iraq is the constant threat from RPGs. U.S. military helicopters are equipped with long-range sensors and devices to jam radar and infrared technology, but they have proven vulnerable to intense gunfire, as well as rocket-propelled grenades.“ (1)

American pilots learned to fear good old fashioned barrage fire in Vietnam and the threat remains just as valid today as then.

Helicopters are particularly vulnerable when landing.  At that time they have no choice but to be low, slow, and non-maneuverable – they have to be in order to unload and to maintain flight control in the inherently “unstable” hover mode.  Consider what this means for aviation assault.

“… pilots …  "yank and bank" in a corkscrew motion when approaching a dangerous or "hot" landing zone, dropping with a gut-churning, nose-high descent. Hovering, a helicopter is at its most vulnerable… Brig. Gen. Robert Milstead, a Cobra pilot who recently returned from commanding a Marine air wing in Iraq claims: "Above about 2,500 or 3,000 feet you are out of small arms range but you've got to worry about the MANPADS threat, by all means avoid 500 to 1,000 feet because you're hanging out there like a grape, to be picked!"

This is bad enough for conventional helos but now consider the MV-22, envisioned by the Marine Corps as the backbone of aviation assault.  The MV-22 is not a helo.  It is a conventional aircraft that can temporarily, carefully, and cautiously enter helo/hover mode for brief periods while landing and taking off.  However, it is even more unstable than helos while in hover mode and cannot even remotely “yank and bank” during its landing.

In Vietnam, helo assault pilots learned to come in fast and hard, hit the ground in a tightly packed grouping, unload the troops in seconds, and haul out.  Now, watch any MV-22 “combat” landing video – there’s plenty on YouTube.  MV-22 landings are the complete opposite of what I just described.  The MV-22 requires large spaces – there will be no such thing as tightly packed landing groups, slow, careful maneuvering to deal with the inherent instability of hover mode and the poor visuals that the pilot has, and a relatively slow rate of unloading.

UH-1 Huey Assault

We previously discussed helo operations and losses in Vietnam where over 5000 helos were destroyed – a 43% loss rate (see, “Helo Assault”).  Consider the helo assault losses in Vietnam and then compare the physical size and performance of the UH-1 Huey versus the MV-22.  As a reminder, here are a few relevant specifications.

UH-1 Huey
-          Size:  57 ft long rotor tip to tail
-          Fuselage:  20 ft x 8’7” approx fuselage =  170 sqft
-          Troop Capacity:  around a dozen troops with wide exits from both sides

-          Size:  57 ft long x 85 ft rotor tip to tip
-          Fuselage:  50 ft x 15 ft approx fuselage = 750 sqft
-          Troop Capacity:  around two dozen troops with one exit at the tail

As seen, the MV-22 fuselage, the major targeting mass, is 4.5 times the size of the Huey when viewed in profile.  Combine that with the greatly reduced combat landing performance of the MV-22 and the loss rate in a contested assault will soar even over the shocking Vietnam loss rates.

MV-22 - Compare the Size to the Huey!

Let’s look at more recent evidence.  Consider the Karbala battle:

2003 – Karbala, Iraq – During Operation Iraqi Freedom, ambush barrage fire from the Iraqi Medina division routed 31 US helos of the 11th Regiment / 3rd Infantry Division.  Two helos were lost (one to a non-combat crash) and all but one were heavily damaged.  The helo unit was effectively wiped out.

Recognize that all these helo losses were under best-case scenarios where the US had total control of the sky and the enemy was generally ill-trained and ill-equipped.  What will losses be against a peer, under contested skies, and against well trained troops with state of the art weapon and sensor systems?

So, with all that said, I have to pose the question,

How are we going to conduct a successful helo/MV-22 aviation assault?

The answer seems pretty obvious:  we aren’t.

If that’s the case, why are the Marines basing so much of their doctrine and acquisitions around aviation assaults?


(1)Defense Update website, “Deadly Scourge of the US Helicopter Pilots in Iraq”, Colonel David Eshel, 2007,

Monday, August 14, 2017

How To Build A Cheaper Carrier

Here’s a companion piece to the recent post describing how to build a better, cheaper aircraft and in only five years (see, "How To Build A Better Aircraft").  In this post we examine how to build cheaper carriers that still operate a full combat air wing.

We’ve noted the precipitous decline in air wing size and the corresponding, if utterly illogical, increase in carrier size (??!!!!).  We’ve also noted the exploding cost of carrier construction (yikes!!!!).  The logical implication of these observations is that we can get by perfectly well with a smaller, cheaper, carrier.  The overarching attribute of such a carrier would be simplicity.  Simplicity is the foundation that leads to size and cost reductions.  The simpler the carrier, the smaller and cheaper it should be.  With that in mind, let’s design a smaller, cheaper, simpler but still highly effective carrier.  Bear in mind that when I’m talking about a smaller carrier, it’s smaller only relative to a Nimitz/Ford supercarrier.  I’m, emphatically, not talking about the usual escort type carrier that so many people seem to want.  That kind of mini-carrier is of very limited use in combat.

As I’ve long harped on, the secret to a good ship design is a solid concept of operations (CONOPS).  With that in mind, the carrier I’m going to describe would operate paired with a regular supercarrier and two such pairs would constitute a carrier task force in combat.  I’m not going into any great detail on the CONOPS because that’s not the point of this post.  I mention the general usage simply to provide a context to understand where and how this ship fits into the overall fleet structure.

Anyway, here are the design points.

  • Ship size target should be the Midway of the 1980’s.

Length = 960 ft (vs. 1100 ft Ford)
Displacement = 50,000 t (vs. 100,000 t Ford)

  • Air wing size and composition should be a full size wing less helos other than a couple for Search and Rescue.

F-18/35 = 44
EA-18G = 6
E-2D = 4
Non-existent Tanker = 6

  • Catapults = 2 at the waist positions
  • Elevators = 2 or 3
  • Radar = TRS-3D or equivalent
  • SeaRAM / CIWS = 4
  • Power will be conventional rather than nuclear.  Naval engineers can determine whether we need 2 or 4 propeller shafts.

Air Wing.  The air wing will be a nearly full, standard wing.  Current air wings have 44 Hornets and so will ours.  We will also have 6 EA-18G Growlers, 4 E-2D Hawkeyes, and 6 non-existent tankers (if we have to pull S-3 Vikings out of the boneyard, we will).  The old Midway operated a larger air wing than this so we know we can fit this wing on a much smaller carrier than a Nimitz/Ford.

The reduced helo component means a significant savings in less maintenance space, parts storage, machine shops, magazine storage, and fuel storage.  The reduced pilot and maintenance tech numbers means less berthing, smaller galley, fewer heads, and less food and water storage.

Catapults / Elevators.  Carriers rarely operate all four catapults simultaneously.  Most of the time, only the two waist catapults are used and the bow is used for parking aircraft.  We’ll simplify and not even install bow cats.  We’ll go with two waist cats and call it a day. 

Without bow cats, we gain space under the deck at the bow that can be used for hangars or any other function.  Without the need for bow cats, we can also reduce the length of the bow and, thus, the overall length of the ship.  Further, with no bow cats, the bow deck space can be devoted exclusively to parking which “increases” the size of the carrier while actually making it smaller – meaning, that the parking area increases while the actual size decreases!

Sensors.  Carriers are always accompanied by Aegis escorts.  Further, carriers don’t radiate during combat.  Finally, carriers have no long range, advanced weapons that require sophisticated sensors.  Thus, there is no need for advanced radar suites.  The $500M Dual Band Radar and the $300M Enterprise Radar can be replaced by a simple TRS-3D, or equivalent – just enough for navigation and a bit more.  Both the SeaRAM and CIWS have their own radars so, again, there is no need for sophisticated ship sensors.

Weapons.  Carriers are always accompanied by Aegis escorts.  We’ll let the escorts do their job and provide the area AAW defense.  Our carrier will have only short range and close in self-defense weapons.  Four SeaRAM or CIWS will comprise the carrier’s weaponry.  Note that both SeaRAM and CIWS have self-contained radars which, again, is why we don’t need a sophisticated sensor suite for the carrier.

Crew.  The smaller ship size, less equipment, less complex equipment, fewer helos, smaller conventional power plant, etc. all translate to a smaller crew.  A smaller crew translates to smaller hotel services support staff – for instance, fewer cooks and food service staff will be needed.  Add in some judicious use of automation and crew size should be around 1/2 to 2/3 of the Nimitz.  Let’s call it 3000, total, including the air wing personnel.

Cost.  The ship will be 87% of the length of a Nimitz and have 50% the displacement which should significantly cut costs.  Admittedly, the basic hull components are the least expensive portion of the ship but the reduction in length and displacement still offers significant savings.  Let’s call it $700M in hull construction savings. 

The use of conventional power will result in significant construction cost savings and if we can get by with only two shafts/props we’ll save even more.  The 2002 Shipbuilding and Conversion budget shows a line item for “Nuclear Plant Propulsion Equipment” of $1.47B.  Let’s call it $1B in savings from the use of conventional power.

The minimal sensor suite will save hundreds of millions of dollars.  Let’s call it $300M.

The elimination of two catapults will save additional money.  Let’s call it $200M.

The various reductions in equipment will allow a reduction in crew size which means fewer berthing areas, smaller galleys, less food/water storage requirements, and generally less of all the ship’s hotel services which, in total, provides significant savings.  Some of that is reflected in the smaller overall size which we’ve already accounted for.  However, a great deal more savings comes from the reduced equipment, utility demands, hotel service equipment, etc.  Let’s call it $300M.

The various savings total up to $2.5B.  That means that compared to the cost of the last Nimitz built, we can build a smaller carrier for $2.5B less.  So, for $2.5B less than the last Nimitz, we can have a fully functional carrier that operates a full size air wing (less helos). 

Since you’re wondering, the last Nimitz class carrier, the Bush, was commissioned in 2009 and cost $6.2B in then year dollars, according to Wiki.  That’s $7.2B in 2017 dollars.  Thus, we can build our carrier for [$7.2B - $2.5B = $4.7B] versus the $14B+ for the Ford class.

Why wouldn’t we do this?

Saturday, August 12, 2017


Lockheed has let it be known that they are investing internal effort at packaging Patriot missiles onto naval vessels (1) – this despite the existence of Standard anti-ballistic missiles that already exist, do the same job, and already have integrated software tying the weapon into the ship’s sensors and fire control system – in other words, a complete and integrated package.  So, why is Lockheed looking at naval Patriots which would, at best, be redundant?  Self-interest.  They’re doing what’s potentially good for Lockheed.  If they can sell an existing product they can make money without any great development cost.

What’s wrong with that?  Nothing.  Self-interest is the foundation of capitalism and free markets.  However, Lockheed’s interests are not necessarily the same as the US military’s interests.  In fact, it would be rare and only coincidental if Lockheed’s interests and the military’s interests aligned. 

Lockheed’s interest is making money.  The military’s interest is combat.  The point is that we, and the military, need to recognize that when we turn to industry for products and support, we’ll get whatever the company believes will generate the most money for them rather than what will provide the best combat option.

When the Navy issues its final Request For Proposal (RFP) to industry for the new frigate, Lockheed Martin and Austal, the manufacturers of the LCS, are not going to respond with a brand new frigate design – they’re going to respond with a modified (to the smallest degree they believe they can get away with) LCS.  Why?  Because that’s what’s in their best self-interest.  It’s how they can make the most money.

When the government initiates the next F-35 program, the manufacturer isn’t going to respond with the most cost effective and efficient manufacturing program – they’re going to respond with the program that is the least likely to be able to be killed off just as Lockheed Martin set up the elaborate fifty sate/one hundred country disbursed manufacturing model that they knew Congress would be unwilling to kill due to the distributed jobs aspect.

When a manufacturer “tests” a developing weapon system, they’re not going to test it under combat conditions to see how it really works.  That’s not in their self-interest.  They’re going to test it in a contrived scenario carefully calculated to make the system appear as good as possible.

If Bath is asked about a potential new destroyer, they’re not going to propose a brand new design – they’re going to propose a modified Burke because that would be in their best self-interest.

Consider all the ship type variants that Huntington Ingalls Industries (HII) has suggested for roles ranging from a frigate to ballistic missile defense (BMD) to amphibious assault, among others.  Each was based on – you guessed it – the LPD-17.  What’s the odds that the optimum frigate, BMD, and assault ship are all met by the same LPD-17 basic design?  Of course they’re not!  HII is proposing what they can make money on, not what would be the most combat effective solution.  HII’s interests do not align with the military’s.

LPD-17 Frigate/BMD/AAW/Assault

The point in this is that we, and the military, need to keep this self-interest concept firmly in mind as we deal with the defense industry.  We need to run everything we hear, see, or procure from industry through the cynical filter of “what’s in it for them?” and recognize that what we’ll get is a sub-optimum response or product that serves industry’s interests not ours.  That means that if we want an optimum service or product we have to drive the acquisition process and not leave it to industry.

When I hear comments like the those from former CNO Greenert, and now Richardson, saying that they can’t wait to see what industry “gives” us next, I cringe.  Industry will give us what is in their best self-interest rather than what we need.  Sure, industry will make some attempt to align their interests with the military’s just because doing so will increase the odds of them getting what they want: money.  That alignment, however, will be as minimal as possible.

There’s nothing wrong with inviting industry to make suggestions as long as that process of research and investigation is divorced from actual acquisition. 

On a related historical note, the Spruance was the first ship design that the Navy threw completely out to industry.  While the Spruance turned out to be a fine design, there was no guarantee that it would.  Witness the more recent LCS which was designed with minimal [useful] input from the Navy and wound up being an unmitigated disaster.

The military needs to stop throwing out open-ended invites to industry which allows industry to pick the product and, instead, start driving the acquisition process.  That means re-establishing in-house expertise, generating extensive and precise requirements, and demanding the exact product that will provide the best combat performance.  If the military doesn’t have a better idea of what’s needed than industry then we need to clean house on military leadership and start over.  The military needs to take back the acquisition process from industry.


(1)Breaking Defense website, “Lockheed Studies Sea-Launched Patriot PAC-3 & New 6-Foot Missile”, Sydney J. Freedberg, Jr., 9-Aug-2017,

Thursday, August 10, 2017

Carriers And Tankers

The recent post about the Navy’s proposed unmanned tanker, the MQ-25 Stingray (see, "Navy Issues Tanker RFP"), engendered a lot of discussion about tankers, the various aircraft that could fill the role, and the need for tankers, in general.

Before anyone goes any further with this, it is mandatory to reread the excellent article on mission tanking written by guest author Mr. Bustamante (see, Why The Navy Needs A Really Large Tanker Aircraft”).

Now that you've done that, let's move on.

All of our tanker aircraft discussion is missing one key point – the only point that really matters, actually – and that is the role of the carrier.  To make the point with a ridiculous example, if we envision the role of the carrier to be one of sitting in a harbor providing combat air patrol (CAP) then we don’t need a tanker at all, or no more than a small, simple tanker for overhead recovery tanking, as a safety measure.  On the other hand, if we envision the carrier conducting 10,000 mile standoff strikes then we need a mammoth mission tanker and some much longer ranged strike aircraft!  

So, what is the role of the carrier?  I’ve answered this before in both posts (see, “AircraftCarrier – What Future”) and comments but it clearly needs repeating so let’s have at it, again, and see what it tells us about tankers.

Historically, the carrier has been a strike platform both for anti-surface and land attack.  Early in WWII, carriers would dart in from a long ways off, under cover of darkness, launch strikes, and retreat before an effective counterattack could be mounted.  Later in the war, when proper carrier groups could be assembled, carriers were a bit more willing to stake out a location and stand and conduct strikes secure in the belief that they had sufficient combat power to deal with any counterattack.

Today, we talk about anti-access/area denial (A2/AD) zones that extend a thousand miles or more from an enemy’s territory.  These zones are established by the range of the weapons that can be brought to bear on any intruder – weapons such as mines, aircraft, land based anti-ship missiles, short range ballistic missiles, air launched anti-ship cruise missiles, submarines, and surface ships.  Compounding the problem for an attacking carrier group is the presence of sophisticated surface to air missile defense systems guarding high value bases and targets – systems with radars that can see and strike aircraft for hundreds of miles around.  Add to this fast, long ranged defensive aircraft armed with long range air to air missiles and it is almost taken as a given that manned aircraft cannot successfully penetrate and attack a land target defended by a peer enemy.

Increasingly, long range, penetrating strike is a mission given to cruise missiles.  That being the case, what role does the carrier serve?  Well, the cruise missiles (Tomahawks, at the moment) are mounted on Burkes and submarines.  Burkes need to get within several hundred miles of their targets.  Depending on how close the targets are to an enemy’s shoreline and how straight a course the missile will fly, the Burkes may need to penetrate hundreds of miles into an A2/AD zone to reach their launch point.  They’ll need protection to do that.  Some of that protection can be provided by their own Aegis/Standard defense systems, of course, but that alone will not be sufficient especially if we want to heavily load the VLS cells with cruise missiles rather than surface to air missiles.  Thus, the ideal escort for the cruise missile shooting Burkes is a carrier.  The carrier provides airborne protection for hundreds of miles in every direction and provides an added layer of protection to the Aegis/Standard missile defense.  Carrier aircraft also substantially decrease the likelihood of an enemy’s sensor platforms finding and targeting the carrier/Burke force.

Thus, the carrier becomes the escort for the Burkes instead of the other way around.  Or, to be more accurate, the carrier and Burkes mutually escort each other with the Burkes providing the group’s striking power.

Cruise missile shooting submarines are fine on their own.  Their inherent stealth makes them an ideal Tomahawk shooting platform and negates the need for a close escort.  Even here, though, we see another mission for the carrier – to hunt and kill the enemy’s anti-submarine forces, both surface ship and airborne.  If the carrier can relieve the pressure on the submarines, the subs can be more effective in the cruise missile shooting role.  Note, that I’m talking about dedicated cruise missile shooting submarines – SSGN’s loaded with 150+ cruise missiles, not SSN’s loaded with 12 cruise missiles – those are an ineffective and inefficient means of cruise missile delivery.

Of course, the Air Force’s long range bombers can also launch cruise missiles, if they can survive to reach their launch points.  Again, the carrier air wing can provide the local air superiority needed to clear transit lanes and safe launch points for bombers.

So, how does all this relate back to the subject of tankers? 

Understanding what the role of the carrier is, we see that the carrier does not, and indeed should not, have the role of deep penetrating, land attack strike against a peer enemy.  The job of the carrier and its aircraft is to secure local (though a very large “local”) air control for the purpose of escort.  Tankers are needed to facilitate that but not long range, stealthy, penetrating, high capacity tankers.  All we need is a medium capability and capacity tanker to support the far flung air superiority aircraft.  A fair amount of speed in the tanker would be helpful to get from one location to the next in an expeditious manner.  Other than that, the tanker would be a plain, non-descript airframe.  Conceptually, a higher speed S-3 Viking would do just fine.

Carriers and tankers are intimately related and yet we persist in discussing them in isolation.  When we discuss tankers we must do so with a clear understanding of the role of the carrier.  Of course, the role of the carrier comes from having a geopolitical strategy and the associated military strategy – one of my favorite, overarching themes.  When we lack a clear strategy we fall into a pattern of haphazard acquisitions, hoping that something we buy may prove useful in the future instead of purpose designing and acquiring assets that we know will support our strategy.

We should also note that as the A2/AD threat is neutralized and the operational distances are greatly reduced, the carrier can revert to its traditional strike role but, by definition, this will involve much shorter distances and require only a medium endurance and medium capacity tanker – just what we described for supporting the carrier’s air superiority fighters.

Monday, August 7, 2017

How To Build A Better Aircraft

As we discuss terminating the F-35 and why it’s a good/bad idea, I continue to hear the notion that we have no choice but to continue because stopping and designing a new aircraft would take too long and cost even more than the F-35.  Given today’s badly broken military development and acquisition practices, that is undoubtedly true.  However, it doesn’t have to be.  In previous posts and comments, I’ve described how to design a new aircraft, put it into production in five years, and do it for less than we’re paying now.  I’d like to pull all those comments and posts together into one post.

Here’s how to build a better aircraft.

To begin, we have to define what we even need in broad terms.

The first key recognition is that there are two main “theaters” of operation for aircraft:  Europe/land masses and the Pacific/oceanic region.  All other likely regions of conflict (Iran, North Korea, Africa) are subsets.  This recognition immediately leads us to the second recognition.

The second recognition is that a new aircraft must not be a multi-service aircraft.  The F-35 has proven the folly of this approach.  The requirements for a European/land mass aircraft will be radically different than for a Pacific/oceanic aircraft.

See?  We’ve already saved money by not trying to build a gargantuan, one-size fits all aircraft!

Being a naval matters blog, this post will now discuss only the Pacific/oceanic aircraft.  The Air Force can design their own European/land mass aircraft.

The third recognition is that the aircraft will perform one main role and only one.  Focus is the key.  Secondary functions are fine as long as they don’t impact the primary function or contribute more than 2% to the cost.  Thus, a fighter that has a mechanism to carry and release a bomb is fine as long as the capability in no way negatively impacts the main role of being a fighter.

See?  We’ve saved money by not trying to make our aircraft a combination strike, fighter, AEW, ISR, EW, tanker, drone controller, arsenal aircraft all rolled into one.

The fourth recognition, closely tied to the third, is that focus comes from a coherent, well thought out concept of operations (CONOPS).  This will tell us exactly what our aircraft requirements are.  Note that I’m not going to offer what I think the aircraft should be/do.  That would just bog us down in technical specifics that are irrelevant to this discussion.  Besides, if you’ve followed the blog, you already know what kind of role I think Navy air should play.

So, we’ve now got a clearly defined aircraft with a very specific and narrow functional role.  At this point, our aircraft program breaks down into two major sections:  technical and program management.

Technical Aspects

Airframe.  Choose an existing airframe.  There are many to choose from.  There are all different wing shapes and sizes, there are stealthy and semi-stealthy airframes.  There are single engine and multi-engine.  And so on.  The point is to pick an existing, proven, debugged airframe, if at all possible.  I suspect the F-22 airframe is a pretty good choice.  Maybe not perfect but perfect is the enemy of affordable.

See?  We’ve saved a gazillion dollars in basic airframe developmental costs by simply using an existing airframe!

Technology.  Choose the most advanced existing, proven technologies for sensors, engines, and weapons.  If it isn’t already in operation somewhere in the world, then it belongs in Research & Development and not on our aircraft.  With only existing technology, we eliminate development altogether and only have to deal with packaging of the items into the airframe and integration through the software.

See?  We just saved a boat load of money by completely eliminating technology developmental costs.

Complexity.  Don’t make it unnecessarily complicated.  The F-35 “do everything” ALIS maintenance, inventory, logistics, and mission planning software is needless complication and is racking up huge costs.  We don’t need sensor fusion unless there’s an existing, debugged, proven software package already out there.  We just need a basic “sense and shoot” level of complexity.

See?  We’ve just saved a bundle of money by keeping everything simple.  KISS is alive and well.

Management Aspects

Design.  Production cannot start until the entire design is 100% complete.

See?  We just saved a ton of money by completely eliminating concurrency costs.

Change Orders.  Design modifications are the enemy of affordable – affordable has a lot of enemies, doesn’t it?  We’ll establish our requirements from the CONOPS, embed them in concrete, embed the concrete in titanium, and not change a single, tiny item.  The inevitable changes can come down the road in the form of upgrades, after the aircraft is in service.

See?  We’ve just saved a ton of money by completely eliminating change orders, alterations, and concurrency costs.

Managers.  Program managers must be appointed for the duration of the program until the aircraft is in full production.  To do less is to lose accountability.  Managers must be held accountable.  If the program misses schedules, runs over budget, or otherwise fails, the managers must pay the price in the form of loss of pay, loss of benefits, possible court martial, and automatic discharge from the service.  This may seem severe but it’s exactly what private industry does with their managers.  Besides, would we really want to retain in service a manager who demonstrates that they can’t successfully manage a program?  Now, the flip side of accountability must also be applied.  If the program comes in on time or early, on or under budget, and meets all technical specifications then the managers should be given significant bonuses, raises, benefits, and promotions.  Together, the threat of punishment and the promise of reward are as powerful a motivational tool as we can provide.

Authority.  Hand in hand with this degree of accountability goes authority.  If we’re going to hold managers accountable to this degree, they need the power and authority to execute their program as they see fit.  Once we commit to a program, no one but the program manager can make decisions about the schedules, funding uses, technical issues, etc.  Yes, there are statutory requirements and milestones that must be met and which are decided by other people but all the program specifics must be under the control of the manager.  No more can some outside Admiral insert his pet feature into a program.  No more can outside forces impose schedule adjustments.  And so on.

Decision Point.  A death point is necessary.  A death point is a go or no go decision point and comes at the 2 year point in a program.  At that point, any competent program manager will know whether the project is viable.  If it isn’t, then we terminate with no further expenditures and no penalty for the manager.  If it is viable, we proceed as described.  Only the program manager can make the go decision.  Thus, he can’t be forced into moving ahead with a project that isn’t viable.  Conversely, the program manager or any outside person or agency with sufficient authority can make the no go decision.  This allows outside agents to terminate the program due to budget, changes in strategic or operational need, or any other reason.

Conflict of Interest.  Employment restrictions will forbid the project manager from ever working for a company that had anything to do with the project.  This eliminates any conflict of interest, delayed bribery/kickbacks, etc.

Contract.  A fixed price contract with cost reduction incentives will be the only type of contract allowed.  With the iron-clad, unchangeable specifications we’ll use, there will be absolutely no unknowns for industry and, therefore, no reason to need any kind of squishy, cost-plus contract.  There will be no separate contracts for multiple lots of aircraft.  There will be only one aircraft and one lot.  The last aircraft built will be absolutely identical to the first.

A side effect of this policy might be that instead of committing to production quantities of thousands, which inevitably get cut to hundreds, perhaps we’ll scale down our production programs to more reasonable quantities that can actually be built.

The entire quantity of aircraft will be specified in the contract.  The contract will specify that the manufacturer gets paid the full contract amount whether the government terminates or reduces the aircraft quantity or not.  Thus, there is no risk for the manufacturer and, therefore, no reason not to accept a fixed price contract.

So, let’s sum up, shall we?

Timing.  We’ve completely eliminated development, leaving only packaging and integration.  Requirements will be unchangeable.  All technology will already exist.  With all that in mind, there is no reason we can’t begin production within 5 years, quite likely less.

Cost.  I’ve noted many instances of huge cost savings.  With no development, existing technology, an existing airframe, and no modifications, there is no reason we can’t build the cheapest aircraft in modern history and cheaper by a huge amount, too!

The interesting thing about this concept is that the vast majority of it could be implemented by the Navy with nothing more than internal policy changes.  Yes, there would be a few aspects that might require legislative involvement but those are relatively minor, actually.

Note:  I don’t want a single comment telling me why this can’t be done under the current reality.  I know it can’t be done under the current reality.  This blog is partly about describing current conditions but also, partly, about describing the way things should be.  This post is one of the “should be” ones.  Let’s treat it as such.

And there you have it.  If we dropped the F-35 today, we could have a fully developed, fully combat capable, state of the art aircraft in production within five years and for a fraction of the cost of the F-35.

That’s how you build a better aircraft.

Friday, August 4, 2017

Time Stands Still

Time Stands Still !

We have witnessed phenomenal advances in military technology since WWII.

  • Aircraft are jet powered and can now supercruise at Mach+ speeds.
  • Weapons can now be precisely guided by lasers.
  • Missiles can home in on their targets using a variety of technologies.
  • Radar can see a mosquito at 200 nm.
  • Stealth ships and aircraft can evade radar.
  • Cruise missiles can travel a thousand miles and hit a pinpoint target.
  • Infrared sensors allow us to see in the dark.
  • Shaped charge warheads can achieve amazing penetrations.
  • Sensors and weapons can be networked to achieve leaps in efficiency.
  • And so on …

The advances in military technology are absolutely stunning.  Most impressive is the fact that the advances have been steady and show no sign of abating.  Not a decade has gone by in aircraft, weapons, and sensor development that has not seen a significant leap in technology.  We can now realistically envision lasers and rail guns.  Star Wars is just around the corner.

As an example, just consider the advances in ship’s armor since WWII.  We’ve developed … uh … new, uh … Boy, I’m drawing a blank on any new advance in ship’s armor.  But, that aside, our ships are now constructed with steel plate that is markedly stronger than … no, wait … Now that I think about it, ship’s plate is actually thinner and weaker than standard WWII hull plating.  I guess we’ve actually gone backward a bit.  Can that be?

It would appear that naval armor development has been mired in a time warp where time has stopped.

Hang on.  Let me make a quick call to the Navy’s engineers.   ………..

Well, that just confirmed it.  I asked them what year it is and they said 1946.  That explains the utter lack of progress in naval armor.

It’s funny.  When we discuss aircraft, weapons, and sensors, it’s always in the future tense.  This next generation of aircraft will have weapons that …  and sensors that will …

But, when we talk about naval armor, it’s always in the past tense.  A WWII battleship can’t stop a cruise missile.  A modern ship can’t carry the weight of WWII armor - proven false in a previous post but it illustrates how we reference armor.  Armor, even WWII armor, can’t stop torpedoes. 

Why don’t we discuss armor in the future tense.  Why don’t we say, this next frigate will have armor that … ?  It’s because there have been no advances and, therefore, we have no expectation of any advances.  We all read the news and we know that no one is even working on armor development. 

Why is that?  Why is no one working on armor development?  Is there something inherent to armor that makes it immune to scientific advancement?

Land vehicle armor has made advances.  Not as much as aircraft, weapons, and sensors but still significant advances.  Chobham ceramic armor lead the way.  We now have layered armor, composite armor, V-shaped armor, perforated armor, spall liners, reactive armor, and probably a bunch of other armors that I don’t know about because I’m not a land warfare expert or because they’re classified.  Why has no one tried to adapt any of these armor technologies to ships?  Why has no one made any effort to develop new naval armor?

Sure, some of these armor technologies may not be suitable for ships but have you even heard of a failed attempt to adapt land armor to ships?  The only adaptation of land armor that I’m aware of is Kevlar linings for use as anti-splinter protection so this can only marginally be considered armor and certainly not in the sense that we’re talking about here.  I am an expert on naval matters and I keep a close eye on naval technology and I can’t recall a single report of any naval armor research, successful or not, in modern times.

Why has the Navy totally abandoned armor research?  And why have we, the observers and commenters, accepted it?  None of us question why a Burke, the most advanced and powerful surface ship on the planet, costing over $2B, has almost no armor and thinner, weaker hull plating than a WWII Fletcher? 

Something is seriously wrong with this picture!

Wednesday, August 2, 2017

Break Up The Burkes

The Burke class destroyers are considered a marvel of modern engineering and have set the bar for all subsequent naval warship design and construction – at least, that’s the opinion of many.  The reality is that the Navy’s warship design has gotten so bad that we now consider a Burke to be “good”.  That’s lowering the bar, not setting it.

Consider, if a WWII ship designer had proposed building a cruiser size ship, which is what a Burke is, with no armor, thinner than normal hull and deck plating, and weaker than normal steel, he’d have been tossed out on his rear end and yet today we consider the Burke to be the gold standard of shipbuilding! 

This, however, is not the point of this post.  I covered that bit of historical comparison merely to set the stage for the main premise by pointing out that the Burkes are not the gold standard – they are, pathetically, the best of the worst in terms of warship design and construction.  With that in mind, we have now disposed of the fiction that the Burkes are a good design and we can move on to consideration of a better design.

To further set the stage, we all recognize the death spiral that the Navy is in.  As we try to make each ship more and more multi-functional, the ships become bigger and more expensive.  Because they are more expensive we can’t afford as many and numbers get cut.  As numbers decrease, unit costs increase and we try to compensate by making each ship even more capable and more multi-functional which further drives up the cost which further reduces the numbers which means we have to put more capability on each ship which drives up the cost which cuts numbers which … 

Ridiculously optimistic (and unfunded) projections of fleet sizes of 355 ships notwithstanding, the reality is that our combat fleet has been steadily shrinking in numbers for the last few decades and that trend shows no signs of stopping.  We have submarine and destroyer shortfalls programmed into our 30 year shipbuilding plan which, itself, is fictionally optimistic!  Our carrier fleet is steadily shrinking.  We’re down to 10 carriers and only 9 air wings.  Our logistics support and replenishment fleet is vanishing.  Our mine countermeasures ships and aircraft are nearly non-existent.  And so on.

How can we break out of this death spiral before we reach a fleet of one mega-ship?  How can we design better warships?  How are those two questions possibly related?

The answer, or at least a major portion of the answer, is the Burke.  The Burke is a poor design which is symptomatic of all that we just discussed.  It is a $2B+ (likely $3B+ for the Flt III) ship that has been designed to perform anti-air warfare (AAW), anti-surface warfare (ASuW), long range cruise missile strike, anti-submarine warfare (ASW), helo-based aviation support operations, and a host of other functions.  Thus, the Burke has lots of capabilities which makes it a flexible and powerful vessel, according to proponents.  The reality is that the very range of capabilities makes the ship of limited use. 

If the Burke is to perform AAW escort for a carrier or amphibious group then, by definition, it can’t go sailing off to perform ASW twenty or thirty miles away.  Thus, the ASW is useless.  Conversely, if the ship is performing ASW twenty or thirty miles away, it can’t provide AAW protection to a group.  Thus, the AAW is useless.  This is a long winded way of saying that one ship can’t be in two places at the same time.

Further, do you really want a $2B+ ship playing tag with a diesel-electric SSK which has all the advantages?  Do you really want to risk the most capable AAW ship in the fleet (along with the Ticonderogas which the Navy is desperately trying to early retire) to be taken away from AAW escort duties to play submarine tag and run the significant risk of being sunk?

What makes the Burke “flexible”?  In large measure, it’s the vertical launch system (VLS) which allows the ship to mix loads of Standard, ESSM, Tomahawk, and ASROC missiles.  The problem is that the more multi-purpose and flexible you make the loadout, the less capable the ship becomes in any one area.  For instance, if you opt to load 50 Tomahawks, you reduce the AAW VLS capacity to only 46 cells.  We see, then, that flexibility comes at a severe price.

So, again, how does all this relate to our death spiral solution?

The answer is to break up the Burkes.  We need to stop building multi-functional, uber destroyers and return the days when we built ships for a single specific purpose.  That’s not to say that a ship couldn’t perform multiple missions but each ship design had a clear, primary function that it was optimally designed for.

We had ASW destroyer escorts.  We had anti-ship destroyers.  We had escort cruisers.  We had strike (surface and land) battleships that also happened to be outstanding AAW escorts.  And so on.

Let’s list the Burkes main functions again.

  • AAW escort
  • Ballistic Missile Defense
  • ASW
  • ASuW
  • Long Range Strike

What would happen if we broke those functions out and allocated them to individual ships?  Here’s the separate ships/functions that would result.

AAW Escort – High value ships require dedicated AAW escorts and that’s what this ship is.  It’s a Burke minus the hanger, flight deck, ASW outfit, and cruise missile capacity.  It’s an Aegis equipped AAW barge that is “tethered” to the ships it escorts.  With no need for extra VLS cells devoted to cruise missiles, the entire VLS load is surface to air missiles (Standards and ESSM) which means we don’t need as many cells.  Burkes have 96 cells but a third or so are typically devoted to Tomahawks.  That means we can build a dedicated AAW escort with only around 60 cells and still match the Burke’s AAW capacity!

Cost.  If we take away the flight deck, hangar, and reduce the VLS capacity to around 60, we should be able to shorten the ship by around 30%.  That will make a significant cost savings.  Eliminating the ASW fit, hull mounted sonar, towed array, and torpedo tubes should save additional significant money.  Finally, the various reductions combined with the deleted helo pilots and maintenance personnel will significantly reduce the size of the crew and the associated berthing, galley space, food and water storage, waste management, and other hotel services which, in turn, further reduces the size of the ship.  Let’s put the crew size at 170 versus the standard Burke crew size of 270 or so.

Conceptually, this ship is akin to the WWII Atlanta class anti-aircraft CLAA.

Atlanta Class Anti-Aircraft CLAA

Cost.  Considering all the reductions, I’m going to put the cost of this ship at $1.1B versus the nominal $2B cost of a standard Burke.  The bulk of the cost is the Aegis/AMDR sensor fit.

ASW Escort – This ship must be cheap enough to be acquired in numbers and cheap enough to be considered expendable since ASW is a high risk mission and we’ll lose a number of these. 

Buckley Class DE
The ship will be optimized for ASW with acoustic isolation of all internal machinery, multi-frequency hull mounted sonar, towed array, variable depth sonar, Hedgehog/RBU, flight deck and hangar for two helos, ASROC launched from either the old Mk112 deck launcher or an 8-cell VLS (I’ll leave it to naval engineers to decide which is preferred – I’m thinking the old Mk112).  Additional capabilities will be short range AAW in the form of SeaRAM/CIWS and a Mk 110 57 mm gun.  Radar will be a TRS-3D or equivalent.  The ship will be around 300 ft long or less, if possible, although the flight deck/hangar probably dictates 300 ft.

Conceptually, this ship is a combination of the WWII Buckley class destroyer escort and the Spruance class ASW destroyer.

Cost.  The ship is significantly smaller than the Freedom class LCS and does not waste space on expansive flight decks or worthless high speed engineering plants.  Thus, the cost should be less than an LCS.  I’ll put the cost at $350M.

ASuW / Land Attack – This ship is a Burke without the AAW fit and somewhat fits the generic destroyer classification.  It has only a medium/short range AAW (ESSM/SeaRAM/CIWS).  Additional VLS cells carry Tomahawk cruise missiles and ASROC.  Let’s call it around 60 VLS cells.  Three to five 5” guns provide additional firepower along with 24 Harpoon/LRASM plus two dozen shorter range surface to surface Hellfire, or equivalent, missiles.  Six 21” torpedo tubes add to the surface attack capability.  Sensors are limited to TRS-4D or equivalent plus 360 degree EO/IR.  A modest ASW fit is included as a secondary function.  There are no helos or flight deck/hangar.

Conceptually, this ship is somewhat akin to a modernized Fletcher class DD.

Cost.  A Burke without AEGIS/AMDR, no flight deck, no hangar, and fewer VLS should cost around $800M.

Ballistic Missile Defense – This could either be combined with the dedicated AAW escort ship or split out as a separate ship.  In this case, as a separate ship, it would be fitted with a specific, optimized, ballistic missile defense radar like the SBX-1 Sea Based X-Band Radar and two dozen SM-3 missiles.  The ship would be a small, cheap, low performance, commercial based vessel.  It would have no flight deck/hangar/helos, no generic AAW defense other than two SeaRAM, no guns, and no ASW.

Cost.  A small, simple, minimally manned, commercial based ship would be very cheap.  Given that we can build a commercial large tanker/cargo ship for $100M or less, let’s call this ship’s cost $100M.  Of course that excludes the SBX-1 radar for which I have no cost estimate whatsoever.


We see, then, that the broken up Burke consists of the following ships:

AAW Escort                $1,100M
ASW Escort                $  350M
ASuW Land Attack          $  800M
Ballistic Missile Defense $  100M

Total Cost                $2,350M ($2.35B)

So, for the cost of a single Burke, we can build four single function ships that perform each of the single functions as well or better than a Burke and can be in four places, performing four functions at once.

Four single function ships that perform their functions better than a Burke increases the overall capability of the fleet, allows four missions to be performed simultaneously in four different locations, increases fleet size by a factor of four for each Burke not built, generates more work for the industrial base, employs more naval architects/designers/construction workers, increases fleet presence by increasing ship numbers, and reduces risk aversion by making each ship cheaper and more expendable – hence, more likely to be committed to the actual task for which they are intended.

There is overwhelming historical precedence for this from WWII.  We didn’t build single, massively multi-functional ships that were too valuable and too expensive to risk in combat.  No, we built multiple, single function ships (yes, they had secondary functions but they were built with a primary function for which they were optimized), that were affordable, could be risked in combat, increased our fleet numbers, and could be in multiple places, performing multiple tasks at the same time.

This makes overwhelming sense.  We need to drastically rethink our fleet composition and start down this distributed functionality path immediately.

Note:  No one, myself included, knows what a non-existent, conceptual ship will cost.  I’ve described how to build focused, affordable ships in previous posts and comments so I’ll stand by my cost guesstimates until something better comes along.  What I won’t do is engage in cost discussions – it would be pointless.  Even if I’m off on the numbers, the concept remains.  Maybe I’ve overestimated the costs and we can build 5 ships for 1 Burke instead of only 4 as I described.  Or, maybe we can only build 6 or 7 ships for every 2 Burkes, instead of 8.  Who cares?  The concept is valid.  Unless you are a naval procurement specialist who deals exclusively with major ship purchases and can factor in my previously described affordable acquisition practices, don’t waste my time debating costs.  It’s pointless and I won’t allow it.  If you care to discuss this post, focus on the overall concept.

Monday, July 31, 2017

Army Gets It

ComNavOps has stated repeatedly that we’ve forgotten what war is.  It’s not even debatable.  Unfortunately, the only service that has even begun to acknowledge the problem and begin preparing for real war is the Army and, interestingly, they seem to be almost frantic about doing so.  They’re desperately up-gunning vehicles and working on the entire electronic/cyber warfare problem.  In the latest example, the Army is trying to “re-field” the SMART-T satellite terminal that was designed to be resistant to jamming and electromagnetic pulses (EMP) but that was fielded and, literally, parked away and forgotten (1).

The Army is also belatedly recognizing that what they’ve developed in the past was unusable by average soldiers.

“What we’re learning after 17 years of war and multiple years out at NIE (Network Integration Evaluations), is what we have out there is far too complicated for our soldiers.” (1)

The Army is also recognizing that their dependence on highly skilled manufacturer’s representatives won’t work in combat.  The reps simply won’t be there.

“Complexity isn’t just a training problem. It’s an operational problem. Systems that only function in the hands of highly trained contractors — the term of art is Field Service Representatives, or FSRs — were awkward but workable in Afghanistan and Iraq, where US troops rotated in and out of well-established Forward Operating Bases. In a Korean crisis, Eastern European war, or Third World flare-up, US forces would have to rapidly deploy all their equipment and people, set up their networks quickly and keep them running with little or no support.”

I’ve done posts on this.  The Navy is sending ships to sea which are totally dependent on manufacturer’s reps to make systems work.  That’s horribly wrong.  If the average sailor can’t operate and maintain the system then the Navy either needs to drastically enhance its training and create super techs or they need to simplify the systems. 

The former is unlikely given that many manufacturer’s reps have spent years acquiring their knowledge and expertise and have advanced degrees.  The Navy just can’t produce that level of capability starting from an 18 year old with no particularly relevant background.

The later is unpalatable to Navy leadership which uses the promise of technology to coax Congressional funding but the alternative is systems that won’t work in combat.  Would you rather have an Aegis/AMDR that can’t be maintained or an old-fashioned revolving SPS-49 that, while limited, works flawlessly and can be maintained and repaired?

The Army is frantically trying to improve their combat capability.  I think what we’re seeing is the recognition that the Army is a lot closer to facing actual combat than the other services and suddenly they’ve woken up to the fact that they’ve been sleeping on the job for decades.  There’s nothing like the threat of actual combat and death to motivate a person or organization to weed out the unnecessary and ineffective systems!  I only wish the Navy would follow the Army’s lead and wake up.  War with China is inevitable and the Navy is still sleeping.


(1)Breaking Defense website, “Army Struggles To Streamline Its Networks For War”, Sydney J. Freedberg Jr., 24-Jul-2017,