Connect with us

News

SpaceX Starship hop debut aborted at the last second by Raptor engine

A SpaceX Starship prototype was forced to automatically abort a hop debut milliseconds before liftoff. (SpaceX)

Published

on

SpaceX’s full-scale Starship hop debut was aborted at the last second after an otherwise successful lead-up to the milestone, forcing the company to try again tomorrow.

Following a minor delay from August 2nd to August 3rd, SpaceX kicked off Starship SN5’s hop debut preparations relatively late into the 12-hour window, closing the highway and clearing the pad around 5pm CDT (22:00 UTC). The Starship SN5 tank section prototype was pressurized with ambient-temperature gas around the same time, while cryogenic liquid methane and oxygen propellant loading appeared to begin at roughly 6:20pm CDT (23:20 UTC).

Soon after, SpaceX CEO Elon Musk revealed that Starship was just 33 minutes away from launch, marching towards the first hop of a full-scale prototype at 6:56pm CDT. Unfortunately, possibly much less than a second before ignition, Starship SN5’s Raptor engine had different plans.

Musk says that one of Raptor engine SN27’s “spin start valves” failed to open moments before ignition, causing Starship to automatically abort the attempt. With more than an hour left in the window, SpaceX had time to briefly troubleshoot the bug and potentially turn the rocket around for a second attempt, but Musk announced some 50 minutes later that the company would stand down and try again tomorrow.

Advertisement

Musk’s description of the hop test abort sounds suspiciously similar to his description of the last abort of Starship SN5’s Raptor engine static fire test, in which a “fuel spin valve didn’t open.” If the root cause of both aborts is the same, there’s a good chance that SpaceX may need more time to properly investigate and fix the problem. A recurring issue is immediately much more concerning compared to a one-off bug, so there’s also a chance that SpaceX will go as far as replacing the Raptor engine currently installed on Starship SN5.

Raptor SN27 was installed on Starship SN5 around July 3rd or 4th. (NASASpaceflight – bocachicagal)

If things look more severe than SpaceX initially thought they were after the static fire abort and a replacement engine is necessary, Starship SN5 will have to complete another static fire test with the new Raptor before it can proceed to a second hop attempt.

Based on live views of the launch attempt from NASASpaceflight and LabPadre, Starship SN5 likely aborted a matter of milliseconds before Raptor SN27 ignition and perhaps just a second or two before liftoff. Just like SpaceX’s workhorse Falcon 9 and Heavy rockets, the vehicle’s flight computer is fully in control of the countdown a minute or two before liftoff and can automatically abort far faster than any human could possibly react. Held to the launch mount by hold-down clamps, Starship could have technically analyzed the engine’s performance after ignition and aborted the launch even later into the count.

Once hold-down clamp release is commanded, Starship SN5 will attempt to fly a roughly 150m-tall (500 ft) arc heading southeast of the launch mount. Perhaps 10 seconds prior to touchdown, Starship will attempt to deploy an array of six odd legs and gently land a few hundred feet from the pad. As of now, assuming Raptor’s finicky valve can be easily rectified, SpaceX will work towards a second Starship SN5 hop attempt sometime between 8am and 8pm CDT on Tuesday, August 4th.

Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.

Advertisement

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

Advertisement
Comments

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.

Published

on

Credit: Tesla AI/X

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).”

Advertisement

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.

Advertisement

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.

DA-26-168A1 by Simon Alvarez

Advertisement
Continue Reading

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.

Published

on

Credit: Tesla

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.

Advertisement

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.

Advertisement
Continue Reading

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.

Published

on

The-boring-company-vegas-loop-chinatown
(Credit: The Boring Company)

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. 

Advertisement

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.”

Advertisement
Continue Reading