Seafighters Will Never Operate In A Logistics-Free World

Every QDR season, Wayne Hughes rousts himself from his Naval Postgraduate School hideout and mounts a push for his beloved teeny-tiny combatant–the “Seafighter”.  His latest, “Sustaining American Maritime Influence,” published in the September 2013 USNI Proceedings, is his usual salesman-like effort (in which he is joined by retired Admiral John Harvey, NPS Operations Research heavy-hitter, the retired Captain Jeffrey Kline, and LT Zachary Schwartz, USN) to get small craft onto the national security agenda.

Hughes’ small ship advocacy has worked–at least to a point. Small LCS-like ships are coming into vogue, yet it is fairly obvious–after perusing his repeated calls for ever-smaller ships–that Hughes thinks LCS, in its current guise, is too big, too pricey and too sophisticated. But his subsequent proposals for ever-smaller ships really risk falling flat because his “tiny ship” argument does not work without simultaneous reinvestment/recapitalization of a much-maligned and costly ship class–the surface-ship tender. (Our gallant cadre of accountant-minded warfighters killed those poor ships off by the early 2000s)

But Hughes, in his sales pitches, doesn’t have much time for tenders. He stays firmly with the sexy and superficial to make his pro-small-ship argument. After all, the Seafighter concept is a seductive “transformational” idea, tuned to catch notice of Congress and defense reformers–small ships are cheap. They can be built in numbers. And in numbers, they offer flexibility. They are wonderful engagement tools. They are now seen as an “alternative” to LCS. Fine. And he’s correct. But there’s just one big problem.

Logistics.

For a forward-deployed Navy, any small-ship scheme–well, any small ship scheme that has aspirations to be more than a coast-bound, Soviet-like homeland defense force–must be logistically supportable. That’s where Hughes and his fellow small-ship boosters run into heavy weather. Once sufficient logistical support is added to any small ship scheme, the economic savings vanish, and we end up generating a host of battlefield problems that Hughes and Kline simply refuse to analyze (in one larger study–recasting the entire Navy as an almost entirely small-craft affair–discussion of the logistical implications and subsequent cost–was just, well, not included).

There’s a big, fat, fiscal reason why tenders were some of the first to be ushered out of the arsenal. The ships were pricey, the crews large and costly, and you had to guarantee a sufficient level of forward operations to make the ships worth their while.

Now, the fact that the NPS Operations crowd comes back, year after year proposing the same concept is admirable, but their refusal–or, frankly, their inability–to address the gaping logistical holes their small-ship argument does the Navy academic community a disservice.  So here’s my message to that crowd: Reorient your small ship advocacy towards explaining logistical requirements needed for small-craft forward operations.

And, mind you, this is coming from somebody who likes Wayne and loves small ships.

First, Small ships don’t operate in a vacuum, and they certainly will not operate forward or be ready for action without refueling capability, ready resupply and maintenance. Think about it. Pick up any book about PT boat operations. Consider the ample shore establishment and fleet train those ships needed back in World War II.

The second reason why we need to have a discussion is this: Nobody knows what they want in a tender. It’s fairly obvious Hughes originally didn’t want just any old cobbled-together auxiliary. Here’s what he wanted back in 2000, in the USNI Proceedings article, “21 Questions for Seafighter”:

“The smaller model [streetfighter] should be sized so that a high-speed mother ship can carry six or eight.  The upper limit is therefore around 300 tons, and the craft must be configured to launch and recover in an open sea.  The crew should be small, so crew endurance is probably going to be the limiting factor on mission time.  Habitability, sustainment and replacement crews must reside in the mother ship.  Aircraft would have to be based within the mother ship, too, thus limiting the radius of action of the small streetfighter for some tasks.

Larger versions of, say, 1,200 tons would have to transit under their own power to their operating theaters and be followed closely by a tender for support….a potential convenience is that six spare destroyer tenders already exist for their support. On the other hand, aircraft carried by the 1,200 ton streetfighters would need support by the tender or an accompanying air-capable ship.”

