News
SpaceX preps Starship, Super Heavy for another week of Raptor testing
SpaceX continues to work around the clock to prepare its latest Starship and Super Heavy booster prototypes for another week of testing – likely focused on firing up the Raptor engines installed on each vehicle.
Known as Booster 7 and Ship 24, SpaceX has been slowly testing both prototypes for approximately four months, beginning in April and May, respectively. Only in early August did the company cautiously begin attempting to ignite their Raptor engines as part of a process known as static fire testing – by far the most difficult and important part of qualifying both vehicles for flight.
Thanks to progress made in 2021, SpaceX already has significant experience testing an earlier orbital-class Starship prototype on the ground, but the process of testing Ship 24 is still fresh and unfamiliar for a number of reasons. For Booster 7, the challenges are even greater.
On top of major design changes made to Starship and Super Heavy over the last year as SpaceX continues to refine the rocket, the company also developed a substantially different version of its Raptor engine. Compared to Raptor V1, Raptor V2 almost looks like a new engine and can produce around 25% more thrust (230 tons versus 185 tons). SpaceX has also tweaked how the engine operates, particularly around startup and shutdown, further weakening the value of past experience testing Raptor V1 and V1.5 engines on Ship 20 and Boosters 3 and 4.
In other words, with Ship 24 and Booster 7 engine testing, it’s possible that SpaceX is effectively starting from scratch. Many aspects of testing – propellant conditioning, thermal characteristics, tanking, detanking, certain test stands – are likely mostly unchanged, but almost every aspect of a rocket is affected by its engines.
Before SpaceX began testing Raptor V2 engines on Starship and booster prototypes, it wasn’t clear if the changes between V1.5 and V2 would invalidate a lot of prior testing. After the start of Booster 7 and Ship 24 static fire testing, it’s now clear that a lot of that earlier work has to be redone. It’s also clear that despite some of the simplifications in Raptor V2’s design, operating the engine on Starship and Super Heavy is much harder get get right.
Since mid-July, SpaceX has completed around 15-20 ‘spin-prime’ tests between Ship 24 and Booster 7 – more of that kind of test than any other prototype in the history of Starbase has performed. Spin-prime tests flow high-pressure gas through Raptor’s pumps to spin them up without igniting anything. It’s unclear why so many of those tests are being done, what SpaceX is gaining from it, or why the company appears to have completely stopped conducting preburner tests (a more life-like spin-prime with partial combustion).
Regardless, eight weeks after the start of engine testing, Booster 7 has only performed three static fires (two with one engine, one with a max of three or four engines), and Ship 24 has only completed one static fire with two engines. Before either vehicle can be considered ready for flight, a day that could easily never come, each will likely need to conduct multiple successful static fires with all of their Raptor engines (6 on S24 and 33 on B7).
If the pace of Booster 7 testing doesn’t change, the vehicle could be months away from a full 33-engine static fire attempt – perhaps the single most important and uncertain test standing between SpaceX and Starship’s first orbital launch attempt. Ship 24’s path to flight readiness should be simpler, but it appears to be struggling almost as much.
According to CEO Elon Musk, “an intense effort is underway” to ensure that Super Heavy B7’s Raptor engines are well contained during anomalies, so that one engine violently failing won’t damage or destroy the booster, other engines, or the launch pad. That could certainly complicate the process of testing Booster 7, and it’s likely that SpaceX is taking some of the same actions to protect Ship 24.
In early September, after a partially successful Booster 7 static fire (its first multi-engine test) and numerous additional Ship 24 tests that failed to achieve ignition, SpaceX replaced engines on both vehicles. Booster 7 had one of 13 Raptor Center engines swapped out, while Ship 24 had one of its three Raptor Vacuum engines replaced.
On September 5th, SpaceX distributed a safety alert to Boca Chica’s few remaining residents, confirming that it wants to restart testing as early as Tuesday, September 6th. Especially as of late, that alert guarantees nothing, but it does at least open the door for SpaceX if Ship 24, Booster 7, and the positions of the stars happen to be in the right mood between 8am and 8pm CDT. Additional opportunities are available on September 7th, 8th, 9th, and 12th.
Tesla has introduced an enhanced visualization in its Supercharger navigation system, building directly on the Site Maps feature rolled out a few months ago.
This latest software update adds detailed 3D icons that represent specific vehicle models parked at charging stalls, offering drivers a more precise view of site occupancy and layout.
The Site Maps debuted in Tesla’s 2025 Holiday Update, providing 3D overviews of select Supercharger locations with real-time stall availability.
Tesla supplements Holiday Update by sneaking in new Full Self-Driving version
Drivers could see which spots were open, occupied, or out of service when navigating to supported stations.
Now, the system takes this capability further by rendering accurate representations of Tesla vehicles, including distinctions between models such as the Model 3, Model Y, Model S, Model X, and Cybertruck. These icons appear as lifelike 3D renderings, complete with recognizable shapes and proportions that match the actual cars charging at the site:
Supercharger update now shows type of Tesla at charger as well.
Pretty cool. pic.twitter.com/J3NRSIgM0m
— DennisCW | wen my L (@DennisCW_) June 2, 2026
This refinement improves the user experience during road trips and daily charging stops. As drivers approach a Supercharger, the navigation display now shows not just generic occupied markers but identifiable vehicle types plugged into each stall.
Blue indicators highlight active charging sessions, while other visual cues denote availability or maintenance status. The feature integrates seamlessly with the existing map interface, allowing quick assessment of the best available spot based on vehicle size and positioning.
Tesla continues to expand the availability of these detailed Site Maps across its global network. Initially piloted at a limited number of locations, the rollout has progressed steadily, with more stations gaining support in recent software versions.
Owners benefit from better planning, as the system helps identify compatible stalls and reduces uncertainty upon arrival. The update reflects Tesla’s ongoing commitment to refining its navigation and charging ecosystem through iterative software improvements.
In addition to model-specific icons, the enhanced maps maintain all prior functionalities, such as integration with nearby amenities and energy usage predictions. This ensures a comprehensive tool for efficient Supercharging.
As Tesla’s fleet grows and the network scales, such features play a key role in optimizing the overall ownership experience. Future updates may extend similar visualizations to additional sites and incorporate even more data points for drivers.
With this piggyback enhancement, Tesla demonstrates how small but thoughtful additions can elevate an already useful tool, making Supercharger visits smoother and more informed for its customers. The company is expected to broaden the feature’s reach in upcoming releases, further solidifying its leadership in EV charging infrastructure.
Tesla Full Self-Driving v14.3.3 driver monitoring was reportedly scaled back in recent releases, but a new version that was released in the early hours of June 3 aimed to do a better job of keeping those in control of their cars honest, according to release notes.
The release notes for FSD v14.3.3, via Software Version 2026.14.6.7 added:
“Improved driver monitoring system sensitivity with better eye gaze tracking, eye wear handling, and higher accuracy in variable lighting conditions.”
However, Tesla said this was already enabled in the first rollout of FSD v14.3.3 in late May. We tested it anyway, especially as the Standard Speed Profile seemed less-than-worried about what you were doing during operation.
I decided to try out the Hurry and Mad Max Speed Profiles for this test, and it gave me results that I would have expected. Tesla has evidently ramped up driver monitoring based on the Speed Profile you are using to travel.
The more aggressive the Speed Profile, the more on the hook you will be for taking your attention away from the road. Our testing showed that Mad Max was less likely to allow you to do normal things like change music or adjust navigation without getting an on-screen warning or nag from the driver monitoring system.
Hurry Mode Results
On Hurry, the driver monitoring system on FSD v14.3.3, via Software Version 2026.14.6.7, was more restrictive than Standard but less restrictive than Mad Max. I found that I could scroll through music options for a considerable amount of time, more than 30 seconds:
Roughly :31 between first touching the center screen and getting the first nag
— TESLARATI (@Teslarati) June 3, 2026
Standard gave me about 80 seconds of phone scrolling with absolutely no nags or warnings in a previous test. It is worth noting that this was a previous branch of v14.3.3, but Standard is such a goodie-two-shoes on the road that it is my impression it would not change much.
Here’s an 80-second phone nag test on Tesla FSD v14.3.3.
No alerts, no nagging, no annoyance. https://t.co/1dxvTOw5Cn pic.twitter.com/vYViFpjfoK— TESLARATI (@Teslarati) May 29, 2026
Mad Max Results
I spent the majority of the drive on Mad Max to see how it truly reacted to the driver having their attention elsewhere. While I did do a short phone test, I am aiming to steer away from those and use the center screen. I think it is a valid criticism that the phone test is dangerous and, not to mention, illegal in Pennsylvania. Changing the navigation and music is a more reasonable, more responsible, and safer test.
With Mad Max being the fastest and most aggressive Speed Profile, I anticipated this being the quickest mode to give me an alert that I needed to look at the road. That was the case with music:
🎥 Testing Tesla FSD v14.3.3 (via 2026.14.6.7) nags on Mad Max https://t.co/qZALU2OujY pic.twitter.com/XddOJ0D47x
— TESLARATI (@Teslarati) June 3, 2026
As well as adjusting Navigation, when I received two nags:
🎥 Testing Tesla FSD v14.3.3 (via 2026.14.6.7) nag while adjusting navigation
Two nags here https://t.co/qZALU2OujY pic.twitter.com/xa3dtaDG1L— TESLARATI (@Teslarati) June 3, 2026
These nags were more than reasonable, and I think it’s probably good that Tesla is ramping up the driver monitoring. I do believe that it should be relatively strict across all of the Speed Profiles, especially with phone use. When using the center screen, the nag intervals should be based on the speed profile you are utilizing at the time.
These driver monitoring adjustments are a great thing to have while FSD is still under its “Supervised” moniker, but I expect Tesla to continue pushing the limits on what it will allow, especially considering CEO Elon Musk has hinted that phone use is capable with the more recent versions.
You can watch the full drive on YouTube below:
Tesla has responded to the skeptics of its Robotaxi program by launching a massive expansion of the unsupervised program in its initial rollout city of Austin.
The company’s geofence, the enabled area of operation for rides, now covers the entire Austin Metropolitan area, an incredible move just days after media headlines attempted to discredit the ride-hailing service.
Those who have access to the Tesla Robotaxi app on their smartphones can now request a ride in any portion of the Austin Metro area. The company confirmed this on the social media platform X:
Unsupervised Robotaxi now in the entire Austin Metro area https://t.co/eXNBdarvVS
— Tesla Robotaxi (@robotaxi) June 3, 2026
This is Tesla’s fifth expansion of the geofence, with the others occurring in July, early August, late August, and late October 2025. It has remained at that size since October 26, but Tesla has now more than doubled that size.
It is now covering the entire area, including suburbs like Pflugerville and Manor, as well as I-35 highways, Gigafactory Texas, and the Austin-Bergstrom Airport.
The move comes just days after various media outlets highlighted the small fleet size of Tesla’s Robotaxi fleet in Austin, something that is a reasonable criticism but an understandable move on the company’s part to prioritize safety.
Tesla has expanded its Robotaxi geofence many times, but its fleet has remained at a relatively conservative size as the company continues to push safety as its most crucial metric.
The latest expansion is a key indicator of Tesla’s comfort level to expand the ride-hailing service. The move shows Tesla is scaling unsupervised autonomy, as it demonstrates that the company’s Full Self-Driving system has reached sufficient reliability for a broader real-world deployment, which is something the company has worked on extensively.
It also shows Tesla is game for a competition with its rivals in the autonomous ride-hailing sector. Tesla has often matched or exceeded competitors like Waymo in coverage area, despite its smaller fleet. This step highlights Tesla’s iterative, data-driven progress toward a high-margin, app-based Robotaxi network.
It’s not the absolute largest area expansion ever, but achieving full unsupervised operations across a major metro is a key moment in the Robotaxi story. It shifts the program from limited pilot/testing toward a more mature commercial service, while gathering the miles needed for faster growth.
Tesla piggybacks recent Supercharger feature with update that takes it further
Tesla Full Self-Driving v14.3.3 driver monitoring: We tested it
