The Artemis Accords Explained, Updated for 67 Signatories
The Artemis Accords are no longer just a diplomatic framework on paper. After Artemis II completed its crewed lunar flyby, the coalition now faces practical dec
The Artemis Accords Explained, Updated for 67 Signatories From eight founding nations to 61 signatories, the Artemis Accords have grown into the operating rulebook for coalition lunar missions. After Artemis II flew around the Moon and returned safely, the framework is no longer just diplomatic scaffolding. It is being tested by real crews, real hardware, and a crowded schedule heading into Lima. Updated May 2, 2026 Artemis II completed, Lima workshop next, signatory count unchanged at 61 The biggest change since late March is simple: Artemis II actually flew. NASA launched the first crewed Artemis mission on April 1 and brought the crew home on April 10 after a nearly 10-day mission, including a lunar flyby on April 6. That matters because the Accords now have a real operational backdrop. Interoperability, emergency assistance, transparency, and multinational mission planning are no longer hypothetical talking points. 61 Signatories Apr 1 Artemis II launch Apr 10 Crew returned safely May 13-14 Lima workshop Introduction: A New Framework The Artemis Accords are bilateral agreements between the United States and partner nations that set shared principles for civil space exploration. NASA and the U.S. State Department drafted them in 2020 to address gaps left by the 1967 Outer Space Treaty, which was written long before commercial spaceflight, lunar mining, or permanent cislunar infrastructure looked near-term. Key Point: The Accords are not a treaty. They do not create binding enforcement. Their influence comes from participation, repeated use, and the fact that major lunar partners increasingly build real missions around these norms. As of May 2, 2026, the signatory count remains 61. Portugal and Oman were the most recent additions in January. The count has not moved since then, but the framework itself has become more important because mission activity is accelerating faster than membership growth. Historical Context The Outer Space Treaty of 1967 established the basic rules, no national appropriation of celestial bodies, no weapons of mass destruction in space, and free access to outer space. It was a Cold War document for a government-only era. Why New Accords Were Needed Commercial operators now plan landers, relay systems, logistics, and resource extraction work outside traditional government structures. Several nations are pursuing lunar missions in the same decade, often targeting the same south-pole regions. Resource extraction rights needed a practical interpretation consistent with the Outer Space Treaty. No modern mechanism existed for notifying others about active operations or temporary exclusion buffers. Cislunar debris management and surface coordination needed norms before congestion arrives. The United States started down this road in 2015 with the Commercial Space Launch Competitiveness Act, which recognized ownership of extracted resources by U.S. entities. The Accords extended that logic into a broader international framework and invited partner nations to align before conflict over sites, traffic, or resources became harder to manage. Core Principles Transparency Signatories commit to sharing information about national policies and planned activities that could affect others. Interoperability Hardware, software, procedures, and interfaces should work across partner systems wherever practical. Resource Use Resource extraction is treated as compatible with the Outer Space Treaty when conducted peacefully and transparently. Emergency Assistance Partners affirm they will assist astronauts in distress, regardless of nationality. Peaceful Purpose Civil exploration must remain peaceful, even when military personnel support logistics or operations. Heritage Preservation Historic landing sites and artifacts should be protected from disturbance. Safety Zones: Still the Hardest Part The Accords call for temporary safety zones around active operations to avoid harmful interference. The principle is easy to support in theory and difficult to standardize in practice. Size, duration, notification methods, and how non-signatories are handled remain unsettled. That uncertainty is exactly why the Lima workshop matters. May 2026 update The coalition jumped from 61 to 67 signatories in one spring NASA's public list now stands at 67 nations. Malta and Ireland signed on May 4, and Paraguay signed on May 7 in Asunción. Ireland's entry is notable because NASA said it means all 23 ESA member states are now Artemis Accords signatories, even though ESA itself does not sign as an agency. The timing matters. The Accords are moving from a Washington-led diplomatic document into a wider operating compact for lunar activity. A larger bloc gives NASA and the State Department more political weight before decisions on landing site coordination, rescue obligations, scientific data release, resource activity, and preservation of historic sites become live operational issues. Sources checked for this update: NASA's Artemis Accords page, NASA's Ireland announcement, NASA's Paraguay announcement, and the U.S. State Department statements on Malta and Paraguay. Current Signatories: 67 Nations ESA is not a signatory. Member states sign individually. The growth curve has accelerated again. NASA counted 67 signatories by May 2026 after Malta and Ireland signed on May 4 and Paraguay followed on May 7. The next phase is no longer just diplomatic expansion. It is turning broad principles into operating procedures that can survive crowded lunar timelines. Most Recent Signatories Country Date Signed Order Latvia April 2026 62nd Jordan April 2026 63rd Morocco April 2026 64th Malta May 4, 2026 65th Ireland May 4, 2026 66th Paraguay May 7, 2026 67th Artemis II Made the Accords Operational On April 1, NASA launched Artemis II, the first crewed mission of the Artemis era. The four-person crew flew 694,481 miles in total and reached 252,756 miles from Earth at the farthest point, according to NASA. They flew past the Moon on April 6 and splashed down safely off California on April 10. That mission did not trigger a diplomatic incident, but it did prove something important. The coalition architecture behind Artemis is real. A Canadian astronaut flew aboard a mission built around U.S. launch hardware and an Orion spacecraft that depends on ESA's service module. Four CubeSats from South Korea, Saudi Arabia, Argentina, and Germany were part of the wider mission package. The Accords are no longer a policy annex hanging off Artemis. They are part of the mission plumbing. Why this changed the story: Before April, the Accords mostly described how countries hoped to cooperate in cislunar space. After Artemis II, they describe a framework already supporting crewed operations, data-sharing expectations, hardware interoperability, and multinational participation. Lima Is the Next Real Governance Test Peru is set to host the next Artemis Accords Workshop on May 13 and 14, the first time the event has been held in Latin America. Peru signed in 2024 as the 41st signatory, and its role as host shows NASA and partner governments are trying to broaden the framework beyond the usual core coalition. The underlying challenge is not membership anymore. It is implementation. Signatories still need better operating guidance on safety-zone declarations, emergency procedures, open scientific data practices, interoperability baselines, and how to communicate with nations that are not part of the Accords but will still fly in the same region. Issues Lima Needs to Move Forward A practical method for declaring and updating safety zones Emergency coordination playbooks for lunar-surface and cislunar incidents Data-sharing expectations that work for both national agencies and commercial providers Interoperability standards that can be adopted before Gateway and surface systems multiply A clearer approach to interaction with non-signatories such as China and Russia Unresolved Questions What counts as harmful interf