Destroyer Squadron 60

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
Destroyer Squadron 60
200px
Destroyer Squadron 60 emblem
Active World War II[1][2]
19 February 2003 – present[3]
Country United States
Branch United States Navy Seal United States Navy
Type Destroyer Squadron
Role Naval surface/strike/anti-aircraft warfare
ballistic missile defense (BMD)
Part of United States Sixth Fleet[3]
Garrison/HQ Naval Station Rota, Spain.[4]
Motto Fighting Forward Toward Victory
Commanders
Commodore Captain James Aiken[5]

Destroyer Squadron 60 (DESRON 60) is a Destroyer squadron of the United States Navy. Destroyer Squadron 60 is one of three U.S. Navy destroyer squadrons permanently based outside the continental United States.[6]

History

World War Two

During World War Two, Destroyer Squadron 60 consisted two destroyer divisions, the 119th and 120th, under the overall command of Captain William L. Freseman.[1][2]

Destroyer Squadron 60, World War Two[1]
Destroyer Division 119 Destroyer Division 120
USS Meredith (DD-726) USS Cooper (DD-695)
USS O'Brien (DD-725) USS Ingraham (DD-694)
USS Laffey (DD-724) USS Moale (DD-693)
USS Walke (DD-723) USS Allen M. Sumner (DD-692)
USS Barton (DD-722), flag ——

Destroyer Squadron 60 was part of the naval force assigned to Omaha Beach during the Normandy invasion of June 1944.[7] On 6 June 1944, the Meredith struck a mine, and after being towed to the Bay of the Seine, sank on 9 June 1944.[8] DESRON 60 subsequently was part of Task Force 129 which carried out the shore bombardment of the French seaport Cherbourg.[9]

File:USS Walke (DD-723) and USS Mississippi (BB-41) in Lingayen Gulf 1945.jpg
Lingayen Gulf (9 January 1945)

During the Pacific War, Destroyer Squadron 60 initially participated in the Philippines campaign. The squadron was part of the escort screen for Task Group 78.3, the amphibious assault force that invaded Leyte on October 1944. The squadron also participated in the ensuing Battle of Ormoc Bay.[10] On 3 December 1944, during an attack on a Japanese convoy, the Cooper was torpedoed and sunk.[11] Destroyer Squadron 60 subsequently operated as part of the destroyer screen for Task Group 77.2, the Bombardment and Fire Support Group for the January 1945 Invasion of Lingayen Gulf (pictured).

Destroyer Squadron 60 next operated with Task Force 38, the U.S. Third Fleet's Fast Carrier Task Force. On 16–17 February 1945, TF-38 flew air strikes against the Japanese home islands, Bonin Islands, and Volcano Islands to prevent any reinforcements of the Japanese garrison on Iwo Jima. During this period, Barton and Ingraham collided, and Moale was detached to escort the two damaged destroyers back to Saipan for repairs.[12]

Destroyer Squadron 60 then operated off Okinawa during Operation Iceberg, with Destroyer Division 120 serving as the escort screen for Task Group 52.1, the escort carrier group providing carrier-based close air support to the Allied invasion force.[13][14] Three units of Destroyer Squadron 60 — Walke, Barton, and Allen M. Sumner — came under intense kamikaze attacks during the squadron's operations in the closing months of the Pacific War.[1]

Re-establishment

On 19 February 2003, Destroyer Squadron 60 was re-established as a permanently assigned, forward-based destroyer squadron staff. It was initially based in Gaeta, Italy, the headquarters of the United States Sixth Fleet.[3] At that time, the squadron's mission was described as to provide the Commander United States Sixth Fleet with a permanently assigned, forward-based destroyer squadron staff for the operational control over destroyers and frigates deployed to the Mediterranean Sea.[3]

Commander responsibilities

With the courtesy title of commodore, the commander of Destroyer Squadron 60 (COMDESRON 60) not only oversees U.S. 6th Fleet surface naval warfare operations in the Mediterranean Sea but also throughout Europe and Africa. The squadron commodore also additionally serves as the executive assistant to the commander of U.S. Naval Forces Europe-Africa as well as the NATO commander of Allied Joint Force Command Naples for such exercises.[15] In the latter NATO role, Commodore James Aiken (pictured) acted as the exercise director for Exercise Sea Breeze 2014, the annual multinational maritime exercise held in the Black Sea involving Standing NATO Maritime Group 2, NATO member navies, and navies involved in the Partnership for Peace initiative.[16]

