News
SpaceX Starship prototype in limbo after engine test lights rocket on fire
The fate of SpaceX’s fourth full-scale Starship prototype appears to be in limbo after a third (seemingly successful) engine ignition test unintentionally caught the rocket on fire.
Now more than 12 hours after Starship SN4 fired up its new Raptor engine, the ~30m (~100 ft) tall, 9m (~30 ft) wide prototype is apparently trapped with one or both of its propellant tanks still partially filled with liquid (or gaseous) methane and/or oxygen. An initial road closure scheduled from noon to 6pm local quickly came and went and SpaceX and Cameron County Texas have since modified the paperwork, extending the closure a full 24 hours. In other words, SpaceX has reason to believe that Starship SN4 may continue to be unsafe (i.e. pressurized) as many as ~30 hours after it technically completed its third static fire test – extremely unusual, to say the least.
There’s only one obvious conclusion to draw. Whether it was something invisible to the public eye or damage related to the off-nominal fire that burned for some 15 minutes after Raptor shut down, SpaceX appears – to some extent – to have lost control of Starship SN4.
At the moment, it’s unclear what is wrong and what SpaceX is attempting to do to resolve the problem. Based on photos of Starship SN4 taken before the fire, there is good news and bad news from what can be publicly ascertained. Controlled from the ground by unprotected wires strung up and down the rocket and connected at its base, the uncontrolled fire that burned in at least two locations around Starship’s aft may have severed some or all of those critical connections.
That would render Starship – potentially perfectly healthy and operational – almost entirely uncontrollable, while also potentially removing SpaceX’s access to telemetry. In other words, the company may currently have no idea how pressurized all or part of Starship SN4 is and may also have little to no control of some or all of the rocket. For that to be true, Starship SN4 would, however, have to have less than fully redundant control hardware. To perform hops, for example, the ship would need both wired and radio links capable of sending telemetry and receiving commands to remain both on the ground and after liftoff.
It’s possible that Starship SN4 has the necessary hardware installed but that it wasn’t activated for the static fire test (think “Starship will never leave the ground, why would we need to enable wireless controls?”). It’s also possible that the blown pipe and methane leak that appeared to cause the secondary fire damaged crucial propellant management hardware (valves, pumps, etc.) or was just a symptom of an even worse overpressure event that damaged or destroyed multiple such systems.
Given that safety is almost certainly the priority, chances are that some combination of fairly mild hardware failure and telemetry/control loss has left SpaceX with just enough uncertainty that it can’t risk sending technicians to the launch site to inspect the damage and reestablish control. As a result, the only option left is to quite literally sit and wait until it’s once again safe to approach the rocket. Thankfully, at this point, the risk of the mystery problem actually destroying Starship SN4 is very low. If, as it appears, only its methane tank is affected, leaving some unknown quantity of latent liquid methane trapped inside, it’s possible that waiting will actually solve the problem and safe the rocket.
The fact that Starship hasn’t exploded yet strongly implies either that the amount of propellant trapped is minuscule or that the vast majority of SN4’s propellant management systems (including vents) remain functional. Assuming that’s the case, any remaining cryogenic propellant will eventually boil into gas, increasing the pressure inside Starship’s tanks, while those tanks will continue to vent to prevent an explosion or rupture. Eventually, Starship SN4 will be empty once again and SpaceX will be able to approach the rocket to regain control and begin inspections and repairs.
Regardless, after such an unintentionally eventful static fire test, it’s extremely unlikely that SN4 will be ready for its inaugural flight test within the next few days. Stay tuned for updates as SpaceX works to regain control over the fourth full-scale Starship prototype.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
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.”
Tesla wins FCC approval for wireless Cybercab charging system
Tesla posts updated FSD safety stats as owners surpass 8 billion miles
