Nuclear Submarine Rammed By Navy Cruiser – UPDATE
Update: The U.S Navy submarine and Aegis cruiser that collided off the East Coast of the United States on 13 October arrived safely in port on the 14th.
USS Montpelier (SSN 765) arrived at Naval Submarine Base Kings Bay, while USS San Jacinto (CG 56) arrived at Naval Station Mayport to further assess and evaluate the damage that resulted from their collision at sea.
Reports indicate that the sonar dome on the San Jacinto may have collapsed in the collision; potentially a very expensive and time-consuming fix, that may affect her future deployment schedule.
A Ticonderoga-class Aegis cruiser, such as the USS San Jacinto, typically takes a very senior role within the carrier strike group. The cruiser typically acts as the primary air warfare asset and is commanded by a Captain (O-6) who is the designated Air Warfare Commander.
Earlier: A U.S. Navy submarine and an Aegis cruiser collided off the coast of the Eastern United States today.
The collision between USS Montpelier (SSN 765) and USS San Jacinto (CG 56) occurred at approximately 3:30 p.m. Eastern Daylight time when the officer of the watch aboard the San Jacinto saw the Montpelier rise to periscope depth less than 250 yards ahead of them.
No personnel aboard either vessel were injured.
Overall damage to both ships is being evaluated. The propulsion plant of the submarine was unaffected by this collision. Both ships are currently operating under their own power.
The incident is currently under investigation. Both the submarine and the ship were conducting routine training at the time of the accident. According to ABC news the two ships were participating in a “group sail” along with another vessel in preparation for an upcoming deployment as part of the strike group for the aircraft carrier USS Harry S Truman.
The Navy official says that at approximately 3:30 p.m. the bridge watch aboard the San Jacinto saw the submarine Montpelier rise to periscope depth about 100 to 200 yards ahead of them. The bridge ordered an “all back,” but still collided with the sub.
Sign up for our newsletter
Be the First
Join the 64,564 members that receive our newsletter.
Have a news tip? Let us know.