Okay.  Aside from the fact that Hughes probably knew that four of the six available destroyer tenders had been struck the year before (the Shenandoah, Cape Cod, Yellowstone and Samuel Gompers), it’s pretty clear Hughes was interested in a gold-plated auxiliary.  Look at the language–”fast” ,”air-capable”, “launch and recover in an open sea”.  Even then, Hughes knew that this LHA/T-AOE/AD/MLP hybrid was going to be far more expensive than the $500 million he suggests as a tender price-point.

But Hughes is not alone. We do not have a good model for tenders.  Frankly, I’m really vexed that we are poised to decommission some of our fast T-AOEs (yes, I know there is a sound engineering reason for that move), and I think the MLP offers all kinds of interesting options that we have yet to fully explore. Logistical ships have been overlooked for far too long, and we must do more to discuss and study them.

My third reason I wish to have wider consideration of auxiliaries is that auxiliaries are entering the fleet! We are ushering MLPs and JHSVs into service and about to design a T-AO(X) for mass production. If small ships can leverage these platforms, or if small ships demand a larger T-AO(X) block buy for support, then the National Security community needs to know now.

Unfortunately, small ship advocates are soft-pedaling their support requirements. Rather than engage in a frank discussion of floating logistical support, small-ship proponents use a fall-back strategy–an impressively simple solution called (you guessed it!) shore-basing.

In Hughes’ 2000 article, that strategy was detailed in one sentence:

“Whenever operations are near a friendly state, a small, prepackaged, transportable shore facility is an alternative.”

In Hughes’ latest act of small ship advocacy, he acknowledges the price of logistical support, but, in the end, he takes pretty much the same tack:

“When they [Seafighters] operated independently in coastal waters, then tender support was conjectured. Exploratory tender support for a large flotilla of 100 missile ships located in many places was disturbingly expensive in manpower and construction costs.

However, we believe our previously outlined worldwide survey—as well as the clearly attractive current Navy plans to base the LCS overseas in Singapore—demonstrates that in real-world circumstances we will usually be collaborating with a state where the ships can be supported ashore. Tender services might be desirable for out-of-the-way places, and so the personnel costs of two or three interim alternatives—to include auxiliary ships or amphibious-assault ships such as the USS Ponce (LPD-15)—should be included in the cost of deploying flotilla squadrons.”

The LCS deployment to Singapore was a bit of a wakeup call. We’ve forgotten that any forward-basing scheme that relies upon host-nation resources is a tough task rife with lots of opportunities for error. With Glen Defense Marine Asia, we learned that lesson–in spades. Aside from the fact that the LCS’s husbanding agent is under investigation for corruption, we are still struggling mightily with the logistical challenge of getting spares, techs and other items into another country in a timely fashion. The cost and delay stemming from customs, export control, security requirements and other issues make forward-deployment a personnel-heavy challenge. For persnickety combatants, it’s a lot easier to have a ship at the pier full of spares, techs and back-up crews dedicated to the task at hand.  (My offhand thought is to take most of the LCSron folks in San Diego and put ‘em all on a tender.)

(A tender also helps grant small ships an added measure of flexibility–I won’t even get into how geopolitics could, at a time of tension, break war plans that depend upon forward-basing schemes to work.)

Yes, other ships do manage to operate forward. There are plenty of success stories out there. But maintaining a solid old T-AO forward is one thing, while maintaining a bunch of new “yet-to-work-out-the-kinks” combatants is something else entirely.

At a minimum, a tender would have made the LCS introduction to forward-basing go far more smoothly. I mean, why have our current shore-basing options in the Gulf–the some ones we cite today as a rationale for “more” forward basing–worked so well?

Those arrangements go smoothly because, twenty years ago, the U.S. Navy brought in tenders, and used those as bases to help develop trusted relationships, a means for engaging local shore support establishment, support protocols and so forth.

With new auxiliaries coming on-line and the current “small ship” showpiece struggling to “win” a forward deployment, it would be far more useful for small ship advocates to take a new tack, and start exploring how to best enable forward operation of small craft. Stop indulging in another set of long, well-trodden discussions of small-ship capabilities, costs and other minutiae. Let’s figure out what we need to do logistically to enable small ships.

