News
SpaceX fires up Starship and Super Heavy booster hours apart
SpaceX appears to have successfully fired up a Starship and Super Heavy booster hours apart, testing a total of three new Raptor 2 engines on the two rockets.
SpaceX says it completed a two-engine static fire with Starship 24 less than three hours after the company successfully ignited a Raptor 2 engine installed on a rocket prototype for the first time. That earlier test, performed by Super Heavy Booster 7, was also the first time SpaceX used its new Starbase orbital launch site to support a static fire test and the second-ever static fire of a Starship booster prototype. Had the company called it quits after Booster 7 survived its first intentional trial by fire, it would have still been an exceptionally successful day.
But SpaceX wasn’t done.
Instead, after Booster 7’s seemingly flawless single-Raptor static fire at 5:25 pm CDT, SpaceX loaded Starship 24 with a small amount of liquid oxygen and methane propellant and ignited two of the ship’s six engines around 8:18 pm. It was not initially clear how many engines were involved but a tweet from SpaceX later confirmed it was two. More likely than not, one of those engines was a sea level-optimized Raptor with a smaller bell nozzle and the other was a vacuum-optimized Raptor with a much larger nozzle.
Almost ten months ago, Starship 20 – SpaceX’s first potentially orbital-class Starship prototype – began static fire testing in a somewhat similar way. Its first day of static fires began with a single Raptor Vacuum engine and ended with a simultaneous RVac and sea-level Raptor test in October 2021. In some ways, SpaceX has been a bit less cautious with Starship 24, which is the second potentially orbital-class prototype to begin proof testing. Ship 24 already has all six Raptors installed, whereas Ship 20 only had four of six engines installed during its first static fire tests. SpaceX also took about three weeks to progress from Ship 20’s first static fire test to its first static fire of all six engines, whereas it appears that Ship 24 could potentially attempt its first six-engine test just a few days to a week later.
On the other hand, Ship 24’s path to its first static fire was substantially longer than Ship 20’s. Ship 20 completed its first static fire test(s) just 25 days after its first proof test, referring to the process of verifying that the prototype was in good working order before moving on to riskier testing with flammable propellant and intentional ignitions. Ship 20 also completed its first six-engine static fire 46 days after testing began. Ship 24, meanwhile, took 75 days to go from its first proof test to its first static fire – almost three times slower than Ship 20, a prototype that was essentially the first of its kind.
It’s possible that Ship 24’s upgraded Raptor 2 engines are partially or fully to blame. Instead of jumping straight into ‘hot’ Raptor testing like Ship 20, which began that particular campaign with a partial-ignition preburner test, SpaceX put Ship 24 through seven ‘spin-prime’ tests before its first static fire. For Raptor, spin-primes test the ignition step before preburner ignition, which is itself a step before main combustion chamber ignition (where the engine starts to produce meaningful thrust). Raptor startup procedures likely involve flowing high-pressure gaseous helium, nitrogen, or propellant (oxygen/methane) through the engine to spin up its turbopumps, ‘priming’ them for preburner and main combustion chamber ignition.
On Raptor 1, the preburners would ignite once a high enough flow rate was achieved, producing hot gas that the main combustion chamber would mix and ignite one last time to start the engine. In a recent interview with Tim Dodd (“The Everyday Astronaut”), CEO Elon Musk revealed that SpaceX was able to “remove torch igniters” from Raptor 2’s main combustion chamber (MCC). It’s unclear if that means that Raptor 2 now has zero MCC igniters, but a major change in the overall ignition process could explain why the start of Ship 24 and Booster 7 engine testing was so sluggish. So could the unintended explosion Booster 7 caused when SpaceX attempted to spin-prime all 33 of its Raptor 2 engines at once.
Regardless, SpaceX has finally crossed that particular Rubicon and, with any luck, Raptor 2 testing will begin to speed up on both Starship 24 and Super Heavy Booster 7. SpaceX has test windows scheduled on August 11th, 15th, and 16th. A warning distributed to Boca Chica, Texas residents on August 10th confirmed that the company intends to perform at least one more static fire test on the 11th.
News
SpaceX and Elon Musk share insights on Starship Ship 36’s RUD
Starship Ship 36 experienced a Rapid Unscheduled Disassembly during a static fire attempt.
Elon Musk and SpaceX provided an explanation for the Rapid Unscheduled Disassembly (RUD) of Starship Ship 36 on Wednesday. As per Musk, preliminary data suggests that a nitrogen composite overwrapped pressure vessel (COPV) in the vehicle’s payload bay failed below its proof pressure.
On Wednesday evening, Ship 36 experienced a RUD during a static fire attempt. Videos of the incident that were shared online showed Starship Ship 36 exploding into a massive fireball at its launchpad in Starbase, Texas. Images taken in the aftermath of the explosion showed significant damage to the plumbing in the area. The site’s pad structure was also destroyed.
Elon Musk shared some information immediately after the incident. In a response to a post from space enthusiast @Erdayastronaut, Musk stated that “Preliminary data suggests that a nitrogen COPV in the payload bay failed below its proof pressure.”
Musk also noted that, “If further investigation confirms that this is what happened, it is the first time ever for this design.”
SpaceX provided more insight into the incident in a post on its official website.
“After completing a single-engine static fire earlier this week, the vehicle was in the process of loading cryogenic propellant for a six-engine static fire when a sudden energetic event resulted in the complete loss of Starship and damage to the immediate area surrounding the stand.
“The explosion ignited several fires at the test site, which remains clear of personnel and will be assessed once it has been determined to be safe to approach. Individuals should not attempt to approach the area while safing operations continue,” SpaceX wrote in its post.
SpaceX highlighted that despite Starship Ship 36’s RUD, the incident will not result in any hazards to the surrounding communities in the Rio Grande Valley. And in a post on X, SpaceX also confirmed that everyone in the Starship team was safe and accounted for after Ship 36’s explosion.
While Ship 36’s RUD is a speed bump for the Starship program, SpaceX is a company that is known to grow stronger with every adversity. Thus, it would not be surprising if SpaceX implemented numerous improvements to Starship after this incident–improvements that would make the vehicle more reliable and safer than before.
News
Tesla has started rolling out initial round of Robotaxi invites
Tesla is putting safety above all in its initial Robotaxi rollout.
Tesla has started rolling out an initial round of invites for its upcoming Robotaxi service in Austin, Texas.
Screenshots shared by several Tesla community members who received the invites provided a quick overview of the autonomous ride-hailing service.
As noted in a techAU report, the initial round of Robotaxi service invites has gone to longtime Tesla owners and active members of the EV community. These include owners such as @SawyerMerritt, @BLKMDL3, @WholeMarsBlog, @ItsKimJava, and @HerbertOng, all of whom shared screenshots of the invitation that Tesla has sent about the upcoming service.
You’re Invited to Early Access of Tesla Robotaxi!
The Future is Now! You’re invited to Early Access of Tesla’s Robotaxi service in Austin, TX!
As an Early Access rider, you can be among the first to use our new Robotaxi App and experience an autonomous ride within our geofenced area in Austin. Through this exclusive preview, you’ll have the opportunity to provide valuable feedback on our Robotaxi service.
Based on Tesla’s message, it appears that participation in the service would be strictly invite-only for now. Participants must also download Tesla’s dedicated Robotaxi App to hail a ride. Rides can also be requested and initiated to and from any location within a geofenced area of Austin.
The robotaxi service will be available from 6:00 AM to 12:00 AM, seven days a week, though these hours may change depending on factors such as inclement weather. Interestingly enough, Tesla is inviting the first participants of the Robotaxi program to share photos and videos of their experience with the service.
While the vehicles themselves are autonomous and would operate without human input, the Robotaxis would still be accompanied by a Tesla staff member to monitor the vehicle. This strategy suggests that Tesla is really putting safety above all in its initial Robotaxi rollout.
News
Texas lawmakers urge Tesla to delay Austin robotaxi launch to September
The letter urges Tesla to delay its initial robotaxi launch in the interest of public safety.
A group of Democratic lawmakers from Austin is asking Tesla to postpone its planned robotaxi rollout, at least until a new state law governing autonomous vehicles takes effect in September.
The letter, which was sent Wednesday, urges Tesla to delay its initial robotaxi launch in the interest of public safety.
What the lawmakers’ letter says
In their letter, the Democratic lawmakers stated that delaying Tesla’s initial robotaxi launch would build trust in the electric vehicle maker’s autonomous vehicle operations.
“We are formally requesting that Tesla delay autonomous robotaxi operations until the new law takes effect on September 1, 2025. We believe this is in the best interest of both public safety and building public trust in Tesla’s operations,” the letter read.
The lawmakers noted that if Tesla wishes to push through with its planned June 22 launch, the company must provide detailed information explaining its robotaxi service’s initial launch.
New rules kick in September
The new Texas law passed state legislature last month, and it introduces stricter requirements for companies deploying fully self-driving cars.
Current state law allows autonomous vehicle testing without a human driver, as long as vehicles meet basic registration and insurance standards. The updated framework gives state agencies more oversight, including the ability to revoke permits if autonomous vehicles pose safety risks.
It remains to be seen if the Democratic lawmakers’ efforts will bear fruit, especially since Texas is state where Republicans hold the governorship and majorities in both legislative chambers, as noted in a Reuters report.
Elon Musk, for his part, confirmed that Tesla’s initial robotaxi launch for Austin this June will start with a small fleet of Model Y vehicles. He also noted the service would initially operate only in parts of the city the company deems safest.
Tesla has not issued a comment about the Democratic lawmakers’ letter as of writing.
SpaceX and Elon Musk share insights on Starship Ship 36’s RUD
Tesla has started rolling out initial round of Robotaxi invites
Texas lawmakers urge Tesla to delay Austin robotaxi launch to September
-
News2 weeks agoI took a Tesla Cybertruck weekend Demo Drive – Here’s what I learned
-
Elon Musk2 weeks agoTesla tops Cathie Wood’s stock picks, predicts $2,600 surge
-
News1 week agoFirst Tesla driverless robotaxi spotted in the wild in Austin, TX
-
Elon Musk2 weeks agoX account with 184 followers inadvertently saves US space program amid Musk-Trump row
-
Elon Musk2 weeks agoSpaceX to decommission Dragon spacecraft in response to Pres. Trump war of words with Elon Musk
-
News2 weeks agoTesla adds useful Model 3/Y feature home chargers will love
-
News2 weeks agoTesla announces massive new achievement with 8 million cars produced
-
Elon Musk1 week agoTesla CEO Elon Musk reveals new details about Robotaxi rollout