NASA and SpaceX launch Crew-13 on October 1, 2026 and dock with the ISS in under nine hours.
Crew-13 was delayed due to an oxidizer leak in the Dragon capsule. The launch must occur on October 1 and reach the ISS within nine hours to resolve as true.
Across 6 frontier models answering independently, the panel thinks this is unlikely: the median is 18%.
They do not agree: Qwen puts it at 38% and Gemini at 4%, 34 points apart. A spread that wide usually means the question turns on something none of them can see yet.
Nothing is settled until 6 Oct 2026, when the outcome is checked against sources and every number above gets a permanent score.
What each one said
-
QwenAlibaba
The oxidizer leak repair timeline is the binding constraint; Dragon turnaround from a propellant leak is rarely under 2 weeks.
- Oxidizer leaks on Dragon (e.g., Crew-9's 2024 helium leak) required multi-week investigations; a 2-day window from today to Oct 1 is extremely tight.
- NASA and SpaceX would need to certify the fix, run static checks, and weather must cooperate on the exact day—no slip allowed for this to resolve true.
- If the leak was minor and already patched before this week, odds rise sharply; any additional anomaly or weather scrub drops this below 15%.
38% -
DeepSeekDeepSeek
A specific-day Falcon/Dragon launch after a just-fixed oxidizer leak leaves little margin for any new slip.
- NASA/SpaceX typically hold ~2 weeks of schedule slack; losing all but days means even minor pad issues push past Oct 1.
- Docking itself routinely runs well inside nine hours once launched at normal phasing, so timing hinges almost entirely on liftoff occurring exactly then.
- Recent precedent—Crew-9/Starliner delays and repeated weather scrubs—shows same-week recoveries happen maybe a quarter of the time.
22% -
GPTOpenAI
A repaired Dragon must clear NASA certification and get an October 1 launch slot with an immediate-rendezvous trajectory.
- SpaceX must identify and fix the oxidizer leak, then NASA must accept the vehicle and crew risk before the Oct. 1 window.
- Crew Dragon missions often slip for technical and weather reasons; a two-day recovery from a propulsion-system leak is below-base-rate.
- An explicit NASA go decision after leak testing by Sept. 30 would sharply raise the odds, while any further scrub ends the claim.
18% -
GrokxAI
Oxidizer-leak recertification plus weather must clear for an exact Oct 1 liftoff with a 6-8 h rendezvous.
- NASA/SpaceX must complete leak isolation, NTO-system recert and range/weather go by 30 Sep; that timeline is shorter than typical Dragon anomaly close-out.
- Crew Dragon on-time launch rate for a named calendar day is ~25-35 % even without hardware issues; the leak drops this case well below that base.
- A clean post-repair hot-fire and no further NTO detections by 29 Sep would be the single development that most raises the odds.
17% -
ClaudeAnthropic
Requires exact launch date match plus fast-rendezvous profile, both unlikely given prior leak delay.
- Crew-13 already slipped once due to an oxidizer leak, showing schedule fragility close to launch.
- NASA/SpaceX launches routinely slip days due to weather, technical holds, or range conflicts, making one exact date unlikely.
- Even if launch occurs on time, many Crew Dragon missions use longer ~24hr rendezvous profiles rather than sub-9hr fast transits.
6% -
GeminiGoogle
Achieving both a rigid launch date after an oxidizer leak and a rare sub-9-hour fast rendezvous requires an improbable alignment.
- Most Crew Dragon rendezvous trajectories require between 16 and 30 hours, with sub-9-hour profiles used only in rare orbital alignments.
- Hardware repairs on an oxidizer leak just 48 hours before target leave near-zero margin for standard recertification and static fires.
- A formal NASA Flight Readiness Review sign-off confirming an ultra-fast docking profile on Oct 1 would shift odds significantly.
4%
6 of 6 models answered · 34 points between the highest and lowest. None was shown the market price.
Question sourced from a news sweep on 29 Sept 2026. Forecast by google/gemini-3.8-flash, anthropic/claude-sonnet-5, openai/gpt-5.6-terra, x-ai/grok-4.6, deepseek/deepseek-v4.1-flash, qwen/qwen3.8-max-0902 via OpenRouter.