Jump to content

USS Yorktown (CG-48): Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
Tag: Reverted
Line 128: Line 128:


==Fate==
==Fate==
''Yorktown'' was decommissioned and struck on 10 December 2004 following Lynne Pujado using a F-301 pen in control. As of 2008, ''Yorktown'' was scheduled to be dismantled in the next five years along with her sisterships {{USS|Vincennes|CG-49|2}} and {{USS|Thomas S. Gates|CG-51|2}}.<ref>{{cite web|url=http://www.navytimes.com/news/2008/02/navy_shipdisposal_080223w/|title=Navy sink list includes Forrestal, destroyers|publisher=NavyTimes|access-date=2011-02-12}}</ref> Since her decommissioning, ''Yorktown'' has been berthed at the [[Naval Inactive Ship Maintenance Facility|Naval Inactive Ships Maintenance Facility]], [[Philadelphia]], Pennsylvania.<ref name="NAVSEA DOI" /> As of September 2016, the ship remained in Philadelphia.<ref>{{cite web |url= http://www.navsea.navy.mil/Portals/103/Documents/TeamShips/SEA21/InactiveShips/InactiveShipInventory-27Sep16(3).pdf |title= Inactive ship inventory |publisher= NAVSEA, US Navy |date= 27 September 2016 }}</ref>
''Yorktown'' was decommissioned and struck on 10 December 2004. As of 2008, ''Yorktown'' was scheduled to be dismantled in the next five years along with her sisterships {{USS|Vincennes|CG-49|2}} and {{USS|Thomas S. Gates|CG-51|2}}.<ref>{{cite web|url=http://www.navytimes.com/news/2008/02/navy_shipdisposal_080223w/|title=Navy sink list includes Forrestal, destroyers|publisher=NavyTimes|access-date=2011-02-12}}</ref> Since her decommissioning, ''Yorktown'' has been berthed at the [[Naval Inactive Ship Maintenance Facility|Naval Inactive Ships Maintenance Facility]], [[Philadelphia]], Pennsylvania.<ref name="NAVSEA DOI" /> As of September 2016, the ship remained in Philadelphia.<ref>{{cite web |url= http://www.navsea.navy.mil/Portals/103/Documents/TeamShips/SEA21/InactiveShips/InactiveShipInventory-27Sep16(3).pdf |title= Inactive ship inventory |publisher= NAVSEA, US Navy |date= 27 September 2016 }}</ref>


[[File:Ticonderoga, Yorktown and Thomas S. Gates at Philadelphia.jpg|thumb|left|''Yorktown'', along with sister ships ''Ticonderoga'' and ''Thomas S. Gates'' laid up at Naval Inactive Ships Maintenance Facility, Philadelphia, Pennsylvania.]]
[[File:Ticonderoga, Yorktown and Thomas S. Gates at Philadelphia.jpg|thumb|left|''Yorktown'', along with sister ships ''Ticonderoga'' and ''Thomas S. Gates'' laid up at Naval Inactive Ships Maintenance Facility, Philadelphia, Pennsylvania.]]

Revision as of 08:51, 19 March 2022

For other ships with the same name, see USS Yorktown.

USS Yorktown on 24 February 2002
History
United States
NameYorktown
NamesakeBattle of Yorktown
Ordered28 April 1980
BuilderIngalls Shipbuilding
Laid down19 October 1981
Launched17 January 1983
Sponsored byMrs. Mary Mathews
Commissioned4 July 1984
Decommissioned10 December 2004
Stricken10 December 2004
Identification
MottoVictory is our tradition
StatusAwaiting scrapping
Badge
General characteristics
Class and typeTiconderoga-class cruiser
DisplacementApprox. 9,600 long tons (9,800 t) full load
Length567 feet (173 m)
Beam55 feet (16.8 meters)
Draft34 feet (10.2 meters)
Propulsion
Speed32.5 knots (60 km/h; 37.4 mph)
Complement30 officers and 300 enlisted
Sensors and
processing systems
Armament
Aircraft carried2 × MH-60R Seahawk LAMPS Mk III helicopters.

USS Yorktown (DDG-48/CG-48) was a Ticonderoga-class cruiser in the United States Navy from 1984 to 2004, named for the American Revolutionary War Battle of Yorktown.

History

Yorktown was launched 17 January 1983 and was sponsored by Mrs. Mary Matthews, widow of Nick Matthews, a prominent citizen of Yorktown, Virginia.[1] Yorktown was commissioned on 4 July 1984 at Yorktown, Virginia, and was designed to take advantage of the American Aegis technology. Among its various weapon systems were surface to air missiles (SAMs), anti-ship/anti-submarine missiles, torpedo launchers, and a mounted cannon. Yorktown's first deployment was from August 1985 to April 1986 and, among other things, involved the Achille Lauro hijacker intercept, two Black Sea excursions (in 1986 and 1988), and a trio of operations off the Libyan coast including Operation El Dorado Canyon and Operation Attain Document and Prairie Fire.

The Soviet Burevestnik M-class frigate Bezzavetnyy intentionally hit Yorktown in 1988.

Yorktown received the Atlantic Fleet's "Top Gun" award for outstanding naval gunfire support in 1987. During the second deployment from September 1987 to March 1988, Yorktown participated in numerous U.S. and NATO exercises, as well as multi-national exercises with Morocco, France, West Germany, Tunisia, and Turkey. It was on this Mediterranean deployment that Yorktown gained worldwide publicity from operations conducted in the Black Sea as part of Freedom of Navigation program.[2] On 12 February 1988, while Yorktown was exercising the "right of innocent passage" through Soviet territorial waters, the Soviet Burevestnik-class frigate Bezzavetnyy (Template:Lang-ru) intentionally collided with Yorktown with the intention of pushing her out of Soviet territorial waters.[3] The Assistant Secretary of Defense for International Security Affairs at the time, Richard L. Armitage, acknowledged that the transit was not operationally necessary, but asserted that it was still a valid innocent passage under international law.[4]

In 1991, Yorktown was awarded the coveted "Old Crow's" award for electronic warfare excellence.[citation needed] In 1992 Yorktown was honored with the Marjorie Sterrett Battleship Fund Award for superb, sustained combat readiness.[citation needed]

Yorktown conducted her third and fourth Mediterranean deployments as the world watched the end of the Cold War and the coalition victory in Operation Desert Storm. During the latter of these two deployments Yorktown participated in the first U.S. military exercises with the Romanian and Bulgarian navies, and played a key role in Operation Provide Comfort, which provided humanitarian relief and security for the Kurdish refugees in northern Iraq. In the summer of 1992, Yorktown participated in BALTOPS '92. During this cruise, Yorktown made a highly acclaimed port visit to Severomorsk, Russia, becoming the first U.S. ship to visit that port since the end of World War II.

In 1993, Yorktown was awarded the Commander, Naval Surface Forces, Atlantic Ship Safety Award for a superior safety record. Yorktown has also been awarded two Navy Unit Commendations and a Meritorious Unit Commendation, and is a four-time winner of the coveted Battle Efficiency "E".

Yorktown served as Flagship for Commander, Task Group 4.1, during counter-drug operations in the Caribbean in May–July 1993. In August 1993, Yorktown participated in the joint military exercise Solid Stance in the North Atlantic. Yorktown's operations through the end of 1993 included an October–November excursion to the Caribbean to support the United Nations embargo of Haiti. In April–May 1994, Yorktown returned to the Caribbean as Force Air Warfare Commander during joint Exercise Agile Provider. While in the Caribbean, Yorktown served as flagship for Commander, Destroyer Squadron Six, coordinating a six-ship, twenty-six missile exercise. In the summer of 1994, Yorktown achieved a resounding score of 101 during naval gunfire support qualification.

In August 1994 Yorktown set sail for the Adriatic Sea as flagship for Commander, Standing Naval Force Atlantic, in support of the United Nations embargo of the Federal Republic of Yugoslavia. During this six-month deployment, Yorktown served as the Air Warfare Commander for the Adriatic Sea, participating in a joint task force of ships from the United States and eight European nations. In May–June 1995, Yorktown proceeded south to serve as Air Warfare Commander for the Caribbean Sea in support of counter-narcotics operations.

Yorktown firing at a target drone during a gun exercise

In May 1997 Yorktown (with a reduced crew aboard) completed a five-month counter-narcotic deployment in the Caribbean followed by tests with George Washington and her accompanying Cruiser-Destroyer Group 2. During these periods Navy Manpower and Analysis Center (NAVMAC) conducted a detailed review of manpower requirements, and the Operational Test and Evaluation Force verified the ship's ability to meet all required operational capabilities in the projected operating environment doctrine for Ticonderoga-class cruisers.

On 21 September 1997, a division by zero error on board the USS Yorktown (CG-48) Remote Data Base Manager brought down all the machines on the network, causing the ship's propulsion system to fail.[5][6]

On 25 September 1999 Yorktown departed Pascagoula for a four-month counter-narcotic deployment in the Caribbean. Before beginning patrolling efforts, Yorktown embarked staff members from Commander, Second Fleet. Supported by the helicopter detachment, the Second Fleet staff surveyed and photographed another island being considered as a potential replacement for training exercises if the Navy was unable to continue at Vieques Island, Puerto Rico. The ship made port calls in Jamaica, Aruba, Cartagena, Rodman, Manta and Cozumel. During this deployment the USS Yorktown was the last U.S. warship to transit the Panama Canal prior to it being turned over to Panama.

Fate

Yorktown was decommissioned and struck on 10 December 2004. As of 2008, Yorktown was scheduled to be dismantled in the next five years along with her sisterships Vincennes and Thomas S. Gates.[7] Since her decommissioning, Yorktown has been berthed at the Naval Inactive Ships Maintenance Facility, Philadelphia, Pennsylvania.[1] As of September 2016, the ship remained in Philadelphia.[8]

Yorktown, along with sister ships Ticonderoga and Thomas S. Gates laid up at Naval Inactive Ships Maintenance Facility, Philadelphia, Pennsylvania.

Smart ship testbed

From 1996 Yorktown was used as the testbed for the Navy's Smart Ship program. The ship was equipped with a network of 27 dual 200 MHz Pentium Pro-based machines running Windows NT 4.0 communicating over fiber-optic cable with a Pentium Pro-based server. This network was responsible for running the integrated control center on the bridge, monitoring condition assessment, damage control, machinery control and fuel control, monitoring the engines and navigating the ship. This system was predicted to save $2.8 million per year by reducing the ship's complement by 10%.

On 21 September 1997, while on maneuvers off the coast of Cape Charles, Virginia, a crew member entered a zero into a database field causing an attempted division by zero in the ship's Remote Data Base Manager, resulting in a buffer overflow which brought down all the machines on the network, causing the ship's propulsion system to fail.[9]

Anthony DiGiorgio, a civilian contractor with a 26-year history of working on Navy control systems, reported in 1998 that Yorktown had to be towed back to Norfolk Naval Station. Ron Redman, a deputy technical director with the Aegis Program Executive Office, backed up this claim, suggesting that such system failures had required Yorktown to be towed back to port several times.[10]

In the 3 August 1998 issue of Government Computer News, a retraction by DiGiorgio was published. He claims the reporter altered his statements, and insists that he did not claim the Yorktown was towed into Norfolk. GCN stands by its story.[11]

Atlantic Fleet officials also denied the towing, reporting that Yorktown was "dead in the water" for just 2 hours and 45 minutes.[10] Captain Richard Rushton, commanding officer of Yorktown at the time of the incident, also denied that the ship had to be towed back to port, stating that the ship returned under its own power.[12]

Atlantic Fleet officials acknowledged that the Yorktown experienced what they termed "an engineering local area network casualty".[10] "We are putting equipment in the engine room that we cannot maintain and, when it fails, results in a critical failure," DiGiorgio said.[10]

Criticism of operating system choice ensued. Ron Redman, deputy technical director of the Fleet Introduction Division of the Aegis Program Executive Office, said that there have been numerous software failures associated with NT aboard the Yorktown.[10]

Because of politics, some things are being forced on us that without political pressure we might not do, like Windows NT. If it were up to me I probably would not have used Windows NT in this particular application ... Refining that is an ongoing process ... Unix is a better system for control of equipment and machinery, whereas NT is a better system for the transfer of information and data. NT has never been fully refined and there are times when we have had shutdowns that resulted from NT.

— Ron Redman[10]

Awards

Bronze oak leaf cluster
Bronze oak leaf cluster
Bronze star
Bronze star
Bronze star
Bronze star
Bronze star

See also

Notes

Public Domain This article includes information collected from the Naval Vessel Register, which, as a U.S. government publication, is in the public domain. The entry can be found here.

  1. ^ a b c d e f g h i j "Yorktown (CG-48) – Final Determination" (PDF). NAVSEA, US Navy. 30 November 2010.
  2. ^ Campbell, "USS Caron's Black Sea Scrape Furthered International Law, National Interest", The Virginian-Pilot and the Ledger-Star, 12 June 1988, at C3, col. 1.
  3. ^ Aceves, William J. "Diplomacy at Sea: U.S. Freedom of Navigation Operations in the Black Sea". International Law Studies. 68.
  4. ^ Lieutenant Commander John W. Rolph (December 2005). "Freedom of Navigation and the Black Sea Bumping Incident: How "Innocent" Must Innocent Passage Be?" (PDF). Military Law Review. 136: 146.
  5. ^ "Sunk by Windows NT". Wired News. 24 July 1998.
  6. ^ William Kahan (14 October 2011). "Desperately Needed Remedies for the Undebuggability of Large Floating-Point Computations in Science and Engineering" (PDF). p. 54.
  7. ^ "Navy sink list includes Forrestal, destroyers". NavyTimes. Retrieved 12 February 2011.
  8. ^ "Inactive ship inventory" (PDF). NAVSEA, US Navy. 27 September 2016.
  9. ^ "Sunk by Windows NT". Wired News. 24 July 1998.
  10. ^ a b c d e f Slabodkin, Gregory (13 July 1998). "Software glitches leave Navy Smart Ship dead in the water". Government Computer News. Retrieved 18 June 2009.
  11. ^ DiGiorgio, Anthony (3 August 1998). "Letters to the Editor: DiGiorgio denies reported statements". Government Computer News. Retrieved 18 June 2009.
  12. ^ Slabodkin, Gregory (31 August 1998). "Smart Ship inquiry a go". Government Computer News. Retrieved 18 June 2009.
Wikimedia Commons has media related to USS Yorktown (CG-48).
Retrieved from "https://en.wikipedia.org/enwiki/w/index.php?title=USS_Yorktown_(CG-48)&oldid=1077995353"