Connect with us

News

SpaceX’s next Starhopper flight needs more analysis for FAA go-ahead, says Elon Musk

Starhopper prepares for a Raptor preignition test on July 15th. (NASASpaceflight - bocachicagal)

Published

on

According to SpaceX CEO Elon Musk, the company’s next major Starhopper flight test is still awaiting FAA approval due to a need for more hazard analysis, presumably required because Starhopper will be traveling much higher than before.

On August 9th, SpaceX completed a routine wet dress rehearsal (WDR) with Starhopper, loading the vehicle with propellant and fluids and replicating a launch countdown up to the point of Raptor ignition. Starhopper remains untethered in a sign that SpaceX doesn’t have plans for a static fire test before the low-fidelity rocket prototype’s next flight milestone. Originally scheduled for August 12th, that milestone – a 200m (650 ft) hop test – has been indefinitely delayed as SpaceX awaits an updated permit from the Federal Aviation Administration (FAA).

The oddity of the apparent difficulty SpaceX is having with the FAA’s experimental permit process is deepened by the fact that Starhopper is already permitted by the FAA and demonstrated its first successful flight just a few weeks ago, on July 25th. On top of the fact that the local Boca Chica and Brownsville, Texas airspace tends to be extremely quiet, it’s unclear what exactly is holding up SpaceX, the FAA, or both in what should otherwise be a relatively streamlined process.

Starhopper stands at SpaceX’s Boca Chica test facilities on August 1st, 2019. (NASASpaceflight – bocachicagal)

A few weeks ago, after one false start on July 24th, Starhopper performed its first untethered flight ever on July 25th, successfully demonstrating its integrated steel propellant tanks, avionics, software, and Raptor propulsion over the course of 20 or so seconds of flight. Starhopper’s inaugural flight was delayed at least several weeks by a major bug with SpaceX’s next-gen Raptor engine, described by Elon Musk as a problem with a certain frequency of vibration (i.e. mechanical resonance).

According to Musk, said resonance failure mode was effectively solved with unspecified modifications made to the sixth Raptor engine produce (Raptor SN06). That engine became the first to successfully pass SpaceX’s regime of pre-hop static fires in McGregor, Texas around July 10th and was shipped south to Boca Chica and installed on Starhopper scarcely 24 hours later.

Assuming those vibration issues have been completely quashed, Musk has also stated that SpaceX is aiming to produce as many as two Raptor engines per day by the end of 2019. It’s believed that all engines preceding SN06 (SN01-05) were either damaged or destroyed during testing, be that a result of intentional testing-to-destruction or anomalous behavior during certain test regimes. It should be noted that full-scale Raptor is still undoubtedly in development and hardware failure during developmental testing is more predictable and valuable than it might seem. As long as the program can handle it, ‘hardware-rich’ development (i.e. moving fast and breaking things) can be equally – if not more – valuable than an extremely cautious get-it-right-the-first-time approach.

Regardless, once SpaceX’s propulsion engineering team is confident that the more major bugs that plagued early Raptor engines have been alleviated, they will likely give the go-ahead for the engine manufacturing team to begin ramping production rates. Musk believes that SpaceX could be ready for the first test flights of either or both of the company’s orbital Mk1 and Mk1 Starship prototypes as early as mid-September, milestones that will eventually require three sea-level Raptor engines and up to three vacuum Raptor engines per rocket.

Meanwhile, although SpaceX has yet to begin assembling the first Super Heavy booster(s), said boosters will require dozens of Raptor engines each for their first flights. Musk says that SpaceX will start out with something like 20 Raptor engines per booster to minimize losses and disruption in the event of a catastrophic failure, eventually expanding to as many as 35 engines per booster as confidence grows.

For now, Starhopper’s next flight test was scheduled from August 16th through the 18th but has since been tentatively rescheduled to Aug. 19-21. Starhopper will remain grounded until the FAA is satisfied with SpaceX’s updated hazard analyses for the rocket’s 200m flight test.

Advertisement

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

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