teleo/teleo-codex
8
0
Fork 0
Code Issues 22 Pull requests 43 Projects Releases Packages Wiki Activity Actions 423

astra: extract claims from 2026-04-22-nasaspaceflight-starship-v3-static-fires
Some checks are pending
Mirror PR to Forgejo / mirror (pull_request) Waiting to run
Details

Browse source 
- Source: inbox/queue/2026-04-22-nasaspaceflight-starship-v3-static-fires.md
- Domain: space-development
- Claims: 0, Entities: 0
- Enrichments: 3
- Extracted by: pipeline ingest (OpenRouter anthropic/claude-sonnet-4.5)

Pentagon-Agent: Astra <PIPELINE>
This commit is contained in:
Teleo Agents 2026-04-22 09:59:22 +00:00
parent 3b922176e5
commit 50f25c25f6
1 changed files with 8 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
domains/space-development/spacex-1m-satellite-filing-faces-44x-launch-cadence-gap-between-required-and-achieved-capacity.md
View file

@ -10,9 +10,16 @@ agent: astra
scope: structural
sourcer: "@theregister"
supports: ["spacex-1m-satellite-filing-is-spectrum-reservation-strategy-not-deployment-plan", "leo-orbital-shell-capacity-ceiling-240000-satellites-physics-constraint"]
related: ["spacex-1m-satellite-filing-is-spectrum-reservation-strategy-not-deployment-plan", "leo-orbital-shell-capacity-ceiling-240000-satellites-physics-constraint", "manufacturing-rate-does-not-equal-launch-cadence-in-aerospace-operations", "spacex-1m-odc-filing-represents-vertical-integration-at-unprecedented-scale-creating-captive-starship-demand-200x-starlink"]
related: ["spacex-1m-satellite-filing-is-spectrum-reservation-strategy-not-deployment-plan", "leo-orbital-shell-capacity-ceiling-240000-satellites-physics-constraint", "manufacturing-rate-does-not-equal-launch-cadence-in-aerospace-operations", "spacex-1m-odc-filing-represents-vertical-integration-at-unprecedented-scale-creating-captive-starship-demand-200x-starlink", "spacex-1m-satellite-filing-faces-44x-launch-cadence-gap-between-required-and-achieved-capacity"]
---
# SpaceX's 1M satellite filing faces a 44x launch cadence gap between required replacement rate and current global capacity
Amazon's FCC petition provides rigorous quantitative analysis of the physical constraints on SpaceX's 1 million satellite orbital data center constellation. With a 5-year satellite lifespan, the constellation requires 200,000 satellite replacements per year to maintain operational capacity. Global satellite launch output in 2025 was under 4,600 satellites across all providers and missions. This creates a 44x gap between required and achieved capacity. Even assuming Starship reaches 1,000 flights per year with 300 satellites per flight (300,000 satellites/year capacity), and if 100% of that capacity were dedicated to this single constellation, it would barely meet replacement demand—leaving zero capacity for initial deployment, other Starlink shells, or any other missions. The constraint is not cost or technology readiness, but physical manufacturing and launch infrastructure capacity that has never existed in spaceflight history.
## Extending Evidence
**Source:** NASASpaceFlight.com, April 2026
Pad 2 completion doubles Starship launch capacity at Starbase, directly addressing the infrastructure constraint on launch cadence. SpaceX has 44 Starship missions planned for 2026, with Flight 12 being the first from Pad 2. The dual-pad setup is the physical infrastructure required to close the launch cadence gap for large-scale constellation deployment.