Connect with us

News

SpaceX repairing upgraded Starship prototype after first test

Ship 24 is pictured on May 29th, two days into minor repairs. (NASASpaceflight - bocachicagal)

Published

on

SpaceX workers have been spotted repairing the company’s newest Starship prototype in the days after the rocket’s first partial test.

Starship S24 was transported to SpaceX’s Starbase, Texas orbital launch site (OLS) on May 26th after about two and a half months of assembly, marking the first time SpaceX transported a new Starship prototype to a test stand since August 2021. Less than 24 hours later, after attaching Ship 24 to a new test bay located beside the actual ‘orbital launch mount,’ the Starship prototype came to life and began its first proof test.

Unfortunately, while it’s impossible to judge with certainty without official confirmation, Ship 24 either failed to complete that test or did not make it through unscathed.

Known as an ambient or pneumatic proof test, the main goal is to pressurize a Starship or Super Heavy prototype with nonflammable, ambient-temperature nitrogen gas to ensure that the rocket and all its plumbing are structurally sound and working as expected. A successful test would likely require a prototype to reach and sustain flight pressures – up to 8.5 bar (~125 psi) as of 2020 – without exhibiting any significant leaks or problems.

Advertisement

For a while, Ship 24’s first ambient proof test went about as expected, with lots of small vents from its main liquid oxygen (LOx) and methane (LCH4) tanks. No activity was visible at the ship’s nose, where vents and plumbing attach to a pair of small landing (header) propellant tanks. Ship 24 is the first Starship with an upgraded version of those tanks after SpaceX decided to remove the methane header tank from the main methane tank and relocate it directly under the oxygen header tank, which takes up the tip of Starship’s nose.

After an hour or two of testing, a muffled bursting noise different from previous vents was heard, followed by a quieter ‘whoosh’ more akin to a long vent. At the same time as the loud noise was heard, a good dozen or so of S24’s thousands of heat shield tiles were knocked off the section of the hull between the Starship’s main tanks and nose cone. SpaceX depressurized Ship 24 soon after and within a few hours, workers could be seen extracting a pipe from the ship that appeared to have been bent almost in half.

SpaceX employees were still hard at work repairing Ship 24 two days later. (NASASpaceflight – bocachicagal)

Three days later, workers were spotted guiding apparent replacement pipes into Ship 24. Altogether, it appears that some small section of Ship 24’s internal piping failed catastrophically after it was pressurized during the vehicle’s first pneumatic proof test, knocking tiles loose and possibly damaging other adjacent plumbing. Given the location of that piping inside Ship 24’s nose section, there’s a nonzero chance that the failure occurred when SpaceX attempted to pressurize the Starship’s new header tanks, which would have started by pressurizing the propellant and gas lines leading to them. That would explain the first muffled burst, the subsequent venting sound that slowly faded to nothing, and the loss of heat shield tiles.

It would also explain why SpaceX decided to leave Starship in place and conduct repairs at the pad. Super Heavy Booster 7, which suffered a dramatic plumbing failure during an early proof test, was moved back to one of Starbase’s covered assembly bays for repairs. Had Ship 24’s incident been severe, it would have likely left the pad as well. The fact that Ship 24 did not move indicates that the failure was fairly minor and contained, only impacting some easily-replaceable plumbing.

A pair of workers focus on finishing Ship 24’s lone ‘raceway’ cover. (NASASpaceflight – bocachicagal)

Additionally, SpaceX appears to have moved Raptor heat shield components and a missing cover for one of Ship 24’s four flaps to the pad since the incident. On top of the team that has been working all weekend to repair the Starship, other sets of workers have set about closing out Ship 24’s ‘raceway’, which protects hundreds of feet of smaller plumbing and cables and a flight termination system that runs from the top to the bottom of the ship’s tanks; and some have begun preparing to fill gaps in Ship 24’s heat shield. Most of that work can be classified as ‘finishing touches’ and none of it would be prioritized if Ship 24 was not in decent shape.

Still, even minor damage is a setback. Ship 24’s next opportunity for redemption is a 10am to 10pm CDT window on Wednesday, June 1st, with backup windows available on Thursday and Friday.

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