Connect with us

News

SpaceX’s high-altitude Starship launch debut unlikely before Crew-1

Starship SN8 completed a cryogenic proof of a small propellant tank located in the tip of its nose. Up next, a second static fire. (NASASpaceflight - bocachicagal)

Published

on

Update: SpaceX canceled its November 5th and 6th Starship SN8 static fire test windows on Thursday, delaying the next Starship test window to November 9th unless additional testing is scheduled on the 7th and 8th.

As previously discussed, SpaceX requested three road closures for “Starship SN8 Static Fire and 15KM Flight” attempts on November 9th, 10th, and 11th on Wednesday. With recent cancellations, NASASpaceflight reporter Michael Baylor says that the odds that Starship SN8 will be ready to fly before SpaceX’s Crew-1 operational NASA astronaut launch debut (NET November 14th) are now minuscule, further indicating that each of the three upcoming test windows will be dedicated to one or more Raptor static fires.

Stay tuned for updates as SpaceX continues to prepare Starship for its most ambitious, challenging, and risky test yet.


In the form of road closure filings, SpaceX has effectively announced the first possible dates for Starship’s high-altitude launch debut, a high-risk test that CEO Elon Musk recently made clear could fail.

Per road closures published on SpaceX’s dedicated Cameron County, Texas page, Starship serial number 8 (SN8) could apparently be ready for its historic launch debut as soon as November 9th in a 12-hour window that opens at 9am CST (15:00 UTC). Identical 9am-9pm windows on November 10th and 11th will serve as backups in the event of one or several launch aborts or delays – fairly likely for a prototype as complex as Starship SN8.

Advertisement

However, several tests stand between SN8 and flight-readiness, further increasing the odds of delays as SpaceX continues to work out the kinks in what amounts to the first fully-assembly, functional Starship.

Musk has already stated that Starship SN8 will need to complete another Raptor static fire test – potentially with one, two, or three engines – before SpaceX will consider the rocket ready for its flight debut. Over the last few days, NASASpaceflight.com reporter Michael Baylor has noted on livestreams that multiple more static fire tests are actually in order before SpaceX will attempt to launch Starship SN8. It’s currently unclear what the purpose of those additional static fire tests is, given that SN8 has already completed a triple-engine Raptor static fire.

In the two weeks since that milestone, however, SpaceX did take a major step forward, mating Starship SN8’s nose section to create what is effectively the first full-scale, functional prototype. Aside from two smaller forward flaps and attitude control system (ACS) cold gas thrusters, that nose section also contains a small secondary liquid oxygen tank known as a header tank – meant to store a small amount of highly pressurized propellant to be used during Raptor reentry and landing burns. Several months back, Musk revealed that Starship SN4 completed a static fire while only feeding on fuel (liquid methane) stored in the rocket’s methane header tank, making it reasonable to assume that SpaceX wants to repeat a similar test with SN8 while using both fuel and oxidizer header tanks.

For Starship SN8, those header tanks will be an irreplaceable necessity during the rocket’s first attempted launch, free-fall, flip maneuver, and landing. In a clear sign of preparation for a header-tank-only static fire test, SpaceX appeared to successfully complete a cryogenic proof of Starship SN8’s newly-installed nose section and nose (LOx) header tank on November 3rd, verifying that liquid nitrogen – standing in for LOx – can be pumped more than 50 meters (~165 ft) from Starship’s launch mount to the tip of its nose to load said tank.

Advertisement
Starship SN8 awaits its launch debut, November 3rd, 2020. (NASASpaceflight – bocachicagal)

SpaceX has one more “SN8 nose cone cryo proof” test window scheduled from 8am to 5pm CST Thursday, November 5th that could be used for one or more of those expected static fire tests. Otherwise, SpaceX’s Starship SN18 15 km (~50,000 ft) launch closures were technically filed for an “SN8 Static Fire and 15 KM Flight,” allowing SpaceX to perform one or several static fires before attempting to launch. All things considered, the odds that Starship SN8 will launch on time between November 9th and 11th are probably less than 50:50, but there is definitely a chance.

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