USS Independence (LCS-2)

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

USS Independence LCS-2 at pierce (cropped).jpg
Independence at Key West, Florida
History
United States
Name: USS Independence
Awarded: 14 October 2005[1]
Builder: Austal USA[1]
Laid down: 19 January 2006[1]
Launched: 26 April 2008[1]
Christened: 4 October 2008
Commissioned: 16 January 2010[2]
Homeport: San Diego[1]
Identification: LCS-2
Status: in active service, as of 2024
Badge: USS Independence LCS2 COA.png
General characteristics
Class & type: Independence-class littoral combat ship
Displacement: 2,307 metric tons light, 3,104 metric tons full, 797 metric tons deadweight[1]
Length: 127.4 m (418 ft)[1]
Beam: 31.6 m (104 ft)[1]
Draft: 14 ft (4.27 m)[1]
Propulsion: MTU Friedrichshafen 20V 8000 Series diesel engines, 2× General Electric LM2500 gas turbines,[3] 2× American VULKAN light weight multiple-section carbon fiber propulsion shaftlines, 4× Wärtsilä waterjets,[4] retractable bow-mounted azimuth thruster, 4× diesel generators
Speed: 44 knots (51 mph; 81 km/h)[5]
Range: 4,300 nm at 18 knots[6]
Capacity: 210 t (210 long tons; 230 short tons)
Complement: 43 core crew (11 officers, 32 enlisted) plus up to 35 mission crew
Sensors and
processing systems:
Electronic warfare
& decoys:
Armament:
Aircraft carried:
Helicopter facilities and the mission bay dominate the stern of the Independence class
Rear view of USS Independence approaches Mayport, Florida, showing Evolved SeaRAM on hangar roof.
Side view of USS Independence

USS Independence (LCS-2) is the lead ship of the Independence-class littoral combat ship. She is the sixth ship of the United States Navy to be named for the concept of independence. The design was produced by the General Dynamics consortium for the Navy's LCS program, and competes with the Lockheed Martin-designed Freedom variant.[10]

Independence, delivered to the Navy at the end of 2009, is a high-speed, small-crew corvette (although the U.S. Navy does not use the term) intended for operation in the littoral zone. She can swap out various systems to take on various missions, including finding and destroying mines, hunting submarines in and near shallow water, and fighting small boats (she is not intended to fight warships). The ship is a trimaran design with a wide beam above the waterline that supports a larger flight deck than those of the Navy's much larger destroyers and cruisers, as well as a large hangar and a similarly large mission bay below. The trimaran hull also exhibits low hydrodynamic drag, allowing efficient operation on two diesel-powered water jets at speeds up to 18 knots (33 km/h; 21 mph), and high-speed operation on two gas turbine-powered water jets at a sustainable 44 knots (81 km/h; 51 mph) and even faster for short periods.

Description

The design for Independence is based on a high-speed trimaran (Benchijigua Express) hull built by Austal (Henderson, Australia). The 418 feet (127 m) surface combatant design requires a crew of 43 sailors.

With 11,000 cubic metres (390,000 cu ft) of payload volume, she was designed to carry two mission modules, allowing the ship to do multiple missions without having to be refitted. The flight deck, 1,030 m2 (11,100 sq ft), can support two SH-60 Seahawk helicopters, multiple UAVs, or one CH-53 Sea Stallion-class helicopter. The trimaran hull will allow flight operations up to sea state 5.[11]

Independence carries a default armament for self-defense, and command and control. Unlike traditional combatants with fixed armament such as guns and missiles, tailored mission modules can be configured for one mission package at a time. Modules may consist of manned aircraft, unmanned vehicles, off-board sensors, or mission-manning detachments.

The interior volume and payload is greater than some destroyers, allowing the ship to serve as a high-speed transport and maneuver platform. The 15,200 square feet (1,410 m2) mission bay takes up most of the deck below the hangar and flight deck.

In addition to cargo or container-sized mission modules, the bay can carry four lanes of multiple Strykers, armored Humvees, and their associated troops. An elevator allows air transport of packages the size of a 20-foot-long (6.1 m) shipping container that can be moved into the mission bay while at sea. A side access ramp allows for vehicle roll-on/roll-off loading to a dock and would have allowed the ship to transport the cancelled Expeditionary Fighting Vehicle.[12]

Bunks and living spaces are below the bridge. The helm is controlled by joysticks instead of traditional steering wheels.[13]

Independence also has an integrated LOS Mast, Sea Giraffe 3D radar and SeaStar Safire FLIR. Side and forward surfaces are angled to reduce the ship's radar profile. In addition, H-60-series helicopters provide airlift, rescue, anti-submarine, radar picket and anti-ship capabilities with torpedoes and missiles.

