Emergency Action Message
An Emergency Action Message (EAM) is a preformatted, encrypted directive transmitted through the United States military's nuclear command, control, and communications (NC3) system, primarily to authorize nuclear-capable forces to execute specific major or limited attack options during crises.[1][2] While primarily for nuclear command and control, EAMs also support transmission of non-nuclear and other time-critical messages to strategic and non-strategic forces.[3] These messages originate from the National Command Authority, typically the President acting through the Chairman of the Joint Chiefs of Staff, and are disseminated to combatant commanders and subordinate units to ensure centralized control, rapid authentication, and prevention of unauthorized actions.[1][4] EAMs employ cryptologic validation procedures to confirm legitimacy, integrating with launch control protocols that require the message to provide essential enabling data absent in peacetime configurations, thereby maintaining positive control over strategic assets like intercontinental ballistic missiles, submarine-launched ballistic missiles, and bomber forces.[5][1] Transmission occurs via secure digital networks to major commands under U.S. Strategic Command, with high-frequency radio broadcasts using the High Frequency Global Communications System (HFGCS) relaying them to airborne alert aircraft and other dispersed elements for redundancy in contested environments.[6] Messages follow standardized formats, most typically 30 characters, but can be up to 292 (or more, though there is no recorded evidence for longer lengths), and are routinely issued for training, system validation, and to obscure patterns from potential adversaries, rather than solely in actual emergencies.[6][4] The system's design underscores causal priorities of deterrence and escalation dominance, prioritizing empirical verification of command intent over speed alone to mitigate risks of erroneous escalation, as evidenced by doctrinal emphasis on authenticated emergency action procedures that integrate human and technical safeguards.[1][2] This framework has evolved to support modern NC3 sustainment programs, such as the Defense Injection/Reception Emergency Action Message Command and Control Terminal (DIRECT), which automate processing while preserving hierarchical oversight.[7]History
Origins in Cold War Nuclear Doctrine
The EAM emerged as an essential element of U.S. nuclear command and control during the Cold War, designed to transmit presidentially authorized execution orders to Strategic Air Command (SAC) forces under the Single Integrated Operational Plan (SIOP). The SIOP, which unified nuclear strike planning across services, was first developed in 1960 and implemented as SIOP-62 effective April 1, 1961, to enable a massive retaliatory response against Soviet targets in line with doctrines of assured destruction and deterrence.[8] EAMs, as preformatted encrypted directives specifying Major Attack Options or limited strikes, addressed the need for centralized positive control over dispersed nuclear assets, preventing premature launches while allowing rapid response to detected inbound threats.[9] This format built on SAC's alert procedures from the mid-1950s, when General Curtis LeMay instituted one-third bomber forces on 15-minute readiness to counter Soviet intercontinental capabilities, evolving into formalized Emergency War Orders (EWOs) by the early 1960s. Red Dot EWOs, declassified from 1964, served as execution codes distinct from preparatory Gold codes, broadcast via high-frequency radio to bomber, missile, and submarine crews for SIOP implementation.[9] The system's origins reflected causal imperatives of nuclear doctrine: vulnerability of fixed command posts to decapitation strikes necessitated survivable dissemination, spurring developments like the SAC Automated Command and Control System (initial operational capability in 1963) and Post-Attack Command and Control System (initiated 1961).[10] Doctrinal emphasis on launch-on-warning, intensified after the 1949 Soviet atomic test and formalized in NSC-68 (1950), drove EAM authentication via dual-key safes and challenge-response codes to balance speed with safeguards against errors or coercion. The 1962 Cuban Missile Crisis tested these mechanisms, exposing gaps in real-time order relay during heightened DEFCON 2 alerts, which prompted refinements in redundancy through airborne command posts like Looking Glass (operational from 1961).[9] By ensuring forces could receive and verify orders even under electromagnetic pulse or jamming conditions, EAMs underpinned the credibility of mutual assured destruction, with SAC's global communications network handling thousands of daily tests to maintain proficiency.[10]Post-Cold War Adaptations and Modernization
Following the dissolution of the Soviet Union in 1991, the United States implemented significant reductions in its nuclear arsenal through the Presidential Nuclear Initiatives, which included the withdrawal of thousands of tactical nuclear weapons from forward deployments and the deactivation of certain delivery systems, thereby altering the operational scope of Emergency Action Messages from large-scale, preemptive strikes to more selective and limited options.[11][12] These changes emphasized flexible response doctrines over massive retaliation, requiring EAMs to support refined targeting via Major Attack Options (MAOs) and Limited Attack Options (LAOs) that aligned with reduced force postures under treaties like START I, ratified in 1991.[13] Despite arsenal cuts, the core EAM dissemination architecture—relying on high-frequency radio and airborne relays—remained intact as a legacy of Cold War-era reliability needs, with minimal format alterations to ensure compatibility across surviving strategic platforms.[14] Nuclear Command and Control (NC2) systems, encompassing EAM generation and authentication, underwent incremental sustainment in the 1990s and 2000s to address post-Cold War requirements like improved survivability against regional threats, though full-scale replacement was deferred due to fiscal constraints and perceived lowered risks.[15] By the 2010s, modernization accelerated amid rising concerns over cyber intrusions and electronic warfare, incorporating upgrades to authentication protocols using multiple-officer verification and codebooks to mitigate unauthorized execution risks.[16] Key efforts included enhancements to the E-6B Mercury airborne command post, with the first upgraded aircraft delivered in June 2023 featuring improved nuclear command, control, and communications (NC3) capabilities for EAM relay.[17] In the 2020s, adaptations have focused on integrating resilient technologies for peer competitors like Russia and China, including the Evolved Strategic SATCOM (ESS) program to replace legacy Advanced Extremely High Frequency (AEHF) satellites by 2032, with $1.05 billion allocated in FY2025 for jam-resistant transmission of EAMs and related directives.[18] Artificial intelligence aids in threat assessment and message processing efficiency, as outlined by U.S. Strategic Command in 2024, while low-Earth orbit proliferated warfighter space architecture satellites—28 operational by late 2024—bolster redundant pathways against space domain disruptions.[19] These upgrades, part of a multi-decade NC3 overhaul, address vulnerabilities exposed in simulations, such as below-threshold conflicts, ensuring EAMs retain positive control amid contested environments.[20][21]Technical Specifications
Message Structure and Format
Emergency Action Messages (EAMs) utilize a predefined, concise format tailored for brevity, error resistance, and secure dissemination in nuclear command and control operations. The structure comprises a preamble, body, and integrated authentication elements, enabling rapid manual or automated processing by recipients such as strategic bombers, submarines, and missile silos. This format derives from Joint Chiefs of Staff protocols, prioritizing clarity over high-frequency voice or Morse code transmissions where interference is common.[6] The message initiates with a preamble, a six-character alphanumeric identifier repeated three times phonetically to confirm reception. This preamble encodes the message type indicator and preliminary authentication data, distinguishing EAMs from routine traffic and initiating verification against current codebooks.[6][22] The body follows as a continuous string of uppercase letters and numerals—excluding 0, 1, 8, and 9 in most cases—concatenated from the preamble onward, with lengths varying from approximately 30 characters for routine updates to over 200 for complex directives like Major Attack Options (MAOs) or force reallocations. It is articulated in phonetic groups of five characters to mitigate transmission errors, encapsulating encrypted instructions without explicit headers for addressees or timestamps, as these are inferred from context and serial tracking.[22] Authentication permeates the format, with embedded groups cross-checked against rotating tables held by operators; mismatches trigger rejection protocols. Final authentication may append the body, often as paired letter groups or numeric challenges broadcast separately for response validation. This layered approach, rooted in Cold War-era safeguards, ensures only valid messages propagate, with precedence overriding standard formats like those in FM 6-99.2 for urgency.[6][23]Encoding, Authentication, and Security Features
Emergency Action Messages (EAMs) are encoded as structured strings of encrypted alphanumeric characters, typically comprising 30 characters in length, though variations such as 6, 22, 28, or longer formats up to 290 characters have been observed.[24][4] The encoding employs cryptographic protocols, including one-time ciphers that require periodic code books for decryption, refreshed daily, weekly, or monthly to maintain security.[25] These pro forma messages follow predetermined formats to ensure compatibility across nuclear command systems.[4] Transmission occurs in a standardized broadcast sequence over high-frequency radio using single-sideband modulation, beginning with the callsign repeated (e.g., "All stations, all stations, this is [callsign]"), followed by the first six characters thrice with "Stand by," then "Message follows," the full encrypted string, a repetition of the message, and conclusion with the callsign and "out."[24] The alphanumeric content is voiced using the NATO phonetic alphabet for resilience against noise and interference.[23] Authentication integrates digital signatures within the cryptographic framework to verify message integrity and origin, preventing forgery or undetected alteration.[23][4] Recipients cross-check against sealed authentication code cards held by authorized officers, with time-dependent two-character authenticators embedded in certain high-priority variants like Foxtrot or Skyking messages.[4] An explicit authentication code, such as a two-letter group (e.g., "Whiskey November"), may precede the encrypted body to enable immediate legitimacy confirmation.[25] Security features emphasize resistance to jamming, nuclear effects, and spoofing, leveraging survivable transmission paths including terrestrial, space-based, and very low frequency systems.[4] EAMs maintain top-secret classification with strict need-to-know access, ensuring only designated nuclear forces can process and act upon them without compromising operational secrecy.[4]Transmission and Delivery
High Frequency Global Communications System
The High Frequency Global Communications System (HFGCS) serves as the primary U.S. Air Force network for disseminating Emergency Action Messages (EAMs) to strategic nuclear forces, including airborne command posts, bombers, and submarines via relay aircraft.[24][26] It employs high-power shortwave transmitters operating in the HF band (3-30 MHz) to achieve global coverage through skywave propagation, which reflects signals off the ionosphere for long-distance transmission independent of line-of-sight or satellite infrastructure.[27] This system provides resilience against disruptions such as electromagnetic pulses from nuclear events or failures in very low frequency (VLF) submarine communications.[28] The network comprises approximately 13 to 15 remotely controlled ground stations situated near major U.S. military installations worldwide, with centralized control from the Network Control Station at Andrews Air Force Base, Maryland.[24][27] Known transmitter sites include:| Site | Location |
|---|---|
| Andersen Air Force Base | Guam, USA |
| Andrews Air Force Base | Maryland, USA |
| Ascension Island | Atlantic Ocean |
| RAF Croughton | United Kingdom |
| Diego Garcia | Indian Ocean |
| Elmendorf Air Force Base | Alaska, USA |
| Hickam Air Force Base | Hawaii, USA |
| Lajes | Azores, Portugal |
| Offutt Air Force Base | Nebraska, USA |
| Puerto Rico | Puerto Rico, USA |
| Naval Air Station Sigonella | Italy |
| West Coast | USA |
| Yokota Air Base | Japan |
Backup and Alternative Methods
The Minimum Essential Emergency Communications Network (MEECN) integrates multiple transmission media to provide redundancy for Emergency Action Message delivery, ensuring reliable dissemination to nuclear forces amid potential disruptions from electromagnetic pulse, jamming, or infrastructure damage.[29] The MEECN is a critical component of the U.S. Nuclear Command, Control, and Communications (NC3) architecture, designed to provide secure, survivable, and jam-resistant communications links to ensure the President and other national leaders can maintain command over nuclear forces even in the event of a nuclear attack or other disruptions.[30] Very Low Frequency (VLF) systems form a key backup pathway, particularly for submerged ballistic missile submarines unable to receive higher-frequency signals, with specialized receivers engineered for EAM decoding in nuclear-denied environments.[31] Fixed VLF sites, such as Naval Radio Station Cutler in Maine, transmit these signals over long distances via ground wave propagation, while the Take Charge and Move Out (TACAMO) fleet—comprising E-6B Mercury aircraft—offers airborne relay capability to evade ground-based vulnerabilities and extend coverage.[32] Extremely Low Frequency (ELF) systems, developed under Project ELF—a scaled-down version of the 1960s Project SANGUINE proposal—provided alerting signals to submerged submarines indicating incoming Emergency Action Messages, requiring them to ascend for full VLF reception due to ELF's low data rate. Operational from 1989 to 2004 and integrated into MEECN for NC3 redundancy, ELF enhanced survivability for strategic submarine communications.[33] Satellite communications provide another hardened alternative, with the Advanced Extremely High Frequency (AEHF) constellation enabling secure, narrowbeam EAM relay to airborne and surface assets; the sixth AEHF satellite achieved full operational capability in March 2020, completing a resilient orbital network for strategic messaging including force direction.[34] Ultra High Frequency (UHF) and Extremely High Frequency (EHF) terminals under programs like Family of Advanced Beyond Line-of-Sight Terminals (FAB-T) further support EAM injection and report-back functions, prioritizing anti-jam features for end-to-end NC2 integrity.[35] These layered approaches, tested through ongoing modernizations, address single-point failure risks identified in audits of satellite-based NC2 segments.[36] Historical systems like the Ground Wave Emergency Network (GWEN), intended for EMP-resistant LF ground wave EAM relay in the 1980s, were ultimately cancelled in 1994 amid funding cuts, shifting emphasis to integrated satellite-VLF hybrids.[37]Message Types and Priorities
Standard Emergency Action Messages
Standard Emergency Action Messages constitute the primary mechanism for routine command and control of U.S. strategic nuclear forces, transmitting preformatted, encrypted instructions from high-level authorities such as the Joint Chiefs of Staff to nuclear-capable units including submarines, bombers, and missile silos.[6][4] These messages direct the execution of specific operational directives, such as Major Attack Options or Limited Attack Options, while also handling non-launch functions like force status updates, code changes, and readiness validations to maintain continuous nuclear deterrence posture.[4] Unlike higher-priority SKYKING FOXTROT broadcasts, which interrupt ongoing traffic for immediate alerts, standard EAMs follow scheduled or as-needed patterns without the distinctive "SKYKING, SKYKING, do not answer" preamble and are not designed for overriding urgency.[26][38] The format of a standard EAM begins with a transmitter callsign—randomly selected each day, such as "RAMSHEAD" or "HARD LUCK"—followed by the message body, which is voiced using the NATO phonetic alphabet for letters and numerals to ensure clarity over high-frequency radio.[26] Typical messages measure approximately 30 characters in length, though variations up to 292 characters or more occur for complex directives, with the longest known EAM recorded and shared online measuring 292 characters (e.g., an INFATUATE callsign transmission on May 1, 2025), with the content digitally encoded prior to voice transmission for authentication and security.[39][40] Authentication relies on predetermined codes and challenges inherent to the preformatted structure, preventing unauthorized alterations while allowing rapid decoding by recipients equipped with compatible systems.[23] Transmission occurs multiple times daily via the High Frequency Global Communications System (HFGCS), utilizing upper sideband (USB) mode on primary frequencies such as 4.724 MHz, 8.992 MHz, 11.175 MHz, and 15.016 MHz, often with echoes from simultaneous multi-frequency broadcasts to enhance global reach.[26][41] These broadcasts originate from U.S. military bases worldwide and are relayed digitally to major commands before voice dissemination to alert aircraft or other assets, ensuring redundancy against jamming or failure.[23] Standard EAMs thus underpin the U.S. nuclear triad's operational tempo, with empirical monitoring by radio enthusiasts confirming their regularity—dozens per day under normal conditions—contrasting with rarer special variants.[6]Skyking Foxtrot Broadcasts
Skyking Foxtrot broadcasts, also referred to as Foxtrot messages or simply Skyking messages, represent a high-precedence variant of Emergency Action Messages (EAMs) transmitted via the U.S. military's High Frequency Global Communications System (HFGCS).[24][42] These broadcasts supersede standard EAMs in priority, capable of interrupting ongoing transmissions to ensure immediate relay to recipients, such as strategic nuclear forces or airborne command elements.[6][4] The standard format begins with the announcer stating "Skyking, Skyking, do not answer," followed by a phonetic codeword—often drawn from names of rock bands or similar cultural references—then Zulu time indicators (typically two digits for the hour), and concluding with an authentication code for verification.[24][42] This structure differs markedly from routine EAMs, which consist of longer encrypted alphanumeric strings without the imperative preamble or codeword. Transmissions occur on HFGCS frequencies like 8992 kHz or 11175 kHz, originating from ground stations such as Andrews or Offutt Air Force Bases, and are directed to unacknowledged recipients to maintain operational security.[43] While the precise operational function remains classified, radio monitoring communities observe these messages as indicators of elevated alert states or directives for rapid force posture changes, potentially including nuclear deployment authorizations, based on their rarity and interruptive nature.[44][22] Unlike the more frequent EAMs, averaging around 15 daily according to regular monitors, Skyking Foxtrot broadcasts are infrequent, with patterns analyzed by enthusiasts logging fewer than several per week under normal conditions.[42] Empirical receptions confirm no public authentication of their exact content or triggers, underscoring reliance on declassified doctrinal hints and signal intercepts rather than official disclosures.[24]Skymaster Broadcasts
Skymaster broadcasts employ the "Skymaster" callsign within the U.S. Air Force's HFGCS to address airborne command post aircraft, such as the E-4B National Airborne Operations Center under U.S. Strategic Command, for the delivery of EAMs.[42][24] These transmissions are particularly associated with training exercises that generate high volumes of EAMs, sometimes exceeding hundreds in a single session, to simulate command and control operations. In distinction from Skyking Foxtrot messages, which serve as interruptive alerts directed to ground-based or diverse recipients, Skymaster specifically targets aerial platforms to ensure secure, real-time relay of directives during flight.[42][24] The format adheres to standard EAM protocols, featuring encrypted alphanumeric strings prefixed by the Skymaster callsign, and is transmitted on HFGCS frequencies from stations including Andrews Air Force Base. Radio monitoring enthusiasts document these broadcasts through signal logs, observing increased activity during events like Global Thunder exercises, which test nuclear deterrence readiness.[45] While operational details are classified, public insights derive from declassified materials and verified intercepts, confirming Skymaster's role in maintaining continuity of government communications.[24]Operational Context
Role in U.S. Nuclear Command and Control
The EAM serves as a primary mechanism for disseminating National Command Authority (NCA) directives to U.S. nuclear forces, enabling the execution of predefined attack options in response to strategic threats.[46] Upon presidential authorization, the nuclear command, control, and communications (NC3) system generates an EAM correlated to specific Major Attack Options (MAOs) or Limited Attack Options (LAOs), which outline targeting, force employment, and execution timelines.[6][4] These messages are preformatted and encrypted to minimize ambiguity and human error during high-stakes decision-making, functioning as a "go code" for nuclear operations while preserving positive control over force employment.[47] In the broader NC3 architecture, EAMs integrate with survivable dissemination networks such as the Minimum Essential Emergency Communications Network (MEECN), ensuring delivery to nuclear-capable commands like U.S. Strategic Command (USSTRATCOM) even under degraded conditions.[30] Authentication protocols embedded in EAMs require recipients—ranging from submarine-launched ballistic missile (SLBM) crews to bomber alert forces—to verify message validity through cryptographic challenges and procedural checks before proceeding with execution, thereby preventing unauthorized or spoofed launches.[1] This process supports the NCA's dual imperatives of deterrence signaling and rapid response, with EAMs relaying digital instructions to alert platforms via secure very low frequency (VLF), high frequency (HF), or satellite links.[23] EAMs also facilitate adaptive force management during crises, allowing for updates to alert postures, force dispersal, or de-escalatory measures without full-scale execution, as evidenced in doctrinal frameworks emphasizing flexible NC3 responsiveness. For instance, on September 11, 2001, an EAM was transmitted at approximately 14:52 UTC to direct worldwide DEFCON 3, as confirmed in a declassified transcript from the National Military Command Center.[48] Their role extends to peacetime testing and readiness exercises, where simulated EAMs validate command chains and operator proficiency, underscoring the system's emphasis on empirical reliability over theoretical vulnerabilities.[49] By prioritizing authenticated, pre-vetted directives, EAMs embody causal realism in nuclear C2, linking strategic intent directly to operational outcomes while mitigating risks from miscommunication or adversarial interference.Execution Protocols and Safeguards
Execution of an Emergency Action Message (EAM) requires rigorous authentication and verification to confirm its validity before any directives are implemented, ensuring compliance with the U.S. nuclear command and control framework. Upon receipt via systems like the High Frequency Global Communications System, designated personnel—such as launch control center operators for intercontinental ballistic missiles or submarine commanding officers—must authenticate the message using predefined codes and cryptographic protocols embedded in its structure.[50][5] This process typically involves cross-verifying the message's format, a structured string of approximately 150 alphanumeric characters, against sealed authenticators or digital signatures to prevent spoofing or alteration.[50][51] A core safeguard is the two-person rule, mandating that at least two cleared, personnel reliability program-certified individuals independently concur on the message's authenticity and content before proceeding with execution steps, such as entering enabling codes into weapon systems.[52][50] This rule applies across the chain of command, from national command authorities to operational units, prohibiting any single individual from authorizing or enacting nuclear-related actions.[52] For strategic assets like Minuteman III missiles, the EAM supplies critical launch-enabling data absent from preloaded systems, rendering premature or unauthorized launches impossible without it.[5] Submarine forces employ similar validation procedures, with post-patrol analyses by independent agencies confirming EAM handling fidelity.[51] Additional protocols emphasize positive control, where nuclear weapon systems maintain inert status until an authenticated EAM provides authorization codes, such as those for permissive action links that arm warheads.[53] Redundant communication channels and procedural drills mitigate risks of misinterpretation or failure, aligning with doctrines that prioritize "always execute valid orders, never execute invalid ones."[53] These measures, rooted in Department of Defense nuclear surety standards, have been iteratively refined since the Cold War to counter technical vulnerabilities and human error, with no verified instances of erroneous execution in operational history.[54]Public Interest and Monitoring
Early Civilian Monitoring
Early organized monitoring and data collection of Emergency Action Messages by civilian radio hobbyists emerged in the mid-1990s through Monitoring Times magazine. Larry Van Horn contributed columns such as the December 1994 "Utility World" piece on the U.S. Air Force Global High Frequency System, the May 1995 explanation of EAMs, and the September 1995 discussion of message meanings. Jeff Haverlah authored "What is an EAM?", detailing broadcast protocols and structure. These efforts established systematic civilian documentation of EAM patterns and transmissions.[4][6]HF Radio Enthusiast Receptions
HF radio enthusiasts, including shortwave listeners and amateur radio operators, routinely monitor the U.S. Air Force's High Frequency Global Communications System (HFGCS) to receive Emergency Action Messages (EAMs), which are broadcast in unencrypted voice format using the NATO phonetic alphabet.[6] These transmissions occur on designated frequencies such as 4724.0 kHz, 8992.0 kHz (primary at night), 11175.0 kHz (primary during the day), and 15016.0 kHz, all in upper sideband (USB) mode, allowing global reception with standard HF equipment like software-defined radios (SDRs) or tabletop receivers.[55][56] EAMs are transmitted multiple times daily from ground stations including Andrews Air Force Base in Maryland and Offutt Air Force Base in Nebraska, with propagation conditions influencing audibility based on time of day and ionospheric conditions.[6] Recordings of these receptions are widely documented and shared by enthusiasts, demonstrating the accessibility of HFGCS signals to civilian listeners equipped with antennas and receivers capable of shortwave bands. For instance, a 2025 reception of an EAM on 8992 kHz USB captured the operator reading a coded message prefixed with a callsign and authentication, lasting approximately 30-60 seconds depending on length.[57] Similarly, a 2024 recording on 15016.0 kHz USB documented a standard EAM broadcast, highlighting the routine procedural format: station identification, message preamble, phonetic readout, and sign-off.[58] Online trackers aggregate real-time submissions from monitors worldwide, logging details such as timestamp, sender/receiver callsigns (e.g., "STAGE FIRE" to "ALPHA FORCE"), and message length, demonstrating continued operational activity. See also comprehensive efforts to record all EAMs for a given day (HFGCS EAM Daily Compilation Series[59]), or transcribe them (Daily Timecard Project[60]). Enthusiast monitoring confirms that EAMs follow consistent protocols, including repetition for reliability and use of discrete frequencies for high-priority "FOXTROT" variants, but the encoded content remains undecipherable without classified keys, limiting receptions to verifying transmission patterns rather than message interpretation.[6] Communities of monitors, utilizing tools like WebSDR networks or portable HF transceivers, report optimal reception during nighttime for lower frequencies due to skywave propagation, with signal strengths varying from S5 to S9 in North America and Europe.[56] These efforts have produced archives spanning years, underscoring the open nature of HF broadcasts despite their military purpose.[61]VLF Radio Enthusiast Receptions
Very Low Frequency (VLF) radio enthusiasts also monitor transmissions related to Emergency Action Messages, particularly those on the VERDIN network used for communicating with submerged ballistic missile submarines. These signals, transmitted at frequencies such as 27.2 kHz from sites like Naval Radio Station Cutler, are receivable with specialized VLF receivers and antennas designed for low-frequency propagation. Hobbyists have documented and shared recordings of these VERDIN EAMs online, illustrating the public interest in backup nuclear command and control systems. For example, a 2025 recording captures a VERDIN EAM transmission at 27.2 kHz, relayed via airborne platforms, demonstrating the format and accessibility to dedicated listeners.[62] Such efforts parallel HF monitoring but require more advanced equipment due to the lower frequencies and ground-wave propagation, with communities archiving signals to track patterns without decrypting content.Documentation of EAM Prefixes by Hobbyists
Radio enthusiasts and shortwave monitors have observed patterns in Emergency Action Messages (EAMs) based on their two-character prefixes (can be letters or numbers), which appear at the beginning of the phonetic message readout and seem to consistently differentiate various types or groups of EAMs. These prefixes are routinely logged in enthusiast databases and recordings, suggesting a structured classification system within the broadcasts. For example, the prefix 'Oscar Oscar' is associated with mission-specific EAMs, often transmitted on HFGCS frequencies such as 8992 kHz, as documented in enthusiast forums like RadioReference.[63] However, the exact purposes of these prefixes and the intended audiences for the corresponding message groups remain officially undisclosed and subject to speculation among hobbyists. Resources like online forums, monitoring logs, and dedicated radio enthusiast sites provide neutral compilations of these observations without interpreting the classified content.[64][24][65]SKYMASTER Message Patterns Documented by Hobbyists
Hobbyists have also documented patterns in SKYMASTER messages, a callsign associated with U.S. Strategic Command airborne command post communications on the HFGCS, often involving bursts of EAMs during exercises. Enthusiasts have identified formulaic patterns in these events, allowing partial predictability based on recurring days of the month, such as Wednesdays or Thursdays. For instance, a September 2025 forum post by NEET INTEL on HF Underground detailed observed activities as follows:| Month | 2022 | 2023 | 2024 | 2025 |
|---|---|---|---|---|
| January | January 11 (2nd Wednesday) | January 11 (2nd Thursday, Wednesday in U.S. time zones) | January 8 (2nd Wednesday) | |
| February | February 1 (1st Wednesday) | February 7 (1st Wednesday) | ||
| April | April 11, April 18 | April 16 | ||
| May | May 15 (3rd Wednesday) | May 28 (4th Wednesday) | ||
| August | August 31 (5th Wednesday) | August 30 (5th Wednesday) | August 21 (3rd Wednesday) | August 20 (3rd Wednesday) |
| September | September 28 (4th Thursday, Wednesday in U.S. time zones) | September 25 (4th Wednesday) | September 24 (4th Wednesday) | |
| October | October 24 (4th Thursday) |