ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

The Soviet Officer Who Stopped Nuclear War During the Cuban Missile Crisis, 1962

Updated on February 10, 2015
The man who prevent a nuclear exchange in 1962
The man who prevent a nuclear exchange in 1962
The sub finally surfaced and taken into custody
The sub finally surfaced and taken into custody
Today, you can see it in San Diego
Today, you can see it in San Diego

His name is Vasili Arkhipov. After all these years before he died, Vasili revealed how close the world was to a nuclear war between the Soviet Union and America during the Cuban missile crisis.

It was on October 27, 1962, when the commander of the B-59 nuclear submarine was given the order to launch its nuclear torpedoes. Distrust and tensions between the two countries were at an all-time high and the B-59's captain, Valentin Savitsky, was under attack by the USS Beale's depth charges. At the time, the B-59 did not know that the depth charges being dropped were only practice depth charges and non-lethal- they made a lot of noise-. The USS Beale had been ordered to drop them in order to force the nuclear submarine to the surface. The hunt for B-59 was joined by other US destroyers dropping non-lethal depth charges. But, to the Soviet crew below, they seemed real. Faced with what seemed like the end and thinking a real doomsday had occurred between the countries, the commander ordered his 10-kiloton nuclear torpedoes armed. Soviet radar had placed its sights upon the American aircraft carrier, USS Randolf, which led the naval task force.

Inside the Soviet sub was the decision that could cause a nuclear exchange. To do this, all three Soviet officers had to be in agreement. Once fired, the USS Randolf would have been sunk. It would highly likely, President Kennedy, would have ordered some of the American nuclear arsenal launched at their planned targets in Russia and of course, Russia would launch their missiles. Millions might have been killed. However, in order for the fire order to occur, the sub commander, its political officer and Arkhipov would all have to agree to fire. The sub commander and the political officer were in agreement, but Arkhipov was unsure what the hell the Americans were doing or trying to do. At the time, he stated to the others that maybe the Americans are just trying to force us to the surface.

As the booms got louder, a heated debate was argued with Arkhipov simply saying, nyet, disbelieving that the Beale was trying to destroy them. At some point, there was a realization that what the Beale was trying to do was to force them to surface. But this was a considerable time after the heated debate between the three Soviet officers.

Arkhipov died in 1998 from radiation posioning that had occurred in 1961 during a mishap aboard the B-59. He was the man that prevented a nuclear exchange.

Comments

    0 of 8192 characters used
    Post Comment

    No comments yet.

    working

    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, hubpages.com uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

    For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at: https://hubpages.com/privacy-policy#gdpr

    Show Details
    Necessary
    HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
    LoginThis is necessary to sign in to the HubPages Service.
    Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
    AkismetThis is used to detect comment spam. (Privacy Policy)
    HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
    HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
    Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
    CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
    Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy)
    Features
    Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
    Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
    Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
    Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
    Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
    VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
    PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
    Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
    MavenThis supports the Maven widget and search functionality. (Privacy Policy)
    Marketing
    Google AdSenseThis is an ad network. (Privacy Policy)
    Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
    Index ExchangeThis is an ad network. (Privacy Policy)
    SovrnThis is an ad network. (Privacy Policy)
    Facebook AdsThis is an ad network. (Privacy Policy)
    Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
    AppNexusThis is an ad network. (Privacy Policy)
    OpenxThis is an ad network. (Privacy Policy)
    Rubicon ProjectThis is an ad network. (Privacy Policy)
    TripleLiftThis is an ad network. (Privacy Policy)
    Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
    Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
    Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
    Statistics
    Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
    ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
    Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)