The Raytheon Evolved SeaRAM missile defense system is installed on the hangar roof. The SeaRAM combines the sensors of the Phalanx 1B close-in weapon system with an 11-missile launcher for the Rolling Airframe Missile (RAM), creating an autonomous system.[14]

Northrop Grumman has demonstrated sensor fusion of on and off-board systems in the Integrated Combat Management System (ICMS) used on Independence.[15]

Independence has an Interior Communications Center that can be curtained off from the rest of bridge, instead of the heavily protected Combat Information Center found on other Navy warships.[16]

Austal claims that Independence will use one-third less fuel than Freedom, but the Congressional Budget Office found that fuel would account for 18 percent or less of the total lifetime cost of Freedom. While it was unable to judge the fuel usage of Independence, the higher purchase price of Independence would dominate her lifetime costs.[17]

History

The contract was awarded to General Dynamics in July 2003.[18] The contract to build her was then awarded to Austal USA of Mobile, Alabama, on 14 October 2005 and her keel was laid down on 19 January 2006. Delivery to the United States Navy was scheduled for December 2008.

The originally planned second General Dynamics ship (LCS-4) was canceled on 1 November 2007.[19] On 1 May 2009, a second vessel was reordered by the Navy, USS Coronado. The keel was laid on 17 December 2009,[20] with delivery scheduled for May 2012.[21] It was delivered 27 September 2013.[22]

For fiscal year 2010, the Navy planned a competition between Lockheed Martin and General Dynamics for the next three littoral combat ships, with the winner building two ships and the loser only one.[23] Independence was christened 5 October 2008 by Doreen Scott, wife of 10th Master Chief Petty Officer of the Navy Terry D. Scott.[24]

Navy leaders said that the fixed price competition offered the Austal design an equal shot, in spite of its excess size and cost and limited service.[25] In June 2009, the development and construction of Independence was 220% over-budget. The total projected cost for the ship was $704 million. The Navy had originally projected the cost at $220 million.[26] Independence began builder's trials near Mobile, Alabama on 2 July 2009, three days behind schedule because of maintenance issues.[27]

In response to problems with the propulsion plant (the port gas turbine shaft seal sprang a leak), General Dynamics rearranged builder's trials to test other systems until this was fixed.[28] The ship completed builder's trials on 21 October 2009[29] and acceptance trials on 19 November 2009.[30]

On 9 December 2009, the Navy announced that the ship had completed its first INSURV inspection. The inspection found 2,080 discrepancies, including 39 high-priority deficiencies, but concluded that all could be resolved before the Navy accepts the ship as scheduled. The ship was delivered to the Navy on 17 December 2009, and the service officially accepted it the next day.[20] However, the ship was found to be incomplete and a second round of acceptance trials was scheduled for 2011.[31]

The ship was commissioned on 16 January 2010 at Mobile, Alabama[32] and completed her maiden voyage in April 2010.[33]

In 2010, the Navy asked for an additional $5.3 million to correct problems found in the sea trials.[34] Galvanic corrosion caused by an aluminum hull in contact with the stainless steel propulsion system with sea water acting as an electrolyte, and electrical currents not fully isolated, caused "aggressive corrosion."[35][36] Prior to the discovery of corrosion, Austal and General Dynamics had both agreed to dissolve their relationship with each other and agree to act as competitors in March.[37] The cause of the split was due to the planned competition between Lockheed Martin and General Dynamics.[37] Prior to the split, General Dynamics was to continue maintenance on the ship after it entered service.[38] In 2011 the corrosion problem was found to be even worse than expected and repair would require time in a drydock to completely remove the water jets.[35] In response, Austal blamed the U.S. Navy for not properly maintaining the ship.[39][40] However the Navy replied that the electrical insulation had been improperly installed during construction.[41] Later Austal said it had found a fix for the problem that would be tested on the third Austal LCS ship.[42] In 2011, seven U.S. senators sent a letter to the Department of Defense questioning the management of the corrosion problems of Independence.[43] In July 2011, Navy Public Information Officer Christopher G. Johnson said that a "cathodic protection system" would be installed on the ship.[44] Such systems generally consist of strategically located deposits of "sacrificial metals" which act as an anode to reduce corrosion of the metal being protected.

On 2 May 2012, Independence completed her maiden voyage to her homeport, Naval Base San Diego, California.[45]

In 2013, U.S. Navy sources described early documents that showed that the ship was to be named Liberty was a mistake.[46]