I’ll be blunt: if those small ships cannot reliably operate forward, then all the effort Hughes and his friends put into promoting small-ship Seafighter design, armament schemes and operational doctrine means nothing.

This article is cross posted with permission from Craig Hooper‘s blog, http://nextnavy.com/

Israeli Private Security in the Suez Canal?

By Jasen Sagman

Suez Canal Authority HQ in Ismailia, Egypt
Suez Canal Authority HQ in Ismailia, Egypt

Egypt’s military-backed government recently dismissed reports that Egypt’s Suez Canal Authority (SCA) has hired Israeli private security company Seagull Maritime Security to guard the vital waterway.

Reports began to circulate on local social media early several weeks ago, with cyber-activists citing the company’s website as saying that Seagull was capable of embarking/disembarking armed guards at locations, all approved of by the local government authorities, including Suez, Egypt.

According to a subsequent SCA statement, the reports “are categorically devoid of truth… and aim to shake security and spread false news,” however a report by the Arab Organisation for Human Rights recently revealed that the security company provides maritime security services for cruises and cargo ships passing through the Suez Canal in Egypt.

In fact, the Egyptian authorities have granted the company a license to work in the Suez Canal and the Red Sea. Additionally, the company is authorized to work in Arab and African ports including Jordan, UAE, and Oman. According to the report, the company is one of the few whose guards are allowed to disembark fully armed on the Egyptian island of Tiran.

The company is a member of the Israeli Association of Private Security Companies, and was founded by its CEO Kfir Magen, who served as an officer in the Israeli navy. The company’s directors were prominent leaders of the Israeli armed forces, including Eliezer Marom who served as a navy commander between 2007 until 2011. The company’s advisory board chairman, Ami Ayalon, served as commander in chief of the navy in 1992, and served as head of the Shin Bet in 1996.

Despite the report, the SCA maintains that the Suez Canal is secured exclusively by Egyptian police and army forces.

Jasen Sagman is pursuing an M.A. in Global Diplomacy from the University of London, SOAS. He works for a Member of Parliament in Ottawa, and holds an Honours B.A. in Political Science from the University of Toronto. This post appeared in its original form at the Atlantic Council of Canada.

A Look at Corvettes and Air Defense

Corvettes, unlike offshore patrol vessels are meant for wartime use without major upgrades.  Their status as warships requires a satisfactory level of survivability against at the very least, common threats.

The design objectives for Corvettes, in regard to anti air warfare (AAW), is typically limited to self-defense. A typical self-defense suite as mounted on German K130 corvettes consist of a 76 mm rapid fire gun, rolling airframe missiles (RAM, short-range air defense / point defense), 27 mm auto-cannons and soft kill countermeasures. The shaping of the hull and superstructure indicates a moderate reduction in radar cross-section and some reduction in infra-red signatures was attempted as well.

This kind of defensive package can be effective against incoming missiles (preferably subsonic ones) and low-flying combat aircraft (threats similar to those the Royal Navy faced in the Falklands).

These aren’t the only common aerial threats, though: There are also guided bombs, specifically laser, TV and infrared guided bombs which cost so very little that a rolling airframe missile (of which only few dozen are on board anyway) costs more.

ASBThe U.S. Air Force demonstrated recently its ability to bomb a speedboat at speed with a laser guided bomb from high altitude, scoring a direct hit. Other munitions, meant for pinpoint attacks on land vehicles, could target and destroy the RAM launcher or the 76 mm gun from beyond their effective range, exposing the ships to almost unrestricted iron bomb attacks.

The proliferation of laser guided bombs since their invention during the Vietnam War leaves no choice but to consider them as a common threat munitions, and corvettes need to be survivable in face of this threat. This leaves but three options:

  • Avoid being targeted, for example by disguising as a civilian ship
  • Stay under the protective umbrella of a AAW frigate, AAW destroyer or a permanent and reliable combat air patrol
  • At the very least carry surface to air missiles with a high effective ceiling into a warzone, even if onboard electronics do not permit to exploit their full performance envelope without external support.

