Passages North

56 years ago, on 4 September 1954, the icebreakers USCGC Northwind and USS Burton Island completed the first transit of the Northwest passage through McClure Strait.

There has been a lot more activity in the North lately (more here and here), with the promise that if the melting continues, passages from Northern Europe to Asia may be cut by up to half (link includes a nice comparisons of the routes). The Russians expect to make some money on fees for passage and the use of their icebreakers.

There is even talk that it may substantially hurt business at the Suez Canal and allow ships to avoid pirates off Somalia. Looks like that is still a few years off since the season is very limited and only ice strengthened vessels can use the route now.

Still other people are planning ahead. China is building their second polar icebreaker and positioning itself to exploit the Arctic. Maybe a little healthy competition is the wake up call we need.

CG 1705 Mid-Air, Where was the Squawk?

The Coast Guard investigation of this mid-air collision found that ” No single factor or individual act or omission caused this mishap. It was the product of a tragic confluence of events, missed opportunities, and procedure/policy issues in an airspace where most aircraft fly under a “see-and-avoid” regime (i.e. where individual aircraft de-conflict themselves).”

The Coast Guard investigation does, however, contain considerable criticism of the action or in-action of FACSFAC San Diego, the agency that oversees this area, as does the Navy’s own investigation.

Mentioned, but receiving far less attention, under action, page 10, para 2.c., of the CG investigation, is a recommendation that the FAA consider review of regulations to more precisely define formation flight… such as requiring, “all formation aircraft squawk a discrete code unless otherwise directed.”

I would like to point out why this is critically important, why there is no reason this should not have been standard procedure, and why this single action might have made all the difference, even if FACSFAC SD had done nothing differently.

This collision involved a CG C-130 actively engaged in a SAR case that required it to repeatedly enter an airspace Warning Area, W-291, and a Marine AH-1W, Cobra gunship, call sign Vengence (V) 38, that was one of a flight of four helicopters that were “flying in formation.”

When the collision occurred, the C-130, CG 1705, was maintaining an established altitude, 1000 feet, all it’s collision avoidance lighting was on, and its transponder was activated.

The four Marine helicopters, two CH-53Es and two AH-1Ws, were practicing night combat conditions using Night Vision Devices. Only one, a AH-1 call sign V-39, in trail and to one side, was displaying full anti-collision lighting. The others were generally displaying only their position lights and they were dimmed. Their anti-collision strobe lights were not activated. Only one helo, CH-53E call sign Warhourse (WH) 53, not involved in the collision, had an active transponder, and it was never keyed to its assigned unique code. At the time of the collision it was still set to 1200, the default for aircraft in operating under visual flight rules, VFR.

Three aircraft in the flight of four were flying without their anti-collision lighting and three were flying without active transponders because they were “flying in formation” which would allow the aircraft to be treated as a single aircraft by air traffic control, for purposes of navigation and position reporting. While all four helos were supposed to be operating in close proximity, and moving as a single aircraft, in fact they were not. They was substantial separation laterally, longitudinally, and in altitude. Even as planned this flight of four was not a standard formation, and no attempt was made to clarify that the formation was non-standard. This point seems to have been missed or glossed over by the investigations.

“A standard formation is one in which a proximity of no more than 1 mile laterally or longitudinally and within 100 feet vertically from the flight leader is maintained by each wingman.” (“formation flight,” Aeronautical Information Manual–Pilot/Controller Glossary) As planned the CH-53s and the AH-1s were to have maintained a 300 ft vertical separation, meaning that this was not a standard formation, even if executed as planned, and should not have been reported as a single unit unless Air Traffic Controller had acknowledged and agreed. The planned lateral and longitudinal separation was to have been 500 feet between aircraft. I fact it was much more.

At the time of impact, the flight of four was heading 276 at 109 knots with WH53 at 900′ and V38 at 1000′. CG 1705 was heading 226 at 184 knots and 1000′. WH53 was 0.766 nautical miles directly in front of CG 1705. V39 was 1.005 nautical miles at approximately the 9 o’clock position from CG 1705. With approximately 1.3 miles separating WH53 and V38 the flight of four no longer met the definition for a standard formation in terms of proximity either.

