News
SpaceX CEO Elon Musk arrives in Texas for milestone Starship engine test
On Saturday evening, SpaceX CEO Elon Musk landed in Waco, Texas – perhaps along with additional SpaceX propulsion engineers – for the critical static fire debut of the first “radically redesigned” Raptor engine, built to power BFR’s Starship upper stage and Super Heavy booster.
If the first operationalized Raptor’s static fire tests go well, there are several possible routes the test program could take, all of which will end up with this engine and several others being tested and ultimately installed on the Starship hopper (Starhopper) prototype under construction roughly 500 miles (800 km) south of SpaceX’s Raptor test cell.
At @SpaceX Texas with engineering team getting ready to fire new Raptor rocket engine pic.twitter.com/ACFM8AtY8w
— Elon Musk (@elonmusk) February 3, 2019
Shortly after Musk revealed official photos of the first operationalized Raptor preparing for an inaugural static fire test at SpaceX’s McGregor, Texas facilities, the SpaceX and Tesla CEO’s private jet was seen landing at Waco, Texas around sunset. Although all SpaceX technical expertise needed for Raptor’s first ignition was probably already on site several days prior, Musk has been known to offer seats on his private planes to SpaceX and Tesla employees when a critical group is needed away from their normal base of operations. The best examples come from Tesla engineering expertise sometimes traveling between Fremont and Gigafactory 1 when needed, often to solve production holdups.
Regardless of whether he was traveling with members of the SpaceX propulsion team, Musk’s arrival at McGregor yesterday signified that Raptor Block 1’s first integrated hot-fire was imminent. Assuming no attempt was made on Saturday night or Sunday morning, SpaceX technicians and engineers are presumably still working on installing what is effectively a new rocket engine and ensuring that Raptor’s test cells – extensively overhauled and upgraded for the occasion – are working as intended. While the development Raptors SpaceX built hovered around 1000 kN (~100t) of thrust, also roughly the same as Merlin 1D, the Raptor now on stand in Texas is reportedly a 200 ton-class engine or more than double the thrust of any single engine SpaceX engineers and technicians have built or test-fired in 15 years of engine development.
- The only official render of Raptor, published by SpaceX in September 2016. The Raptor departing Hawthorne in Jan ’19 looked reasonably similar. (SpaceX)
- Technically speaking, this Raptor is the smaller (sea-level) version of the engine. (SpaceX)
- SpaceX’s current Texas facilities feature a test stand for Raptor, the engine intended to power BFR and BFS to Mars. (SpaceX)
- A Raptor prototype is seen here during its first-ever ignition test. (SpaceX)
- A 2017 test-firing of the mature development Raptor, roughly 50% less powerful than the full-scale system. (SpaceX)
A fork in the R&D road
Prior to completing Raptor Block 1 (unofficial designation), SpaceX cumulatively test-fired dev Raptors for far more than 1200 seconds over the course of more than 24 months. It’s unclear how extensively the company’s engineers will be able to test the pathfinder hardware built on the back of that extensive test program. Nominally, one would expect hundreds or thousands of seconds of additional testing to properly characterize the design and production of a brand-new, optimized engine like Raptor while primarily ensuring that it performs within engineering specifications.
Knowing CEO Elon Musk’s self-admitted tendency to push for impractical deadlines and schedules that often appeared rushed for the sake of rushing, it’s not impossible that the first Raptors could find themselves installed on the Boca Chica-based Starhopper test article after Merlin-esque acceptance testing and nothing more. For M1D and MVac, acceptance testing usually takes the shape of a full-duration burn with throttle and gimbal activity to closely simulate a true Falcon 9 or Heavy launch. For the 200-ton Raptor now in Texas, comparable acceptance testing could take a variety of forms, ranging from short Starhopper-relevant burns (10-60 seconds for small hops) to simulating conditions during a Super Heavy launch and landing or even a 6 or 7-minute orbital insertion burn indicative of the performance needed for Starship.

Depending on the interplay between the route SpaceX engineers would likely prefer and the Starhopper test schedule executives and managers might want, this first Raptor engine (and two more soon to follow) could be installed on Starhopper anywhere from a few weeks to several months from now. Elon Musk indicated in early January that he expected hop tests would occur 4-8 weeks later, shortly followed by unplanned damage to the craft’s nose cone that pushed the debut back “a few weeks”.
Aiming for 4 weeks, which probably means 8 weeks, due to unforeseen issues
— Elon Musk (@elonmusk) January 5, 2019
I just heard. 50 mph winds broke the mooring blocks late last night & fairing was blown over. Will take a few weeks to repair.
— Elon Musk (@elonmusk) January 23, 2019
Realistically, hop tests should thus be expected to begin no earlier than (NET) 8-12 weeks from the first week of January, translating to NET March or April. This would give SpaceX propulsion engineers a decent amount of time to gain at least a few hundred (or maybe 1000+) seconds of experience operating the newest and most advanced iteration of Raptor.
Check out Teslarati’s newsletters for prompt updates, on-the-ground perspectives, and unique glimpses of SpaceX’s rocket launch and recovery processes!
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.
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 Tesla UI team absolutely crushed it with the infotainment software. Nicely done @CarCoder!
One feature request: Allow folks to pull up the rear & repeater cameras on demand. This would be great especially for peace of mind. https://t.co/mNAOSLx6pE
— Dan Burkland (@DBurkland) October 10, 2026
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.
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.
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.
One month after launch, we’ve scaled to 300+ Cybercabs serving Austin – an 8x increase in 30 days https://t.co/EagJy2JAsm
— Robotaxi (@robotaxi) October 10, 2026
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.
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.
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.
Dear Prime Minister Ambani,
Please accept my humble apologies for not realizing that you are the real boss of India.
Naturally, you would prefer to maintain your monopolistic exploitation of the great people of India, but would you nonetheless consider allowing Starlink to compete?
There are many areas of India, as there are in all countries, with no Internet access, which denies children the opportunity for education and for small businesses the opportunity to sell their goods to a global market. Starlink would change their lives for the better.
Thank you 🙏
— Elon Musk (@elonmusk) October 9, 2026
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.




