Get AI summaries of any video or article — Sign up free
How Humanity Almost Destroyed Itself thumbnail

How Humanity Almost Destroyed Itself

Veritasium·
6 min read

Based on Veritasium's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Midair accidents and weapon handling failures have repeatedly threatened nuclear detonation, including the 1966 Palomares collision over Spain.

Briefing

Nuclear catastrophe has repeatedly been one mechanical failure, human error, or bad signal away—not from deliberate attack, but from accidents involving bombs, missiles, and early-warning systems. The most vivid example came on January 17, 1966, when a B-52 carrying four hydrogen bombs collided midair with its refueling tanker over Spain. The crash killed seven crew members and four tanker crew members, scattered the bombs on land and sea, and left one missing for nearly three months—an unsettling reminder that the world’s deadliest weapons have sometimes been lost in plain sight.

The Palomares incident involved hydrogen bombs roughly 75 times more powerful than the Hiroshima device. Two of the four bombs detonated only with conventional explosives on impact, but the internal design required a symmetrical trigger to set off the fission-and-fusion sequence. Because the conventional charges exploded on the ground, the shockwave was not symmetrical, so the plutonium core was dispersed without triggering a full nuclear detonation. The result was radioactive contamination along a 2.6-square-kilometer stretch of coastline that still persists. A third bomb was recovered intact, while the fourth remained missing for 81 days until it was finally found and recovered—after an extensive multi-ship search.

This was not treated as an outlier. The Pentagon’s official tally lists 32 “Broken Arrow” accidents between 1950 and 1980—incidents involving nuclear weapons that could have led to nuclear detonation or other severe consequences. Five of those occurred during Operation Chrome Dome, including earlier B-52 crashes in 1961 and 1966. In one 1961 case over North Carolina, conventional explosives failed to detonate, leaving a risk that the hydrogen bomb could have been armed and ready to trigger. Later declassified reporting disputed official assurances, indicating the bomb may have been armed—potentially sensitive to a single switch.

Other near-misses extended beyond aircraft. A 1968 Greenland crash burned four hydrogen bombs in a fire, requiring months of decontamination. A 1965 training accident off Japan left a hydrogen bomb on the seafloor for decades, and the missing weapon count includes cases where warheads were never recovered. The best-known silo incident occurred in September 1980 at a Titan II site in rural Arkansas: a ratchet wrench socket fell, punctured the missile’s fuel tank, and led to an explosion after fuel vapors ignited. The hydrogen warhead was blown out of the silo but did not detonate.

The danger also comes from misreading signals. During the Cuban Missile Crisis, both superpowers still conducted high-altitude nuclear tests, raising the risk that a test could be mistaken for a first strike. In 1983, the Soviet satellite early-warning system detected an ICBM launch; officer Stanislav Petrov judged it likely false and rejected an automatic counterattack policy. In 1995, a Norwegian rocket launch was misidentified by Russian radar as a Trident ICBM, prompting emergency escalation that involved the delivery of nuclear launch codes to President Boris Yeltsin.

Across these episodes, the pattern is consistent: nuclear risk is not only about intent. It’s about the fragility of systems—technical, procedural, and psychological—under stress. Even as global nuclear stockpiles have fallen from more than 70,000 weapons in 1986 to 12,705 in 2022, the remaining arsenal means the future still depends on luck and careful judgment.

Cornell Notes

Accidents and false alarms have repeatedly brought nuclear weapons close to catastrophe, showing that the biggest risk is often not deliberate use but freak failures and misinterpretations. The 1966 Palomares collision over Spain scattered four hydrogen bombs; two detonated conventionally but failed to trigger nuclear fusion because the required symmetrical conditions were not met, while one bomb was missing for 81 days. The Pentagon’s “Broken Arrow” record lists dozens of such incidents, including a 1980 Titan II silo accident where a dropped tool punctured fuel tanks and caused an explosion without detonating the warhead. Early-warning mistakes have also nearly triggered war, including the 1983 case where Stanislav Petrov rejected a likely false satellite alert. Together, these events argue that nuclear safety depends on both technology and human decision-making under uncertainty.

What happened during the 1966 Palomares B-52 tanker collision, and why didn’t it produce a nuclear detonation?

On January 17, 1966, a B-52 carrying four hydrogen bombs collided midair with its refueling tanker over Spain. The boom arm broke off the B-52’s left wing, killing multiple crew members and causing the bombs to fall. Two bombs detonated only their conventional explosives on impact, but hydrogen-bomb triggering requires a symmetrical setup to initiate the fission stage that then creates the conditions for fusion. Because the conventional charges detonated on the ground, the shockwave was not symmetrical, so the fission/fusion sequence did not start. The conventional explosion still blew apart the plutonium core, contaminating a 2.6-square-kilometer coastline area with radioactive material.

Why was the missing bomb in Palomares such a major concern?