Point (3) deserves an elaboration: In theory a corvette in a picket role could serve as an area air defence missile launcher, cooperating with a separate search and fire control unit such as an AEW&C aircraft as long as the missile doesn’t require shipboard support during flight. The corvette itself does not need illumination systems if the missile seeker isn’t employing semi active radar homing and it doesn’t need an area radar search capability if it enjoys the benefits of a datalink to an AEW or AAW platform. Finally, it doesn’t need to possess a sophisticated AAW control centre, as its fire control can be done remotely, using cooperative engagement capability (CEC). If the Corvette and the controlling unit are equipped with this capability, the Corvette needs only a few vertical launch silos to be able to engage the attacking aircraft rather than weapons it drops.

Corvettes are of course not intended for employment as task force ships, but the destroyer escorts of 1944 weren’t intended to fight against battleships in defence of escort aircraft carriers either (Battle of Samar, ’44).

“Sven Ortmann is a German blogger. Since begun in 2007, his blog, “Defence and Freedom,” has covered a range of military, defence policy and economic topics, with more than a million page views. His personal military background is his service in the Luftwaffe. He has guest-blogged at the Small Wars Journal Blog and other blogs on military topics.  http://defense-and-freedom.blogspot.com/

Offshore Patrol Cutters (OPC), the Other LCS

The US Coast Guard is currently in the first part or a two part program to select a design for a planned class of 25 ships referred to as Offshore Patrol Cutters (OPC) also called the Maritime Security Cutter, Medium (WMSM). In many respects these might be thought of a third class of Littoral Combat Ships. They have different characteristics and different strengths and weaknesses, but there is considerable overlap in there characteristics. Like the LCS they will be small, shallow draft, helicopter equipped warships with the 57mm Mk110 gun. It seems likely the OPC will be 2,500 to 3,500 tons, similar in size to the Freedom and Independence class LCS.

The only information we have on Huntington Ingalls’ concept for the OPC is this photo tacked onto the end of a DefenseNews.Com report.

The existing LCS classes emphasize adaptability, are faster and have more spacious aviation facilities. The cutters will emphasize seakeeping and will:

  • have greater range (minimum 7,500 miles @14 knots) and endurance using all diesel propulsion. Typical operations as outlined in the Concept of Operations (CONOPS) were 14 days between refueling, 21 days between replenishment, and 45-60 day patrols.
  • be ice-strengthened,
  • have ballistic protection over critical areas,
  • have a larger crew, and
  • be able to operate their boats and aircraft in higher sea states (through sea state 5).

Illustration from Bollinger Shipyards

The acquisition process:

A two step Acquisition process is being used. First, up to three contractors will be selected to develop their concepts into fully detailed contract proposals. This selection is expected by the end of the second quarter of FY2014. These three will then compete for a contract which will include all documentation, construction of the first OPC (expected delivery in FY2020) and options for up to ten follow-on ships.

Eight yards have submitted bids:

  • Bollinger Shipyards, Lockport, La.
  • Eastern Shipbuilding, Panama City, Fla.
  • General Dynamics Bath Iron Works, Bath, Maine
  • General Dynamics Nassco, San Diego
  • Huntington Ingalls Industries, Pascagoula, Miss.
  • Marinette Marine, Marinette, Wis.
  • Vigor Shipyards, Seattle; and
  • VT Halter Marine, Pascagoula, Miss.