Converging on a bearing of approximately 190 from CG1705 to the Cobra, the two aircraft covered the 5.5 miles in less than four minutes with CG1705 overtaking the darkened Cobra, with it’s low visibility paint scheme, from its starboard quarter as it climbed into the flight path of the C-130. The closing rate was approximately 82.5 knots.

The most commonly understood function of the transponder is to provide information to air traffic controllers. It is capable of enhancing the radar presentation, providing a unique code used to identify the aircraft, and in all but the least sophisticated versions, providing altitude information. But it can also provide information directly to other aircraft, if they are equipped with a Traffic Collision Avoidance System (TCAS). This system can alert other aircraft in the area of their relative bearing, proximity, relative altitude, and can recognize and provide alerts when there is a risk of collision and in some cases even provide recommendations for evasive action. The C-130 was equipped with a TCAS and it was functioning. Just seconds before the collision, the TCAS detected a danger of collision and issued a warning, apparently with regard to the only Marine helo with an active transponder, CH-53 WH53, still more than three quarter of a mile a head. CG1705’s pilot initiated a climb, apparently based on this warning, just before impact. I saw no indication if the Marine helicopters were equipped with TCAS, although if it were civilian aircraft, Their maximum takeoff weight would have required installation of one. If the mishap AH-1 had had a TCAS and it was in operation, presumably it would have alerted the pilot of the impending collision.

I understand the need to secure lights and transponders in combat. I can understand the need to practice night flying in darkened condition with lights dimmed or even off, since bright lights would adversely effect night vision devices, but I cannot understand the need to secure transponders for this exercise since presumably, it would have no impact on the execution of the mission. In prep for the mission, turn the transponder off to get in the habit, because that  is what you would do “going into combat,” but then make a conscious decision to turn it back on, because you are in a training environment.

The see-and-avoid concept works on the presumption that aircraft will want to be seen and will have lights on at night. Helicopters without lights and with paint schemes intended to minimize visual detection work against the basic presumptions. Recognizing this, the Marine helos should have made every effort, that would not have interfered with their training, to enhance detection of their aircraft. There is already provision for this, “If necessary for separation between a nonstandard formation and other aircraft assign an appropriate beacon code to each aircraft in the formation or to the first and last aircraft in trail.” (FAA JO 7110.65S)

This tragedy, as COMPACFLT noted, was entirely preventable.

Arming Merchant Ships, Yes, err–No!

An interesting bit of bureaucratic conflict here. It seems we want merchant ships carrying our cargoes off Somalia to hire armed guards on one hand, but then we make it difficult and add to the cost. There is also the question of letting armed vessels into US waters. There are many aspects to this issue, including action by the Coast Guard that was reversed.

Operation Dragoon, the Invasion of Southern France, 15 Aug. 1944

The Naval History and Heritage Command reminded those who follow it, that, today is the anniversary of Operation Dragoon, the invasion of Southern France. They featured USS Samuel Chase (APA-56), a Coast Guard manned attack transport. USS Samuel Chase also participated in the invasion of North Africa (8 Nov. 1942), the invasion of Sicily (10 July 1943), the invasion of Italy at Salerno (9 Sept. 1943), and the Normandy invasion (6 June 1944). She also managed to spend some time off Okinawa after the invasion while kamikazes were still a danger (24 July-10 Aug. 1945). She was also used for Operation “Magic Carpet” the return of American service men to US.

——————————————–
8 new photos

——————————————–

There were probably a number of other Coast Guard and Coast Guard manned ships involved in Operation Dragoon as well. One, the 327, USCGC Duane (WPG-33/WAGC-6/WHEC-33) (my old ship) served as flag ship of one of the six Naval Task Forces.

More on Operation Dragoon here.

Hovercraft

It has been quite a while since the Coast Guard tried using hovercraft. It may be time to have another look. Here is an interesting video (sales pitch) about how other services are using hovercraft. Many of the users in the video are in areas where ice and snow covered surfaces are common. With the Arctic opening up, there might be a place for these craft there.

The Indian Coast Guard has had some experience with these craft and have decided to triple their fleet to 18 craft.

