News
Report: SpaceX to launch at least five back-to-back Crew Dragon missions for NASA
Update: Wasting no time at all, NASA has confirmed the Ars Technica report one day later, announcing that rookie astronauts Nicole Mann and Josh Cassada have been reassigned from Boeing Starliner missions to SpaceX’s Crew-5 Crew Dragon launch – currently no earlier than August 2022.
Ars Technica’s Eric Berger reports that NASA has begun the process of moving a number of astronauts assigned to Boeing’s ailing Starliner spacecraft to a SpaceX Crew Dragon mission scheduled no earlier than August 2022.
Per sources close to Berger, NASA has chosen to reassign two rookie astronauts to Crew Dragon as hopes of a crewed Starliner launch – and thus an opportunity for them to gain hands-on spaceflight experience – in the next 6-12 months continue to wither. Barring surprises, the implied change of plans behind those actions means that SpaceX now appears to be scheduled to fly five operational NASA Crew Dragon missions back to back before Boeing’s Starliner flies a single astronaut – let alone its first operational mission with four crew aboard.
In December 2019, nine months after Crew Dragon’s own uncrewed March 2019 debut, Starliner lifted off for the first time on a ULA Atlas V rocket. However, whereas Crew Dragon performed a practically flawless orbital launch, space station rendezvous, docking, departure, reentry, and splashdown on its first try, Starliner’s Orbital Flight Test (OFT) went horribly wrong as soon as it separated from Atlas V.
Due to shoddy prelaunch testing that failed to detect several gaping holes in Starliner’s software, the spacecraft effectively lost control as soon as it was under its own power. Aside from making ground communication and control far harder, Starliner burned through most of its propellant and pushed most of its maneuvering thrusters past their design limits in the first hour or two after launch. Due to the catastrophic software failure and lack of propellant margins, NASA unsurprisingly called off a planned space station rendezvous and docking attempt and Boeing ultimately ordered Starliner to reenter a few days after launch.
Mere hours before reentry, Boeing apparently detected and fixed another major software error at the last second, potentially preventing Starliner’s propulsion and service module from smashing into the capsule’s fragile heat shield and dooming the spacecraft to burn up during reentry. Ultimately, it’s likely that the only reason Boeing didn’t suffer a total loss of vehicle (LOV) during Starliner’s OFT debut spacecraft was dumb luck. Had the initial clock error been worse, Starliner could have failed to reach orbit entirely or burned through all of its propellant, resulting in an uncontrolled reentry. Had there been no clock issue, it’s hard to imagine that Boeing’s software team would have attempted the panicked, impromptu bug hunt that detected and fixed the service module recontact issue.
Now, 22 months after Starliner’s catastrophic OFT, Boeing has been forced to stand down from a second self-funded orbital flight test (OFT-2) due to the last-second discovery of more than a dozen malfunctioning valves on the second spacecraft’s service module. Aside from raising the question of how Boeing and NASA yet again failed to detect a glaring Starliner issue until the day of launch, Starliner’s valve issues appear likely to cause another multi-month delay as Boeing is forced to investigate the problem, find the root cause, and implement a fix on all impacted service modules.
NASA reassigning some of the astronauts scheduled to helm Starliner on its Crewed Flight Test (CFT) and first operational mission to Crew Dragon’s August 2022 Crew-5 launch seemingly implies that the space agency is not confident that Boeing will have completed Starliner OFT-2, passed extensive post-flight reviews, and readied another Starliner for CFT by Q3 2022. Given that NASA took some 14 months to OK Crew Dragon’s Demo-2 crewed flight test after Demo-1’s March 2019 success and a catastrophic April 2019 failure during a ground test of the recovered capsule, it’s not unreasonable to assume that NASA will take about a year after OFT-2 to approve Starliner’s first crewed flight test.
If significant issues arise during OFT-2, which is now unlikely to occur before early 2022, a year-long gap is even more likely. Ultimately, that means that there is now a significant chance that SpaceX’s Crew Dragon spacecraft will complete not just five – but six – back-to-back operational NASA astronaut launches before Starliner is ready for its first operational ferry mission. SpaceX, in other words, is now expected to singlehandedly hold the line and ensure biannual NASA access to and from the International Space Station (ISS) for more than two years despite charging NASA $2 billion less than Boeing (~$5B vs ~$3B) to develop Crew Dragon.
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
