News
Musk blames SpaceX’s latest Starship explosion on Raptor engine leak
CEO Elon Musk says that SpaceX’s latest Starship test flight ended with a midair explosion because a “small” leak started on one of the rocket’s three Raptor engines.
As promised, the new information offers some insight into the cause of Starship SN11’s premature demise and the challenges of iteratively developing systems as complex as a fully-reusable Saturn V-class launch vehicle. On March 30th, after about a week of delays, Starship SN11 lifted off on SpaceX’s fourth high-altitude launch and landing test while all but completely obscured by a thick bank of fog.
Despite the unfortunate weather conditions, which prevented almost any kind of view of the launch outside of Starship’s own cameras, the rocket performed about as well as its three predecessors, reaching a planned apogee of 10 km (6.2 mi) before free-falling belly-first back to earth. At T+5:49, however, things went wrong.
At that point, Starship tried to ignite its three Raptor engines to flip into a tail-down landing configuration, at which point two of those engines would be shut down, leaving the healthiest of the three to attempt a soft landing. Something immediately went wrong and both telemetry, live video, and the countdown clock froze with a view of one partially ignited Raptor engine.
Notably, as pictured in the image at the top of this article, it’s possible that the “small [methane] leak” Musk has blamed for SN11’s failure was visible on Raptor engine SN52 less than 30 seconds after Starship lifted off, leaving plenty of time for a high-pressure fire to severely damage the faulty engine and its adjacent partners. The SpaceX CEO says that the resultant fire “fried part of [the] avionics” controlling one or all three Raptors, “causing [a] hard start” that damaged or destroyed one or all of the engines when they attempted to begin their landing burns.
Based on analysis of unofficial videos taken by cameras near the Starship launch site, it’s been deemed likely that SN11 exploded not because its flight termination system (FTS) triggered – but because of Raptor’s violent, explosive “hard start.” Ultimately, it’s not clear if ever SpaceX itself will ever be able to paint a truly clear picture of what exactly happened to SN11, but Musk says that the suspect Raptor leak “is getting fixed [six] ways to Sunday.” It’s possible that an upgraded Raptor engine Musk has hinted will debut on Starship SN15 has already fully or partially dealt with whatever is at the root of SN11’s engine leak and hard start(s).
Either way, SN15 is already expected to roll to the launch pad as early as this week – mere days after SN11’s explosion – and SpaceX wont have to wait long to test whatever fixes it implements as the upgraded vehicle works towards static fire tests and its own launch debut.
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.
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:
Tesla appears to be implementing some sort of feature that will now pull over if someone is tailgating you to let the car by
Really cool feature, definitely get a lot of this from those who think they drive race cars
— TESLARATI (@Teslarati) February 26, 2026
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:
What has happened to Mad Max?
At one point it was going 32 in a 35. Traffic ahead had pulled away considerably https://t.co/bjKvaMVTNX pic.twitter.com/aaZSWmLu5v
— TESLARATI (@Teslarati) January 24, 2026
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.
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.
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.”
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.
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.
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.
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.
Tesla Full Self-Driving’s newest behavior is the perfect answer to aggressive cars
Tesla Megapack powers $1.1B AI data center project in Brazil
