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.

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.

Advertisement
-

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.

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

Lifestyle

Tesla’s mirrorless Cybercab will give riders a visibility upgrade

Tesla engineer confirms Cybercab update letting riders pull up rear and repeater cameras on demand.

Published

on

By

Tesla Cybercab camera visibility for passengers (Credit: Dan Burkland via X)
Tesla Cybercab camera visibility for passengers (Credit: Dan Burkland via X)

Tesla is working on a Cybercab update that would let passengers pull up the vehicle’s rear and side cameras on demand, and the request came straight from a rider.

The exchange played out on X late Friday. Cybercab rider Dan Burkland shared photos of the two-seater’s cabin screen after an evening ride, praised the UI team’s work, and left one request: let riders open the rear and repeater cameras whenever they want, “especially for peace of mind.” Tesla UI software engineer Evan (@CarCoder) answered with two words: “In development.”

The idea fits a pattern Teslarati has tracked since public rides began. Days after paid Cybercab service opened in Austin, Tesla sent riders a survey that asked them to rate the touchscreen, the app and the cabin, and to pick the features they wanted most. We reported on that survey in September, and a camera view is the kind of small software change Tesla can push quickly if riders keep asking.

It also speaks to something unique about the vehicle. With no steering wheel, no pedals and no driver, passengers have no mirror to check and no way to see behind them. The hardware is clearly built for camera awareness, from the repeater cameras to the rear camera. Letting a passenger look through those same cameras would give a nervous first time rider a way to confirm what is around the car.

The timing matters because the fleet is growing fast. Tesla’s Robotaxi account said on Saturday that more than 300 Cybercabs are now serving Austin, an eightfold increase in 30 days, and Tesla AI chief Ashok Elluswamy named Dallas as the next city. More cars and more cities mean more people riding in a driverless vehicle for the first time, which is exactly when small trust features carry weight.

For now, the feature is confirmed only as in development. If Tesla follows its usual pattern with Cybercab software, riders could see it appear in a point release without any announcement, and Teslarati will watch for it.

Continue Reading

News

Tesla’s Cybercab fleet jumped 8x in a month, with Dallas up next

Tesla confirms its first official Cybercab fleet number as Austin scales fast and Dallas looms.

Published

on

By

Tesla says more than 300 Cybercabs are now serving Austin, the first time the company has put an official number on its active Cybercab fleet. The figure came from the Robotaxi account on X on Saturday, which wrote that one month after launch the service had “scaled to 300+ Cybercabs serving Austin – an 8x increase in 30 days.”

Ashok Elluswamy, Tesla’s head of AI software, quoted the post with a line that carried the bigger news. “Two years since the 10/10 Cybercab WeRobot event, the cabs are everywhere in Austin now. Dallas soon,” he wrote. It is the first time Tesla has named the next city for public Cybercab rides.

Tesla opened Cybercab rides to the public in Austin on September 4, as Teslarati reported, a day after an invite only launch event. The ramp since then has been steep. Our September 28 report had the fleet at well over 100 units after availability jumped from 58 to 125 in a single week. On Thursday, Tesla added 150 Cybercabs to the Texas automated vehicle registry, lifting its registered count to 319 from 169. The first seven appeared on the registry on August 31.

RobotaxiTracker, a community site that counts vehicles from sightings and state records, listed 275 vehicles in unsupervised service in Austin on Saturday, 105 of them Cybercabs, which is well below Tesla’s figure. Tracker counts can lag official numbers, though Sawyer Merritt noted that Cybercab wait times in Austin stayed short on Saturday evening even with more than 2,000 fans in town for X Takeover.

Regulators are watching the rollout. NHTSA opened an audit query into Tesla’s certification that the Cybercab meets federal safety standards, and sworn answers are due October 30. Tesla reports third quarter earnings on October 21, which gives the company a natural venue to define its fleet numbers and put a date on Dallas.

Continue Reading

Elon Musk

Elon Musk roasts India’s billionaire Mukesh Ambani as Starlink fight heats up

Elon Musk sarcastically calls Mukesh Ambani ‘Prime Minister’ as the Starlink India standoff escalates again.

Published

on

By

Elon Musk escalated his public fight over Starlink’s launch in India on Friday, addressing Reliance chairman Mukesh Ambani as “Prime Minister Ambani” in a sarcastic post on X. “Please accept my humble apologies for not realizing that you are the real boss of India,” Musk wrote, before accusing Ambani of “monopolistic exploitation” and asking whether he would “consider allowing Starlink to compete.” In follow up posts, he said Starlink has proven essential during natural disasters and would help parts of India with no internet access.

The post came two days into a fight that Musk sparked up on Wednesday, when he said Starlink was “being blocked by certain oligarchs in order to maintain their monopolistic chokehold on the Indian people.” He called it “a crime against the people of India” and left the names out, adding only, “You can guess who they are.” Jio and Airtel together hold more than 80% of India’s telecom market. On Thursday, Musk asked whether Ambani is “the real boss of India” and said Starlink has spent five years complying with “every single law and requirement” of the Indian government.

India’s government has pushed back each time. The Ministry of Communications called the suggestion that its framework is unfair or discriminatory “baseless and misconceived.” Communications Minister Jyotiraditya Scindia said Friday that three companies hold satcom licenses: Starlink, Jio Satellite Communications, and Bharti backed Eutelsat OneWeb. Amazon’s Kuiper, now Amazon Leo, is still going through the process. None can launch until regulators finalize satellite spectrum pricing and the Home Ministry signs off on each company’s security compliance. Scindia said the telecom regulator and the Department of Telecommunications are close to a decision on pricing, The Hindu reported. Bharti chairman Sunil Mittal also said OneWeb is still waiting on approvals.

Starlink received its operator license in 2025 after a three year wait, and the space regulator IN-SPACe granted what industry executives called the last approval needed in July. The holdup since then centers on security, particularly concern that foreign operators could bypass Indian gateways.

Musk and Ambani have been on opposite sides of this before. In late 2024, Ambani argued for auctioning satellite spectrum, which Musk criticized as out of step with the rest of the world, and India chose administrative allocation instead. By March 2025, the two sides had signed a deal to sell Starlink devices in Reliance stores, and Starlink secured its telecom license that June. That partner is now also a competitor. Jio is reportedly weighing a constellation of 1,600 to 1,650 satellites costing an estimated $10 billion to $15 billion, while Akash Ambani has told shareholders Jio plans to lease capacity from global providers to move quickly.

Continue Reading