Latest / The Shadow Dossier / The Shadow Dossier — The Man Who Said No to the Machine
Transcript
- 0:00the shadow dossier act i the night shift at serpukhov
- 0:0615. just after midnight on september 26 1983
- 0:13lieutenant colonel stanislav petrov sat at the
- 0:18command console of serpukhov 15 the bunker south
- 0:22of moscow that housed the soviet union's oko
- 0:25early warning satellite system His job that night
- 0:28was simple in theory and almost unbearable in
- 0:32practice. Watch the screens. And if the system
- 0:36reported an American missile launch, pass that
- 0:39warning up the chain of command within minutes.
- 0:41So Soviet leadership could decide whether to
- 0:44retaliate before incoming warheads arrived. This
- 0:50was barely five weeks after Abel Archer had already
- 0:53stretched Soviet nerves to their limit. A period
- 0:57this dossier has already examined in detail.
- 1:01What it hadn't yet revealed is that before that
- 1:04NATO exercise even began, the actual machinery
- 1:08meant to detect a real American strike had already,
- 1:11once, told the Soviet military that the strike
- 1:15had started. The alarm came without warning.
- 1:27OKO's computers reported a single intercontinental
- 1:30ballistic missile launch from the United States,
- 1:33tracked and confirmed by the satellite system's
- 1:37own algorithms. Then, within minutes, for more
- 1:41launches registered behind it. The system's assessment,
- 1:45displayed in red letters on the command room's
- 1:47main screen, was as unambiguous as Soviet software
- 1:51could make it. Launch. Petrov's protocol was
- 1:58not ambiguous either. He was required to report
- 2:02the launch immediately to his superiors who would
- 2:06then decide whether to recommend a retaliatory
- 2:09strike to the Soviet leadership under a doctrine
- 2:12that assumed, correctly, that a real American
- 2:15first strike would leave almost no time to verify
- 2:18itself before it needed to be answered. He had.
- 2:25By his own later account, something under five
- 2:28minutes to decide what to tell them. Petrov did
- 2:40not report a launch. He told his chain of command
- 2:43the system had malfunctioned. He had no proof
- 2:49of this in the moment. What he had was a set
- 2:52of instincts that ran against everything the
- 2:55screen in front of him was reporting. A real
- 2:57American surprise attack, he reasoned, would
- 3:00almost certainly come as an overwhelming first
- 3:03strike. Hundreds of missiles launched simultaneously
- 3:06to eliminate Soviet retaliatory capability before
- 3:10it could respond. Not a staggered handful of
- 3:13five. Ground radar. which took longer to confirm
- 3:17anything but which Petrov trusted more than the
- 3:20satellite system's newer, less battle -tested
- 3:24software, showed nothing. And Petrov, unlike
- 3:28many of his colleagues in the military chain,
- 3:30had a working knowledge of how the satellite
- 3:33detection system itself was built, its known
- 3:36tendency to mistake high -altitude sunlight reflecting
- 3:39off cloud tops for the heat signature of a missile
- 3:42launch. a false positive risk that had been flagged
- 3:46internally but not fully resolved. He also understood
- 3:52something about the moment itself, sharpened
- 3:56rather than dulled by the tension of the previous
- 3:58months this dossier has already covered. An apparatus
- 4:02already primed by Operation Ryan to expect an
- 4:05attack, staffed by officers who understood that
- 4:09confirming the leadership's fear was the safer
- 4:11career move, made false alarms more, not less,
- 4:15likely to be believed. Petrov chose to be the
- 4:19one person in the chain that night who treated
- 4:22the system's confidence as a reason for more
- 4:25suspicion rather than less. Act 4. Waiting for
- 4:32the ground to shake. He reported a malfunction
- 4:37and then did something the record makes clear
- 4:40took considerable nerve. He waited. If he was
- 4:44wrong, the missiles his own instruments had detected
- 4:47would begin striking Soviet territory within
- 4:50roughly 25 minutes of launch. There was no way
- 4:54to recall the judgment once made and no time
- 4:57left to reverse it. if the impacts began he simply
- 5:01sat in the command room aware that the working
- 5:04assumption he'd just overridden might be about
- 5:08to prove itself correct in the worst possible
- 5:11way no missiles arrived later investigation confirmed
- 5:17petrov's read of the situation precisely The
- 5:21Oko satellites had picked up sunlight reflecting
- 5:24off high -altitude clouds over Montana, a rare
- 5:28alignment of satellite, sun, and cloud cover
- 5:32that the system's software had misclassified
- 5:34as the infrared signature of missile launches,
- 5:37and the fall signal had cascaded. One misread
- 5:41trigger producing four more as the system continued
- 5:45analyzing the same bad data. Petrov was not decorated
- 6:00for what he'd done. He was, by most accounts,
- 6:03quietly reprimanded for failing to complete his
- 6:06paperwork correctly during the incident, and
- 6:09a broader Soviet military bureaucracy had little
- 6:12institutional interest. in publicizing an episode
- 6:15that exposed the expensive early warning system
- 6:18as unreliable at exactly the moment it needed
- 6:22to be trusted most the incident was folded into
- 6:25classified files and left there petrov left the
- 6:30military only a few years later and a story of
- 6:33what had happened in that bunker remained essentially
- 6:36unknown outside a small circle for over a decade
- 6:43It surfaced publicly only in the 1990s, after
- 6:47the Soviet collapse, when a former commander
- 6:49of Petrov's unit mentioned the incident in his
- 6:52memoirs. Petrov, tracked down and interviewed
- 6:56years afterward, was famously matter -of -fact
- 6:59about night. Some historians consider one of
- 7:02the handful of moments a full nuclear exchange
- 7:05came down to a single person's judgment call,
- 7:08rather than any technical or political safeguard.
- 7:12He maintained, consistently, that he wasn't certain
- 7:15he'd made a hero's decision at all. He'd made,
- 7:19in his own description, essentially a 50 -50
- 7:23guess based on incomplete information and a professional
- 7:27hunch about how real attacks tend to look and
- 7:30simply happen to guess correctly. What the incident
- 7:36actually demonstrates sits close to what this
- 7:39dossier has already established about Operation
- 7:42Ryan and Abel Archer, but from the opposite direction.
- 7:45Ryan showed a system that manufactured false
- 7:49confirmations because everyone in it understood
- 7:51what answer their superiors wanted. Petrov's
- 7:54night at Serpukhov, 15 shows what it looks like
- 7:58when exactly one person in that same system refuses
- 8:02to give the expected answer. and gets it right
- 8:04not through better technology but through a working
- 8:07skepticism of the technology in front of him
- 8:10the safeguard that actually held on the one night
- 8:13it was tested most literally wasn't a protocol
- 8:17or a piece of hardware it was a single officer
- 8:20deciding that a screen full of red letters was
- 8:23less trustworthy than his own read of what a
- 8:26real attack would look like This concludes declassified
- 8:33file number 0032 of the Shadow dossier. The man
- 8:38who said no to the machine. What dangerous secrets
- 8:44await in our next file? If you want early access
- 8:50to upcoming files and censored intel briefings
- 8:54and bonus dossiers, join our Patreon network
- 8:57at patreon .com. slash stories by Mia. Subscribe
- 9:04on Apple Podcasts, Spotify, RSS .com, and YouTube
- 9:09so you never miss an official declassification.
- 9:15This is the Shadow Dossier. Thank you for listening.