The Collision Compact: How Two Navies Agreed to Risk Nuclear Catastrophe Rather Than Admit the Game Was the Problem
Forty-two years ago today, a Soviet nuclear submarine surfaced directly into the path of an 80,000-ton American aircraft carrier in the Sea of Japan. Both vessels were carrying nuclear weapons. The jet fuel leaked but did not ignite. The warheads did not detonate. Both navies blamed the Soviet captain, closed the file, and kept playing the same game. They are still playing it. This paper names the fallacy, identifies the center of gravity, and proposes the doctrine that forty-two years of institutional silence have failed to produce.
The Fallacy: The Blameless Carrier
On 21 March 1984, during Exercise Team Spirit 84-1, Soviet submarine K-314, a Project 671 Victor I-class nuclear attack boat, collided with USS Kitty Hawk (CV-63) at 2207 local time, approximately 150 miles east of Pohang, South Korea. The official narrative pinned the collision squarely on Captain Vladimir Evseenko: bad seamanship, failure to display navigation lights, violation of the 1972 Incidents at Sea Agreement. The Soviets concurred, relieving Evseenko of command. Washington blamed Moscow. Moscow agreed. Case closed.
The fallacy is that the collision was one man’s mistake. It was not. It was the predictable outcome of two institutional doctrines operating exactly as designed. RADM Richard M. Dunleavy, Director of the Carrier and Air Stations Program, later acknowledged that K-314 had been detected by Battle Group Bravo’s helicopters and simulated-killed more than 15 times in the preceding three days, having first been spotted on the surface 50 nautical miles ahead of the carrier. Fifteen kills. And the submarine was still there, still tracking, still close enough to collide. If you kill an adversary 15 times and it keeps coming, you have not solved the problem. You have documented your failure to solve it.
When Kitty Hawk shifted to flight operations, turning into the wind and accelerating to 30 knots, nobody accounted for the fact that the course change put the carrier on a direct collision bearing with K-314’s last known position. The Soviets were reckless. The Americans were complacent. Blaming Evseenko allowed both navies to preserve the system that produced the collision. That is the fallacy: scapegoating an individual to protect a doctrine.
Identify the Center of Gravity: The Shadow-and-Pursuit Doctrine
The center of gravity is not a submarine captain’s judgment. It is the shadow-and-pursuit doctrine itself: the unwritten bilateral agreement between the U.S. and Soviet navies that nuclear-armed platforms would routinely operate at knife-fighting range, each side shadowing the other’s capital ships, each side accepting catastrophic proximity as the price of intelligence collection and competitive prestige.
Soviet submarine captains were trained to shadow American carrier groups at close range. Their promotion depended on it. American carrier groups were trained to detect and evade them. Prestige depended on it. The INCSEA Agreement, signed on 25 May 1972 by Secretary of the Navy John Warner and Fleet Admiral Sergei Gorshkov during the Nixon-Brezhnev summit, was supposed to constrain this behavior. It required submarines surfacing near surface vessels to display navigation lights and give way. K-314 surfaced in darkness with no lights. The agreement assumed rational actors operating with perfect information in an environment defined by imperfect information and institutional pressure to take risks. It was a gentleman’s handshake in a knife fight, and the knife fight always wins.
Both vessels were carrying nuclear weapons. Kitty Hawk held several dozen tactical nuclear warheads as standard Cold War loadout. K-314 probably carried two nuclear torpedoes. The carrier also held thousands of tons of JP-5 jet fuel, some of which leaked into the sea from the hole punched in her bow. It did not ignite. The warheads did not detonate. These are not safety features. They are luck.
The collision sequence itself reveals the architecture of compounded failure. K-314 had lost track of Kitty Hawk in deteriorating weather. Evseenko rose to periscope depth, ten meters, to reacquire the carrier. Through the periscope he found the entire strike group only four to five kilometers away, closing on a reciprocal heading at speed. He ordered an emergency dive. It was too late. The 80,000-ton carrier struck the 5,200-ton submarine, rolling K-314 onto her back. Evseenko’s first thought was that the conning tower had been destroyed and the hull was cut to pieces. They checked: periscope intact, antennas intact, no leaks. Then a second impact, starboard side. The propeller. The first hit had bent the stabilator. K-314 lost propulsion and had no choice but to surface, exposing herself to the very adversary that had just run over her.
A slightly different angle, a slightly greater force, a structural failure in the wrong compartment, and the calculus changes from embarrassing incident to ecological catastrophe to superpower confrontation in the time it takes metal to tear. Neither navy had a protocol for this scenario, because planning for it would require admitting the game was the problem. The shadow-and-pursuit doctrine created the proximity. The proximity created the collision geometry. The collision geometry created the nuclear risk. The center of gravity is the doctrine, not the captain.
Converge the Silos
The Kitty Hawk/K-314 collision sits at the intersection of five institutional silos, none of which could see the convergence:
Anti-Submarine Warfare Operations treated K-314 as a tactical problem: detect, track, simulate-kill, repeat. Fifteen simulated kills in three days. The ASW teams were doing their jobs by the metrics that measured success: contact maintained, weapons solutions generated, kill tallies rising. But ASW doctrine had no gate between detection and safe separation. The tactical game rewarded proximity. The closer the track, the better the data. Nobody in the ASW chain was measured on whether the submarine maintained safe distance from the carrier, because that was not the metric. Killing a contact on paper and managing its physical proximity to the carrier were treated as the same problem. They are not. The distinction cost both navies a near-catastrophe.
Diplomatic Agreements treated INCSEA as a constraint on behavior. It was a constraint on the willing. The moment operational pressure exceeded diplomatic courtesy, the agreement evaporated. Warner and Gorshkov signed paper. Submarine captains and carrier groups operated in physics. The agreement’s fundamental weakness was its assumption that both sides would choose compliance over advantage in the moment of decision. Evseenko did not choose to surface without lights to violate INCSEA. He surfaced because he had lost contact and needed to reacquire. The agreement was irrelevant to the operational reality that produced the collision.
Nuclear Weapons Safety assumed separation between nuclear-armed platforms and kinetic risk. The shadow-and-pursuit doctrine eliminated that separation by design. Nuclear weapons aboard both vessels were the stakes of a game neither navy acknowledged was being played. No nuclear weapons safety protocol accounted for the possibility that two nuclear-armed platforms would physically collide during peacetime operations, because accounting for it would require admitting that the operating doctrine routinely placed nuclear weapons inside the blast radius of potential kinetic events.
Intelligence Collection retroactively celebrated the collision as a windfall. The U.S. Navy recovered fragments of K-314’s anechoic tiles, pulled a propeller blade from Kitty Hawk’s hull, and photographed the crippled submarine’s exposed innards while the frigate USS Harold E. Holt stood watch. The crew painted a red submarine victory mark on the carrier’s island, later ordered removed. Branding an accident as an intelligence coup substitutes for the harder question of why the accident happened.
Accountability Structures punished the individual and preserved the system. Evseenko was relieved. Nobody on the American side faced consequences. Captain David N. Rogers reported a violent shudder on the bridge, launched helicopters to render assistance, and continued his career without interruption. Both navies chose to downplay the incident rather than lodge formal protests, because a formal investigation would require both sides to admit what they already knew.
Coin the Term: The Collision Compact
The Collision Compact is the unspoken bilateral agreement between adversary navies to accept catastrophic proximity as a cost of doing business, to treat the resulting incidents as individual failures rather than systemic products, and to preserve the doctrine that generates those incidents because no institution can afford to admit the game itself is the problem.
The Compact has three structural components. First, mutual escalation: both sides shadow and pursue because both sides shadow and pursue, creating a self-reinforcing cycle neither side can unilaterally exit without conceding advantage. Second, mutual silence: when the inevitable collision occurs, both sides minimize it because both sides have something to hide. The Soviets hid incompetent seamanship. The Americans hid a complacent ASW posture. Third, mutual scapegoating: the individual operator absorbs the blame that belongs to the doctrine, the incentive structure, and the operational culture that put two nuclear-armed platforms in the same water at the same time in the dark.
The Collision Compact is not a Cold War artifact. It is the operating logic of every naval interaction where nuclear-armed platforms operate in contested proximity: the Western Pacific today, the North Atlantic, the Eastern Mediterranean. The players change. The Compact does not.
Propose the Doctrine: Five Pillars
Pillar 1: Escalation Authority at the Proximity Threshold. Detecting a threat is not the same as managing it. Every ASW commander knows the safest submarine is the one you can see, which is why the community resists separation: breaking contact means losing the track, and a lost track inside the operating area is worse than a close one. The tension between the ASW imperative (maintain contact) and the force protection imperative (maintain distance) is real, and no current authority structure resolves it. What Kitty Hawk lacked was not a distance rule but a decision authority: a defined threshold at which the force protection commander can override the ASW commander and direct the carrier to alter operations until safe separation is reestablished. That authority did not exist on Kitty Hawk’s bridge in 1984. The shift to flight ops, the course change into the wind, the acceleration to 30 knots, all happened without reference to K-314’s last known position, because nobody in the chain had the mandate to say stop until we know where the submarine is. The fix is not a published distance, which would hand the adversary a targeting metric. The fix is a classified escalation authority tied to confirmed proximity of a nuclear-armed contact, vested in a specific watch station, exercised without requiring flag-level approval in the moment of decision.
Pillar 2: Unilateral Operational Rules That Assume Noncompliance. INCSEA and its successors, including the Code for Unplanned Encounters at Sea, are constraints on the willing. Any defense posture that relies on adversary compliance with behavioral norms is built on sand. The principle is not new. The U.S. military plans against peer adversaries on the assumption of noncompliance in every other domain. But if the Navy actually operated this way at sea, Kitty Hawk would not have shifted to flight ops without verifying K-314’s position relative to the new course. The 2017 Comprehensive Review after the McCain and Fitzgerald collisions identified systemic failures in training, manning, and operational tempo, and the Navy responded with additional training requirements layered on top of the same operational culture. Training requirements do not change incentive structures. The unilateral rule is simple: when a hostile submarine has been tracked inside the carrier’s operating area within the preceding 24 hours, no course or speed change proceeds without a current plot of the contact’s last known position against the intended track. This is not a diplomatic instrument. It is an internal standing order that treats the adversary’s presence as a navigational hazard, which is exactly what it is.
Pillar 3: Nuclear Proximity Escalation Authorities. Nuclear-armed vessels operating in close proximity to adversary platforms have zero margin for accident. The Kitty Hawk/K-314 collision proved this. The institutional response was to get lucky and move on. The vulnerability is not the absence of a minimum distance threshold, which would be exploitable if published and unenforceable if classified. The vulnerability is the absence of a defined escalation authority: who on the carrier has the mandate to alter the ship’s operational posture when a nuclear-armed adversary platform is confirmed inside a proximity that puts nuclear weapons at kinetic risk. In 1984, nobody on Kitty Hawk had that authority or the institutional incentive to exercise it. The doctrine should establish that when a nuclear-armed contact is confirmed inside a defined classified range, a specific watch station has standing authority to suspend flight operations, alter course, or reduce speed without waiting for flag-level concurrence. The authority gap is the vulnerability, not the distance gap.
Pillar 4: Systemic Accountability with an Independent Enforcement Mechanism. Scapegoating individuals preserves systemic failure. Every post-incident review since Vincennes in 1988 has recommended extending investigations beyond the bridge to the doctrine, incentives, and operational culture that created the conditions. The 2017 Comprehensive Review explicitly did this. And then the institution fixed the training, kept the tempo, and the culture remained intact, because no mechanism exists to compel an institution to indict its own doctrine. The enforcement mechanism must be external: an independent review authority, modeled on the National Transportation Safety Board, with access to classified operational data and the mandate to publish findings on systemic causes without requiring the Navy’s concurrence. The NTSB model works in aviation precisely because the investigating body is not the operating body. Asking the Navy to investigate its own doctrine is asking the institution to admit the game is the problem. Forty years of identical recommendations prove that will not happen voluntarily.
Pillar 5: Unilateral Dual-System Incident Modeling. Both navies chose mutual silence after the collision because mutual silence was mutual cover. A bilateral incident review mechanism would require bilateral trust, which is the one thing adversary navies do not have. Neither side will expose its doctrine, its decision-making chain, or its operational vulnerabilities to the other. The INCSEA annual review framework exists and has never been used for honest systemic examination because doing so would hand the adversary an intelligence product on your own weaknesses. The operationally credible alternative is unilateral: mandate that the U.S. Navy conduct its own adversarial incident review that models the adversary’s likely systemic causes alongside its own, treating every incident as a product of two interacting doctrinal systems rather than one bad operator. This is what competent intelligence analysis already does. The failure is not analytical. The failure is institutional: the analysis exists but never flows back into the doctrine that produced the incident. The mandate is not to share findings with the adversary. The mandate is to ensure that the Navy’s own post-incident analysis models both halves of the Collision Compact and feeds the results into doctrine review, not just training revision.
Closing Assessment
The collision between USS Kitty Hawk and K-314 was not an isolated failure. It was the Collision Compact operating exactly as designed: competitive posturing accepted catastrophic risk, luck prevented catastrophe, institutional silence preserved the doctrine, and an individual officer absorbed the blame. The same pattern has repeated across four decades of naval incidents: USS Greeneville surfacing into the Japanese fishing vessel Ehime Maru in 2001, USS Hartford colliding with USS New Orleans in the Strait of Hormuz in 2009, USS John S. McCain and the merchant vessel Alnic MC in 2017, USS Connecticut striking an uncharted seamount in the South China Sea in 2021. The specific failure modes vary. The Compact does not.
The institutional response each time is textbook: blame the individual, preserve the system, classify the details, move on. Evseenko bore the consequences in 1984. The doctrine that put him under an 80,000-ton carrier at 30 knots in the dark bore none. The American ASW posture that tracked a hostile submarine for three days without ever establishing safe separation bore none. The INCSEA Agreement that had already been proved worthless bore none. Every institution involved emerged exactly as it had entered, having learned nothing that would require it to change.
Forty-two years later, the game continues. Chinese submarines trail American carrier groups in the Western Pacific. Russian submarines probe NATO’s Atlantic defenses. The agreements assume what the physics deny: that there will always be time to communicate, always room to maneuver, always a rational actor on the other end of the signal. Kitty Hawk and K-314 proved that assumption wrong on 21 March 1984. Nothing structural has changed to make it right.
Resonance
Egorov, Boris. (2019). “Why a Soviet Nuclear Submarine Rammed a U.S. Aircraft Carrier.” Russia Beyond. https://www.rbth.com/history/330178-soviet-nuclear-submarine-rammed-carrier. Summary: Captain Evseenko’s firsthand recollections of the collision, the week-long chase, the moment he spotted the carrier strike group at 4–5 km through the periscope, and the collision sequence from the Soviet perspective.
Larson, Caleb. (2025). “Navy Aircraft Carrier and Russian Nuclear Sub Had ‘Unexpected Collision.’” National Security Journal. https://nationalsecurityjournal.org/navy-aircraft-carrier-and-russian-nuclear-sub-had-unexpected-collision/. Summary: Analysis covering the intelligence windfall from recovered anechoic tiles, INCSEA Agreement violations, the mutual decision by both superpowers to downplay the incident, and CNO Admiral Watkins’s assessment of the Soviet captain’s judgment failure.
Lendon, Brad. (2022). “Kitty Hawk: US Aircraft Carrier, Site of a 1972 Race Riot at Sea, on Way to Scrapyard.” CNN. https://www.cnn.com/2022/03/14/asia/aircraft-carrier-kitty-hawk-scrapping-history-intl-hnk-ml/index.html. Summary: Independent reporting citing former U.S. Navy intelligence officer Carl Schuster, NHHC records confirming the 15 simulated kills, and the crew’s red submarine victory mark painted on the carrier’s island.
Leone, Dario. (2023). “The Day Soviet Nuclear Submarine K-314 Rammed USS Kitty Hawk.” The Aviation Geek Club. https://theaviationgeekclub.com/when-russian-nuclear-submarine-k-314-rammed-uss-kitty-hawk-the-americans-blamed-the-sub-captain-for-the-incident-and-the-soviets-concurred/. Summary: Detailed reconstruction citing Naval History and Heritage Command data, including collision coordinates (37°3′N, 131°54′E), RADM Dunleavy’s acknowledgment of 15 simulated kills, Captain Rogers’s bridge account, and the Subic Bay repair transit.
Leone, Dario. (2026). “Former US Navy Submariner Explains Why K-314 Captain Was at Fault.” The Aviation Geek Club. https://theaviationgeekclub.com/former-us-navy-submariner-explains-why-k-314-captain-was-at-fault-when-his-submarine-rammed-uss-kitty-hawk/. Summary: Former U.S. Navy submariner’s analysis of how Kitty Hawk’s shift to flight operations altered course and speed, creating the collision geometry, and the passive sonar limitations in the Sea of Japan.
Naval History and Heritage Command. (2009). “USS Kitty Hawk (CVA-63).” Dictionary of American Naval Fighting Ships. https://www.history.navy.mil/research/histories/ship-histories/danfs/k/kitty-hawk-cva-63-ii.html. Summary: Primary government source for USS Kitty Hawk’s operational history, including the March 1984 collision with K-314 during Team Spirit exercises and subsequent repair at Subic Bay.
Pedrozo, Raul. (2018). “Revisit Incidents at Sea.” U.S. Naval Institute Proceedings, Vol. 144, No. 3. https://www.usni.org/magazines/proceedings/2018/march/revisit-incidents-sea. Summary: Analysis of the 1972 INCSEA Agreement’s history, negotiation, and operational limitations, including the refusal to specify fixed encounter distances and the agreement’s inability to prevent incidents when operational pressure exceeded diplomatic courtesy.
U.S. Department of State. (1972). “Agreement on the Prevention of Incidents On and Over the High Seas.” https://2009-2017.state.gov/t/isn/4791.htm. Summary: Full text of the INCSEA Agreement signed 25 May 1972 in Moscow by Secretary of the Navy John Warner and Fleet Admiral Sergei Gorshkov, establishing rules of conduct for naval vessels on the high seas.