Yanakiyev and the Secret Soviet Plan to Blind the Sixth Fleet

By Marcus Boone · September 24, 2026

Kept secret for 43 years, an internal Warsaw Pact blueprint for naval surveillance exposes the technical gaps the Soviets feared would let NATO slip through.

A naval commander enters a room and finds he cannot speak to his allies, and a destroyer slips past his radar because his computer center is out of date. In the high-stakes theater of the Black Sea, these were not hypothetical failures but the primary anxieties of the men tasked with barring the West from the Soviet south.

The record is a June 11, 1974, memorandum from the CIA to the Director of Central Intelligence. It summarizes an article from a SECRET Soviet publication titled Information Collection of the Headquarters and the Technical Committee of the Combined Armed Forces. The author was Rear Admiral V. G. Yanakiyev, who served as Chief of Staff before becoming Commander-in-Chief of the Navy of the Bulgarian People's Republic, a force that participated in the 1968 invasion of Czechoslovakia but otherwise saw little combat during its existence. Yanakiyev was writing for an audience of Warsaw Pact officers—the military alliance designed to integrate the command of the Eastern Bloc under Moscow's thumb—and his subject was the systemic failure of their naval coordination.

The Bulgarian Admiral

Yanakiyev’s article, appearing in issue No. 4 of the secret journal in 1972, does not read like the confident output of a monolithic superpower. Instead, it is a plea for modernization and professionalization. He argues for the "necessity of creating a reliable system for controlling combined Warsaw Pact naval actions," specifically within the Black Sea, the marginal sea bordered by the USSR, Turkey, and several other nations that served as the primary maritime corridor for Soviet southern operations.

The record shows Yanakiyev was preoccupied with the basics of command: communication, recognition, and warning. He explicitly notes that "the system for controlling allied naval forces can be improved still more," urging a move toward "standardizing the equipment of command posts" and "establishing communications among computer centers." The irony is sharp; the Bulgarian Admiral was effectively lecturing the Warsaw Pact headquarters in Moscow on how to manage its own satellites. He suggests that without a "single document to regulate coordinated efforts," any attempt to organize a convoy service or a defense of sea lanes in the event of war would be mere "improvisation, which cannot produce the necessary effect."

1972 and the Sixth Fleet

The catalyst for this anxiety was the persistent presence of the US Sixth Fleet, the numbered fleet headquartered in Naples that maintained a strategic presence in the Mediterranean. The record notes that because the Sixth Fleet entered the Black Sea several times a year, Yanakiyev considered it "advisable to introduce unified planning and control measures to detect enemy groupings and maintain surveillance of them."

This reveals a critical tension in the Soviet approach to the region. While the public record establishes the Black Sea Fleet as a dominant force, Yanakiyev’s internal concerns suggest that this dominance was a facade of numbers rather than a reality of control. He argues that the "operational axes and the strike objectives of the navies of the allied countries will, as a rule, coincide," yet the means to coordinate those objectives were missing. The record highlights his specific alarm over "radio-electronic warfare," warning that if measures taken by one navy affect another without a "single plan and concept," the results could be "unfavorable."

The Moscow Leak

The procurement of this journal is where the record moves from naval strategy to espionage. The CIA memorandum explicitly warns that "because the source of this report is extremely sensitive, this document should be handled on a strict need-to-know basis." This is not the language used for a document found in a trash bin or intercepted via signals intelligence; it is the language of a high-value human asset.

The desk's reading is that the CIA had a source embedded deeply within the Warsaw Pact Headquarters in Moscow, someone with access to the inner circle's technical journals. The procurement of a 'SECRET' internal publication, combined with the extreme handling instructions, points to a mole who could provide the Americans with the Soviets' own internal self-critiques.

However, a glaring discrepancy exists in the timeline. The article was published in 1972, but the CIA memo is dated June 11, 1974. The pattern suggests a delayed processing of a bulk intelligence haul or a retrospective shift in priority. The CIA did not react to Yanakiyev's concerns in real-time; they mined them two years later, perhaps as the technical specifications of the Sixth Fleet's capabilities evolved.

The Missing Pages

The memorandum is part of a larger "Intelligence Information Special Report," but the CIA's release provides only the summary and the article itself. The distribution list for the full report is telling: it went to the Director of Science and Technology and the National Security Agency (NSA).

If this file is shaped the way it looks, the missing pages of the Special Report contained a technical vulnerability map for US electronic warfare targeting. Yanakiyev provided the roadmap—admitting that the Warsaw Pact lacked unified computer centers and synchronized radio-electronic warfare—and the NSA likely used that admission to calibrate how to jam or spoof the very communications the Bulgarians were desperately trying to build. The record gives us the Admiral's complaints; the missing pages likely give us the Americans' exploitation of those complaints.

The Logic of the Gap

The most telling part of the record is Yanakiyev’s insistence on "permanent operations groups"—exchanging officers between national headquarters to overcome the "language barrier" and build "work habits." This is a confession of fragmentation. The pattern suggests that Soviet command and control over its satellite navies was not only technically deficient but culturally fractured. The "monolithic" Warsaw Pact was, in reality, a collection of national navies that could barely speak to one another without a manual.

The desk's reading is that the primary intelligence value of this file was not the strategic desire to block NATO, but the identification of specific vulnerabilities in the Warsaw Pact's emerging digital C3 (Command, Control, and Communications) architecture. By admitting that their "control organs" required "mechanization and automation," Yanakiyev handed the US a list of the Soviets' own technical voids.

The full release of these files would likely show that the US did not need to build a better fleet to dominate the Black Sea; they simply had to wait for the Warsaw Pact to fail at the basic task of synchronization. The cost of this failure was borne by the officers like Yanakiyev, who saw the gaps in their own shield and shouted into a void, unaware that the very documents they used to request help were being read in Langley. The still-withheld pages are protecting not the Soviets, but the specific methods the NSA used to turn a Bulgarian Admiral's professional frustration into a tactical weapon.