News
SpaceX Starship rocket catches fire during third Raptor engine test
SpaceX appears to have successfully fired up its fourth full-scale Starship prototype for the third time, although the Raptor engine test ended with the aft end of the ship catching fire and burning for quite some time.
Around May 7th, hours after Starship SN4 completed its second wet dress rehearsal and Raptor static fire in ~24 hours, SpaceX removed the SN18 Raptor engine it had used to support those tests, transporting it back to storage facilities a mile down the road. Three days later, SpaceX sent Raptor SN20 down the same same road and installed it on Starship SN4 – a swap made for unknown reasons.
Regardless, that swap meant that SpaceX would need to perform at least one more static fire test to prove that Starship and its new Raptor engine were getting along before the company could proceed to hop test preparations. After several days of at least 4 aborted Starship static fire attempts, SpaceX has finally managed to fuel Starship SN4 and ignite Raptor engine SN20 – but not before a new challenge cropped up.
Just shy of 1:01 pm CDT (18:01 UTC), Starship SN4 appeared to successfully fire up Raptor SN20 for at least several seconds, serving as an in-situ acceptance test for the advanced rocket engine. Like the Merlin 1D engines that power Falcon 9 boosters, Raptors are built in Hawthorne, California, shipped to McGregor, Texas for standalone acceptance testing, installed on their assigned rocket, and static fired one more time before SpaceX deems them ready for launch.
This static fire thus served to verify that Starship SN4 and Raptor SN20 were both still in good health after a busy week of numerous tests and several weeks or months in storage, respectively. If fully successful, it would likely clear Starship SN4 to attempt what would be the inaugural flight of a full-scale Starship prototype, potentially ready to occur as early as May 21st (pending an FAA license, of course). Unfortunately, when Raptor SN20 ignited, it appeared to shake or overpressurize one or several plumbing lines, catching what must have been a methane vent or drain line on fire.

While the rocket itself is likely totally fine, much like its Starhopper predecessor suffered even worse fires during its summer 2019 test campaign, the dark smoke that appeared shortly after the secondary fire started is not a great sign. As methane and oxygen burn quite cleanly, that smoke likely means that the fire(s) got to some of the extensive wiring covering Starship and connecting to its test stand and ground controllers. If damaged, all of that wiring will need to be replaced, while the leaky methane pipe that burned for a solid 15 minutes will also need to be fixed.
As such, it’s likely that Starship SN4 will need to wait at least several more days – and may even need to complete a fourth static fire test – before SpaceX can clear it for an inaugural 150m (~500 ft) hop test.
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.