Connect with us

News

SpaceX rapidly constructing Starship’s first Florida launch pad and tower

SpaceX is rapidly building Starship's first Florida launch pad and launch tower. (SpaceX)

Published

on

After restarting work on the project a few months ago, SpaceX appears to have gotten back up to speed and begun to make rapid progress on the construction of Starship’s first Florida launch pad and tower.

Located at NASA’s Kennedy Space Center (KSC) Launch Complex 39A facilities, SpaceX has intended to construct a Starship launch site there for several years. A serious attempt was made in late 2019 but SpaceX soon abandoned the effort and redirected its energy towards Starship prototyping and a much different launch pad design. Two years later, SpaceX’s second attempt shares only a little in common with the first. Both are to be located within the eastern half of Pad 39A’s shield-like footprint, although the specific location of the tower and launch mount has been modified. If this attempt comes to fruition, Starship’s first East Coast launch facilities will still sit just a few hundred feet away from the only SpaceX pad capable of launching Crew Dragon, Cargo Dragon, or Falcon Heavy.

Beyond those two characteristics, SpaceX’s second attempt is almost entirely different.

Instead of continuing with an older launch pad design, Starship’s 39A facilities will likely be close to a direct copy of Starbase’s first orbital launch site (OLS), which SpaceX began constructing in earnest in late 2020. It’s safe to assume that some lessons have been learned from Starbase OLS construction and that some modifications will be made to the Florida pad’s design, but no obvious changes are thus far visible.

Advertisement

Most of the visible work SpaceX has done this year centers around the company’s KSC-based Roberts Road facilities, where it has built a major Falcon processing facility and a staging yard for Starship pad construction and broken ground on a massive East Coast Starship factory. At that staging yard, SpaceX began assembling prefabricated sections of Starship’s Pad 39A ‘launch tower’ around March 10th after tower parts began arriving at KSC sometime in February. Within two weeks, SpaceX had completed the basic structure of two tower sections. Another two more weeks after that, around April 11th, a third section had reached a similar level of completion and SpaceX had begun assembling a fourth.

Starbase’s launch tower assembly was carefully tracked by fans like Twitter user @Furqan263, offering an invaluable benchmark for future Starship tower work.

Compared to SpaceX’s Starbase tower assembly, Florida Starship work appears to be proceeding at a similar pace. SpaceX began assembling the fourth Florida tower section about 30 days after starting the first, while Starbase took about 25 days to reach the same point. However, SpaceX does appear to be taking a slightly different approach for Pad 39A. On top of tower section assembly, SpaceX is constructing an extra four sets of the small concrete foundations and steel frames each tower section is assembled on, implying that Starship’s Florida launch tower could be almost entirely prefabricated before SpaceX begins to combine those sections.

That differs from Starbase, where SpaceX rarely constructed more than two or three tower sections at a time before removing and stacking each completed section and beginning to assemble the next on the same foundation and jig. However, while undeniably efficient, SpaceX workers then had to spend months outfitting the tower with plumbing, wiring, additional structure, and more. It’s likely that SpaceX has concluded that it’s better to do as much of that work as possible before the tower is assembled, in which case each Florida section may end up spending more time on the ground. Given the obvious challenges imposed by attempting a major construction project at an active, one-of-a-kind launch pad like LC-39A, it would make even more sense for SpaceX to want to complete as much work as possible before moving Starship pad hardware into the line of fire.

Pad 39A, April 8th. Note the four ‘legs’ of the Starship launch tower’s concrete base. Directly behind it is the foundation for 39A’s Starship launch mount. (SpaceX)
Starbase’s launch mount legs and tower base as of March 2021. (Nomadd – NASASpaceflight)

Nonetheless, work will still have to be done at the pad itself. In recent weeks, SpaceX has made significant progress on the foundations 39A’s Starship launch tower and mount require. The bottom half of the concrete base that each steel tower section will eventually sit on has also progressed rapidly. All told, SpaceX is will on its way to replicating Starbase’s orbital Starship launch site on the East Coast, hopefully ensuring that Starship will be able to begin orbital test flights within the next 6-12 months even if the company’s Starbase environmental review continues to be bogged down by bureaucracy.

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

Advertisement
Comments

News

Tesla faces Full Self-Driving pushback in EU over ‘speeding’

Published

on

Credit: Tesla

A new report from Reuters claims that a transport authority in Sweden is pushing back against the approval of Tesla’s Full Self-Driving suite because it will travel over speed limits.

The report says the Swedish Transport Administration (TRV) recommends the European Union votes against FSD’s approval. TRV believes it should not be approved until Tesla disables FSD’s ability to speed.

TRV sent a letter to the European Union’s Technical Committee on Motor Vehicles (TCMV), which is set to meet on June 30 to discuss the potential approval of the Tesla FSD suite in the country. Tesla, which has received various approvals in Europe over the past two months, has not provided a comment.

Tesla Full Self-Driving gets first-ever European approval

Teslas operating on FSD do travel over the speed limit, depending on the Speed Profile that is chosen. Drivers have the ability to disengage FSD at any point; Tesla specifically states that those supervising the suite are responsible for its actions.

Let’s cut to the chase: humans operating any vehicle speed almost daily in the United States. Realistically, speed limits in the U.S. are more frequently treated as speed minimums. However, other countries are different, and driving behaviors are less aggressive.

TRV believes that “allowing automated systems to systematically exceed legal speed limits…risks undermining both the legal framework and the expected safety benefits of ​vehicle automation,” the report stated. It’s surprising that Tesla has not received this claim from other countries previously.

This could be a good argument to bring Max Speed back, the setting that previously allowed the driver to choose the absolute fastest the car would travel.

