SpaceX names span launch sites, test and manufacturing locations, orbital programs, and vehicle designations. This reference explains Starbase in Texas, historic Cape Canaveral and Vandenberg operations, Cape Canaveral Space Force Station and NASA’s Kennedy Space Center proximity, and key fleet tags such as Falcon 9, Falcon Heavy, and Starship. It also clarifies mission naming conventions, Dragon service modules, and test site identifiers used across flights and facilities. The result is a durable overview that helps readers decode how SpaceX labels its sites and programs for operations, engineering, and commercial purposes.
Primary Launch Complexes and Sites
SpaceX uses several named launch complexes across the United States. Each site carries a facility identifier used in mission planning, regulatory filings, and public communications. The main operational bases are in Florida, Texas, and California, with frequent expansion and naming updates in environmental and licensing documents.
Starbase, Texas
Starbase, located near Boca Chica Village in Cameron County, Texas, serves as the primary development and launch site for Starship and Super Heavy. The location is frequently referenced as Starbase, Boca Chica, or Starbase Texas in mission logs and environmental records. It is designated for both orbital and suborbital testing, manufacturing, and engine testing, forming the core of long term Mars and lunar development efforts. Environmental impact reports and Federal Aviation Administration license documentation use Starbase as the formal site name.
Cape Canaveral Space Force Station and Kennedy Space Center
SpaceX operates from Launch Complex 40 at Cape Canaveral Space Force Station and from Launch Complex 39A at NASA’s Kennedy Space Center, the latter shared with commercial and government missions. Historically referred to as Cape Canaveral, the eastern Florida coastal range provides access to inclined and direct orbital trajectories. These sites host Falcon 9 and Falcon Heavy launches, with mission designations such as SLC‑40 and KSC‑39A used in official tracking and telemetry files.
Vandenberg Space Force Base, California
Vandenberg Space Force Base, on California’s Central Coast, hosts polar and sun-synchronous launches. SpaceX uses Space Launch Complex 4E for Falcon 9 missions requiring southern trajectories over the Pacific. The site’s designation in regulatory and tracking systems is Vandenberg Space Force Base, often shortened to VAFB in flight data and launch manifests.
Vehicle and Fleet Names
SpaceX consistently names its launch vehicles and spacecraft families. These names signal capability class, mission role, and generational improvements. Understanding this naming system helps interpret press releases, regulatory filings, and flight history.
Falcon 9
Falcon 9 is a partially reusable two-stage rocket named for the Falcon spacecraft and the Merlin engine family’s nine first-stage engines. The ‘Block’ or ‘Version’ suffix indicates major upgrades, such as Falcon 9 Block 5, the currently active variant optimized for reusability and cadence.
Falcon Heavy
Falcon Heavy uses three Falcon 9 cores strapped together, making it the company’s highest thrust operational vehicle. Named to signal lift capacity, it supports heavy payloads to geostationary transfer orbit and beyond. Reuse information for side boosters and the center core is tracked individually in mission summaries.
Starship
Starship refers to both the fully reusable super heavy lift system and the spacecraft itself. The system comprises Super Heavy, the first-stage booster, and Starship, the second-stage spacecraft. The entire stack is commonly called Starship, with Booster and Ship designations used in engineering, manufacturing, and flight test documentation.
Mission and Test Naming Patterns
SpaceX mission names combine launch site, vehicle, and serial identifiers. As programs mature, naming becomes more structured. Observers should treat developmental test flights as iterative, with public names evolving as the program progresses.
Operational Missions versus Developmental Tests
Operational missions, such as commercial satellite launches or Crew Dragon flights, carry concise names like Starlink 6-1 or Crew-6. Developmental tests, particularly for Starship, use descriptive labels such as IFT‑1 (In-Flight Test 1) or IFT‑2, reflecting their role in gathering engineering data rather than operational deployment.
Booster and Ship Identifiers
Individual Falcon 9 boosters and Starship prototypes receive internal serial numbers used in tracking and anomaly investigations. These identifiers, while not always public in full form, appear in regulatory filings and post-flight reports. Reuse records, landing outcomes, and fleet rotation notes are maintained in company and regulator documents.
Tracking Terminology and Common Reference Points
When reading about SpaceX names, it helps to distinguish between site labels, vehicle names, and shorthand used in media and regulatory text. Consistent reference points reduce confusion between locations, hardware generations, and test objectives.
Quick Reference Table
| Name / Identifier | Verified Detail | Source Type |
|---|---|---|
| Starbase | Primary Starship development and launch site near Boca Chica, Texas | FAA and state environmental records |
| Cape Canaveral SFS LC‑40 | Primary Falcon 9 and Falcon Heavy launch site | Space Force and SpaceX mission logs |
| Kennedy Space Center LC‑39A | Shared pad for Crew, Dragon, and select Falcon missions | NASA and SpaceX manifest data |
| Vandenberg SLC‑4E | Falcon 9 polar and sun-synchronous launch site | Space Force licensing documents |
| Falcon 9 Block 5 | Current operational version of Falcon 9 focused on reusability | SpaceX vehicle specifications and flight history |
| Falcon Heavy | Heavy-lift variant using three Falcon 9 cores | SpaceX mission announcements |
| Starship | Fully reusable super heavy lift system (Booster + Ship) | FAA environmental and licensing filings |
| IFT | In‑Flight Test designation for Starship developmental flights | SpaceX test flight summaries and FAA reports |
Why Names and Identifiers Matter
Clear naming supports safety reporting, regulatory compliance, and mission tracking. Regulators, partners, and the public rely on consistent labels for launch sites, vehicles, and test objectives. Misidentification can obscure performance trends, environmental impacts, and safety outcomes. Using verified names and identifiers improves accuracy in research, reporting, and public understanding of SpaceX operations.
Common Points of Confusion
Readers sometimes conflate geographic proximity with operational naming. Cape Canaveral and Kennedy Space Center are neighboring sites but use separate identifiers. Boca Chica is frequently called Starbase in informal discussion, yet regulatory documents use the formal site name. Developmental test labels such as IFT are often mistaken for mission names rather than test phases. Recognizing these distinctions clarifies communication and documentation.
Reliable Sources for Verification
Key details in this overview are drawn from FAA environmental reviews, SpaceX launch manifests, Space Force and NASA records, and publicly indexed flight history databases. These sources maintain consistent naming conventions for sites, vehicles, and tests, providing a durable basis for reference and comparison over time.
Navigating Updates and Naming Changes
As Starbase develops and new variants emerge, naming in filings and public communications may evolve. Vehicle generations, such as Block upgrades and Starship revisions, are tracked in regulatory submissions and technical summaries. Staying aligned with official documents ensures accurate interpretation of SpaceX names across operational and historical contexts.