Connect with us

News

SpaceX’s Elon Musk hints at “notable” Starship changes, explains static fire anomaly

Starship SN8; humans for scale. (NASASpaceflight - bocachicagal)

Published

on

CEO Elon Musk has offered an explanation for SpaceX’s recent Starship static fire anomaly and says that an overview of the next-generation rocket development program will be delayed to account for some “notable” design changes.

Over the last several months, Musk has promised to do one of his (thus far) usual annual Starship updates, either in the form of a presentation in South Texas, an article published on SpaceX’s website, or both. Originally expected in September or October, the CEO’s tentative schedules have come and gone several times. Simultaneously, however, SpaceX has been preparing Starship serial number 8 (SN8) for a range of crucial tests and Starship program firsts, recently culminating in a successful cryogenic proof test, multiple wet dress rehearsals (WDRs), nosecone installation, the first triple-Raptor static fire test, engine tests using smaller ‘header’ tanks, and more.

Unfortunately for SN8, the most recent Raptor engine header static fire – drawing propellant from two small internal tanks mainly used for landing burns – did not go according to plan, resulting in some kind of high-temperature fire and severing Starship’s hydraulic systems. For SpaceX test controllers, that meant a total loss of control of most vehicle valves and pressurization systems, essentially putting one of Starship SN8’s header tanks through an unplanned pressure and failsafe test. In the days since, what exactly caused that unfortunate failure has been the subject of a great deal of discussion – discussion that can finally be put to rest with new information from Musk himself.

In a surprise, SpaceX had apparently decided to add a failsafe to Starship SN8’s new nose section, installing what is known as a burst disk – effectively an automatic single-use valve. Once the upper (liquid oxygen) header tank reached dangerous pressures, the force of that pressure broke the seal, allowing the rocket to vent excess pressure and avoid what would have otherwise been a potentially catastrophic explosion.

Advertisement

The cause of that near-miss, according to Elon Musk, was as simple as debris kicked up during the Starship SN8 Raptor engine static fire directly prior. Producing up to 200 metric tons (~450,000 lbf) of thrust and an exhaust stream traveling some 3.3 kilometers per second (2 mi/s, Mach ~10), Musk says that Raptor tore apart a special ceramic coating covering the concrete directly beneath Starship SN8. Likely accelerated to extreme velocities in milliseconds, shards of that coating reportedly “severed [an] avionics cable, causing [a] bad [Raptor engine shutdown].”

Raptor engine SN42 took SN32’s place after debris caused damage when the engine attempted to shut down. (NASASpaceflight – bocachicagal)

Prior to Musk’s comments, SpaceX technicians had already removed on of SN8’s three Raptors – SN32 – on November 14th and replaced it with Raptor SN42 on November 16th, effectively confirming that any damage suffered by Starship’s engine section was easily repairable. It’s unclear how exactly a single severed cable could result in a Raptor engine seemingly dripping molten metal but regardless of the cause, the fix appears to have been a quick one.

A second Starship test stand and the beginnings of a Super Heavy-class orbital launch mount are pictured to the left and right of prototype SN8. (NASASpaceflight – bocachicagal)

In response to the anomaly, Musk says that Starship avionics cables will ultimately be routed inside steel pipes to shield them from debris, while “water-cooled steel pipes” will be added to the launch pad to help limit the damage Raptors can cause. Perhaps as a partial result of SN8’s troubles at the launch pad, Musk says that his Starship blog post will have to wait, as SpaceX “[may be] making some notable changes” to the launch vehicle.

Prior to Starship SN8’s failed November 12th Raptor test, SpaceX was expected to attempt three consecutive static fires before clearing the rocket for an ambitious 15 km (9.5 mi) flight test. One of those static fires had already been completed on November 10th and it’s unclear if SpaceX’s SN8 test plan has remained unchanged or if the static fire counter has been effectively reset. Either way, barring more surprises, there’s still a definite possibility that Starship SN8 will be ready for its launch debut by the end of November and an even better chance that it will launch some time between now and 2021. Stay tuned for updates!

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

Advertisement
Comments

Elon Musk

Tesla Full Self-Driving’s newest behavior is the perfect answer to aggressive cars

According to a recent video, it now appears the suite will automatically pull over if there is a tailgater on your bumper, the most ideal solution for when a driver is riding your bumper.

Published

on

Credit: Tesla

Tesla Full Self-Driving appears to have a new behavior that is the perfect answer to aggressive drivers.

According to a recent video, it now appears the suite will automatically pull over if there is a tailgater on your bumper, the most ideal solution for when a driver is riding your bumper.

With FSD’s constantly-changing Speed Profiles, it seems as if this solution could help eliminate the need to tinker with driving modes from the person in the driver’s seat. This tends to be one of my biggest complaints from FSD at times.

A video posted on X shows a Tesla on Full Self-Driving pulling over to the shoulder on windy, wet roads after another car seemed to be following it quite aggressively. The car looks to have automatically sensed that the vehicle behind it was in a bit of a hurry, so FSD determined that pulling over and letting it by was the best idea:

We can see from the clip that there was no human intervention to pull over to the side, as the driver’s hands are stationary and never interfere with the turn signal stalk.

This can be used to override some of the decisions FSD makes, and is a great way to get things back on track if the semi-autonomous functionality tries to do something that is either unneeded or not included in the routing on the in-car Nav.

FSD tends to move over for faster traffic on the interstate when there are multiple lanes. On two-lane highways, it will pass slower cars using the left lane. When faster traffic is behind a Tesla on FSD, the vehicle will move back over to the right lane, the correct behavior in a scenario like this.

Perhaps one of my biggest complaints at times with Full Self-Driving, especially from version to version, is how much tinkering Tesla does with Speed Profiles. One minute, they’re suitable for driving on local roads, the next, they’re either too fast or too slow.

When they are too slow, most of us just shift up into a faster setting, but at times, even that’s not enough, see below:

There are times when it feels like it would be suitable for the car to just pull over and let the vehicle that is traveling behind pass. This, at least up until this point, it appears, was something that required human intervention.

Now, it looks like Tesla is trying to get FSD to a point where it just knows that it should probably get out of the way.

Continue Reading

Elon Musk

Tesla Megapack powers $1.1B AI data center project in Brazil

By integrating Tesla’s Megapack systems, the facility will function not only as a major power consumer but also as a grid-supporting asset.

Published

on

Credit: Tesla

Tesla’s Megapack battery systems will be deployed as part of a 400MW AI data center campus in Uberlândia, Brazil. The initiative is described as one of Latin America’s largest AI infrastructure projects.

The project is being led by RT-One, which confirmed that the facility will integrate Tesla Megapack battery energy storage systems (BESS) as part of a broader industrial alliance that includes Hitachi Energy, Siemens, ABB, HIMOINSA, and Schneider Electric. The project is backed by more than R$6 billion (approximately $1.1 billion) in private capital.

According to RT-One, the data center is designed to operate on 100% renewable energy while also reinforcing regional grid stability.

“Brazil generates abundant energy, particularly from renewable sources such as solar and wind. However, high renewable penetration can create grid stability challenges,” RT-One President Fernando Palamone noted in a post on LinkedIn. “Managing this imbalance is one of the country’s growing infrastructure priorities.”

Advertisement

By integrating Tesla’s Megapack systems, the facility will function not only as a major power consumer but also as a grid-supporting asset.

“The facility will be capable of absorbing excess electricity when supply is high and providing stabilization services when the grid requires additional support. This approach enhances resilience, improves reliability, and contributes to a more efficient use of renewable generation,” Palamone added.

The model mirrors approaches used in energy-intensive regions such as California and Texas, where large battery systems help manage fluctuations tied to renewable energy generation.

The RT-One President recently visited Tesla’s Megafactory in Lathrop, California, where Megapacks are produced, as part of establishing the partnership. He thanked the Tesla team, including Marcel Dall Pai, Nicholas Reale, and Sean Jones, for supporting the collaboration in his LinkedIn post.

Advertisement
Continue Reading

Elon Musk

Starlink powers Europe’s first satellite-to-phone service with O2 partnership

The service initially supports text messaging along with apps such as WhatsApp, Facebook Messenger, Google Maps and weather tools.

Published

on

Credit: SpaceX

Starlink is now powering Europe’s first commercial satellite-to-smartphone service, as Virgin Media O2 launches a space-based mobile data offering across the UK.

The new O2 Satellite service uses Starlink’s low-Earth orbit network to connect regular smartphones in areas without terrestrial coverage, expanding O2’s reach from 89% to 95% of Britain’s landmass.

Under the rollout, compatible Samsung devices automatically connect to Starlink satellites when users move beyond traditional mobile coverage, according to Reuters.

The service initially supports text messaging along with apps such as WhatsApp, Facebook Messenger, Google Maps and weather tools. O2 is pricing the add-on at £3 per month.

Advertisement

By leveraging Starlink’s satellite infrastructure, O2 can deliver connectivity in remote and rural regions without building additional ground towers. The move represents another step in Starlink’s push beyond fixed broadband and into direct-to-device mobile services.

Virgin Media O2 chief executive Lutz Schuler shared his thoughts about the Starlink partnership. “By launching O2 Satellite, we’ve become the first operator in Europe to launch a space-based mobile data service that, overnight, has brought new mobile coverage to an area around two-thirds the size of Wales for the first time,” he said.

Satellite-based mobile connectivity is gaining traction globally. In the U.S., T-Mobile has launched a similar satellite-to-cell offering. Meanwhile, Vodafone has conducted satellite video call tests through its partnership with AST SpaceMobile last year.

For Starlink, the O2 agreement highlights how its network is increasingly being integrated into national telecom systems, enabling standard smartphones to connect directly to satellites without specialized hardware.

Advertisement
Continue Reading