The fourth hydrogen bomb—about 75 times the Hiroshima yield—was missing after the crash. It took 29 U.S. Army ships and 81 days to locate and recover it. The concern wasn’t just the possibility of detonation; it was also the risk that a lost weapon could be found later under unpredictable conditions, potentially involving arming mechanisms, recovery attempts, or further accidents.

What does “Broken Arrow” refer to, and how many such incidents were officially listed for 1950–1980?

“Broken Arrows” is the term used for accidents involving nuclear weapons. The Pentagon officially lists 32 such accidents between 1950 and 1980. During Operation Chrome Dome specifically, five Broken Arrow cases involved B-52 crashes carrying hydrogen bombs.

How did the 1980 Titan II silo incident unfold, and what was the near-miss outcome?

In September 1980, maintenance work inside a rural Arkansas Titan II missile silo involved a fueled, launch-ready missile with a 9-megaton hydrogen bomb in its nose cone. A ratchet wrench socket fell 24 meters, puncturing the missile’s fuel tank and causing rocket fuel to leak into the silo. After about 8.5 hours, fuel vapors ignited, producing an explosion that killed one person and injured 21. The silo door flew more than 60 meters, and the warhead was blown out about 30 meters—but it did not detonate.

How did Stanislav Petrov’s decision in 1983 prevent a likely nuclear exchange?

On September 26, 1983, the Soviet satellite-based early warning system detected an ICBM launch and policy required an immediate counterattack if inbound missiles were detected. Officer Stanislav Petrov doubted the reading, reasoning that a real first strike would likely involve hundreds of ICBMs simultaneously rather than a single launch. When the system reported additional missiles, he treated them as a glitch. His skepticism and decision to not escalate helped avoid a full-blown U.S.-Soviet nuclear exchange.

What was the 1995 Norway rocket incident, and why did it escalate?

On January 25, 1995, scientists launched a rocket off the coast of Norway to study the Northern Lights. Russian radar interpreted the launch as having a similar flight pattern and speed to a submarine-launched Trident ICBM. The seriousness of the misidentification led to emergency steps, including bringing a briefcase containing nuclear launch codes to Russian President Boris Yeltsin.

Review Questions

  1. Which design requirement prevented the hydrogen bombs in Palomares from triggering fusion even though conventional explosives detonated?
  2. What reasoning did Stanislav Petrov use to judge the 1983 satellite alert as likely false?
  3. Across the examples, what recurring failure modes appear—technical breakdown, procedural error, or information misinterpretation? Give one example for each.

Key Points

  1. 1

    Midair accidents and weapon handling failures have repeatedly threatened nuclear detonation, including the 1966 Palomares collision over Spain.

  2. 2

    Hydrogen bombs can fail to detonate nuclearly even when conventional explosives explode, because fusion triggering depends on specific, symmetrical conditions.

  3. 3

    The Pentagon’s “Broken Arrow” tally documents dozens of nuclear-weapon accidents between 1950 and 1980, including multiple B-52 crashes during Operation Chrome Dome.

  4. 4

    Silo and aircraft incidents show that even when warheads are damaged or displaced, detonation is not guaranteed—yet the consequences of near-misses remain severe.

  5. 5

    False alarms and misinterpretations of early-warning data have nearly triggered nuclear retaliation, as in the 1983 Petrov incident and the 1995 Norway rocket confusion.

  6. 6

    Nuclear risk is not limited to intentional use; it also depends on system reliability and human judgment under uncertainty.

  7. 7

    Even with declining stockpiles, the remaining arsenal means future safety still hinges on preventing accidents and improving detection accuracy.

Highlights

On January 17, 1966, a B-52 carrying four hydrogen bombs collided with its refueling tanker over Spain, killing crew members and leaving one bomb missing for 81 days.
Two Palomares bombs detonated conventionally but did not trigger nuclear fusion because the shockwave was not symmetrical—yet plutonium contamination still spread along the coastline.
The Pentagon lists 32 “Broken Arrow” accidents between 1950 and 1980, including multiple hydrogen-bomb B-52 crashes during Operation Chrome Dome.
Stanislav Petrov’s refusal to escalate a 1983 satellite alert likely prevented an automatic counterattack under Soviet policy.
In 1980, a dropped tool punctured a Titan II fuel tank, leading to an explosion that displaced the hydrogen warhead without detonating it.

Topics

  • Nuclear Accidents
  • Broken Arrow
  • Cold War
  • Early Warning Systems
  • Hydrogen Bombs

Mentioned

  • Larry Messinger
  • Jack ReVelle
  • Arthur Schlesinger Jr.
  • Vasili Arkhipov
  • Stanislav Petrov
  • Boris Yeltsin
  • Alexander Lebed
  • ICBM
  • B-52
  • TNT
  • CIA
  • USSR
  • US
  • D-Day