News
SpaceX Starship aborts Raptor engine test, briefly catches fire
Update: On March 15th, SpaceX got within milliseconds of Starship serial number 11’s (SN11) first Raptor engine test but suffered an abort just before full ignition, briefly leaving the rocket on fire.
Around 12:26 pm CDT, after an otherwise nominal static fire flow, Starship SN11 momentarily ignited one or two of its three Raptor engines’ preburners, referring to a central component that burns cryogenic liquid propellant into gas that’s ready for combustion. As with all preburner tests, intentional or otherwise, the end result looked a bit like a weak static fire and produced a small but visible amount of flame and thrust. Unlike intentional preburner tests, the static fire abort seemingly ignited something hidden inside Starship SN11’s and appeared to burn for at least another 30-40 seconds.
Raptor has proven itself to be an extremely durable engine, up to and including surviving visible onboard fires during actual Starship flight tests. Nevertheless, depending on the source of SN11’s post-abort fire and what it may or may not have burned or damaged, it’s no surprise that SpaceX ended testing for the day instead of quickly trying again, which it’s done several times prior. If the fire was largely harmless, SpaceX has already distributed notices suggesting a second attempt could happen as early as 6am to 12pm CDT (UTC-5) on Tuesday, March 16th. If more time is needed, SpaceX has the rest of the week to conduct any necessary repairs or swap out SN11’s Raptor engines.
Public documents show that SpaceX has plans to static fire and launch its latest Starship prototype within a two-day period that could begin later today.
SpaceX shipped Starship SN11 from its Boca Chica, Texas rocket factory to test and launch facilities a mile down the road on March 8th, less than five days after Starship SN10 exploded minutes after touchdown. The very next day, SpaceX completed ambient-temperature proof testing, filling Starship with benign nitrogen gas to check for leaks and verify system health. Two days after that, Starship SN11 appeared to complete a several-hour cryogenic proof test – swapping nitrogen gas for its supercool liquid form – without issue.
Despite the seemingly successful ‘cryo proof,’ something prevented a subsequent static fire test planned on March 12th before any attempt could be made, delaying the next attempt until after the approaching weekend. An agreement between SpaceX, Cameron County, and the state of Texas currently prevents road closures (and thus rocket testing) on weekends falling between Labor Day and Memorial Day, rules meant to preserve some level of public access to Boca Chica Beach.
As a result, unless SpaceX is already ready to launch (it has waivers for three such weekend closures for launch attempts), the company has to wait until Monday even if a minor issue fixable in hours or a day or so scrubs Friday test plans. While inconvenient, it’s worth noting that the existence of that public beach and the strong regulations that protect its public domain is likely one of the only reasons the general public can still get as close as they can to SpaceX’s Boca Chica ‘Starbase’.
For whatever reason, that road closure agreement does still mean that SpaceX will (in theory) be able to test and launch any day of the week from May 31st to September 6th, save for a few holidays, effectively boosting the number of opportunities by 40% for those 14 weeks. Until then, SpaceX is doing everything it can to take full advantage of the five days a week it is allowed to test Starship prototypes. N
Notably, although Starships SN8 and SN9 both hit a few weeks of technical and regulatory snags while preparing for their high-altitude launch attempts, SpaceX has been gradually speeding up that process over time. Starship SN10, the first prototype of its kind to land in one piece, took just 33 days to go from pad arrival to liftoff and spent just 8 days between its first static fire and launch attempts. The same feats took Starship SN8 77 and 50 days, respectively, with SN9 splitting the difference at 43 days from transport to liftoff and 28 days between its first static fire and launch attempts.
Road closure requests, a safety warning for residents, and a Temporary Flight Restriction (TFR) filed with the FAA all suggest that SpaceX’s current plan is to attempt Starship SN11’s first triple-Raptor static fire between 6am and 12pm CDT on Monday, March 15th. If that test goes almost perfectly, SpaceX wants to turn the rocket around for a 10 km (6.2 mi) launch attempt on Tuesday, March 16th – the very next day. Given the past performance of high-altitude Starship prototypes, that target is decidedly ambitious and likely to incur delays, but it still reveals the true scope of SpaceX’s goals even at this early stage of development.
If Starship SN11 does manage to launch within a few days of its first static fire attempt, SpaceX would still crush SN10’s 33-day record by a factor of three. Stay tuned for updates on Monday’s possible Starship static fire and rapid Tuesday turnaround attempt
Elon Musk
Tesla Giga Berlin growth could stall if not “free from external influences”: Elon Musk
The comments were delivered in a pre-recorded video discussion.
Tesla CEO Elon Musk has reportedly warned that future expansion of Gigafactory Berlin could be jeopardized if the site does not remain “free from external influences.”
Musk’s comments were delivered in a pre-recorded video discussion with employees and came at a sensitive moment for the facility, where union representation has been a recurring issue.
According to reports from Handelsblatt and Der Spiegel, citing participants at the event, Musk suggested that if Giga Berlin is no longer “free from external influences,” further expansion would become unlikely. He did not, however, hint that the plant would shut down.
While Musk did not name IG Metall directly, his remarks were widely interpreted as referencing the union, which is currently the largest faction on the works council but does not hold a majority, as noted in an electrive report.
The video conversation was conducted between Musk in Austin and Grünheide plant manager André Thierig, then played back to the workforce in Germany. Works council elections are scheduled for early March, heightening the tension between management and organized labor.
The CEO has previously voiced concerns that stronger union influence could limit Tesla’s operational flexibility and long-term strategy in Germany.
Despite the warning on expansion, Musk praised the Giga Berlin site during the same address, describing it as one of the most advanced factories worldwide and highlighting its cleanliness and team culture.
The discussion also reportedly touched on battery cell production. According to attendees cited in German media, Musk indicated that Tesla has begun ramping cell production at the site. That would mark a notable shift from earlier expectations that large-scale cell manufacturing in Brandenburg would not begin until 2027.
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.