5 minute read•Updated 4:05 PM EDT, Fri June 6, 2025
Cape Canaveral, FL – The U.S. Department of the Air Force (DAF), in coordination with the Federal Aviation Administration (FAA), NASA, and other federal partners, has officially released the Draft Environmental Impact Statement (EIS) for SpaceX to bring Starship to Cape Canaveral Space Force Station (CCSFS) in Florida.
The proposed action would enable SpaceX to build 2 pads where they would launch and land its Starship-Super Heavy vehicle up to 76 times annually.
The Proposed Action: Redevelopment of SLC-37
The proposal aligns with U.S. strategic goals outlined in 10 U.S.C. § 2273 and § 2276, which underscore the importance of assured access to space for national security payloads and encourage collaboration with commercial space entities to enhance Department of Defense (DoD) space infrastructure.
According to the EIS, the purpose of the proposed action is to expand U.S. space launch capacity to meet growing national security and commercial demands, while the need stems from increasing launch frequency requirements, limited capacity at current sites, and federal policy to leverage private-sector innovation.
SLC-37, formerly the home of the United Launch Alliance’s Delta IV Heavy, was officially vacated after the rocket’s final flight in April 2024.
The DAF and SpaceX are now seeking to transform the 230-acre complex into a state-of-the-art, high-cadence launch and landing site for Starship-Super Heavy operations.
Key elements of the proposed site include:
Two 600-foot tall integration towers
Two 225-foot diameter concrete landing pads with catch arms
Launch flame diverters, water deluge systems, and retention ponds
Natural gas pretreatment and methane liquefaction facilities
Liquid oxygen and liquid methane storage tanks
Roadway widening from SLC-37 to Kennedy Space Center (KSC), including 7 miles of Phillips Parkway
The first launch is targeted for 2026, with full operations supporting up to 76 launches and 152 landings annually—divided between Starship and Super Heavy booster recoveries.
Launch and Landing Operations
If approved, operations at SLC-37 would transform Cape Canaveral into the core of Starship’s rapid-reuse architecture. Each launch would be preceded by tank tests, spin tests, wet and dry dress rehearsals, and static-fire tests.
SpaceX anticipates reducing the frequency of static-fire tests as reliability improves.
The proposed annual operations could include up to 76 Starship/Super Heavy launches, each potentially accompanied by a Super Heavy booster landing shortly after liftoff and a Starship landing upon mission completion, totaling up to 244 combined launch and landing activities. Additionally, up to 16 scrubs—canceled or delayed launches—could occur, representing up to 20% of total launch attempts.
Testing activities may involve up to 76 static-fire tests each for both Starship and Super Heavy, adding 152 test events per year. Altogether, the maximum annual operational activity, including launches, landings, scrubs, and tests, could reach 396 events.
SpaceX plans to recover the Super Heavy booster using the "chopsticks" catch system at SLC-37 or land on floating offshore platforms. Starship itself could return to the launch site, splashdown in the ocean, or be expended in rare cases. Every landing is expected to generate a sonic boom, some over land.
Components would be transported from Starbase in Texas via barge, then overland to the launch pad. SpaceX would also operate refurbishment and integration on site to achieve a "factory-to-launchpad" turnaround model.
Noise & Environmental Impact
The Draft EIS also identifies potential impacts from noise, air quality, water use, and visual pollution.
With Starship’s powerful 33-engine Super Heavy booster, sonic booms and acoustic energy levels will be more intense than those from Falcon 9 or Falcon Heavy. Sensitive areas—including schools, national parks, and wildlife refuges—were assessed, with a focus on Merritt Island, Playalinda Beach, and Titusville.
Restricted access and maritime exclusion zones will be enforced around the launch windows. SLD 45 will manage scheduling to minimize public disruption and balance with other operators.
Why Not Elsewhere? Eliminated Alternatives
The EIS outlines extensive criteria used to evaluate alternative sites. These include proximity to a Space Force installation, compatible land use, ability to support 76 launches per year, support for eastward trajectories, and existing infrastructure.
Launch Sites Considered and Eliminated:
SLC-40 (CCSFS)
Current Use: Falcon 9
Why Eliminated: Cannot support 76 Starship launches annually without disrupting up to 50 Falcon launches. Potential conflict with ULA’s Vertical Integration Facility.
SLC-50 (CCSFS)
Status: Undeveloped greenspace
Why Eliminated: High ecological sensitivity (endangered species and archaeological sites). Lacks infrastructure, does not meet reuse criteria.
LC-39A (KSC)
Current Use: Falcon 9, Falcon Heavy, Crew Dragon, and under development for Starship
Why Eliminated: Conflicts with crewed launch operations. Limited capacity for high-frequency Starship flights. Environmental concerns due to proximity to Merritt Island National Wildlife Refuge (MINWR) and Canaveral National Seashore (CANA).
LC-49 (KSC)
Status: Undeveloped and part of MINWR
Why Eliminated: Public accessibility and land management restrictions prevent safe launch operations.
SLC-4 and SLC-6 (Vandenberg SFB, CA)
Why Eliminated: Do not support required eastward launch trajectories. Focus remains on polar or sun-synchronous orbits.
Starbase (Boca Chica, TX)
Current Use: R&D and low-frequency Starship launches
Why Eliminated: Lacks proximity to a USSF installation and cannot support the required annual cadence. Regulatory limits remain in place.
Other Undeveloped East Coast Locations
Why Eliminated: Not adjacent to USSF property; lack environmental clearances and logistical infrastructure.
What’s Next?
The public comment period is currently open. Once comments are reviewed and incorporated, a Final EIS and Record of Decision (ROD) will determine whether SLC-37 will be leased to SpaceX.
If approved, construction could begin by late 2025, with Starship’s first launch from SLC-37 tentatively scheduled for 2026. SpaceX would receive two separate lease agreements covering areas north and south of Patrol Road to enable phased development.
