News
SpaceX completes Falcon 9 test fire, space station supply mission up next
After almost exactly 15 months of dormancy, SpaceX’s Launch Complex 40 (LC-40) came to life with the roar of nine Merlin 1D rocket engines as Falcon 9 1035 conducted its second pre-launch static fire in preparation for the company’s 13th Commercial Resupply Services mission, CRS-13. Previously tasked with the launch of the CRS-11 Cargo Dragon, the booster completed its mission and returned safely to Landing Zone-1 (LZ-1) on June 3 2017. The path towards LC-40’s reactivation has delayed the launch approximately one week, but December 6th’s successful static fire bodes well for the current launch date, 11:46 AM on December 12.
Static fire test of Falcon 9 complete—targeting launch of CRS-13 on December 12 from Pad 40, followed by launch of Zuma from Pad 40 in early January.
— SpaceX (@SpaceX) December 6, 2017
On September 6 2016, LC-40 was effectively destroyed over the course of the Amos-6 failure. In months that followed, SpaceX reactivated LC-39A in order to continue chipping away at the company’s launch manifest, but also began the slow process of damage assessment and reconstruction of LC-40. It is safe to assume that almost every single component of the ground support equipment (GSE) was completely replaced, and interviews with Cape Canaveral’s 45th Space Wing commander suggest that SpaceX went further still, transforming the painful situation into an opportunity.
In an exclusive and frank conversation between Brig. Gen. Wayne Monteith and Florida Today’s Emre Kelly, the commander suggested that extensive design changes and additional hardening measures implemented during reconstruction are expected to make LC-40 exceptionally resilient to the rigors of rocket launches. Most tellingly, if perhaps overly optimistic, Monteith estimated that a second vehicle failure on the order of Amos-6 might only take two months to recover from, compared to the 15 months that followed Amos-6. He attributed this claim to GSE that is now largely buried underground, theoretically protecting the vast apparatus of hand-welded piping necessary to fuel the Falcon 9 launch vehicle. The replacement Transporter/Erector/Launcher (TEL) tasked with supporting Falcon 9 during integration and launch also appears to have been modernized, and will likely end up looking quite similar to the monolithic white TEL that resides at LC-39A.
Rocket and spacecraft for CRS-13 are flight-proven. Falcon 9’s first stage previously launched SpaceX’s eleventh resupply mission for @NASA, and Dragon flew to the @Space_Station in support of our sixth cargo resupply mission. pic.twitter.com/RY4F2TrWO2
— SpaceX (@SpaceX) December 6, 2017
With CRS-13’s static fire now complete, the mission is set to become the fifth operational reuse of a flight-proven Falcon 9 booster in 2017, thanks to NASA’s unusually rapid acceptance of the new practice. Further still, if Iridium-4’s December 22 launch date holds, and it does look to be stable for the moment, SpaceX will rather incredibly have conducted five commercial reuses of a Falcon 9 in its first year of operations, meaning that one third of SpaceX’s 2017 missions will have launched aboard flight-proven boosters. Also impressive is SpaceX’s full-stop move towards the reuse of Cargo Dragon capsules, and the company stated over the summer that it was hoping to almost completely redirect Cargo Dragon’s manufacturing facilities towards Dragon 2, also known as Crew Dragon. This was most recently reiterated several months ago and is presumed to still be the company’s goal moving forward, and CRS-12 is believed to have been the last “new” Cargo Dragon that will fly. CRS-13’s Dragon previously flew the CRS-6 mission in April 2015.
Photos shared privately with the author show CRS-13’s Falcon 9 to be covered in a graceful layer of soot from its previous recovery, similar in appearance to Falcon 9 1021 seen above. (Instagram/bambi_mydear)
In a December 6 tweet, SpaceX further confirmed that the deeply secretive Zuma mission, previously delayed from an early-November launch as a result of concerns about fairing defects, has now been moved from LC-39A to LC-40 and is understood to be targeting January 4 2018. This will give SpaceX approximately three weeks after the launch of CRS-13 to verify that everything is functioning nominally in what is essentially a new pad.
Meanwhile, with Zuma now officially moved to 40, LC-39A is completely free from routine operations, meaning that SpaceX’s ground crew can now work at will to ready the pad for the inaugural launch of Falcon Heavy, now aiming for early 2018. Aside from Falcon Heavy, recent FCC filings point to two additional SpaceX launches aiming for January, although slips are probable in light of CRS-13’s minor delays. Regardless, December and January are likely to be thrilling months for followers of the intrepid space exploration outfit.
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