Not that we would want them everywhere, but perhaps for some environments, they would be just what we need.

USCGC Spencer (WPG/WAGC/WHEC-36) Legacy

Nice piece about the current Spencer (WMEC- 905) honoring a sailor from the previous Spencer (WPG/WAGC/WHEC-36).

The earlier Spencer was unique in Coast Guard history, in that she is believed to have sunk at least two U-boats.

For some excellent photos of all seven of the 327s, from construction through the end of World War II, the Coast Guard Historian has a nice collection of photos with commentary showing their changing configuration.

National Security Cutter as Navy Patrol Frigate

Navy Times’ “Scoop Deck” asks what the Navy will do “After the frigates are gone” and suggest that variants of the National Security Cutter (NSC) might be a better solution than the Littoral Combat Ship (LSC).

Back in March, Defense News also suggested that the NSC might be the Navy’s best option.

This has been an on going discussion for a long time, fueled no doubt by Northop Grumman’s desire to sell more ships. But the suggestion has been taken seriously. In July 2009, the Congressional Budget Office Study did a study that included an upgraded 20 NSCs as an option to 25 of the LCS.

That study suggested that these 20 NSCs be upgraded as follows:

“For approximately $260 million, the Navy could replace the Close-In Weapon System (CIWS) currently used on the national security cutter with the SeaRAM Mk-15 CIWS. Unlike the former system, which consists of a rapid-firing gun designed to engage subsonic antiship missiles at close ranges, the SeaRAM CIWS would incorporate a rolling airframe missile on the same physical space but provide the ship with the ability to engage supersonic antiship cruise missiles out to 5 nautical miles. The SeaRAM system includes its own sensor suite—a Ku band radar and forward-looking infrared imaging system— to detect, track, and destroy incoming missiles.

“An additional layer of antiship missile defense could be provided by installing the Mk-56 vertical launch system with Evolved Sea Sparrow Missiles (ESSMs) along with an Mk-9 Tracker/Illuminator system to detect, track, and engage antiship missiles. The ESSM can engage supersonic antiship missiles at a range of nearly 30 nautical miles. Installing 20 sets of a 12-cell launching system (which would carry 24ESSMs), buying the missiles, and integrating the weapons with the ships would cost about $1.1billion.”

So these upgrades would cost $1.360B/20 ships or $68M/ship

With many more critics than supporters, there is a lot speculation that the Navy will not build anywhere near the 55 LCSs currently planned. The black-eye lean manning is getting in the Navy lately, and the fact that the LCSs are designed for lean manning with no apparent option for growing the crew, is adding to criticism of its limited weapons and poor endurance. The Coast Guard is looking smart for providing the NSCs and OPCs with both realistic crews and room for growth.

If the government wanted to open an option for the future, it might be smart to increase the CG buy of NSCs to 12, to make up some of the shortage of ship days that is certainly in our future and direct that the last 6 be made as a “B” class with a weapons fit including the systems sited above, a towed array sonar, and all necessary space and equipment for support of two MH-60Fs, with the marginal cost paid out of the Navy budget. The nation would have an additional capability and the Navy would have have a ready option in a mature design, that could take on the functions of the FFGs.

A Relatively Painless Submarine Detection Capability

If the Coast Guard should ever again decide it needs a submarine detection capability, there may be a way to add it to vessels as small as the 87 ft WPBs.

The Navy is currently fielding a new version of it’s  ASW helicopter, the MH-60R, and it’s new dipping sonar is proving much more effective than it’s predecessor.  The complete sonar system can weigh less than 600 pounds.

The Soviets also used dipping sonars, but not just on helicopters. They used them on small surface craft as well. These vessels would work in teams using a sprint and drift tactic.

The same transducer might also be hull mounted with relatively little impact. There is also the possibility that with relatively minor modifications it could be made into a towed variable depth sonar. A combination of hull mounted transducer and variable depth sonar working off the same console could offer some advantages.

Certainly not very effective for chasing nucs, and I’m not suggesting we need a big program to  look for Narco subs, but, should the need arise, it could be work against the ultra quiet but slow moving diesel electric subs that might lurk in the high noise areas of the littorals.