File:U.S. Navy Commodore James Aiken, at lectern, the commander of Destroyer Squadron 60 and the director of exercise Sea Breeze 2014, speaks during the opening ceremony for the exercise aboard the guided missile 140908-N-IY142-185.jpg
Commodore James Aiken, USN, COMDESRON 60 (8 September 2014)

Commander Destroyer Squadron 60 conducts combat and/or non-combat operations as Commander Task Force 60 or as Sea Combat Commander, and when directed, as Maritime Interception Operations Commander. Depending on the missions to be undertaken, COMDESRON 60 employs surface warships, submarines, aircraft, SEAL teams, U.S. Marines, U.S. joint forces, and NATO forces assigned to the Sixth Fleet's area of operations to keep open the sea lines of communications throughout the U.S. European Command's area of responsibility.[3]

2013 saw two major changes on the command responsibilities for the squadron:

  • On 21 March 2013, the billet of Commander Destroyer Squadron 60 was renamed Commander Task Force 65, with Task Force 65 being the designation for the Sixth Fleet's surface combatant force.[4][17]
  • On 9 May 2013, Commander Destroyer Squadron 60 (COMDESRON 60) was formally re-established to provide type-command administrative oversight for those four BMD-capable destroyers assigned to the squadron.[4][18]

In this new "type" capacity, COMDESRON 60 supervises the training, readiness, maintenance, schedules, material, supply, discipline, and morale for those assigned BMD-capable destroyers.[4] Commander Destroyer Squadron 60 continued to command Task Force 65 in a "dual-hatted" role, and both Destroyer Squadron 60 and Task Force 65 are now based at Rota, Spain.[4][18]

Operational history

Africa Partnership Station

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

Main article: Africa Partnership Station
File:US Navy 071204-N-8933S-152 The amphibious dock landing ship USS Fort McHenry (LSD 43) sits anchored off of the coast of Limbe. Africa Partnership Station (APS) is aboard Fort McHenry conducting training for Cameroonian Sailors.jpg
USS Fort McHenry - APS 2007

On 29 October 2007, the first Africa Partnership Station (APS) began under the command of Captain John Nowell, who was serving as Commander Destroyer Squadron 60 at the time. The APS task group, CTF-365, departed from Naples, Italy, with the dock landing ship USS Fort McHenry (LSD-43) (pictured) serving as its flagship and accompanied by the high-speed support ship USS Swift (HSV-2). En route to the region, the Fort McHenry augmented its passenger list with specialists from France, Germany, the United Kingdom and Spain and officers from Nigeria, Cameroon and Ghana. Denmark, Italy and Portugal were also provided military staff support. During its seven-month deployment,CTF-365 visited Senegal, Liberia, Ghana, Cameroon, Gabon, Angola, and Sao Tome and Principe. Africa Partnership Station 2007 developed cooperative partnerships among the regional maritime services while improving safety and security for the host nations. APS 2007 also supported over 20 humanitarian assistance projects during this deployment.[19]

During her tour as Commander Destroyer Squadron 60, then-Captain Cynthia N. Thebaud commanded two multi-national African Partnership Station deployments that focused on maritime security capacity-building in West and Central Africa.[20]

European Phased Adaptive Approach

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

Main article: European Phased Adaptive Approach

On 5 October 2011, US Secretary of Defense Leon Panetta announced that the United States Navy will station four Aegis-equipped BMD warships at Naval Station Rota, Spain, to strengthen its presence in the Mediterranean Sea and bolster the ballistic missile defense (BMD) of NATO as part of the European Phased Adaptive Approach (EPAA) initiative. On 16 February 2012, it was reported that the Arleigh Burke-class destroyers Donald Cook and Ross (pictured) will be relocated to Rota during Fiscal Year 2014, followed by Porter and Carney (pictured) in fiscal year 2015.[18] On 9 May 2013, Commander Destroyer Squadron 60 was formally designated to perform type-command administrative oversight for the four BMD-capable destroyers based at Rota, Spain.[4]

On 31 January 2014, the first BDM-arm destroyer, the Donald Cook, departed Naval Station Norfolk, Virginia, for its new home-port of Rota, Spain.[21] On 3 June 2014, the next BDM-arm destroyer, the Ross, departed Naval Station Norfolk, Virginia, for its new home-port of Rota, Spain, arriving on 16 June 2014.[22] The third destroyer, the Porter, joined Destroyer Squadron 60 on 30 April 2015.[23]

  • US Navy 030114-N-3235P-502 The guided missile destroyer USS Donald Cook (DDG 75) underway conducting missions in support of Operation Enduring Freedom.jpg

    USS Donald Cook (DDG-75)

  • US Navy 030614-N-4374S-001 The Arleigh Burke-class, guided missile destroyer USS Ross (DDG 71) steams through the Baltic Sea during the annual maritime exercise Baltic Operations 2003 (BALTOPS).jpg

    USS Ross (DDG-71)

  • USS Porter (DDG-78) 2007.jpg

    USS Porter (DDG-78)

  • US Navy 050303-N-0780F-079 The guided missile destroyer USS Carney (DDG 64) approaches the Marathi NATO pier facility in Souda Bay for a scheduled port visit.jpg

    USS Carney (DDG-64)