There has been international interest in the project. VT Halter has partnered with French Defense Contractor DCNS. Vigor is allied with Ulstein, Bollinger is working with Dutch Ship builder Damen. It appears Eastern may have teamed with STX (supposition on my part, based only on their concept‘s similarity to the New Zealand Navy’s Protector Class OPV.

VT Halter Marine, Inc. (VT Halter Marine), a subsidiary of VT Systems, Inc. (VT Systems), today announced its partnership agreement with DCNS to submit a proposal to the Department of Homeland Security (DHS) for the design and construction of the U.S. Coast Guard (USCG) Offshore Patrol Cutter (OPC). VT Halter Marine will be the prime contractor and DCNS will be its exclusive subcontractor for the OPC platform design.

An early DCNS concept

The funding schedule is expected to look like this:

  • FY 2016 Detail Design
  • FY 2017 OPC #1 Construction
  • FY 2018 OPC #2
  • FY 2019 OPC #3
  • FY 2020 OPC #4 and #5
  • FY 2021 OPC #6 and #7
  • FY 2022 OPC #8 and #9
  • FY 2023 OPC #10 and #11

There was also a statement of intent to hold the maximum price of units four through nine to $310M each.

Specifications:

The ships are to be built to modified American Bureau of Shipping Naval Ship Rules excluding explosive or underwater shock hardening.

They are expected to operate in cold climates. They will be equipped “to operate in areas of broken plate, pancake, and sea ice ranging from 10 to 30 inches thick.”  There is also a required capability to operate an ice capable small boat and to have automated topside de-icers.

“The WMSM will provide increased protection for (sic.) small caliber weapons and shrapnel fragmentation around the bridge, CIC, and magazine spaces.”

It will tow up to 10,000 tons.

The ships are expected to be able to do Fueling at Sea (FAS), Replenishment at Sea (RAS), Vertical (Helicopter) Replenishment or VERTREP, and to refuel smaller vessels (apparently reflecting an expectation of sustained operations with smaller patrol vessels (WPCs or WPBs) at locations remote from their bases).

I did not have access to the latest specifications, but have deduced some details of the proposed equipment from the Allowance Equipage List included in the Draft RFP. All the systems below are referenced. (In a few cases there may be duplicate listing if different nomenclature is used for the same system.) The outfit, in most respects, repeats or even improves on that of the National Security Cutter:

Communications:

  • Military SAT com
  • Tactical Data Link System
  • IFF
  • SBU (presumably “Sensitive but Unclassified”) Network
  • SIPRNET (Classified Network)
  • NIPRNET (Unclassified Network)
  • Entertainment System

Sensors:

  • TSR-3D RARAD System, a multimode surface and air surveillance and target acquisition radar
  • Electro-Optic/Infrared Sensor system
  • RADIAC

Weapons:

  • Mk 48 mod 1 Gun Weapon System (pdf), which includes the Mk 110 57mm gun, AN/SPQ-9B  Surface search and Fire Control Radar, Electro-Optical sensor system Mk 20 mod 0, the Mk 160 GCS Mod 12, and Mk 12 Gun Computer System
  • Mk 15 mod 21-25 CIWS (Phalanx) (apparently equipped for but not with)
  • Mk 38 mod 2 25 mm
  • Gun Weapon System SSAM (remotely controlled stabilized .50 cal)
  • Four crew served .50 mounts including Mk 16 and Mk 93 mod 0 or mod 4 mounts
  • Mk 46 optical sight

Electronic Warfare:

  • Mk 53 Decoy launcher
  • AN/SLQ-32 (v)2

Navigation:

  • Encrypted GPS
  • Electronic Chart Display and Information System

Intelligence:

  • Ships Signals Exploitation Space
  • Special Purpose Intel System

Aviation:

  • Hangar for helicopter up to and including Navy and Coast Guard H-60s (There may have been some backtracking on the requirement for a helicopter larger than the HH-65)
  • Facilities for the support of unmanned Aerial Systems (UAS)
  • TACAN
  • Visual Landing Aids

Coast Guard HH-65 Dolphins

Unresolved

Having watched this program develop over a number of years, it is remarkable that the specifications have moved from specific to general as the need to minimize cost has resulted in softening of the requirements. As with many contracts, threshold and objective characteristics were defined, but if there are incentives for going beyond threshold requirements, they have not been made public. For this reason there seems little reason to expect the capabilities to exceed the threshold requirement which include a speed of 22 knots (objective 25).

The aviation support requirements also seem to have gone soft and may result in the ability to support only smaller helicopters and UAVs

Potential Naval Roles

Weapons–A minimal projected fit has been identified, but the Commandant has stated that the ships will have space and weight reservation for additional weapons, but I have not been privy to the extent of this reservation. It may be limited to replacing the Mk38mod2 with a Phalanx, but there is reason to hope the ships have greater potential.

The ships do have an unusual specification. For the Alien Migrant Interdiction Operations, they are required to be able to feed and provide basic shelter for up to 500 migrants for 48 hours, all while keeping them on the main deck or above.  This actually constitutes a substantial weight/moment reserve for other missions. If we assumed 150 pounds for each person, that would equate to 37.5 tons.

Modules–While there was apparently no stated requirement to host mission modules or containers in the specifications, some of the foreign designed potential contenders may already include provision for taking containers. For instance, the Damen designed OPV 2600 (ton) has provision for five 20 foot containers. Others may use containers as part of their plan to meet the 500 Alien Migrant holding requirement.

Vigor Offshore Patrol Craft 01

Vigor concept with its Ulstein X-bow. It was reported to have a length of 328 feet, a beam of 54 feet, a draft of 16.5 feet, and a max speed of 22knots. It included a reconfigurable boat hangar.

Manning:

The Coast Guard’s latest Manpower Estimate for the Offshore Patrol Cutters (OPCs), completed 18 March 2011, was 104 (15 officers, 9 CPOs, 80 E-6 and below) plus an aviation detachment (five personnel) and Ship’s Signals Exploitation Space (SSES) detachment (seven personnel) for a total of 116. Accommodations are planned for at least 120 (threshold requirement) and hopefully as many as 126 (“objective”). The manning assumes four section underway watches.

Unlike the two current LCS classes, the OPCs are expected to train junior personnel: “The Coast Guard depends on cutters to expose our junior personnel, officers and enlisted, to our wide mission set. With this real world experience derived from a first tour operational assignment, these sailors populate critical billets such as law enforcement detachments, independent duty corpsmen, and XOs on patrol boats.”

These ships, like the LCS are expected to have multiple crews, with four crews for a group of three ships, allowing them to operate up to 225-230 days away from home port per year. (I personally don’t like the concept as proposed)

Survivability: The preliminary manning documents assumes that two full Repair Lockers (27 crew members in each locker) plus a Rapid Response Team (RRT) will be constituted for General Emergency Situations, but only one full Repair Locker and the RRT will be available at General Quarters. Two engine rooms will provide a degree of propulsion redundancy.

LCS Council:

The CNO saw the need for high level coordination of the introduction of the LCS to insure that they made the most of their potential. Since established they have added oversight of the Joint High Speed Vessels.

I see a need for the Coast Guard to also have a seat the Council to

  • share experiences with multiple crewing and other lessons learned
  • maximize the wartime potential of the Offshore Patrol Cutters by exploiting commonality with the LCS
  • ease coordination of Navy’s LCS and JHSVs partnership station, drug interdiction, and constabulary efforts which often involving Coast Guard detachments.

LCS 2.0, or a Missed opportunity?:

I keep hearing that many, including former undersecretary Bob Work, may not be entirely happy with the characteristics of the existing LCS designs, but that because they are the design we have, we should continue to build them. I have hoped that the Offshore Patrol Cutters would offer a possible alternative for an LCS 2.0. It may be that cost considerations and program choices will make them unsuitable, but at the very least, the eight design proposals and the three fully developed contract proposals should make interesting reading for those who would like to consider alternatives to the existing designs.

In addition, these ships, or designs developed from them, may offer a cheaper alternative basis upon which to offer our allies interested in American built corvettes or OPVs.

If I had my druthers:

If I had my druthers these ships would be designed, but not necessarily equipped, from the start, for wartime roles including ASW and NSFS.

Background: “What might Coast Guard cutters do in wartime.”

Chuck Hill blogs at http://chuckhillscgblog.net/. He retired from the Coast Guard after 22 years service. Assignments included four ships, Rescue Coordination Center New Orleans, CG HQ, Fleet Training Group San Diego, Naval War College, and Maritime Defense Zone Pacific/Pacific Area Ops/Readiness/Plans. Along the way he became the first Coast Guard officer to complete the Tactical Action Officer (TAO) course and also completed the Naval Control of Shipping course. He has had a life long interest in naval ships and history.

Fostering the Discussion on Securing the Seas.