13 times the U.S. almost destroyed itself with its own nuclear weapons (13 items)
In two days, it will be the 69th anniversary of the the first ever atomic test, conducted in the deserts of New Mexico on July 16, 1945. The bomb was found to have the same destructive force as 15,000 to 20,000 tons of TNT, according to PBS. PBS also gave an account of General Leslie Groves, who was there to witness the testing and described it as "successful beyond the most optimistic expectations of anyone."
However, the U.S.' record with nuclear weapons has not always been quite as "successful" as its first atomic test. In fact, the U.S. has had several close encounters with its own nuclear weapons that could easily have ended in disaster. Compiled here are the stories of 13 nuclear near-misses of catastrophic proportions.
1 of 13. January, 1961: Goldsboro, North Carolina
McNamara was speaking, according to CNN, about the damaged mechanism that was the sole preventer of a nuclear explosion in Goldsboro.
The two bombs were released when the Air Force bomber that was carrying the weapons broke in half midflight. The parachute for the first bomb, pictured left, activated and prevented detonation. The parachute for the second bomb failed to open, and the bomb was armed when it hit the ground.
Had it exploded, CNN calculates that it would have killed 28,000 people and injured 26,000, emitting radiation over a 15 mile radius.
Five of the eight man crew survived the bomber crash.
2 of 13. October 25, 1962: Duluth, Minnesota
A guard at the compound shot at the intruder, who was in the act of climbing the fence. This shot activated the "sabotage alarm," which triggered warnings at all military bases in the area including the base at Volk Field, Wisconsin.
The Volk alarm had been wired incorrectly, and instead of a simple warning the system ordered nuclear armed F-106A interceptors to go to the alarm's point of origin — Duluth. Due to the Cuban Missile Crisis, the country was at DEFCON 3, a time when there were no practice drills. The pilots expected to be dropping their nuclear payload that night.
Immediate communication came from Duluth, informing Volk that something had been miscommunicated and a nuclear strike was not needed. The planes, which were already headed down the runway towards Minnesota, were called off by a car that raced from the Volk command center as soon as the communication from Duluth was received, stopping the planes' takeoff.
The intruder was later revealed to be a black bear.
3 of 13. September 19, 1980: Damascus, Arkansas
The repairman accidentally dropped a wrench into the silo, and the heavy tool punctured the fuel tank of the missile. The missile leaked fuel for over eight hours before it finally exploded, killing a service member, injuring 21 others, and destroying the compound where the silo was held.
Despite the massive blast, the nuclear warhead was recovered intact.
4 of 13. November 9th, 1979: Washington, D.C.
The U.S. prepared retaliation missiles and conducted an immediate threat assessment conference. After six minutes of scanning airspace and satellite data, no Russian missiles were found, and the U.S. found no need to return fire.
The cause of the alarm was later found to be a military training tape describing a fictional Soviet attack. The tape had accidentally been loaded into the early warning computers. After the scare, a new facility was created for the sole purpose of running these training tapes in isolation from other compounds.
5 of 13. March 14, 1961: Yuba City, California
The commander, meanwhile, stayed on board the failing aircraft in order to steer the plane away from the densely populated areas of Yuba City, California, that the plane was directly over.
The commander bailed from the plane at 4,000 feet after steering the plane away from populated areas. The plane crashed several miles from the city and the weapons were torn from the plane, although their safety mechanisms prevented them from exploding or releasing any contamination.