| Outcome | Probability | Yes Bid | Yes Ask | 24h Change | Volume | |
|---|---|---|---|---|---|---|
| Before Apr 6, 2026 | 0% | 0¢ | 0¢ | — | $0 | Trade → |
| Before Apr 5, 2026 | 0% | 0¢ | 0¢ | — | $0 | Trade → |
| Before Apr 2, 2026 | 0% | 0¢ | 0¢ | — | $0 | Trade → |
| Before Apr 7, 2026 | 0% | 0¢ | 0¢ | — | $0 | Trade → |
| Before May 1, 2026 | 0% | 0¢ | 0¢ | — | $0 | Trade → |
| Before Apr 4, 2026 | 0% | 0¢ | 0¢ | — | $0 | Trade → |
This market asks when NASA's Artemis II mission will launch, an event that marks the first crewed flight in the Artemis lunar program. Market interest matters because launch timing reflects technical readiness, program management, and broader schedule risk for human lunar exploration.
Artemis II is the follow-on mission to Artemis I and is planned as the first crewed Orion flight in NASA's program to return humans to the Moon. The mission schedule depends on the results of previous integrated tests, hardware maturation (SLS rocket and Orion spacecraft), and coordination among NASA, prime contractors, and range authorities. Historical slips on complex launch programs and the outcomes of recent Artemis program milestones provide relevant context for timing uncertainty.
Prediction market prices represent the collective market view on when the launch will occur, aggregating new technical updates, test results, budget actions, and schedule announcements. Treat those prices as a real-time, consensus indicator subject to rapid change when new data (test outcomes, program announcements, or anomalies) arrives.
Key milestones include successful integrated testing of Orion and SLS hardware, completion of mission dress rehearsals and simulations, formal safety and flight readiness reviews, and final range and environmental approvals; each milestone can reveal issues that shift timing.
Artemis I test data and post-flight reviews inform necessary repairs, firmware or software updates, and verification steps for Artemis II; any anomalies or additional testing identified in Artemis I typically translate into added schedule margin for the follow-on crewed mission.
NASA (program and mission offices), the SLS and Orion prime contractors, NASA safety and mission assurance teams, launch range operators, and supporting subcontractors all play direct roles through spacecraft readiness, certification, and launch support.
Failures in pre-launch tests usually trigger troubleshooting, hardware replacement or redesign, and additional verification steps; the severity and root-cause complexity determine whether a delay is short (weeks to months) or longer (many months to years).
Treat official announcements and review outcomes as informative inputs: confirmations of completed milestones typically shorten expected timelines, while identified issues or requests for additional testing tend to extend them; always consider the lag between internal program status and public disclosure.