News
SpaceX Starship booster survives record-breaking 31-engine static fire
SpaceX’s Starship rocket has survived a record-breaking engine test – potentially the most powerful static fire in the history of rocketry.
According to CEO Elon Musk, Super Heavy Booster 7 (B7) ultimately ignited 31 of its 33 Raptor engines. One engine was manually disabled “just before” the static fire, while the other faulty engine automatically shut down while attempting to ignite. The other 31 Raptors, however, completed a “full duration” static fire that lasted about five seconds. Musk says that even with two engines disabled, those that remained were “still enough…to reach orbit” – an excellent result despite the static fire’s imperfections.
Most importantly, Super Heavy Booster 7 survived the test without catching fire, exploding, or popping its tanks. To partially counteract the thrust of its Raptor engines, the rocket’s tanks were filled with some 3000 tons (6.6M lbs) of liquid oxygen and methane propellant. The stool-like orbital launch mount (OLM), which also survived the test in one piece, held Starship down with 20 clamps to counteract any remaining thrust. From SpaceX’s perspective, the fact alone that its only orbital-class Starship launch site survived the ordeal is likely enough for it to consider the static fire a success. But the test was much more than that.
The update that's rolling out to the fleet makes full use of the front and rear steering travel to minimize turning circle. In this case a reduction of 1.6 feet just over the air— Wes (@wmorrill3) April 16, 2024
Incinerating rocket records
Despite losing two Raptors, SpaceX still broke the all-time record for the number of rocket engines ignited simultaneously. That record was held by the Soviet N1 rocket, which launched four times with 30 NK-15 engines in the late 1960s and early 1970s. None of its test flights were successful, but N1 still set the record for the most thrust produced by a single rocket, generating up to 4500 tons (9.9M lbf) of thrust at liftoff.
Neither SpaceX nor CEO Elon Musk has confirmed it, reducing the odds that Super Heavy Booster 7 broke that historic thrust record. But it certainly could have. Each Raptor 2 engine can generate up to 230 tons (507,000 lbf) of thrust at sea level. Raptor is theoretically designed to throttle as low as 40%, or 92 tons (~200,000 lbf) of thrust. With 33 engines operating nominally at their minimum throttle setting, Super Heavy would have produced 3036 tons (~6.7M lbf) of thrust during today’s static fire – not a record.
For 31 Raptors to break N1’s thrust record, the average throttle setting would have had to be around 64% or higher – far from unreasonable. From a data-gathering perspective, a full-thrust static fire would be the most valuable 33-engine test SpaceX could attempt, but it would also be the riskiest and most stressful for the rocket and pad.
Former SpaceX executive Tom Mueller says that SpaceX broke N1’s record. Mueller is effectively the father of the Raptor engine, and likely still gets information straight from SpaceX engineers he used to work with. Still, one would expect SpaceX itself to proudly confirm as much if a rocket it built became the most powerful in history.
The most powerful rocket test in history?
Whether or not Starship became the most powerful rocket in history, it has likely become the most powerful rocket ever tested on the ground. The first stage of Saturn V produced around 3400 tons (7.5M lbf) of thrust during its first sea-level static fire in 1965. Likely contributing to its failure, N1’s booster was never static-fired. Other powerful rockets like the Space Shuttle and SLS use or used a combination of solid rocket boosters and liquid engines that cannot be tested together on the ground.
Unless SpaceX’s goal was a minimum-throttle static fire, Starship’s 31-Raptor static fire likely beat Saturn V’s record to become the most powerful ground test in the history of rocketry.
SpaceX’s next steps
While the 31 that did ignite appeared to perform about as well as SpaceX could have hoped, the two engines missing from February 9th’s historic Starship static fire have probably complicated the company’s next steps. To be fully confident in Starship’s ability to launch and fly a safe distance away from the launch site, SpaceX would likely need to complete a full 33-engine test. Meanwhile, Starship can’t fly until the Federal Aviation Administration approves a launch license, and the FAA could be stodgy enough to deny SpaceX a license without a perfect 33-engine static fire.
Alternatively, the FAA may accept that Starship could still safely launch and reach orbit while missing several Raptors. SpaceX could also guarantee that it will only allow Starship to lift off if all 33 engines are active, in which case a second 33-engine static fire attempt may not be necessary.
If SpaceX is happy with Booster 7’s 31-engine test results and isn’t too put off by any pad damage the test may or may not have caused, it will likely focus on finishing Starship 24. Ship 24 will then be transported back to the pad and reinstalled on top of Booster 7. SpaceX may choose to conduct another wet dress rehearsal or a static fire with the fully-stacked Starship, but it may also deem additional testing unnecessary.
Once all those tasks are completed, Ship 24 and Booster 7 will be ready to support Starship’s first orbital launch attempt. Prior to February 9th’s static fire, SpaceX CEO Elon Musk and COO/President Gwynne Shotwell agreed that Starship’s orbital launch debut could happen as early as March 2023. After today’s test, a March 2023 launch may be within reach.
Rewatch Super Heavy Booster 7’s historic static fire below.
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
