Urgent.News

What's breaking now, across thousands of outlets.

Tech

SpaceX Bids for Space Dominance, Plans 456 Starship Launches Per Year

SpaceX's plans for Starship are out of this world, and quite simply boggle the mind.

In 2000, U.S. space companies launched a total of 28 rockets. From 2001 to 2010, the U.S. space odyssey slowed, averaging 18 rocket launches per year. SpaceX, founded in 2002, launched its first Falcon 9 rocket in 2010 and turned it into a reusable rocket by 2020. That year, U.S. companies conducted 44 launches, the most since the Apollo era, with more than half carried out by SpaceX.

Since then, SpaceX has launched increasing numbers of rockets annually, with 161 in 2025. Now, SpaceX plans to launch its Starship megarocket 456 times in a single year, according to a Federal Aviation Administration (FAA) disclosure. The company has requested permission to conduct up to 100 launches per year in Phase 1, expanding to 456 launches per year in Phase 2.

This would result in over 68,400 tons of payload into orbit annually, surpassing the total payload ever launched in human spaceflight history. SpaceX currently has permission for up to 25 annual launches from its Boca Chica Launch Site in Texas. However, the process to implement these plans involves numerous studies and potential challenges, including environmental impact assessments, land use, and socioeconomic studies.

Written by urgent.news from Motley Fool's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Also reported by 1 other outlet

Read the original at fool.com →

More in Tech

Closing a Terminal Sends Your Coding Agent SIGHUP. How Session Hosts Keep It Alive

Book: System Design Pocket Guide: Interviews The series: Pocket Guides for Developers — 8 short books on agents, RAG, prompts, observability, events, databases and system design — the whole series My…

  • Closing terminal window kills coding agent process
  • SIGHUP signal from kernel to shell ends the job
  • tmux creates new session, keeps agent alive

BLACKBOX: Giving Incident Response a Memory

Production incidents rarely arrive as isolated problems. A single alert can be connected to a recent deployment, a downstream dependency, an overloaded database, an unfamiliar service owner, or a…

  • BLACKBOX AI tool helps SRE teams investigate incidents by connecting services, alerts, and runbooks.
  • Uses knowledge graph FalkorDB for multi-hop reasoning to identify root causes and blast radius.

More from Sunday 18 October →