Forward Deployed Naval Forces

2013 Ghouta chemical attack

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

Main articles: Syrian civil war and Ghouta chemical attack
File:Operational navy1.jpg
Ramage, Barry, and Stout conducting a replenishment-at-sea with Leroy Grumman (September 27, 2013)

The U.S. Navy initially delayed the departure of the Aegis-equipped guided-missile destroyer Mahan from the U.S. Sixth Fleet amid allegations that the regime of Syrian president Bashar al-Assad used chemical weapons during the ongoing Syrian civil war, including the gas attacks that occurred on 21 August 2013. Both the Mahan and its relief, the Ramage, remained in the Eastern Mediterranean with two other Aegis-equipped destroyers, the Barry and Gravely. All four destroyers are capable of intercepting ballistic missiles as well as launching land-attack Tomahawk cruise missiles.[24]

On 28 August 2013, the U.S. Navy announced that a fifth Arleigh Burke-class destroyer, the USS Stout (DDG-55), was en route to join the other four Burke-class destroyers in the Eastern Mediterranean.[25] On 4 September 2013, the US Navy announced that USS Mahan had departed for its home-port of Naval Station Norfolk, Virginia, leaving four Burke-class destroyers operating in the Eastern Mediterranean.[26] On 13 September 2013, the Mahan returned to Naval Station Norfolk, Virginia, completing an ​8 1⁄2-month deployment with the U.S. Sixth Fleet.[27]

On 12 September 2013, the U.S. Department of Defense announced that the remaining four Burke-class destroyers will remain in the eastern Mediterranean as Russian and American diplomats negotiate the turn-over of Syria's stockpile of chemical weapons to the United Nations, with Pentagon spokesman George E. Little noting: "We have no plans at this time to change our military posture in the Mediterranean. We’re prepared for any potential military contingencies that might involve Syria."[28] On 31 October 2013, the Organisation for the Prohibition of Chemical Weapons announced that all declared equipment and facilities related to Sysria's chemical weapons production have been destroyed.[29]

2014 Black Sea incident

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

See also: 2014 Russian military intervention in Ukraine, 2014 Crimean crisis, and 2014 pro-Russian conflict in Ukraine
Black Sea

On 14 March 2014, Desron-60 guided-missile destroyer USS Donald Cook (DDG-75) departed for its first patrol as a forward deployed naval vessel of the U.S. Sixth Fleet.[30] On 10 April 2014, Donald Cook entered the Black Sea.[31] According to Pentagon spokesman Colonel Steven Warren, U.S. Army, the deployment of the Donald Cook to the Black Sea was "to reassure NATO allies and Black Sea partners of America’s commitment to strengthen and improve interoperability while working towards mutual goals in the region."[32]

On 12 April 2014, the Donald Cook was operating in the western Black Sea when a pair of unarmed Russian Su-24 Fencer attack aircraft enter the area. One Su-24 left its formation and began to fly closer to the Donald Cook. A total of twelves passes took place over a 90-minute period, and the Russian aircraft approached within about 1,000 yards of the Donald Cook.[33]

In the aftermath of this incident, Pentagon spokesman Colonel Warren stated: "This provocative and unprofessional Russian action is inconsistent with international protocols and previous agreements on the professional interaction between our militaries."[34] On 14 April 2014, the Donald Cook paid a port call at Constanta, Romania, which included a visit by Romanian president Traian Băsescu.[35] The Donald Cook conducted a multilateral training exercise with the Romanian warships Regina Maria and Mărășești, as well as the frigate Taylor.[36]

The Donald Cook departed the Black Sea on 24 April 2014.[37] After a port visit to Durres, Albania, and training with Albanian forces, the Donald Cook returned to Rota, Spain, on 25 July 2014, completing its first forward-based deployment.[36] Donald Cook's next Black Sea cruise, 28 December 2014 to 14 January 2015, transpired without incident.[38]

2015 Black Sea incident

On 21 May 2015, the destroyer USS Ross (DDG-71) entered the Black Sea to conduct joint operations with NATO and regional navies as part of Operation Atlantic Resolve.[39] On 25 May 2015, the Ross began a 3-day training exercise with the frigates Regina Maria and Marasesti of the Romanian Navy.[40]

