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.
News
Tesla lands approval for Robotaxi operation in third U.S. state
On Tuesday, Tesla officially received regulatory approval from the State of Arizona, making it the third state for the company to receive approval in.
Tesla has officially landed approval to operate its Robotaxi ride-hailing service in its third U.S. state, as it has landed a regulatory green light from the State of Arizona’s Department of Transportation.
Tesla has been working to expand to new U.S. states after launching in Texas and California earlier this year. Recently, it said it was hoping to land in Nevada, Arizona, and Florida, expanding to five new cities in those three states.
On Tuesday, Tesla officially received regulatory approval from the State of Arizona, making it the third state for the company to receive approval in:
BREAKING: Tesla has officially received approval from the Arizona Department of Transportation to launch its Robotaxi service on public roads in the state!
I just confirmed directly with the Arizona DOT that @Tesla applied for a Transportation Network Company permit on Nov 13th.… pic.twitter.com/iKbwfGfiju
— Sawyer Merritt (@SawyerMerritt) November 18, 2025
Tesla has also been working on approvals in Nevada and Florida, and it has also had Robotaxi test mules spotted in Pennsylvania.
The interesting thing about the Arizona approval is the fact that Tesla has not received an approval for any specific city; it appears that it can operate statewide. However, early on, Tesla will likely confine its operation to just one or two cities to keep things safe and controlled.
Over the past few months, Robotaxi mules have been spotted in portions of Phoenix and surrounding cities, such as Scottsdale, as the company has been attempting to cross off all the regulatory Ts that it is confronted with as it attempts to expand the ride-hailing service.
It appears the company will be operating it similarly to how it does in Texas, which differs from its California program. In Austin, there is no Safety Monitor in the driver’s seat, unless the route requires freeway travel. In California, there is always a Safety Monitor in the driver’s seat. However, this is unconfirmed.
Earlier today, Tesla enabled its Robotaxi app to be utilized for ride-hailing for anyone using the iOS platform.
News
Tesla ride-hailing Safety Monitor dozes off during Bay Area ride
We won’t try to blame the camera person for the incident, because it clearly is not their fault. But it seems somewhat interesting that they did not try to wake the driver up and potentially contact Tesla immediately to alert them of the situation.
A Tesla Robotaxi Safety Monitor appeared to doze off during a ride in the California Bay Area, almost ironically proving the need for autonomous vehicles.
The instance was captured on camera and posted to Reddit in the r/sanfrancisco subreddit by u/ohmichael. They wrote that they have used Tesla’s ride-hailing service in the Bay Area in the past and had pleasant experiences.
However, this one was slightly different. They wrote:
“I took a Tesla Robotaxi in SF just over a week ago. I have used the service a few times before and it has always been great. I actually felt safer than in a regular rideshare.
This time was different. The safety driver literally fell asleep at least three times during the ride. Each time the car’s pay attention safety alert went off and the beeping is what woke him back up.
I reported it through the app to the Robotaxi support team and told them I had videos, but I never got a response.
I held off on posting anything because I wanted to give Tesla a chance to respond privately. It has been more than a week now and this feels like a serious issue for other riders too.
Has anyone else seen this happen?”
My Tesla Robotaxi “safety” driver fell asleep
byu/ohmichael insanfrancisco
The driver eventually woke up after prompts from the vehicle, but it is pretty alarming to see someone like this while they’re ultimately responsible for what happens with the ride.
We won’t try to blame the camera person for the incident, because it clearly is not their fault. But it seems somewhat interesting that they did not try to wake the driver up and potentially contact Tesla immediately to alert them of the situation.
They should have probably left the vehicle immediately.
Tesla’s ride-hailing service in the Bay Area differs from the one that is currently active in Austin, Texas, due to local regulations. In Austin, there is no Safety Monitor in the driver’s seat unless the route requires the highway.
Tesla plans to remove the Safety Monitors in Austin by the end of the year.
Tesla has officially opened Robotaxi access to everyone and everyone, but there is one catch: you have to have an iPhone.
Tesla’s Robotaxi service in Austin and its ride-hailing service in the Bay Area were both officially launched to the public today, giving anyone using the iOS platform the ability to simply download the app and utilize it for a ride in either of those locations.
It has been in operation for several months: it launched in Austin in late June and in the Bay Area about a month later. In Austin, there is nobody in the driver’s seat unless the route takes you on the freeway.
In the Bay Area, there is someone in the driver’s seat at all times.
The platform was initially launched to those who were specifically invited to Austin to try it out.
Tesla confirms Robotaxi is heading to five new cities in the U.S.
Slowly, Tesla launched the platform to more people, hoping to expand the number of rides and get more valuable data on its performance in both regions to help local regulatory agencies relax some of the constraints that were placed on it.
Additionally, Tesla had its own in-house restrictions, like the presence of Safety Monitors in the vehicles. However, CEO Elon Musk has maintained that these monitors were present for safety reasons specifically, but revealed the plan was to remove them by the end of the year.
Now, Tesla is opening up Robotaxi to anyone who wants to try it, as many people reported today that they were able to access the app and immediately fetch a ride if they were in the area.
We also confirmed it ourselves, as it was shown that we could grab a ride in the Bay Area if we wanted to:
🚨 Tesla Robotaxi ride-hailing Service in Austin and the Bay Area has opened up for anyone on iOS
Go download the app and, if you’re in the area, hail a ride from Robotaxi pic.twitter.com/1CgzG0xk1J
— TESLARATI (@Teslarati) November 18, 2025
The launch of a more public Robotaxi network that allows anyone to access it seems to be a serious move of confidence by Tesla, as it is no longer confining the service to influencers who are handpicked by the company.
In the coming weeks, we expect Tesla to then rid these vehicles of the Safety Monitors as Musk predicted. If it can come through on that by the end of the year, the six-month period where Tesla went from launching Robotaxi to enabling driverless rides is incredibly impressive.
Tesla lands approval for Robotaxi operation in third U.S. state
Tesla ride-hailing Safety Monitor dozes off during Bay Area ride