On 19 May 2014, a spokesman for the U.S. Pacific Fleet confirmed that Independence would take part in RIMPAC 2014, reversing an earlier decision to keep littoral combat ships in southern California to carry out tests and various exercises. The ship would join more than two dozen foreign ships and similar number of Navy ships in exercises off Hawaii from 6–25 July 2014.[47] Independence engaged in an exercise with US and allied special forces during RIMPAC.[48] Independence was operating out of San Diego testing its MCM package when it was decided that it would take part in RIMPAC 2014, so the ship returned to port and switched out the MCM package for the surface warfare package in 96 hours; components of the package included two 30 mm guns, 11 metres (36 ft) RHIBs, an aviation detachment of two MH-60S helicopters, and 19 extra sailors. Once switched, the 30 mm cannons were tested, the aviation detachment was qualified, launching the RHIBs using a twin-boom extensible crane was exercised, and the ship's combat system and communications suite including Link 16 were brought on line. The first RIMPAC scenario was acting as plane guard for the aircraft carrier USS Ronald Reagan, which required integration of communications and combat systems to the strike group; Independence received "Bravo Zulu" (well done) from the strike group commander for having sustained operations with Link 16 in a strike group environment. In a four-hour event, the ship played opposition force alone against four other vessels, and went nearly two hours without being located. Independence performed its first joint combined operations, acting as an afloat forward staging base for helicopter crews doing fast-roping for five US and foreign operating teams. It showed it could operate two helicopters near simultaneously while launching and recovering boats during boarding and search exercises. The ship performed two to three tasks per day and completed them all while not needing to pull into port and being refueled twice. RIMPAC exercises were at a much higher operating tempo than previous tests, and Independence accomplished its tasks without experiencing any major difficulties.[49]

Independence tested the MCM and ASW mission modules for the littoral combat ship designs during the summer of 2014. It was the first time the ship had conducted end-to-end missions, and the crew successfully performed at the high operational tempos. When moving through a mock minefield twice, the suite of counter-mine technologies detected mines each instance and completed search, detect, and destroy phases; it was also the first time all three components of the MCM package had been integrated on board the ship. Testing of the ASW package was conducted in September, where for the first time both the active and passive sonars were towed at once to make sure the two systems did not cross.[50]

See also

References

  1. 1.0 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. 7.0 7.1 7.2 7.3 7.4 7.5 Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. USS Independence LCS 2 – General Info[dead link]
  12. General Dynamics Littoral Combat Ship brochure[dead link]
  13. Lua error in package.lua at line 80: module 'strict' not found. (subscription required)
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found. (subscription required)
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. 20.0 20.1 Lua error in package.lua at line 80: module 'strict' not found.
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. Wilkinson, Kaija, "Independence's Day: Austal Warship Christened", Mobile Press-Register, 5 October 2008.
  25. Navy says the field is level for teams competing for LCS contract[dead link]
  26. Lua error in package.lua at line 80: module 'strict' not found. (subscription required)
  27. Lua error in package.lua at line 80: module 'strict' not found. (subscription required)
  28. Lua error in package.lua at line 80: module 'strict' not found. (subscription required)
  29. Lua error in package.lua at line 80: module 'strict' not found. (subscription required)
  30. Lua error in package.lua at line 80: module 'strict' not found. (subscription required)
  31. Lua error in package.lua at line 80: module 'strict' not found.
  32. Lua error in package.lua at line 80: module 'strict' not found.
  33. Lua error in package.lua at line 80: module 'strict' not found.
  34. Little changing for Corps in funding shift
  35. 35.0 35.1 Lua error in package.lua at line 80: module 'strict' not found.
  36. Lua error in package.lua at line 80: module 'strict' not found.
  37. 37.0 37.1 Lua error in package.lua at line 80: module 'strict' not found.
  38. Lua error in package.lua at line 80: module 'strict' not found.
  39. Lua error in package.lua at line 80: module 'strict' not found.
  40. Lua error in package.lua at line 80: module 'strict' not found.
  41. Lua error in package.lua at line 80: module 'strict' not found.
  42. "Austal develops corrosion management solution for LCS." Marine Log, 23 June 2011.[dead link]
  43. Lua error in package.lua at line 80: module 'strict' not found.
  44. Lua error in package.lua at line 80: module 'strict' not found.
  45. Lua error in package.lua at line 80: module 'strict' not found.
  46. Lua error in package.lua at line 80: module 'strict' not found.
  47. Lua error in package.lua at line 80: module 'strict' not found.
  48. Lua error in package.lua at line 80: module 'strict' not found.
  49. Lua error in package.lua at line 80: module 'strict' not found.
  50. Lua error in package.lua at line 80: module 'strict' not found.

External links