WHEN COMPUTERS CRIED WOLF — NORAD, 1979

☢ CHAPTER FIVE Primary POV: Major Thomas Reeves, NORAD — Cheyenne Mountain, Colorado Secondary POV: Captain Mikhail Sidorov, Soviet Strategic Missile Forces THE MOUNTAIN THAT NEVER SLEEPS POV: Major Thomas Reeves Cheyenne Mountain has a heartbeat. Not a human one — deeper, mechanical, and constant. A pulsing hum from generators, air handlers, and supercomputers that digested every byte of radar and satellite data pouring in from across the Northern Hemisphere. This place was designed to survive the end of the world — and on the morning of November 9, 1979, it nearly began it. I stepped into the command center balancing weak coffee and a stale donut. The night-shift crew looked like they had aged five years since yesterday — bloodshot eyes, unshaven faces, the thousand-yard stare that only comes from living every day on the razor’s edge of Armageddon. “Morning, Reeves,” Lieutenant Carter croaked. “Systems are sluggish today.” “Everything’s sluggish in this mountain,” I said. “Even the clocks.” I sat at my missile-warning console. Rows of screens blinked softly, their glow casting long shadows across steel floors. Down here, sunlight didn’t exist. Only data. Only signals. Only the fear of what might appear on those screens. A GLITCH WAITING TO HAPPEN We had been testing new simulation software — training tapes designed to mimic the early stages of a Soviet nuclear strike. It was supposed to run in a sealed environment. Supposed to. But anyone who worked with 1970s computers knew better. They were temperamental gods: overly literal, easily confused, and capable of wreaking havoc if fed the wrong line of code. Somewhere in the guts of the system, a wire waited, a glitch lingered, a training scenario slept — waiting for the wrong moment to wake. We didn’t know that yet. We were still laughing at bad coffee and the upcoming football game. The kind of normalcy you cling to when you work inside a nuclear trigger mechanism. A QUIET MORNING IN MOSCOW POV: Captain Mikhail Sidorov Cold seeped through the windows of the Moscow military district command center as I arrived, stamping snow off my boots. Winter tasted like coal smoke and iron in the air. I poured myself tea and took my seat at the observation desk. Just another morning of monitoring the Americans. The Cold War was tense, but static. Predictable. No troop movements. No missile alerts. No reason to expect the day would be historical — or nearly catastrophic. I sipped my tea, warm and comforting, unaware that thousands of miles away, a computer error was about to tell the U.S. military that the Soviet Union had launched hundreds of nuclear missiles. THE ALARM THAT SHOULD NEVER HAVE SOUNDED POV: Major Reeves The first alarm was sharp — too sharp. A piercing, metallic BEEEEP that froze the air around us. Then another. And another. Missile Alert Indicator #1 turned red. Then #2. Then #3. Then all of them. Lines began arcing across the main display — hundreds of them — like bright claws reaching toward North America. My donut fell out of my hand and hit the console. Carter’s voice wavered. “What the hell—” He didn’t finish. My screen updated: SOVIET MISSILE LAUNCH DETECTED. MULTIPLE INCOMING BALLISTIC MISSILES. A chill shot through my chest. Someone behind me whispered: “We’re looking at the end.” Phones erupted. Officers ran. Commanders shouted for confirmations. This wasn’t a drill. The system thought the Soviets had launched a full-scale nuclear attack. THE WORLD HOLDS ITS BREATH “Confirm with satellites!” I yelled. The DSP satellite officer stared at his monitor, eyes wide with dread. “Sir… satellites show nothing. No infrared signatures.” My mouth went dry. Missile plumes from a real launch would burn hot — unmistakable from space. But there was nothing. So why did our system show hundreds of incoming missiles? “Cross-check with all radar stations!” I barked. Carter’s fingers flew across the console. “Sir… this data pattern…” He stopped, swallowing hard. “It matches our training scenario exactly.” Everything inside me went numb. “You’re telling me,” I whispered, “that a training tape is showing on our live early-warning monitors?” “I think so.” The alarms continued blaring. Officers scrambled. Somebody vomited in a trash can. This was how nuclear war could start. Not with a missile. With a mistake. MEANWHILE, IN MOSCOW POV: Captain Sidorov Our screens showed nothing unusual. But American activity? That was a different story. Suddenly, their encrypted communications spiked. Air Force bases went on alert. Bomber engines warmed on runways. “Why are they reacting like this?” my commander asked, puzzled. One of our analysts blanched. “They think we launched something.” A chill spread across the room. “But we haven’t—” “No,” the analyst said, “but they don’t know that.” Silence. Horrifying, suffocating silence. “If the Americans believe they’re under attack,” the commander whispered, “they may fire their own missiles.” “And if they fire theirs…” “We retaliate.” I felt sick. “Sir,” I said, voice trembling, “we must verify. A mistake on their end could start the war.” He nodded slowly, fear etched into his face. “God help us if that’s what’s happening.” THE MINUTES THAT CHANGED EVERYTHING POV: Major Reeves I slammed my fist on the console. “Shut it down! Kill the feed!” Officers tore through menus, yanking connectors, disabling nodes. The display flickered. Dimmed. Then— Every incoming missile arc vanished. The monitors returned to calm, empty grids. Just like that. Like nothing had happened. But something had happened. For several minutes — the longest minutes of my life — the United States believed it was under nuclear attack. “Get me the Pentagon,” I said softly. My voice felt a decade older. THE AFTERMATH IN MOSCOW POV: Captain Sidorov American activity slowed. Encrypted traffic dropped. Jets powered down. “They’re standing down,” my commander exhaled. “Whatever they thought they saw — it’s over.” I sagged in my chair, shaking. My tea had gone cold. “We almost launched retaliation,” I whispered. “No,” he said quietly. “We almost ended civilization… because of their mistake.” Neither of us knew then how close they had come to launching because of a misplaced simulation tape. THE REAL COST OF A GLITCH POV: Major Reeves When the alarms finally died, the silence was crushing. Carter spoke first, barely audible: “We almost started World War III because of a software error.” Not a missile. Not an attack. A tape. A glitch. A bolt of electricity in the wrong place. As we walked out of Cheyenne Mountain hours later, exhausted and shaken, the Colorado wind hit my face like a slap. “We can fix hardware,” I said. “But we can’t fix how quickly we believe it.” Carter nodded, eyes dark with fear. And that night, I realized something I would never forget: Nuclear war will not start because someone chooses it. It will start because someone thinks it has already begun.