The Department of the Air Force has issued a positive Final Environmental Impact Statement for SpaceX Starship at LC-37 at Cape Canaveral Space Force Station. This SpaceX rendering shows what the area could look like when complete. Credit: SpaceX
The proposal would turn the old Delta IV pad into a fully rebuilt launch site capable of hosting up to 76 Starship flights a year. Each mission would include a booster landing just minutes after liftoff and a Starship landing hours—or in some cases years—after launch. In short, the skies above the Space Coast are going to be very busy.
The review concludes that the project would bring no major environmental obstacles across most categories.
Still, two issues stand out: air quality and noise.
The EIS points to significant community annoyance from Starship’s noise and sonic booms, especially during nighttime launches. While the report says structural damage is unlikely, the sound levels will be noticeable across the Space Coast on launch days. SpaceX plans to use heavy sound-suppression systems and coordinate public notifications in advance. Sonic booms from returning boosters and Starship itself will be endemic, day or night.
Level at which sustained exposure may result in hearing loss
80-90
City Traffic
85
Many household appliances
80
Chamber music, in a small auditorium
75-85
Vacuum cleaner
75
Normal conversation
60-70
Business Office
60-65
Household refrigerator
55
Suburban area at night
40
Whisper
25
Quiet natural area with no wind
20
Threshold of hearing
0
Sustained Exposure Hearing Loss: the common benchmark for this threshold is an 8-hour time-weighted average exposure to 85 dBA on a repeated basis. The time exposure for a Starship launch will be measured in minutes.
During operations, the rocket’s emissions are expected to exceed federal insignificance thresholds for nitrogen oxides. The Air Force and SpaceX plan to use an adaptive management strategy, reviewing new data as operations ramp up.
Minimal Impacts Across Other Categories
The review found:
Environmental Impact Summary
Starship/Superheavy Environmental Impact Summary
Category
Assessment
Traffic
Increases during construction and launch days are manageable.
Local Wildlife
Southeastern beach mouse and Florida scrub-jay will be protected through relocation and habitat restoration plans.
Water Resources
Wetlands will see construction impacts, but all fall under federal permitting and mitigation requirements.
Historic Sites
Expected to remain unaffected, with ongoing monitoring for potential noise-related impacts.
Marine Areas
No long-term closures; only short safety zones during launches.
Overall, the report concludes that the project can proceed without causing significant long-term environmental harm, provided mitigation measures remain in place.
What Comes Next
The Air Force must still issue its Record of Decision, and the FAA will release its own determination before any Starship launches or landings take place at the site. Airspace-closure details are still being finalized, with additional FAA analysis expected. At the same time, this was one of the major hurdles the SpaceX project had to clear on its way to becoming a reality.
When approved, the redevelopment of SLC-37 would position Cape Canaveral as a major operational hub for Starship activity, supporting national security missions, commercial flights, and NASA needs. SpaceX’s Boca Chica facility will work in tandem with the SpaceX Eastern Range facility to support the giant spacecraft.
As a company, SpaceX moves quickly. Once approved, it is unlikely the company will delay construction at LC-37, and once started, the work will proceed rapidly until the facility is ready for its initial use. In Boca Chica, SpaceX has constructed Starship launch and landing facilities in months, as opposed to the multi-year efforts NASA has had with SLS. It is reasonable to expect much the same here in Florida.
Oddly, SLC-37 may not be the first Starship pad to enter service on the Space Coast. Given its construction lead, that distinction is likely to go to LC-39A at Kennedy Space Center. The FAA is still finalizing its Environmental Impact Study for that facility, but SpaceX has been steadily constructing its Starship launch pad on the KSC site.
Sputnik 1 ascends aboard a Soviet R-7, October 4, 1957. Photo is from a Soviet documentary, “Ten Years of Space”
On October 4, 1957, the Space Age began in earnest: on that day, the Soviet Union orbited Sputnik 1, shocking the world and especially the United States. Sputnik was flying overhead, the Russians were having a propaganda feast, and military leaders were confronting a sobering new reality.
Fear and anger washed over the West. If the Soviet Union could orbit the entire planet, then their missiles could strike any target any place in the world too. Suddenly, the Cold War was a lot colder. Nobody was safe. Anywhere.
Then came the questions: Were the Russians that far ahead of everyone, especially the US? Could America have orbited a satellite first? Then, of course, the biggest question, the one that was usually shouted: What are we going to do about it?
The answer to the last question was to orbit our own artificial moon, or satellite. Soon.
The answers to the other questions are nuanced. The US was indeed capable, and could have been the first to orbit, probably. Even if it had, America was still technically behind the Russians, who could loft more mass than the US.
President Dwight D. Eisenhower (1953 to 1961)
From the convenience of the hindsight offered by history, the short answer is technically that the United States rocket probably could have won the race to orbit, but politically, not under President Dwight D. Eisenhower.
Geopolitical Chess Games
Eisenhower deliberately chose a civilian path to America’s first satellite to set a crucial legal precedent for future reconnaissance, and he kept the Army’s rocket team (ABMA) on a tight leash until after Sputnik flew. Meanwhile, the Army had nearly complete orbit-capable rockets stored in an Alabama warehouse long before October 4, 1957, and the launch of Sputnik 1. Eisenhower sidelined them.
Years before Sputnik, Eisenhower was already pursuing reconnaissance satellites. In 1954, he had established The Killian Panel to devise technology for global intelligence gathering that would reduce the possibility of a surprise nuclear attack. The result was an initial concept for the WS-117L reconnaissance satellite program, which the Air Force began in earnest in 1956, with the result being the first American spy satellites.
Eisenhower’s advisers worried before Sputnik that if the United States put a military satellite such as a WS-117L spacecraft over other countries first, it could trigger diplomatic protests that outer space was sovereign airspace above each nation below.
To negate this idea, the White House therefore backed a civilianInternational Geophysical Year (IGY) satellite using the Navy’s Vanguard, precisely to establish the norm that satellites could lawfully overfly national territory—a principle dubbed “freedom of space.”
When Sputnik crossed American skies without international protest, Eisenhower saw that the norm was effectively validated. The concept of “Freedom of space” remains relevant to this day. So do reconnaissance satellites.
The firestorm was intense and instantaneous. ‘America,’ many political commentators said, ‘cannot let this stand.’
Publicly, the President downplayed Sputnik’s military significance but privately, he took it as a useful assist to the overflight precedent he wanted for reconnaissance. The punch certainly stung, but Eisenhower, ever the cagey strategist rolled with it.
It took Eisenhower four days to order an acceleration of the first U.S. launch. On Oct. 8, 1957, he directed the Pentagon to ready the Army Ballistic Missile Agency (ABMA) to orbit a satellite; the formal go-ahead arrived in Huntsville on Nov. 8. Explorer 1 flew on Jan. 31, 1958.
Did The US Have An “Orbit-Capable” Rocket Before October 4, 1957?
“The Redstone flew in ’53 the first time, and even before that, in about ’52, von Braun and I met each other in the hallway one day, and just in passing, he said to me, “With the Redstone we can do it.”
From a technical standpoint, the Army’s Jupiter-C was close to being an orbital launcher. But “close” is not “on the pad.” Juno did not have a flight-ready payload assembled and qualified, nor had it been authorized for an orbital mission. The ABMA team was dealt out despite holding the best hand at the table. Moreover, the orbital configuration’s design existed, had even been flight tested, but had never, of course, gone into orbit.
In 1956–57, Jupiter-C performed high-altitude nose-cone tests and ABMA and JPL engineers knew that adding a small fourth stage a small payload could reach orbital velocity—the configuration that lofted Explorer 1. In those earlier tests, the highest stage was intentionally “dead” (often described as being ballasted with sand) to prevent any accidental satellite. Those were orders, not a lack of know-how. The fourth stage would have to wait.
Were Orbit-Capable Rockets Just “Sitting In A Warehouse?”
One of the enduring stories claims ABMA had “orbit-capable rockets sitting in a warehouse” before Oct. 4, 1957. There is a kernel of truth wrapped in myth that has become legend.
ABMA did keep Jupiter-C hardware available from its nose-cone test series in storage in Huntsville, and senior Army leaders argued they could orbit a small satellite quickly if authorized. Those rockets were, of course, in Alabama, and not here in Florida, where they would eventually launch.
Later accounts (and Army memoirs) recall these “surplus” Jupiter-C vehicles “on the shelf” and describe efforts to ensure no accidental orbital launches resulted during previous test flights.
“Tucked away inside the Jupiter-C program was a well-known secret agenda to assemble one of these vehicles with a 4th stage that could place a small object into orbit about the earth. One of the Jupiter-Cs received special handling and security. When we conducted the SFT, which included testing all the electronics necessary to activate the 2nd, 3rd, and 4th stages, the Commanding General and Dr. von Braun were on hand to observe the test.
“When that test was completed, the whole assembly was wrapped and carried to a sealed hanger to await the possible permission to orbit a satellite.”
That supports the notion of ready hardware—but not a complete, cleared satellite mission waiting only for a countdown. Some final preparations would be needed. A payload needed to be designed, built and tested. The rockets would need to be transported to the Cape, they’d need to be prepared, tested, payload installed, tested some more, taken out to the launch pad then prepared to launch, etc. before finally flying. Once flying, telemetry would need to be monitored, a global task then involving international cooperation and even ships placed at points mid-ocean.
Those preparations are demanding and exacting and encountering problems during a launch campaign is almost expected. Especially when it is your first time doing it.
The Flop Heard Around The World: Vanguard TV3
On December 6, 1957, the US made its first reply to the Soviet feat.
Here at Cape Canaveral, Vanguard Test Vehicle-3 (TV-3) managed to rise only about 4 feet before it lost power. The rocket then collapsed back onto the launch pad and detonated in a tremendous fireball. It was a highly visible and embarrassing setback for the US.
Newspapers derided the failure with nicknames like “Flopnik” and “Kaputnik,” playing off the Soviets’ Sputnik triumph. Though the Vanguard payload was hurled clear of the blast and later recovered, it was too damaged for any further use. The rocket was in thousands of pieces and for it, there was no repair. For the time being, Vanguard was out. Redstone and ABMA were the US best hope to reply to the Soviet Union.
Now tasked to orbit a satellite after Sputnik, ABMA and JPL went to work as preparations for another Vanguard attempt continued elsewhere. The ABMA / JPL teams fielded the Juno I / Explorer 1 booster and satellite combination and launched successfully on Jan. 31, 1958.
If that sounds simple, it wasn’t. VL Pinson, Sr., an ABMA employee then located here in Cocoa said, “We checked, then we rechecked, then we checked again. When we were asleep we were dreaming about what we should check the next day. Everything had to be right.”
Turned out, the ABMA and JPL team did a whale of a good job. They successfully launched to orbit on their first try, a feat that even today is notable. In 1957, it was an incredible achievement.
William Pickering, James Van Allen, and Wernher von Braun celebrating at the announcement of Explorer I’s successful launch in 1958.
That mission is obviously the stuff of legend: in 119 days, the United States joined the Soviet Union as a spacefaring nation. While the two countries had launched “scientific” satellites, the meaning was very clear to military leaders from both sides of the Iron Curtain: either side can strike the other at any place and at any time. The reality of Mutual Assured Destruction was coming quickly into focus.
The speed of the ABMA Juno-1 turnaround underscores how mature the hardware was—but also that it was policy, final approvals and geopolitical gamesmanship that stood between Huntsville and an actual pre-Sputnik orbit.
So, Could The US Have Gone First?
There are a lot of ifs, but yes, under different political circumstances, the US probably would have beaten Sputnik 1.
If Washington had chosen the Army’s route in 1955–56 instead of Vanguard, the U.S. might have launched first. ABMA and its Redstone family were farther down its development timeline, its team more experienced, and its platform more robust. Its chances of success were always higher than Vanguard.
On the surface, that might suggest the US backed the wrong horse. Still, Eisenhower’s decision to support the Vanguard program was strategic and never careless: it prioritized a civilian image and the overflight precedent essential for the reconnaissance satellites that his administration was already developing.
So, sometimes when you lose, you win.
As NASA’s own history notes, the administration viewed Sputnik less as a military threat than as an (unwelcome) but useful boost to establishing “freedom of space.” Once that point of international law was established, Eisenhower unleashed Huntsville and JPL—and Explorer 1 was in orbit within weeks. And not so long afterward,
The Space Age was born and the starting gun for the Space Race had been fired…twice. The world and especially the areas around Cape Canaveral would never be the same.
A recent Executive Order signed by President Trump aims to reshape the regulatory landscape for the U.S. commercial space industry. There are some huge potential implications for the Eastern Range in Florida — and its residents.
Titled “Enabling Competition in the Commercial Space Industry” and signed on Wednesday, August 14, 2025, the EO aims to cut through red tape, lower environmental and regulatory hurdles as well as speed up launch licensing.
The order calls for a streamlined process across multiple federal agencies to reduce delays in launch approvals, environmental reviews, and spaceport development. It also encourages deregulation of emerging space activities and infrastructure, with the goal of maintaining U.S. leadership in commercial space operations.
Some important aspects of the EO:
Faster environmental reviews for launch and reentry licenses.
Eliminating outdated regulations that hinder new space tech and infrastructure.
Assessing state-level barriers to spaceport development under the Coastal Zone Management Act (CZMA).
Streamlining federal reviews between NASA, Department of Defense, and Department of Transportation to remove duplication.
Establishing new leadership roles at the Department of Transportation and FAA to drive reform.
Strengthening U.S. leadership in space to stay ahead of global competitors, especially in defense, aerospace, and satellite industries.
Effects On The Eastern Range
As the world’s busiest spaceport, the new Executive Order will have an effect on both Cape Canaveral and Kennedy Space Center. Since the Eastern Range operates under coordination between the U.S. Space Force and NASA, the directive’s push for interagency alignment could help eliminate overlapping permitting processes. That may translate to fewer bureaucratic hurdles and quicker project approvals.
The Starship Tower (right) under construction at LC-39A. SpaceX has also begun construction for support facilities on Roberts Road inside KSC. Photo: Charles Boyer / Talk of Titusville
More launches means more jobs, and the Space Coast area will benefit from that. It is said that a rising tide floats all boats, and in this case, more activity on the Eastern Range will greatly benefit the area’s economy across the board.
Part 450 Changes Ordered
The Executive Order directs the DOT Secretary to reevaluate and amend or rescind 14 CFR Part 450 of Federal Aviation Administration regulations, the current regulatory structure for launch licenses and re-entries. Originally, Part 450 was intended to streamline launch and reentry in the era of commercial spaceflight, but it is widely seen as having failed to meet its objective.
Launch operators often face delays due to reviews required under the National Environmental Policy Act (NEPA). By streamlining or eliminating redundant checks, the Eastern Range could see faster launch timelines and increased throughput.
Slow and ponderous consideration and disposition of license requests have long generated complaints by operators, something the EO is designed to speed up and simplify. Details are forthcoming regarding any changes that will be made, as is the timeline for their release. At this point in time, the DOT Secretary has just received the order.
State Environmental Laws To Be Examined
The Executive Order also calls for a review of how state compliance with the Coastal Zone Management Act (CZMA) may be affecting spaceport development. This review could lead to reduced friction between Florida’s regulatory agencies and federal space operators, potentially easing constraints on new infrastructure.
If implemented, the changes could allow companies such as Blue Origin, SpaceX, Firefly, and Relativity Space to expand more rapidly and with greater ease. With fewer regulatory delays, the Eastern Range could support more launch pads, more missions, which would bring additional economic activity in the region.
Blue Origin’s New Glenn on its debut launch in January. Photo: Charles Boyer / Talk of Titusville
On the other hand, more launches, more launch pads, and fewer regulations might put an additional burden on already strained resources in the region. Port Canaveral, for example, is nearly bursting at the seams with cruise ship business, freighters, and in the past ten years, SpaceX returning boosters to port regularly.
The Local Effect
Local residents will hear the roar of rocket launches more often, and as the industry shifts towards rocket reusability generally, they will will hear more sonic booms when spacecraft return to The Cape. SpaceX, for example, is planning dozens of flights a year of its new Starship Heavy when it goes operational, and each booster return to launch site mission will have a sonic boom. There will be a second sonic boom after the given mission’s conclusion and the Ship — the second stage and payload bay for Starship — returns to land at The Cape as well.
While space launch activities are not a particularly large contributor to pollutants in the Indian River Lagoon, there is always the possibility of a spill or leak from support infrastructure or during construction. More activity means more opportunity for that to happen, though it should also be said in the same breath that does not mean it will happen, but instead, that it could. NASA, the Space Force and launch companies are very good stewards of their facilities and surrounding land, and the KSC/CCSFS area is a bright spot for wildlife and fauna in the Space Coast region.
Bottom line is that there are many other pain points and growth issues at the Eastern Range, all of which will need to be remediated as growth there continues.
What About The LC-39A and LC-37 Environmental Studies Underway?
This Executive Order could potentially affect Starship’s development at Launch Complex 39A (LC-39A) and Launch Complex 37 (LC-37), but how much depends on how the implementing agencies interpret the “streamline environmental reviews” directive.
Both LC-39A and LC-37 are currently in the middle of Environmental Impact Studies (EISs) with final drafts expected in the coming months. After that, Final Decisions on both sites will be rendered, and given the ongoing construction at LC-39A for Starship, it would appear that the decisions are fait accompli and that Starship will be a regular on The Cape’s launch calendar.
The Executive Order specifically directs the Secretary of Transportation (through the FAA’s Office of Commercial Space Transportation) to eliminate or expedite environmental reviews for launch and reentry licenses. In theory, this could allow the FAA to shorten the review process, remove redundant steps, or rely on less time-intensive environmental assessments instead of full EISs.
However, EIS timelines are also influenced by other agencies—including NASA (which owns LC-39A) and the U.S. Space Force (which oversees LC-37 at Cape Canaveral). The EO also instructs these agencies to align their processes and eliminate duplication, which could expedite the process if multiple reviews are being conducted for the same project. Whether this will affect the two EISs that are nearing their final phases is an open question. It would seem that the studies are already completed and that final reports and decisions on adoption are not far away.
One complicating factor: environmental review requirements come from statute (NEPA) as well as agency policy. The EO can direct agencies to streamline within the law, but it can’t waive NEPA entirely. That means some level of review is still required, especially for projects with substantial potential environmental such as methane-fueled launches. Stoke Space, Relativity and other launch vendors might see some benefit. SpaceX probably won’t need it.
At the end of the day, it’s fair to say that the new Executive Order is smoothing the path for growth that was already coming, and that it will limit the ability of outside organizations (like environmental groups) to have much effect on decision-making regarding space launches. Whether that is a good thing remains to be seen.
ULA’s Vulcan with the USSF-106 mission on the launch pad. Photo: Charles Boyer / Talk of Titusville
United Launch Alliance (ULA) is preparing to launch Vulcan on its first national security mission early next week from SLC-41 at Cape Canaveral Space Force Station. Scheduled for Tuesday, August 12, the USSF-106 mission will lift off from Cape Canaveral’s Space Launch Complex 41, carrying the U.S. Space Force’s Navigation Technology Satellite-3 (NTS-3) into geosynchronous orbit.
Current T-0 confirmed by official or reliable sources.
Window Opens
Tuesday, 08/12/2025 7:59 PM EDT
Window Closes
Tuesday, 08/12/2025 8:59 PM EDT
Destination
Geosynchronous Orbit (GEO)
Mission Description
USSF-106 is a U.S. Space Force mission deploying multiple payloads—including the NTS-3 (Navigation Technology Satellite 3), a demonstration satellite testing a reprogrammable digital signal generator to improve navigation resilience—directly into GEO using the new Vulcan Centaur VC4S rocket.
Information current as of: August 10, 2025, 11:54 AM EDT
Launch dates and liftoff times are subject to change at any time.
USSF-106 will be Vulcan’s first operational flight, a milestone years in the making. ULA started work on the Vulcan family of rockets in 2014, and later the same year decided to use Blue Origin’s BE-4 methane-oxygen (methalox) engines. The decision was somewhat controversial at the time, given that Blue had not completed the final design of BE-4 much less started producing them at scale. It is ULA’s first rocket that the company has designed completely by itself.
This decision was a result of a way to move away from reliance on Russian RD-180 engines, which powered ULA’s Atlas V, and to ensure a domestically produced alternative for national security launches, and was mandated by Congress.
High Stakes for ULA
The mission is a key test not only of the rocket’s technical reliability but also of ULA’s ability to deliver on commitments that have been delayed by the vehicle’s troubled rollout. Military leaders, including Major General Stephen G. Purdy, have voiced frustration with setbacks that pushed back four major national security missions.
Vulcan CERT-2, midflight. Photo: Charles Boyer / Talk of Titusville
For ULA, this launch is more than just another flight; it is a chance to restore customer confidence after the near-disaster of Vulcan’s second certification mission last October. That launch succeeded in reaching orbit, but only after a solid rocket booster nozzle broke off mid-flight, causing asymmetric thrust that had to be corrected in real time by the in-flight software and by ground controllers. The incident raised concerns about the Vulcan’s Northrup Grumman-built GEM 63XL solid rocket motors, which lead to months of investigation and a test firing before certification for Vulcan was granted in March.
ULA holds a $5.3 billion contract to provide launch services through 2034, a lucrative and strategically important deal that depends on consistent, fault-free performance. A successful USSF-106 flight would help Vulcan’s place as a major part of the nation’s launch capability. A failure would put the company’s reputation and perhaps even government contracts in peril.
Photo: Charles Boyer / Talk of Titusville
Payload
The mission’s payload, NTS-3, is an experimental navigation satellite designed to test advanced technologies designed to augment the GPS system.
The Air Force Research Lab released this video describing NTS-3:
Artist’s concept for NTS-3 in geostationary orbit. L3Harris Corporation will integrate NTS-3 using Northrop Grumman’s ESPAStar bus, building on EAGLE’s flight heritage. Graphic Credit: 1st Lt. Jacob Lutz
A DJI Mavic drone. Photo: Mark Stone, Florida Media Now
By Mark Stone, Florida Media Now: A 71-year-old Chinese-born Canadian citizen, Xiao Guang Pan, has entered a guilty plea in a federal case involving unauthorized drone flights over Cape Canaveral Space Force Station.
According to court documents, Pan traveled to the U.S. on a tourist visa in early January and used a DJI Mavic Pro 3drone to capture nearly 2,000 photos and videos—more than 250 of which showed military infrastructure including submarine docks, munitions bunkers, payload processing buildings and security checkpoints on federal defense property. A naval base located on the Cape Canaveral station frequently sees the comings and goings of US Nuclear submarines via the main channel of Port Canaveral.
A criminal information filed February 13, 2025, by the U.S. Attorney’s Office for the Middle District of Florida charges Pan with three counts of “using an aircraft for the unlawful photographing of a defense installation without authorization.” Each count carries a maximum penalty of one year in prison and a fine of up to $100,000.
Federal investigators reviewed flight logs showing Pan launched the drone on nine separate occasions between January 5 and 7. On January 5, from several miles away, he recorded two videos and 21 photos of launch complexes and contractor facilities using a telephoto lens. The following day, he moved closer, capturing an additional nine videos and 166 photographs from different angles—a day later, on January 7, Pan launched the drone from Class D controlled airspace outside the CCSFS restricted zone without FAA authorization, seizing images of roads, power lines, mission control buildings, fuel and munitions storage, and submarine infrastructure.
Pan maintained that he was unaware the drone was near a military installation, claiming it sent no alerts. But screenshots from his phone showed satellite images pinpointing “Cape Canaveral Space Force Station” at his takeoff point, and the drone’s flight data confirmed he did in fact receive violation warnings as he flew the drone. Pan maintains an Instagram account with dozens of photos of architecture and landscapes taken with his drone.
The investigation involved agencies such as Homeland Security Investigations, the Air Force Office of Special Investigations, the FBI, FAA, CBP, Federal Air Marshals, NASA’s OIG, and the Brevard County Sheriff’s Office. In his plea agreement, Pan acknowledged these details and agreed to the terms; prosecutors noted the document “does not include … all the events, persons involved, or other information relating to this case”.
Pan was released from custody to return to Ontario for medical treatment, citing concerns related to his coronary artery disease and diabetes.
His sentencing hearing is scheduled for October 1, 2025, in Orlando. If sentenced to the maximum for all counts, Pan could face up to three years in prison and fines totaling $300,000.
Concerns about drones spying on sensitive US facilities have heightened in the last year following a wave of suspicious drone sightings across the country. Even though most of those sightings have turned out to be hobbyists legally flying their drones, authorities remain concerned about spying by the Chinese. DJI, who makes the type of drone used by Pan, has been said by some to relay information to Chinese intelligence sources. That concern led to a ban on the use of DJI products by US agencies. Even so, DJI remains one of the most popular drone manufacturers in the world among hobbyists.
Talk of Titusville is republishing this story with permission from Florida Media Now, who is responsible for the content.
The last Delta IV Heavy at LC-37A stands at the launch pad in April 2024. The rocket family is now retired and the infrastructure in this photo is now demolished. Photo: Charles Boyer / Talk of Titusville
Much of the infrastructure at Launch Complex 37’s launch pad was demolished in a controlled explosion today, marking the end of one era and the beginning of another. For those who knew the site, who watched Delta IV rockets claw their way into orbit or remembered the echoes of the Apollo era, the moment was as much about letting go of the past as it was embracing the future.
Out With The Old, In With The New
The primary targets of Thursday’s demolition were the massive Mobile Service Tower and supporting infrastructure built for Delta IV operations. These towering steel and concrete structures were no longer needed and stood as reminders of a program that had fulfilled its mission. Shortly after 9:00 AM ET a series of explosive charges, precisely placed along key support points, triggered a cascading collapse. Within seconds, the launch tower folded in on itself, kicking up clouds of dust that drifted over the grounds where giants once stood.
Apollo 5 launches from LC-37 on January 22, 1968 Photo: NASA
Crews began rigging the complex for demolition earlier this spring, following the final Delta IV Heavy launch in April 2024. Afte that final flight, United Launch Alliance (ULA) has fully retired the Delta family, closing the door on a long-running chapter in the US launch industry. The demolition marks the next major step in a broader shift at Cape Canaveral, as SpaceX prepares to reshape LC-37 for its Starship launch system as well as at LC-39A.
In both cases, a final Environmental Impact Statement will be released in the coming months for both sites. A draft of the LC-37 EIS was recently released, with findings of No Significant Impact for all ecological, cultural and land use aspects of Starship launches at the site, albeit with one major exception: Starship launches will be the loudest rocket ever launched from the Space Coast, something the Draft EIS noted with its finding of a Significant Impact being the result of Starship launches from Cape Canaveral.
After the debris is cleaned up, new construction can begin in earnest.
Note: Talk of Titusville was unable to create any original photographs of the demolition or its aftermath, as this reporter is western Canada today.
Rocket Cargo illustration U.S. Air Force illustration/Randy Palmer
The Department of the Air Force has selected an isolated Pacific island as a test site for landing rockets designed to deliver cargo quickly across the globe. The department announced its intent on Monday to build two rocket landing pads on Johnston Island, part of Johnston Atoll, a U.S. territory located roughly 818 nautical miles westwards of Honolulu. This information was published in a notice in the Federal Register.
Location of Johnston Island, relative to Hawai’i and the continenal US.
The Air Force Research Laboratory’s Rocket Cargo Program plans to lease commercial rockets to transport cargo more efficiently than traditional aircraft. According to the program’s website, the goal is to deliver up to 100 tons of cargo anywhere on the planet within tactical timelines.
Currently, the information is very generic and non-specific — no designation of launch sites, for example — but one would assume SpaceX has a strong lead in providing this capability with Starship.
AFRL expects to award several contracts to develop this capability. The major solicitations and contracts are expected to be awarded to companies that can provide launch services, and companies that can develop concepts to advance the rest of the logistics cycle (loadmaster load/unload capability, rapid launch clearance, schedulers, environment survivability). For launch services, AFRL hopes to award contracts to and partner with all viable commercial providers of this capability to encourage a broad future vendor base for the operational service.
At the same time, other American aerospace companies also have launch and soft landing capabilities, for example, Blue Origin has demonstrated landings of New Shepard boosters and capsules in an operational setting. Further development of that platform could ostensibly make it a contender in this race.
Rocket Lab has designs on reusable soft-landing spacecraft as well and is in the middle of a development cycle for its Neutron vehicle. Neutron is slated to carry about 3,000 kilograms (28,700 lbs) to LEO, suggesting that it would be well short of 100 tons even in a suborbital setting, but at the same time, it is a point to point rocket by design and could just as easily return to its launch site via a second flight from the cargo destination.
All that said, it’s obvious that SpaceX is the 800 lb gorilla in this fight.
Test Cadence Would Be Relatively Slow
The proposed landing pads would support up to 10 rocket reentry landings per year over four years. These tests would evaluate the capabilities of the Rocket Cargo Vanguard program. The department anticipates that the rocket delivery tests will begin this year. Again, details are scant, but that is how the military operates.
Johnston Island Wikimedia Commons
Potential missions for the rocket cargo system include rapidly restoring mission-critical operations and delivering humanitarian aid in disaster relief scenarios.
In October 2020, Army Gen. Stephen Lyons, then head of the U.S. Transportation Command, mentioned working with SpaceX on rocket cargo deliveries, but the recent Federal Register notice does not mention any SpaceX involvement in the current trials. That makes sense, given it is an environmental assessement, but that environmental assessment does not mention any Starship infrastructure. At this time, participants in the trials is not publicly known.
Lyons previously suggested that these rockets could transport the equivalent of a C-17 Globemaster III cargo plane’s payload anywhere in the world in under an hour. His remarks, made to the National Defense Transportation Association, were cited in an Air Force news release from October 2020.
U.S. military forces are preparing for potential missile attacks on established bases in a conflict with China over Taiwan or the South China Sea. To increase operational flexibility, the Air Force has been upgrading World War II-era airfields in locations ranging from Micronesia to the Philippines.
Officials considered other locations, including Kwajalein Atoll, Midway Island, and Wake Island, before selecting Johnston Island for the rocket landing site.
Area Is Familiar To The US Military
Johnston Island has a history of military use. The US Navy first started construction on the island in the 1930s and it served as a naval airfield during World War II. During the 1950s and 1960s, it served as a launch site for rockets supporting nuclear tests, notably serving as a key base for Operations Hardtack I and Hardtack II and Operation Fishbowl, all of which tested atomic weapons in the relative vicinity of the island. Between 1958 and 1975, various scientific rockets were also launched from the island. Until 2003, the site was used for the storage of chemical weapons.
A mushroom cloud rises from a nuclear test during Operation Hardtack I in 1958 Source: National Nuclear Security Administration
Environmental Impact Statement Required
Before proceeding with construction, the department must conduct an environmental assessment. This evaluation will examine the potential effects of the landing pads on essential fish habitats, migratory birds, and other protected species. Johnston Atoll is part of the Pacific Islands Heritage Marine National Monument, which adds further environmental considerations to the project.
The Air Force, which includes the Space Force, expects minimal environmental impact from the construction and operation of the landing pads. A draft environmental assessment may be available in April, allowing for a 30-day public comment period.
Photos of the aftermath of atomic testing at Johnston Atoll
You must be logged in to post a comment.