News
SpaceX Starship booster heads to launch pad for the fifth time
For the fifth time in five months, SpaceX has transported its most advanced Starship booster prototype from the Starbase factory to the launch pad, setting the stage for another round of testing.
Super Heavy Booster 7 (B7) returned to the factory for the fourth time on August 12th after becoming the first prototype of any kind to perform a static fire engine test while installed on SpaceX’s orbital Starship launch mount. In the days prior, the booster completed two back-to-back static fire tests with one of the 20 Raptor engines installed on the rocket, both of which apparently gave SpaceX enough confidence to prepare for the next phase of testing.
That relatively cautious progress only came after SpaceX attempted to test all 33 of the prototype’s Raptors at once during its first engine test. Whether it was the fault of overzealous managers or executives or a genuine oversight is not clear, but the combined behavior of Super Heavy and the orbital launch pad was not properly characterized before testing began. As a result, the cloud of flammable gas the rocket released during its attempted 33-engine ‘spin-prime’ test found an ignition source and violently exploded on July 11th, causing damage throughout Booster 7’s aft engine section that required several weeks of repairs between July 15th and August 6th.
When the Super Heavy rolled to the pad for the fourth time on August 6th, it was missing all 13 center Raptors, leaving only the outer ring of 20 Raptor Boost engines partially installed for the tests that followed. Thankfully, things went much better on the second try and Booster 7 completed two spin-prime tests with a single Raptor engine, followed by two successful static fire tests on August 9th and 11th. The latter test was the longest Starbase static fire ever (by a factor of ~3) and lasted about 20 seconds, allowing SpaceX to test Booster 7’s autogenous pressurization. That system pressurizes Super Heavy’s tanks by turning small quantities of cryogenic liquid propellant into gas, ensuring that its tanks remain stable as they’re rapidly drained of thousands of tons of propellant.
On August 12th, Booster 7 returned to the factory, where workers installed the rocket’s 13 center engines for the second time. Booster 7 headed back to the orbital launch site (OLS) on August 23rd and the pad’s robotic launch tower used a pair of arms to lift the rocket off its transport stand and place it on the launch mount by the end of the day.
In addition to readying Booster 7 for its next phase of static fire testing, teams of SpaceX workers took advantage of the unplanned lull in testing to modify the orbital launch mount. It’s impossible to know what exactly was done without official confirmation, but it’s likely that SpaceX was attempting to quickly fix the shortcoming(s) that allowed the July 11th explosion to happen. Without a fix, it’s unlikely that SpaceX would want to proceed with plans to ignite large numbers of Raptor engines simultaneously – a series of tests that must be completed before Starship can safely attempt its first orbital launch.
It’s unclear what exactly that fix entails, but it could involve a system to constantly flood the engine section with fire-stopping nitrogen gas or potentially take the shape of a system of vents that will connect to every Raptor engine and remove methane gas before it can turn into flammable clouds.
It’s possible that Booster 7 has returned to the launch pad solely for fit checks or some other basic proof-of-concept testing. It’s also possible that the returns signifies that SpaceX is confident in its quick launch mount fix and ready to restart static fire testing.
As Booster 7 prepares for that next phase of testing, SpaceX may also be ready to restart static fire testing with Starship S24, which paused shortly before Super Heavy returned to the factory. SpaceX appears to be modifying the suborbital launch mount and test stand Ship 24 is installed on, which could explain the lack of ship testing since August 11th. SpaceX has 12-hour test windows tentatively scheduled on August 24th and 25th, either of which could be used to test either or both prototypes.
If all goes to plan, Ship 24 and Booster 7 will eventually complete all the qualification testing SpaceX can throw at them and be ready to support Starship’s first orbital launch attempt sometime before the end of 2022.
Tesla’s Automatic Collision Evasion feature can be seen in one of the first owner videos of it in action.
Tesla owner Spencer (@scotsrule08) posted on Monday that the feature “worked flawlessly,” saying FSD reengaged itself just as he was about to hit a curb. Ashok Elluswamy, who leads Tesla’s AI team, shared the clip and wrote, “A guardian angel always looking out for you.”
The video arrives in the middle of a staged rollout. Tesla first shipped Automatic Collision Evasion with FSD (Supervised) v14.3.9 in software update 2026.27.6 earlier this month, which Teslarati covered as it reached cars. Update 2026.27.10, which began going out on September 19, carried the feature improvements with FSD v14.3.10, according to release notes tracked by Not a Tesla App. The newer 2026.27.11 build is now reaching another wave of vehicles.
The new Automatic Collision Evasion feature worked flawlessly! FSD reengaged itself just as I was about to hit a curb.
Kudos @Tesla_AI team! 👏 pic.twitter.com/Fbp15HhpL2
— Spencer (@scotsrule08) September 28, 2026
The feature only runs on HW4 vehicles, and it requires an active FSD purchase or subscription with both FSD (Supervised) and Automatic Emergency Braking enabled. HW3 owners receive FSD v14.2 Lite in the same updates, but that build does not include collision evasion.
Tesla’s release notes describe two triggers. The first is an imminent frontal collision that braking alone may not prevent, in which case the car can activate FSD to steer, brake or accelerate around the hazard. That scenario is limited to highways below 85 mph, with no pedestrians or cyclists detected and no slippery road surface. The second covers a driver who appears inattentive, such as reaching into the back seat, or who seems to have switched off FSD by accident. Spencer’s curb clip appears to fall into that second category.
Tesla plans big safety improvements for Full Self-Driving v15
Once the system takes over, the accelerator is muted and light brake input will not cancel the maneuver. Drivers need to apply firm, deliberate steering force to take back control, and the car chimes to hand control back once the danger has passed.
Elluswamy recently noted that earlier hazard prediction, faster reaction time and better collision avoidance would arrive with FSD v15, the next major version.
Tesla is delaying its event for the Roadster, moving it from this Thursday, October 1, to Thursday, October 15, due to unfavorable weather.
The company has said it has been tracking the weather for this Thursday closely with local meteorologists, and because the event can only be held outside, Tesla is making the call to delay it:
“We’ve been tracking the weather closely with local meteorologists, but given the severe conditions predicted & because this event can only be held outdoors, we’ve made the difficult decision to reschedule. New date is October 15. Additional details to follow.”
Roadster event update
We’ve been tracking the weather closely with local meteorologists, but given the severe conditions predicted & because this event can only be held outdoors, we’ve made the difficult decision to reschedule.
New date is October 15. Additional details to…
— Tesla (@Tesla) September 28, 2026
We are sure that this is bringing back PTSD for some Tesla fans, and we know it is not ideal, but this also reveals some things about the event. Tesla said that this can only be held outdoors, meaning it bodes well for the rumors that the vehicle could potentially hover.
Some believe that this was essentially confirmed by the FAA airspace restriction they were granted, but this could have been for a drone show or to keep drones from spying on the event.
Tesla Roadster is available for order once again following brief hold
The Roadster event has been long-awaited, and it is unfortunate that the weather is going to keep us all waiting a little bit longer.
The Tesla Roadster will be unveiled in Waco, Texas.
Elon Musk
SpaceX turned a heralding moment for Starship into its greatest
Starship reached orbit despite losing an engine, deployed 26 Starlink V3 satellites on Flight 14.
SpaceX’s Starship reached orbit for the first time on Monday, and for a few nail-biting minutes it looked like it wouldn’t. During ascent on Flight 14, one of Ship 41’s six Raptor engines shut down early, and SpaceX’s livestream host Dan Huot told viewers the team had decided not to commit to orbit. Minutes later, after what Huot described as a lot of conversation in the control room, the final poll came back in favor, and a roughly 19 second burn of a single Raptor pushed the ship into orbit about 170 miles up.
The reversal matters because SpaceX had written the exit ramp into the mission plan. The company said it would only fire the orbital insertion burn if flight controllers confirmed enough backup hardware remained for the deorbit burn, a condition Teslarati laid out ahead of the flight. Losing an engine was exactly the scenario that rule was built for.
Pressing forward fits Elon Musk’s history. Falcon 1 failed three straight times before its fourth launch reached orbit in 2008, with SpaceX nearly out of money, and Starship was developed by flying prototypes until they broke. What changed this year SpaceX going public, and with $SPCX sliding below its IPO price in July when Flight 13 slipped, the short interest climbed significantly, as Teslarati reported at the time. A Starship potentially lost today with revenue generating next-gen Starlink satellites aboard would have landed directly on shareholders.
Splashdown confirmed. Congratulations to the entire SpaceX team on the first orbital flight of Starship! pic.twitter.com/urjmiwnvNl
— SpaceX (@SpaceX) September 28, 2026
That pressure showed up after orbit. SpaceX cut a flight planned to last nearly 10 hours to about three, moving splashdown from west of Chile to the North Pacific near Hawaii. SpaceX gave no reason, though Musk said this month the company was being extremely cautious about debris risk. The single Raptor for deorbit worked, and Ship 41 completed its flip and landing burn before breaking apart in the water, an outcome SpaceX expected. Musk has structured SpaceX’s governance to shield long term bets from market pressure.
The payload is the bigger business story. Musk posted that all 26 Starlink V3 satellites deployed and are “operating nominally.” Each V3 is rated for about 1 Tbps of downlink and 160 Gbps of uplink, so this single launch adds roughly 26 Tbps, about 10 times what a Falcon 9 load of V2 Mini satellites adds. The V3 is too large for Falcon 9, making Starship the only vehicle that can build out the planned 100,000 satellite constellation, at up to 60 per flight once it reaches routine service. Unlike the 20 V3 units on Flight 13, which reentered on a suborbital path, these will raise their orbits and could begin serving customers within weeks and bring in hundreds of millions of additional dollars in projected Starlink revenue.
SpaceX has already begun winding down Falcon 9 Starlink launches from Florida in favor of Starship. Reported targets put Flight 15 as early as October 19, leaving about three weeks to diagnose Monday’s engine shutdown before the next orbital attempt.
Starship’s 14th flight is set to launch on Monday, Sept 28. The 75-minute launch window opens at 7:15 a.m. CT. Live coverage of the mission starts ~35 minutes before launch → https://t.co/uQKQvgaTmJ
— SpaceX (@SpaceX) September 27, 2026
Watch Tesla’s “guardian angel” FSD feature take over for collision evasion
Tesla Roadster event gets delayed due to unfavorable weather
