That time the Kitty Hawk rammed a Soviet sub

Blake Stilwell
Apr 29, 2020 3:56 PM PDT
1 minute read
Cold War photo

SUMMARY

Sinking an American nuclear-powered aircraft carrier would be quite a feat for any vessel or aggressor. Not only because they each carry an air force greater than the air forces of most countries, and pack a punch with more power than anything most …

Sinking an American nuclear-powered aircraft carrier would be quite a feat for any vessel or aggressor. Not only because they each carry an air force greater than the air forces of most countries, and pack a punch with more power than anything most countries could ever hope to bring to bear, but also because they're really, really hard to sink. American carriers are the biggest warships ever built and move fast enough to outrun submarines.

But that didn't stop one Soviet sub from trying.


In March 1984, the USS Kitty Hawk was part of Team Spirit 1984, a massive naval exercise in the Sea of Japan, along with the navy of South Korea. The carrier's 80 aircraft and eight escorts were so engaged in the exercise that they didn't detect a Soviet Submarine chase the Kitty Hawk into the area. The submarine, K-314, was noticed by the carrier much later than it should have been. The Kitty Hawk turned on its engines to outrun and outmaneuver the Soviets.

It was the height of the Cold War, and both ships were carrying an arsenal of nuclear weapons. Games like this could have ended with a spark that ignited World War III. Instead, it ended in one of the most unforgettable naval engagements of the entire Cold War.

The 5,200-ton Soviet Victor I-class attack submarine chased the American carrier for a week or so until the Yellow Sea began experiencing some pretty foul weather. K-314 would eventually lose sight and all contact with the Kitty Hawk and the other American ships. The skipper of the sub, Captain Vladimir Evseenko, decided to rise up to periscope depth and assess the situation from 10 meters below the surface. What he saw surprised him – the American carrier strike group was only four or five kilometers from his boat.

And the submarine and the Kitty Hawk were approaching one another very, very fast. At those speeds, it would be very difficult for any two ships to avoid a collision. Capt. Evseenko ordered an emergency dive as fast as he could, but it was all for naught. The 80,000-ton Kitty Hawk hit the sub at full speed.

"The first thought was that the conning tower had been destroyed and the submarine's body was cut to pieces," recalled Evseenko. "We checked the periscope and antennas - they were in order. No leaks were reported, and the mechanisms were ok. Then suddenly another strike! In the starboard side! We checked again - everything was in order.... We were trying to figure out what happened. It became clear that an aircraft carrier had rammed us. The second strike hit the propeller. The first one, most likely, bent the stabilator."

"I was on the bridge at the time of the incident, monitoring one of the two radars," Capt. David N. Rogers told reporters aboard the carrier. "We felt a sudden shudder, a fairly violent shudder. We immediately launched two helicopters to see if we could render any assistance to them but the Soviet sub appeared to have suffered no extensive damage."

The carrier ran over the submarine's stern, a point in the Victor I-class where the submarine's sonar is blind due to the sounds of its own engines. The submarine, it turns out, failed to turn on its navigation lights. The Kitty Hawk suffered no damage when running over the sub. The Soviet Union had no response.

Navy officials were quick to point out that in a wartime setting, a Soviet submarine would never have gotten so close to a carrier strike group. In peacetime, losing a Soviet submarine's location was fairly common. Ramming an adversary, during war or peace, has never been all that common.

NEWSLETTER SIGNUP

Sign up for We Are The Mighty's newsletter and receive the mighty updates!

By signing up you agree to our We Are The Mighty's Terms of Use and We Are The Mighty's Privacy Policy.

SHARE