File:150602-N-FQ994-311 - The guided-missile destroyer USS Ross (DDG 71), front, transits the Black Sea with the Ukranian navy frigate Hetman Sahaydachniy (U 130) June 1, 2015.JPG
Ross, front, with Hetman Sahaydachniy in the Black Sea (June 1, 2015)

On 30 May 2015, the Ross was over-flown by Russian Su-24 Fencer aircraft while the ship was underway in the Black Sea.[41][42] Citing Russian military sources, the state-operated news agency RIA Novosti reported:

“The crew of the ship acted provocatively and aggressively, which concerned the operators of monitoring stations and ships of the Black Sea Fleet,” the source in the Russian armed forces in Crimea told RIA. Su-24 attack jets were scrambled in response. They "demonstrated to the American crew readiness to harshly prevent a violation of the frontier and to defend the interests of the country," the source said. The destroyer then turned around and left for neutral waters. "Apparently, the Americans have not forgotten the April 2014 incident when one Su-24 practically 'blacked out' all of the electronics on board the newest American destroyer Donald Cook," the source said.[43]

In its 31 May 2015 press release, the U.S. Navy noted that:

Ross observed the routine flights of SU-24 aircraft and had no interaction while both operated in international waters. Ross continued on her mission after observing the aircraft return to base. At no time did Ross act aggressively nor did she deviate from her planned operations. The conduct of her crew has been and continues to be professional.[44]

On 1 June 2015, U.S. Defense Department spokesman Colonel Steven Warren, U.S. Army, further noted that the Russian military aircraft in the incident "were naked. In other words, no weapons aboard, no weapons on her wings."[41] Also on that date, the U.S. Navy released a video of the Russian aircraft overflight.[45] Finally, on this date, the Ross began a two-day naval exercise with the Ukrainian frigate Hetman Sahaydachniy (pictured). On 3 June 2015, the Ross departed the Black Sea, concluding an 11-day cruise.[40]

NATO operations

Desron-60 destroyer Porter entered the Black Sea on 5 July 2015 to join Dutch frigate Tromp, the Portuguese frigate D. Francisco de Almeida, and Spanish minesweeper Tajo for the NATO Sea Breeze 2015 naval exercises. The exercise will include 30 ships and around 1,700 personnel from Greece, Bulgaria, Turkey, the Netherlands, Spain, and the United States, as well as NATO's Standing NATO Maritime Group 1 and Standing NATO Mine Countermeasures Group 2. Sea Brezze 2015 was scheduled to take place between 3–12 July 2015.[46]

See also

Notes

  1. ↑ 1.0 1.1 1.2 1.3 Lua error in package.lua at line 80: module 'strict' not found.
  2. ↑ 2.0 2.1 Roscoe. U.S. Destroyer Operations in WW2, pp. 361, 455.
  3. ↑ 3.0 3.1 3.2 3.3 3.4 Lua error in package.lua at line 80: module 'strict' not found.
  4. ↑ 4.0 4.1 4.2 4.3 4.4 4.5 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. ↑ 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. ↑ U.S. Destroyer Operations in WW2, pp. 360–362.
  10. ↑ Roscoe. U.S. Destroyer Operations in WW2, pp. 454–455.
  11. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  12. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  13. ↑ Roscoe. U.S. Destroyer Operations in WW2, p. 493.
  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. and Lua error in package.lua at line 80: module 'strict' not found.
  17. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  18. ↑ 18.0 18.1 18.2 Lua error in package.lua at line 80: module 'strict' not found.
  19. ↑ Lua error in package.lua at line 80: module 'strict' not found. and Lua error in package.lua at line 80: module 'strict' not found.
  20. ↑ 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. and 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. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  25. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  26. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  27. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  28. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  29. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  30. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  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. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  35. ↑ Lua error in package.lua at line 80: module 'strict' not found. and Lua error in package.lua at line 80: module 'strict' not found.
  36. ↑ 36.0 36.1 Lua error in package.lua at line 80: module 'strict' not found.
  37. ↑ 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. ↑ 40.0 40.1 Lua error in package.lua at line 80: module 'strict' not found.
  41. ↑ 41.0 41.1 Lua error in package.lua at line 80: module 'strict' not found.
  42. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  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.

References

This article incorporates text from the public domain Dictionary of American Naval Fighting Ships.

  • Lua error in package.lua at line 80: module 'strict' not found.

External links

  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
Retrieved from "https://infogalactic.com/w/index.php?title=Destroyer_Squadron_60&oldid=694780983"