Connect with us

News

SpaceX shuffles Starships, gears up for more Super Heavy static fires

Published

on

SpaceX is busy preparing for the orbital launch debut its next-generation Starship rocket, but the company’s South Texas rocket factory is also working around the clock to prepare several more sets of ships and boosters for the flight testing that will follow.

That was more obvious than usual on November 8th, when SpaceX made moves to prepare both of its finished Starships for new phases of testing. SpaceX kicked off the busy day by removing Starship S25 – a newer prototype that arrived at the launch site just three weeks prior – a stand dedicated to proof testing ships. Three hours later, after spending three of the last four weeks sitting on top of Super Heavy Booster 7, Starship S24 was ‘destacked’ (lifted off of B7 and lowered onto a stand on the ground) in the early afternoon.

Booster 7, Ship 24, and Ship 25 have all been busy since mid-October. SpaceX stacked Booster 7 and Ship 24 for the first time on October 11th and then attempted to test the fully-stacked rocket on October 13th. By some accounts, although almost nothing was visible to the public, the first full-stack test may have gone poorly, potentially even endangering pad technicians that approached the rocket to troubleshoot. On October 16th, SpaceX fully destacked Ship 24, and CEO Elon Musk noted that the company was “proceeding very carefully” to avoid an explosion that could set “Starship progress back by ~6 months.”

But if there was a major issue on October 13th, SpaceX didn’t show it, and Ship 24 was reinstalled atop Booster 7 on October 20th without any obvious maintenance or repairs. SpaceX then kicked off an unusual series of tests on October 24th, during which it only filled the liquid oxygen (LOx) or liquid methane (LCH4) tanks of Super Heavy B7, Ship 24, or both vehicles at once. A rare NASA briefing on October 31st later called them “single-species prop[ellant]” tests – a kind of extra-cautious testing that had never been seen before at Starbase. A few days prior, a member of NASA’s Aerospace Safety Advisory Panel (ASAP) noted that an accidental explosion that damaged Booster 7 in July had caused SpaceX to “increase [the rigor of its] systems engineering and risk management,” explaining the sudden influx of unusually conservative testing.

By the time Ship 24 was destacked from Booster 7 on November 8th, SpaceX had completed seven single-species tests, four of which involved loading LOx or LCH4 into both stages and three of which only tested Super Heavy. Booster 7 and Ship 24’s tanks were fully filled and LCH4 and LOx were never simultaneously loaded on either stage.

NASA’s October 31st briefing reported that SpaceX had plans to destack Ship 24 before conducting additional static fire testing with Booster 7. While B7 completed 1, 3, and 7-engine static fires in August and September, those tests were nowhere close to the full 33-engine static fire required to properly qualify the most powerful rocket in history. According to NASASpaceflight.com managing editor Chris Bergin, SpaceX’s next goal is to fire up approximately half of Super Heavy B7’s Raptors.

Advertisement
-

Strangely, although Ship 24 was believed to have completed all of the standalone testing needed to clear it for flight, SpaceX installed the vehicle on a stand used for Starship static fire testing on November 9th, implying that more standalone testing may be required. For now, that shouldn’t pose a problem as long as SpaceX wraps up any additional Starship testing around the same time as Booster 7’s next static fire campaign wraps up, but it could delay full-stack launch readiness if it takes any longer.

Finally, after Ship 25 was removed from SpaceX’s other Starship test stand on November 8th, it was rolled back to Starbase’s Starship factory. Ship 25 first rolled to the launch site on October 19th and has since completed four visible tests. On October 28th, Ship 25 survived a pneumatic proof test that showed that its tanks were leak-free and capable of surviving flight pressures (roughly 6-8.5 bar or 90-125 psi). Three cryogenic proof tests followed on November 1st, 2nd, and 7th. The first cryoproof was likely just that – a test that pressurized Ship 25’s tanks and filled them with cryogenic liquid nitrogen (LN2) or a combination of liquid oxygen and LN2.

The next two tests likely took advantage of the customized test stand, which has been semi-permanently outfitted with a set of hydraulic rams that allow SpaceX to simulate the thrust of six Raptor engines while Starship’s structures are chilled to cryogenic temperatures and loaded with roughly 1000 tons (~2.2M lb) of cryogenic fluids. If a Starship can survive those stresses on the ground, the assumption is that it will likely survive similar stresses in flight.

Assuming that Ship 25’s first several proof tests were successful, which they appear to have been, SpaceX returned the prototype to its Starbase factory to install six Raptor engines and a series of shields and firewalls that will protect those engines from each other. Once fully outfitted, Ship 25 will return to the launch site for static fire testing and take Ship 24’s place on Suborbital Pad B. Ship 24 took approximately two months to go from its last cryoproof to its first static fire. But its testing got off to a relatively rocky start, so Ship 25 could be ready sooner.

SpaceX could begin the next phases of Booster 7 and Ship 24 testing as early as November 10th or November 13th.

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

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