ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

The Mystery Behind the Vela Incident of 1979

Updated on June 11, 2018
Dean Traylor profile image

Dean Traylor is a freelance writer and teacher. He wrote for IHPVA magazines and raced these vehicles with his father (who builds them).

The Satellite Vela Hotel
The Satellite Vela Hotel | Source

The Cold War was heating up. The Soviets and the Americans had their missiles aimed at each other while other nations were scrambling to start their own nuclear weapons programs. The world in 1979 was a scary place. So, when a mysterious double-flash was detected over the southernmost part of the Indian and Atlantic Ocean by a spy satellite on September 22 of that year, tensions within the American intelligence community were elevated.

The double-flash was an unwelcome find; it meant someone had exploded a nuclear bomb. Yet, the usual suspects, The Soviet Union and China, were not known to have test sites in this area. Neither were the French or South Africans, despite having island territories near the suspected region.

The mystery deepened after countless reconnaissance missions by the US Air Force failed to register any evidence of the type of radioactivity a nuclear bomb would release.

The mystery of the Vela Incident of 1979 was an event with no easy answers. Speculations about its cause has run the gamut; scientists, national labs, and government panels had put forward several theories such as a top secret nuclear test, meteoroids entering the atmosphere, or a possible malfunction on the Vela Hotel satellite.

To this day – after more than 30 years – its exact origin is still being debated, even after the tensions of the cold war years have dissipated. This incident has become one of the Cold War’s greatest mysteries.

The Satellite’s Mission

Possible location of the Incident
Possible location of the Incident | Source

In understanding how the incident occurred, one has to look at the mission of the satellite that recorded it. Launched on May 23, 1969, the Vela Hotel satellite was one of two satellites used for Project Vela. It was designed to detect atmospheric nuclear testing throughout the world. It collected data and sent the readings to a base in the United States where it was interpreted by a member of an intelligence agency. One of its components, a Bhangmeter, was a type of photometer intended to detect atmospheric nuclear detonation. This particular tool would prove to be the one under scrutiny.

Vela Hotel (also known as Vela 6911) was not just used to detect an explosion. Its purpose was to ensure that all the nuclear and non-nuclear states that signed 1963’s Partial Limited Test Ban Treaty were adhering or reducing testing of nuclear weapons in the atmosphere, underwater, or in outer space.

By the late '60s, most of these nations (United States, Britain, and the Soviet Union) had moved their tests to underground facilities. Only France and China continued to do atmospheric testing throughout the 1970s and early 1980s. France continued until 1974 and China until 1980.

Another goal of the satellite was to gauge a few “non-declared nuclear” nations. During this period, several nations were suspected of starting a nuclear weapons program or in possession of a nuclear bomb. Israel, India, and South Africa were the suspect nations.

While the satellite was equipped with state-of-the-art detection equipment, Vela Hotel had several faulty systems. For one thing, the satellite had been orbiting the Earth for more than 10 years and had already gone two years beyond its so-called design lifetime (Matt’s Today in History.com, 2011). Another problem was noted; it had a failed electromagnetic pulse sensor and a faulty recording memory. According to an entry in Wikipedia, that fault cleared itself by March 1978.

Suspicious Nations

Source

Due to the location of the suspected double-flash, two nations were suspected of conducting the supposed test. It occurred between The French possession of Crozet Islands and South Africa’s Prince Edward Islands. The Crozet Islands were small and sparsely inhabited and fairly isolated from other countries. It would have been an ideal place to do atmospheric nuclear tests. However, France had moved toward underground testing by this time.

South Africa and Israel became the other culprits. According to an article edited by Jeffery.

...wind pattern studies confirmed that fallout from an explosion in the suspected region could reach southwestern Australia.

Richelson for the National Security Archive website, South Africa had been preparing for a nuclear test in August 1977 before Soviet and US satellites detected it. Also, there had been reports – according to the article – that there was an Israeli-South African cooperation (much of this was speculated and obscure at best). Through diplomatic pressures from the U.S and Soviets, South Africa abandoned their program.

Another plausible, but unlikely, suspect was India. The country supposedly conducted a nuclear test in 1974. However, India had signed the Limited Test Ban Treaty and had complied with it by exploding their bomb underground (Eventually, in the 1990s, India and its rival Pakistan would officially declare they had nuclear bombs).

Another country mentioned as a possible culprit was Taiwan. This particular claim came from a video segment from How Stuff Works. Not much is given as to why Taiwan would be involved.

Where’s the Radiation?

The US wasn’t going to sit by and speculate if South Africa had nukes. Several US Air Force WC-135B surveillance aircraft flew over the Indian Ocean and South Atlantic region soon after the double-flash was reported. The planes were equipped to detect the presence of radioactive dust; however, the planes failed to detect any signs of nuclear radiation.

The mystery of the flash deepened. In Southeastern Australia, low levels of iodine-131 were detected in thyroid glands of sheep. Iodine-131 is a short-life product of nuclear fission released soon after a detonation. According to Frank Barnaby, writer of the book The Invisible Bomb, wind pattern studies confirmed that fallout from an explosion in the suspected region could reach southwestern Australia.

Another report gave credence to a covert nuclear detonation theory. At the Arecibo Ionospheric Observatory and Radio Telescope in Puerto Rico, the researchers at the facility reported detecting “anomalous Ionospheric waves during the morning of September 22, 1979, which moved from southeast to northwest, an event which had not been observed previously by the scientists (Wikipedia, 2011). “

An Act of Nature or Man-Made

Originally retrieved from www.elakiri.com
Originally retrieved from www.elakiri.com

In 1980, A Presidential panel commissioned by Frank Press – Science Advisor to President Jimmy Carter and chairman of the Office of Science and Technology - came to the conclusion that the double-flash was not caused by a nuclear detonation. The data collected from the satellite, including those recorded by the Bhangmeter, were either inconclusive or in dispute. The council concluded that the satellite may have been hit by a meteoroid.

The panel’s finding came under fire, not just by independent labs but by governmental groups. The Defense Intelligence Agency (DIA) was one of these groups who believed that the data supported the detection for a nuclear detonation.

Since then, several speculations have been made. While there are those in the intelligence community who state that it was either a nuclear explosion or a meteoroid, others claim that the satellite may have detected the presence of lightning, meteor showers, or had a malfunction.

In the long run, the flashes didn’t turn out to be a major event. While it sent jitters throughout the intelligence community, it never led to serious military or diplomatic actions. Still, the Vela Incident is an example of how technology doesn’t always provide the clearest picture to what’s happening in the world.

Originally posted on http://controversyandmystery.blogspot.com/2013/12/the-vela-incident.html
Originally posted on http://controversyandmystery.blogspot.com/2013/12/the-vela-incident.html

Vela Incident from How Stuff Works

© 2016 Dean Traylor

Comments

    0 of 8192 characters used
    Post Comment

    • profile image

      jgshorebird 

      2 years ago

      Interesting. Thanks.

    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)