SpaceX’s Florida Starship Plans Face Rival Objections
▼ Summary
– SpaceX is expected to begin launching Starship rockets from Cape Canaveral next year, according to the military commander of the spaceport.
– Blue Origin and United Launch Alliance have complained that frequent Starship launches could force them to routinely clear personnel from their launch pads for safety.
– This is not the first time SpaceX’s rivals have attempted to block its activities, having previously tried to prevent NASA from leasing a launch pad to SpaceX in 2013.
– The Space Force unit confirmed that Starship launches will sometimes restrict neighboring companies’ access to their launch pads, at least initially.
– SpaceX is constructing Starship launch sites at both Kennedy Space Center and on Space Force property, with the range prepared to support launches by early to mid-next year.
The prospect of SpaceX launching its massive Starship rocket from Florida’s Space Coast as early as next year is generating significant operational friction among its launch facility neighbors. The commander of the military unit overseeing the Cape Canaveral spaceport confirmed the anticipated timeline, setting the stage for a new era in spaceflight from the storied launch pads.
This development has not been met with universal applause. SpaceX’s primary competitors, Blue Origin and United Launch Alliance (ULA), have lodged formal complaints, arguing that the proposed launch cadence of up to 120 Starship missions annually would severely disrupt their own operations. Their central concern revolves around safety protocols that would frequently force them to evacuate personnel from their own launch sites whenever a Starship is preparing for flight.
This is not the first instance where these aerospace giants have attempted to stymie SpaceX’s expansion. A similar dispute arose a decade ago when the same companies unsuccessfully challenged NASA’s decision to lease a dormant launch complex to SpaceX, a move that ultimately paved the way for the company’s current dominance.
Col. Brian Chatman, who leads the Space Force unit known as Space Launch Delta 45, acknowledged the logistical challenges. He confirmed to reporters that Starship launch operations will, especially in the initial phases, periodically restrict neighboring companies from accessing their own facilities. His unit manages the Eastern Range, the entity responsible for public and personnel safety for all launches originating from Cape Canaveral Space Force Station and the adjacent Kennedy Space Center.
The primary duty of Chatman’s command is to guarantee that all individuals remain outside designated hazard areas during critical testing and launch countdowns. This safety mandate extends beyond the spaceport’s fences to protect the surrounding public.
Despite the operational hurdles, Col. Chatman expressed immense optimism about the Space Coast’s current trajectory. “There is no better time to be here on the Space Coast than where we are at today,” he stated. “We are breaking records on the launch manifest. We are getting capability on orbit that is essential to national security, and we’re doing that at a time of strategic challenge.”
SpaceX’s construction of a Starship launch site is already well advanced. The company is building within the historic grounds of Launch Complex-39A at Kennedy Space Center, a location it already uses for its reliable Falcon 9 rocket missions. Plans are also in motion for a second Starship launch facility a few miles to the south on property managed by the Space Force, indicating a long-term commitment to a high-frequency launch schedule from the region.
Col. Chatman provided a clear forecast for the program’s initiation, saying, “Early to mid-next year is when we anticipate Starship coming out here to be able to launch. We’ll have the range ready to support at that time.” This timeline confirms that the Space Force is actively preparing its infrastructure to accommodate the world’s most powerful rocket, even as it navigates the complex dynamics between competing commercial space entities.
(Source: Ars Technica)
