News
SpaceX uses robot dog to inspect Starship after first engine test in months
SpaceX’s first orbital-class Starship prototype has survived the first of several expected Raptor tests, kicking off an engine test campaign that could mark a number of new milestones.
With just 20 minutes left in a seven-hour test window, Starship prototype S20 (Ship 20) appeared to either unsuccessfully attempt its first Raptor static fire test or complete its first intentional Raptor preburner test around 11:40 pm CDT (UTC-5) on Monday, October 18th. Rather than a violent jolt and roar kicking up a cloud of dust, Ship 20 came to life with a (relatively) gentle fireball that lasted for several seconds.
In pursuit of maximum efficiency, Starship’s Raptors require two separate closed-cycle gas generators known as preburners to – as the name suggests – turn its cryogenic (very cold) liquid oxygen and methane propellant into a hot gas mixture that the engine re-ignites to produce thrust. A preburner test, if that’s what Starship S20 completed on Monday night, thus involves activating only the first half of that equation, rapidly producing a giant cloud of flammable gas without actually igniting to produce meaningful thrust.
Preburner tests have become increasingly rare as SpaceX’s sea-level Raptor design matured over the course of tens of thousands of seconds of ground testing and, later, thousands of seconds of ground and flight testing on Starship prototypes. Starship S20 had two engines during its first test. One Raptor was the sea-level optimized variant SpaceX has built dozens of and fired for 30,000+ seconds on the ground. The other, however, was a vacuum-optimized Raptor with a much larger nozzle – the first of its kind to participate in any kind of test while installed on a Starship prototype.
It’s possible that Raptor Vacuum (RVac) engines have even more design tweaks outside of their larger expansion nozzles. Regardless, SpaceX has only built and tested around 10 RVac prototypes over the last year, making it a less mature engine than its sea-level cousins. That could explain why SpaceX appears to have chosen to perform a preburner test first instead of jumping straight into a wet dress rehearsal and static fire. That also means that October 18th’s test was likely the first time a Raptor Vacuum engine has (partially) ignited while installed on a Starship.
The above view from a uniquely situated LabPadre camera all but guarantees that Starship S20’s first engine test was a Raptor Vacuum preburner test and doesn’t offer any strong evidence that it was a two-engine test. Ship 20 still has a number of crucial tests ahead of it before SpaceX can even begin to consider it (or its general design) qualified for flight. That includes multiple static fires, including the first side-by-side static fire of two Raptor variants (RVac and Raptor Center), the first simultaneous static fire of more than three engines, and the first Starship static fire with a full six engines installed.
Ship 20’s preburner test is SpaceX’s first Starbase Raptor test since the first Super Heavy booster static fire in mid-July, almost exactly three months ago.
With any luck, S20’s first preburner test has opened the door for an inaugural static fire of one or both installed engines later this week. However, during that preburner test, the giant fireball Raptor Vacuum emitted appeared to ignite several pieces of pad hardware. SpaceX took advantage of one of at least two Boston Dynamics Spot robots on-site to physically walk a camera up to the active pad and inspect several secondary fires. Ultimately, SpaceX appears to have successfully safed Starship with no damage to the vehicle itself, but odds are good that the sources of those secondary fires will need to be fixed and any pad damage repaired before Ship 20 proceeds into static fire testing. SpaceX has two more 5pm-12am test windows scheduled on October 19th and 20th.
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
