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 wins FCC approval for wireless Cybercab charging system
The decision grants Tesla a waiver that allows the Cybercab’s wireless charging system to be installed on fixed outdoor equipment.
Tesla has received approval from the Federal Communications Commission (FCC) to use Ultra-Wideband (UWB) radio technology in its wireless EV charging system.
The decision grants Tesla a waiver that allows the Cybercab’s wireless charging system to be installed on fixed outdoor equipment. This effectively clears a regulatory hurdle for the company’s planned wireless charging pad for the autonomous two-seater.
Tesla’s wireless charging system is described as follows in the document: “The Tesla positioning system is an impulse UWB radio system that enables peer-to-peer communications between a UWB transceiver installed on an electric vehicle (EV) and a second UWB transceiver installed on a ground-level pad, which could be located outdoors, to achieve optimal positioning for the EV to charge wirelessly.”
The company explained that Bluetooth is first used to locate the charging pad. “Prior to the UWB operation, the vehicular system uses Bluetooth technology for the vehicle to discover the location of the ground pad and engage in data exchange activities (which is not subject to the waiver).”
Once the vehicle approaches the pad, the UWB system briefly activates. “When the vehicle approaches the ground pad, the UWB transceivers will operate to track the position of the vehicle to determine when the optimal position has been achieved over the pad before enabling wireless power charging.”
Tesla also emphasized that “the UWB signals occur only briefly when the vehicle approaches the ground pad; and mostly at ground level between the vehicle and the pad,” and that the signals are “significantly attenuated by the body of the vehicle positioned over the pad.”
As noted by Tesla watcher Sawyer Merritt, the FCC ultimately granted Tesla’s proposal since the Cybercab’s wireless charging system’s signal is very low power, it only turns on briefly while parking, it works only at very short range, and it won’t interfere with other systems.
While the approval clears the way for Tesla’s wireless charging plans, the Cybercab does not appear to depend solely on the new system.
Cybercab prototypes have frequently been spotted charging at standard Tesla Superchargers across the United States. This suggests the vehicle can easily operate within Tesla’s existing charging network even as the wireless system is developed and deployed. With this in mind, it would not be surprising if the first batches of the Cybercab that are deployed and delivered to consumers end up being charged by regular Superchargers.
Elon Musk
Tesla posts updated FSD safety stats as owners surpass 8 billion miles
Tesla shared the milestone as adoption of the system accelerates across several markets.
Tesla has posted updated safety stats for Full Self-Driving Supervised. The results were shared by the electric vehicle maker as FSD Supervised users passed more than 8 billion cumulative miles.
Tesla shared the milestone in a post on its official X account.
“Tesla owners have now driven >8 billion miles on FSD Supervised,” the company wrote in its post on X. Tesla also included a graphic showing FSD Supervised’s miles driven before a collision, which far exceeds that of the United States average.
The growth curve of FSD Supervised’s cumulative miles over the past five years has been notable. As noted in data shared by Tesla watcher Sawyer Merritt, annual FSD (Supervised) miles have increased from roughly 6 million in 2021 to 80 million in 2022, 670 million in 2023, 2.25 billion in 2024, and 4.25 billion in 2025. In just the first 50 days of 2026, Tesla owners logged another 1 billion miles.
At the current pace, the fleet is trending towards hitting about 10 billion FSD Supervised miles this year. The increase has been driven by Tesla’s growing vehicle fleet, periodic free trials, and expanding Robotaxi operations, among others.
Tesla also recently updated the safety data for FSD Supervised on its website, covering North America across all road types over the latest 12-month period.
As per Tesla’s figures, vehicles operating with FSD Supervised engaged recorded one major collision every 5,300,676 miles. In comparison, Teslas driven manually with Active Safety systems recorded one major collision every 2,175,763 miles, while Teslas driven manually without Active Safety recorded one major collision every 855,132 miles. The U.S. average during the same period was one major collision every 660,164 miles.
During the measured period, Tesla reported 830 total major collisions with FSD (Supervised) engaged, compared to 16,131 collisions for Teslas driven manually with Active Safety and 250 collisions for Teslas driven manually without Active Safety. Total miles logged exceeded 4.39 billion miles for FSD (Supervised) during the same timeframe.
Elon Musk
The Boring Company’s Music City Loop gains unanimous approval
After eight months of negotiations, MNAA board members voted unanimously on Feb. 18 to move forward with the project.
The Metro Nashville Airport Authority (MNAA) has approved a 40-year agreement with Elon Musk’s The Boring Company to build the Music City Loop, a tunnel system linking Nashville International Airport to downtown.
After eight months of negotiations, MNAA board members voted unanimously on Feb. 18 to move forward with the project. Under the terms, The Boring Company will pay the airport authority an annual $300,000 licensing fee for the use of roughly 933,000 square feet of airport property, with a 3% annual increase.
Over 40 years, that totals to approximately $34 million, with two optional five-year extensions that could extend the term to 50 years, as per a report from The Tennesean.
The Boring Company celebrated the Music City Loop’s approval in a post on its official X account. “The Metropolitan Nashville Airport Authority has unanimously (7-0) approved a Music City Loop connection/station. Thanks so much to @Fly_Nashville for the great partnership,” the tunneling startup wrote in its post.
Once operational, the Music City Loop is expected to generate a $5 fee per airport pickup and drop-off, similar to rideshare charges. Airport officials estimate more than $300 million in operational revenue over the agreement’s duration, though this projection is deemed conservative.
“This is a significant benefit to the airport authority because we’re receiving a new way for our passengers to arrive downtown at zero capital investment from us. We don’t have to fund the operations and maintenance of that. TBC, The Boring Co., will do that for us,” MNAA President and CEO Doug Kreulen said.
The project has drawn both backing and criticism. Business leaders cited economic benefits and improved mobility between downtown and the airport. “Hospitality isn’t just an amenity. It’s an economic engine,” Strategic Hospitality’s Max Goldberg said.
Opponents, including state lawmakers, raised questions about environmental impacts, worker safety, and long-term risks. Sen. Heidi Campbell said, “Safety depends on rules applied evenly without exception… You’re not just evaluating a tunnel. You’re evaluating a risk, structural risk, legal risk, reputational risk and financial risk.”