On 9 November 1979, and again on 3 and 6 June 1980, North American Aerospace Defense Command warning channels generated false indications of Soviet missile attack that pushed U.S. command posts into threat-assessment conferences and precautionary force moves. Sensors that actually look at the sky—DSP, BMEWS, and related radars—did not show matching launches. Human conference calls stood the forces down. The General Accounting Office, a Senate Armed Services staff investigation by Senators Gary Hart and Barry Goldwater, and declassified Defense Department memoranda to President Carter document the causes and the fixes. The Archive tension is not whether computers lied. It is how institutional safeguards—not a lone-hero myth borrowed from a different country's 1983 duty shift—contained the errors.
The Alerts
On 9 November 1979, false indications of a mass raid appeared when simulated or exercise data was inadvertently introduced into the NORAD Computer System at Cheyenne Mountain. Displays at NORAD, SAC, and the National Military Command Center showed attack traffic that did not match live sensors. Interceptors launched; the National Emergency Airborne Command Post left Andrews. Within minutes NORAD confidence in the warning collapsed and the episode ended. Soviet leader Leonid Brezhnev later messaged concern about the danger of such errors.
On 3 June 1980, at about 2:26 a.m. Eastern, SAC displays indicated submarine-launched ballistic missiles, then rapidly escalating counts; similar corruption appeared at other posts while NORAD's own warning screens showed nothing unusual. A faulty integrated circuit in a communications processor—press shorthand later called the "46-cent chip"—was corrupting routine "000" missile-count fields into phantom numbers. SAC crews went to aircraft; NEACP taxied. Conference calls comparing sensor feeds ended the alert. On 6 June, while NORAD ran the system in a configuration meant to isolate the fault, another false indication appeared and again produced precautionary SAC moves before stand-down.
GAO MASAD-81-30 PDF: https://www.gao.gov/assets/masad-81-30.pdf
Senate Hart/Goldwater report (govinfo): https://www.govinfo.gov/content/pkg/CPRT-96SPRT68531O/pdf/CPRT-96SPRT68531O.pdf
Official Posture: Conferences and Sensors
Doctrine did not treat a single display as launch authority. Threat assessment conferences pulled senior officers onto common voice nets to compare NORAD, SAC, NMCC, and sensor pictures. When radar and infrared launch-detection systems contradicted the corrupted message traffic, confidence dropped and irreversible actions were not ordered. Secretary of Defense Harold Brown told President Carter that human safeguards remained essential precisely because unrelated malfunctions could recur. That is institutional language, not folklore about one officer unilaterally "saving the world."
FRUS 1977–80 Vol. IV Doc 202 (Brown on June alerts): https://history.state.gov/historicaldocuments/frus1977-80v04/d202
What GAO and the Senate Put on Paper
GAO's MASAD-81-30 reviewed NORAD missile-warning failures and corrective actions: an offsite software development and testing facility so exercise data would not again inject into live Cheyenne Mountain operations; reforms to missile-warning transmission procedures, line-check formats, and outgoing messages. The Hart/Goldwater Senate print reconstitutes the June chronologies, explains threat-assessment conference practice, and lists the 1979–80 conference occasions—including the 9 November sim-data event and the June chip events. National Security Archive Nuclear Vault briefing books assemble Brown memoranda, William Odom notes, and Aerospace Defense Command history excerpts that match those findings.
NS Archive — False Warnings briefing book: https://nsarchive.gwu.edu/briefing-book/nuclear-vault/2020-03-16/false-warnings-soviet-missile-attacks-during-1979-80-led-alert-actions-us-strategic-forces
NS Archive EBB 371 (Nuclear Vault): https://nsarchive2.gwu.edu/nukevault/ebb371/
GAO products page — MASAD-81-30: https://www.gao.gov/products/masad-81-30
Corrective Actions Without Erasing Risk
After November, NORAD moved to isolate testing from operations. After June, hardware and message-design fixes targeted the communications processor path; continuous voice-tell watches gave commanders a way to override false computer-driven indications. Brown still warned Carter that another unrelated malfunction could someday generate another false alert. The documentary lesson is layered defense and honest residual risk—not a claim that software became perfect in 1980.
Why the Displays Disagreed
The June faults did not paint identical phantom raids on every console. SAC and Pentagon message displays could show rising SLBM and ICBM counts while NORAD's own warning screens—closer to the sensor fusion mission—showed nothing matching. That disagreement was the operational clue. Conference participants treated inconsistency across posts as evidence against a real mass raid, then checked independent sensors. Viral retellings that describe "NORAD saw 2,000 missiles" without the split-display detail erase why the stand-down was available inside doctrine.
Brown's Residual-Risk Line
In memoranda collected by the National Security Archive and published in FRUS, Brown told Carter the specific June cause was being chased—including the stubborn fact that the suspected circuit would not reliably fail again on the bench—while insisting another unrelated malfunction could someday repeat the scare. He argued confidence should remain in people reading warning data, not in a promise of perfect hardware. That residual-risk sentence is the opposite of meme certainty.
Petrov Sibling Without Merge
Stanislav Petrov's September 1983 episode inside the Soviet early-warning duty system is a neighboring Cold War false-alarm story. It is not the NORAD 1979–80 spine. Different year, different country, different machine, different command culture. Viral captions that merge "the man who saved the world" onto American chip failures erase GAO and Senate paperwork about conferences, sensors, and institutional fixes. Neighbor Petrov for comparative false-alarm culture; do not merge.
Myth Discipline
Frame as documented U.S. missile-warning system failures with declassified investigative trails. Refuse "one wrong key almost launched Minuteman" slogans that erase threat-assessment conferences and sensor cross-checks. Refuse dating conflations that put a midnight Brzezinski phone drama on the morning 9 November tape incident. Refuse Petrov-merge hero captions as substitutes for Hart/Goldwater and GAO.
What the Paper Trail Settles
Settled on GAO, Senate, FRUS, and NS Archive doors: 9 November 1979 sim/exercise data into live NORAD warning channels; 3 and 6 June 1980 communications-processor faults producing phantom missile counts at some posts; precautionary SAC/NEACP moves; sensor disagreement and conferences ending the alerts; corrective testing isolation and message reforms. Overclaim to refuse: world-saved-by-one-American merges with the Petrov sibling.
Officials said human safeguards held. The reports say the computers failed and the conferences worked. NORAD 1979–80 is that documented gap—read with MASAD-81-30 and the Hart/Goldwater print open.