Connect with us

News

SpaceX’s Starship Mk1 prototype heads to the launch pad – but why?

On October 30th, SpaceX installed half of Starship Mk1 on a new launch mount constructed at its Boca Chica launch pad. (NASASpaceflight - bocachicagal)

Published

on

SpaceX has transported (half of) its Starship Mk1 prototype to its South Texas launch pad for the first time ever, signifying that the company is about to enter a major new stage of testing.

The move, however, raises the question: why is SpaceX transporting only half of Starship Mk1 to the launch pad?

Following SpaceX CEO Elon Musk’s September 28th presentation on Starship, the spacecraft prototype was partially disassembled, having essentially been mocked up to stand as a backdrop at the event. The impact was fairly minor, taking up no more than a few days of work, but Starship Mk1 remains in two large, separate pieces – a curved nose section and the ship’s cylindrical propellant tank and propulsion section.

Starship Mk1’s nose and tail sections were separated on October 1st. (NASASpaceflight – bocachicagal)

A little over a month after Musk’s presentation, SpaceX technicians freed Starship Mk1’s lower tank section from a steel mount and temporarily installed the giant half-spacecraft on framework mounted to a Roll Lift transporter. SpaceX has consistently relied on Roll Lifts for the task of transporting Starship’s massive segments both around and between its Boca Chica, Texas build and launch facilities. This time around, only Starship Mk1’s lower half was loaded onto the transporter before being staged overnight near the main gate of SpaceX’s build site.

Although work continued throughout the night, around dawn on October 30th, transport activity restarted in earnest, with technicians preparing to move Starship. A road closure filed with Cameron County suggested that something would occur on the 30th, with followers speculating that Starship Mk1 would be transported to SpaceX’s South Texas launch pad. As it turned out, that speculation was correct, and (half of) Starship Mk1 was indeed moved to the launch pad and installed atop a new launch mount that was built from scratch in just a few months.

(Half a) Starship on the pad

While it’s undeniably thrilling to see Starship Mk1 head to SpaceX’s Boca Chica launch pad for the first time ever, it remains to be seen why exactly only half of the rocket was transported – no mean feat. Although a great deal of progress has been made over the last month outfitting Starship Mk1 with all the wiring, electronics, plumbing, and other subsystems the prototype will need to function, it’s plainly visible that a significant amount of work remains before Starship will be ready for integrated testing.

Advertisement
A panorama of Starship Mk1’s business end and tank section. Recent work has focused on outfitting Mk1 with an array of wiring and piping, some of which is visible here. (NASASpaceflight – bocachicagal)
SpaceX has made a huge amount of progress on Starship’s new launch mount over the last 1-2 months, but plenty of work clearly remains before it will be ready for full-scale operations. (NASASpaceflight – bocachicagal)

Most notably, as pictured above, the launch mount frame is certainly more or less complete, but most of the complex plumbing, wiring, and power equipment it will need to serve its function is not obviously present. There is admittedly a possibility that SpaceX will reuse the ‘quick disconnect’ umbilical ports used by Starhopper on Starship Mk1, but that remains to be seen.

Starship Mk1 itself has a ways to go before it will be ready for integrated testing. Near the orange plastic is what is believed to be a large propellant feed line, needed to fuel Starship. Those lines have yet to be closed off. (NASASpaceflight – bocachicagal)

Additionally, Starship Mk1 also has some level of work left before it will be ready for its first propellant loading test, let alone flight. Aside from a large amount of wiring and avionics that still needs to be partially run, harnessed, and connected, Starship’s main liquid oxygen and methane feedlines – needed to fuel the rocket – are largely complete but still unfinished.

There are at least a few obvious possible explanations for SpaceX moving the Starship Mk1 tank section to the launch pad in its partially-finished state. The easiest explanation is that SpaceX wants to perform leak and pressure tests of Starship’s tanks as early as possible, even if that involves testing the rocket without its nose (the host of Mk1’s batteries, power controllers, COPVs, pressurization tanks, and more). It’s not clear that Starship Mk1 is – at present – capable of performing a wet dress rehearsal (WDR), a common aerospace test where a rocket is fully fueled and counts down to launch without actually igniting.

Starhopper performed several wet dress rehearsal tests before its final 150m flight test in August 2019. (LabPadre, 07/14/19)

Instead, SpaceX could potentially perform a pressure (or at least leak) test with a neutral gas (or perhaps liquid nitrogen) just to verify that Starship Mk1 is structurally sound before kicking off cryogenic propellant loading. Additionally, it’s possible that SpaceX could get around Mk1’s incomplete propellant feed lines by attaching pad umbilicals directly to the ends of the incomplete feed lines.

At the same time, it’s possible that SpaceX has decided to finish assembling Starship at the launch pad itself, hinted at when a local photographer captured a number of Mk1’s control surfaces and aero covers being moved around shortly after Starship was moved to the pad. Time will tell. For the time being, SpaceX has no more road closures scheduled (meaning no nose section transport) until November 7th and 8th, followed by another on the 12th.

Stay tuned to find out what transpires!

Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.

Advertisement

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