This would still put the responsibility of supervision in the hands of the driver. It would allow the driver to choose whether the car would travel over the speed limit or not, acknowledging that they set the speed, and if they get pulled over, there would be no ability to argue it.

However, it does not seem as if this is something Tesla will do, especially considering many U.S. drivers have requested the feature in an effort to eliminate speeding or at least tone it down. The company has not shown any interest in bringing it back.

Tesla has approvals for FSD in Europe in Estonia, Lithuania, Denmark, the Netherlands, and Belgium.

Continue Reading

Elon Musk

Tesla teases greater Grok FSD integration and ‘Banish’ feature ‘in about 3 months’

Published

on

Credit: Tesla

Tesla is going to let you guide Full Self-Driving with Grok in 3 months, CEO Elon Musk confirmed on X.

The response from Musk, which revealed Tesla plans to allow drivers to effectively control the car and its navigation more explicitly using Grok, puts the feature for about September.

A Tesla owner said that Full Self-Driving is great, but owners should be able to “converse with Grok like we can with an Uber driver.” She then used examples like, “Grok, turn right here,” and “Drop us off right here, we’ll walk due to traffic,” and finally,” Drop at entrance first, then park far away.”

Coincidentally, the final piece of dialogue would also mean features like Banish are potentially on the way soon.

Banish is also referred to as “Reverse Summon,” and would enable the car to self-park while dropping occupants off at their destination.

This would be a great way to improve the overall experience while supervising FSD. Navigation is already a major painpoint that many owners complain about. Manual overrides when a maneuver is requested or canceled (like using the turn signal stalk to override a navigation route), do not always work.

The feature could be especially useful in street parking scenarios in a city, where spots are sometimes tough to come by. Many of us who grab dinner in a more populated area will park a street or two over from wherever we’re going, because sometimes you know that’s the best you will get. If a driver using FSD could say, “Hey Grok, turn right here on Queen St. and park in that open spot on the right,” it could save a lot of confusion FSD might have on its own.

Musk teased that a similar feature was “coming” back in February:

Tesla Full Self-Driving set to get an awesome new feature, Elon Musk says

It is certainly surprising that Tesla is doing it at this point. The company’s more recent moves have been more evident of taking control and inputs away from humans and putting them in the AI’s hands more frequently. The biggest example of this was taking away Max Speed in AI4 cars, giving us Speed Profiles, and not having any input on the fastest speed the car will travel.

Of course, giving navigation preferences to Grok is availble already in Teslas, but not at the drop of a hat. Instead, you can suggest a certain route at the beginning of your drive.

Here’s an example of that from December:

Finally, the original post that Musk responded to mentioned a parking preference after dropping off the occupants, which describes the Banish feature that Tesla has teased for years.

We’re not sure if Musk was responding more to the ability to guide the car with Grok, or whether he also was including Banish in the three-month prediction timeframe.

Continue Reading

News

Tesla Cybercab has one important piece that AI4 cars might need for FSD

Published

on

Credit: @tpgoebel | X

A close-up image of a Cybercab engineering vehicle in Peabody, Massachusetts, reveals a compact triangular side repeater camera housing equipped with an integrated washer mechanism.

This seemingly small hardware addition could prove to be one of the most critical components for achieving reliable, unsupervised Full Self-Driving (FSD) — not just for the dedicated Robotaxi but potentially for existing AI4-equipped vehicles as well.

The washer system’s importance cannot be overstated in Tesla’s vision-only autonomy approach. Cameras are the sole sensory input for the neural networks powering FSD, constantly interpreting the environment for safe navigation. In real-world conditions, however, lenses quickly accumulate rain, snow, mud, dust, or road spray.

Many of us Tesla owners, especially those who deal with any sort of winter weather at all, know the all-too-common alert that pops up when cameras are obstructed:

Even brief obstructions can drop perception confidence, trigger safety disengagements, or force the vehicle to pull over, although these are relatively rare. Instead, most of the time, the camera will need a wipe from the owner next time they stop the car.

But unlike human drivers who can manually clear their view, a Robotaxi operating 24/7 without a steering wheel or mirrors must maintain pristine vision autonomously. The Cybercab’s side repeater washer delivers targeted cleaning bursts precisely where needed for merging, lane changes, and blind-spot monitoring — functions that demand uninterrupted visibility from the external cameras:

This hardware directly tackles a known pain point in current FSD deployments. Owners frequently report camera-related alerts during inclement weather, which is understandable, but needs to be solved for a true autonomous experience.

For a production Robotaxi fleet aiming for high utilization and minimal downtime, robust washer systems represent a foundational reliability upgrade; essentially, they’re a must-have. Early sightings suggest the design may extend to rear cameras as well, creating a comprehensive cleaning architecture that keeps the entire vision suite operational in harsh environments.

Without it, even the most advanced neural nets struggle when their “eyes” are compromised.

What Does This Mean for AI4 Cars?

This Cybercab detail raises timely questions for AI4 cars already on the road. While Hardware 4 delivers superior compute and camera resolution compared to earlier versions, production models typically lack dedicated side and rear washers. Tesla has included them on Model Y robotaxis that it is using in the fleet:

Tesla Robotaxi has a highly-requested hardware feature not available on typical Model Ys

As Tesla refines unsupervised FSD for broader release, the gap in environmental resilience becomes evident. Software improvements can help mitigate issues, but they cannot fully replace physical cleaning in heavy rain or muddy conditions. Analysts and owners increasingly speculate that AI4 vehicles may eventually require similar washer retrofits — or a future AI4.5 variant — to match the Cybercab’s all-weather readiness and support the same level of autonomy.

As testing progresses, the Cybercab’s washer mechanism highlights Tesla’s pragmatic focus on real-world robustness. It may well become the hardware piece that determines how quickly and reliably FSD scales from prototypes to everyday vehicles.

Continue Reading