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
News
Tesla reveals plans for Robotaxi charging hub in Austin
Tesla has revealed plans through permit submissions for a massive Robotaxi charging hub in Austin, Texas.
Tesla plans to build the Supercharger hub in multiple phases, with the second phase potentially introducing wireless induction charging, something the company has been developing for the Robotaxi fleet.
Initially, 48 Tesla Robotaxi-geared Superchargers will be built on a lot just across from the St. Elmo, Texas, Service Center. There are about 80 additional spots that will not be impacted by phase 1 of the construction process.
Filings show that the second phase of the project will turn those 80 additional spots into wireless charging for Robotaxi, but it might be an error. The Key Notes state that item 3 is listed as “V4 Charging Cabinet to Support 80 Wireless Chargers in Phase 2. However, the drawings point to V3 Cabinets that are already tied to Superchargers:

There are roughly 128 total spots in the lot, but it is unclear if they will all be used for charging based on what appears to be some sort of typo in the blueprint.
A new Robotaxi fleet charging hub is coming soon to Austin, Texas!!
Permits have been filed for the installation of 48 (V3) stalls in a vehicle storage lot across the road from Tesla’s St Elmo service center. pic.twitter.com/xwRgSWDqht
— MarcoRP (@MarcoRPi1) August 18, 2026
This is among the first Robotaxi charging hubs Tesla has started to develop, as it currently has four others planned throughout various areas: one in Phoenix, one in San Antonio, another in Irving, which will serve the Dallas-Fort Worth area, and another in Las Vegas.
These projects are necessary as Tesla expands its Robotaxi program. Now that preparations have started for the public launch of Cybercab, Robotaxi will likely be expanding aggressively, especially over the next two to three years.
Last night, The Information reported that Tesla was planning to launch Cybercab as soon as the end of August. Hours later, Tesla then announced it was launching a competition for fans to potentially ride in Cybercab during its first public rides.
Tesla’s plan to expand its charging infrastructure in the regions where Robotaxi will initially operate is great preparation for the expanding service. There is still a lot to do, including launching the Cybercab on time.
News
Tesla Semi gets its largest order yet
Tesla got its largest order for the all-electric Class 8 Semi yet, a 500-unit order from Einride AB, a Swedish trucking company.
Einride made the announcement this morning following its second-quarter earnings call. The company said it plans to use 500 Tesla Semi units on its fleet intelligence platform, called Saga AI. The deployments will serve large companies like Amazon and will extend Einride’s electric freight network across logistics routes in California, New Jersey, Texas, Illinois, and Georgia.
🚨 Tesla has received a MASSIVE order from Swedish freight company Einride AB, which placed an order for 500 Tesla Semi trucks
Tesla’s biggest order for the Semi yet! pic.twitter.com/PrtLp5yzvh
— TESLARATI (@Teslarati) August 18, 2026
The deployment is being carried out in several phases over the next two years as Tesla ramps production of the Semi at its dedicated production facility in Sparks, Nevada. Einride will receive its first Semi units in September.
Saga AI
Saga AI is Einride’s dedicated fleet intelligence platform. It enables scaled adoption of electric trucks for freight use and allows shippers to integrate electric capacity without the operational burden or capital risks of managing a fleet. This helps integrate cost-efficient logistics and makes budgeting and forecasting much more accurate.
Tesla Semi’s Adoption
The Tesla Semi is now gathering large-scale clients past those who have helped the company operate a Pilot Program to gain initial information and feedback from real-world drivers.
Perhaps the biggest and most notable is that of Frito-Lay and PepsiCo., who have worked with Tesla for the past several years to dial in the finer details of the truck, including its efficiency and operation-related components.
Tesla Semi gets strange-but-understandable comparison from Jay Leno
There has been tremendous progress in that time, and it even catalyzed Tesla to make some design changes, which were unveiled earlier this year.
But Einride CEO Roozbeh Charli says his company’s partnership with Tesla will continue to push those things forward:
“This deployment is yet another proof point that we can execute at the scale our customers demand. Working closely with Tesla to bring next-generation Semis into active operations quickly and at scale is a testament to the strength of that partnership, and how quickly this technology is maturing from promise to daily operations.”
Additionally, Dan Priestley, the Director of the Semi Program at Tesla, said the partnership is ideal due to Einride’s focus on sustainable transport:
“Einride is at the forefront of sustainable freight, and we are thrilled to deepen our relationship with them through this order of 500 Semis. EV heavy trucks provide lower costs per mile from fuel savings, reduced maintenance, and better uptime over diesel trucks. These savings increase further through operational efficiency when deploying EV trucks at scale, and we are excited that Einride recognizes this and look forward to supporting their deployments.”
Elon Musk
India tells Elon Musk’s X to “Follow the Law” in latest censorship update
Elon Musk says X now exposes government censorship, but India’s secrecy laws complicate that promise.
Elon Musk’s promise to make government censorship requests on X “clearly visible” is running into a wall in India, where the law forbids the very disclosure Musk is promising.
On August 15, Musk responded to an update from X’s open-source algorithm team by writing “Any censorship required by governments is now clearly visible.” The claim referred to a change X pushed two days earlier to its public xai-org/x-algorithm repository, which now includes a controversial filter written directly into the code. The filter suppresses posts from 665 accounts flagged by Brazil’s Superior Electoral Court from appearing in the For You feed of any viewer located in Brazil, unless the viewer already follows the account. The election tied to the filter is scheduled for October 4.
India’s government wasn’t as impressed, and responded on Monday that “X will have to follow the law of the land,” in response to Musk’s transparency push covered by the Times of India. The problem is structural rather than political. India issues content blocking orders under Section 69A of its IT Act, and Rule 16 of the accompanying 2009 Blocking Rules requires those orders to stay confidential. Publishing an India equivalent of the Brazil filter, naming specific accounts and citing specific government orders, would itself violate Indian law. Government use of Section 69A has grown from roughly 6,000 orders a year between 2018 and 2023 to about 24,300 in 2025, according to a Tech Times report.
The contrast puts Musk’s transparency pledge in an odd spot. It works largely as advertised in Brazil, where electoral law requires disclosure and X can point to specific account IDs and a specific court order in public code. It cannot work the same way in India, where the law requires the opposite. X users in India will keep seeing content disappear from search and their feeds without any public accounting of why, even as X tells the rest of the world that its censorship compliance is now inspectable.
This isn’t the first time X’s fights with a national government have shaped how the platform operates. Brazil’s Supreme Court ordered X to suspend the accounts of sitting lawmakers and journalists in 2024, a standoff that cost X its Brazilian revenue for months and froze Starlink’s local accounts before the investigation into Musk and X was closed in March with no evidence of wrongdoing found. X also sued California over a state law requiring moderation disclosures, arguing the mandate itself violated the First Amendment.
Whether India’s government pursues anything beyond a public statement remains to be seen. For now, the mismatch between what X can legally publish and what different governments legally allow it to publish is the real story behind Musk’s seven word claim.
