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!
Elon Musk
Tesla Cybercabs narrowly miss deadly Amazon cargo plane crash
An Amazon cargo plane crash near Miami’s airport stopped feet from dozens of Tesla Cybercabs.
An Amazon Prime Air Boeing 767 cargo jet overran the runway at Miami International Airport on Sunday afternoon, killing five people and injuring five more. The jet, operated by North Carolina based carrier 21 Air as Flight 7598, touched down around 2 p.m. after arriving from San Juan, Puerto Rico, then crossed the airport perimeter, plowed across NW 67th Avenue and struck multiple vehicles before catching fire, according to the Associated Press.
Photos and video from the scene show the aircraft’s nose stopped within meters of a fenced staging lot holding dozens of gold painted Tesla Cybercabs, the steering wheel free robotaxi Tesla began putting on public roads in Austin last week. Miami-Dade Fire Rescue has confirmed the plane struck “multiple vehicles” but has not said whether any Cybercabs were among them, and neither Tesla nor airport officials have addressed the fleet directly.
The Cybercabs had not yet entered commercial service in Miami. Tesla’s existing Robotaxi operation there runs on modified Model Y vehicles and has been unsupervised since Ashok Elluswamy confirmed the detail on X in July.
Footage of the plane crash from earlier today | #ONLYinDADE pic.twitter.com/iGoOtnd6cD
— ONLY in DADE (@ONLYinDADE) September 6, 2026
Elon Musk offered the briefest of reactions. Replying to a Zero Hedge post about the Cybercabs sitting so close to the wreckage, he wrote a single word: “Weird.” He has not commented further, and Tesla has not issued a statement.
The timing puts Tesla’s newest vehicle near an unrelated but highly visible tragedy just days after its Austin debut, a launch that had already drawn scrutiny from federal regulators. The National Highway Traffic Safety Administration opened an audit how Tesla certified the Cybercab as compliant with federal vehicle safety standards, a process Teslarati covered after the vehicle’s September 3 launch event. That inquiry concerns the car’s lack of a steering wheel and pedals, not the Miami crash.
Investigators from the FAA and NTSB are focused on the plane, not the parking lot beside it. Flight data reviewed by outlets including Simple Flying show the 767 touched down around 170 knots, well above the 135 to 140 knot range typical for the aircraft, though investigators have not determined a cause. Amazon said it is working with authorities and that its priority is the safety of everyone affected.
Whether any Cybercabs were damaged, and what Tesla plans for the fleet parked near one of the country’s busiest airports, remain open questions.
News
Tesla crosses major Unsupervised Self-Driving milestone
Tesla has reached a notable benchmark in its autonomous driving program after its Robotaxi fleet surpassed one million miles of unsupervised operation. The company made the announcement during its Cybercab event in Austin on September 3.
Tesla Vice President of AI Ashok Elluswamy told attendees he was happy to report the fleet had achieved one million miles of unsupervised Robotaxi operation as a testament to safety.
The new total marked a sharp increase from the 380,000 unsupervised miles Tesla disclosed during its second-quarter 2026 earnings update in late July.
In roughly six weeks, the company added about 620,000 miles. That acceleration followed Tesla’s decision to remove in-vehicle safety monitors from most of its operations outside the San Francisco Bay Area.

Credit: Tesla
Tesla first launched Robotaxi service in Austin in June 2025 with safety drivers present. It later began fully unsupervised rides and expanded into Dallas, Houston, Miami, Orlando, and Tampa. The San Francisco Bay Area remains the exception, where a safety monitor still rides in the vehicle under California permitting rules.
The company has not released a city-by-city breakdown of the one million unsupervised miles.
The milestone arrived as Tesla began offering public Cybercab rides in Austin. The purpose-built vehicle has no steering wheel or pedals and is designed only for autonomous ride-hailing. Production versions joined the existing fleet of modified Tesla vehicles already operating in the service.
Tesla’s unsupervised mileage is growing at a double-digit weekly rate according to earlier company comments, yet its fleet size remains modest compared with established competitors. Waymo has accumulated more than 200 million fully autonomous rider-only miles. Tesla has described its own unsupervised operations as having recorded zero notable incidents in the period leading up to the July update.
The one-million-mile figure reflects Tesla’s shift from supervised testing to broader driverless service in multiple states. It also highlights the company’s strategy of using both existing Model Y vehicles and the new Cybercab to scale its network.

Credit: Tesla
Whether the rapid recent growth continues will depend on further city expansions, regulatory approvals, and the performance of the purpose-built Cybercab in everyday paid rides. Tesla has not specified how many of the latest miles involved the new vehicle versus the rest of the fleet.
The announcement underscores Tesla’s progress toward a larger robotaxi network while illustrating the remaining gap in total autonomous experience relative to longer-operating rivals.
News
Tesla Robotaxi will be a 24/7 service: here’s when
Tesla AI lead Ashok Elluswamy said this week that 24-hour Robotaxi service is close. Replying on X to a rider who wanted Cybercab trips all night, he wrote that the capability would arrive “next month or so” once “the next tech to merge on the v15 plan” is ready.
The comment landed on September 4, one day after Tesla opened public Cybercab rides in Austin. It is the clearest near-term timeline yet for overnight unsupervised operation. Tesla’s paid Robotaxi network currently runs from 6 a.m. to 10 p.m. seven days a week across Austin, Dallas, Houston, Miami, Orlando, and Tampa.
next month or so. the next tech to merge on the v15 plan will enable it.
— Ashok Elluswamy (@aelluswamy) September 4, 2026
That 16-hour window is shorter than the 6 a.m. to 2 a.m. schedule the company used for much of the prior year.
Elluswamy did not name the specific feature or say whether the change would apply first to purpose-built Cybercabs, the existing Model Y fleet, or both. He also offered no city-by-city rollout list. The link to Full Self-Driving v15 is nevertheless significant.
Tesla has described v15 as a step-change architecture with seven parallel improvement tracks and roughly ten times more parameters than earlier builds. Early versions of that software already operate on the Robotaxi fleet and contain about 40 percent of the planned gains.
By July 2026, the unsupervised fleet had logged more than 380,000 miles across six cities in two states with what the company called an impeccable safety record and no notable incidents caused by the vehicles themselves. Tesla has repeatedly argued that camera-based end-to-end neural networks, rather than extra sensors, are the core of the solution.
Overnight service would test that claim in lower-light conditions and would also raise vehicle utilization, a key variable for Robotaxi unit economics. The company has already begun using public Superchargers at night and is building dedicated Robotaxi charging sites.
Riders have asked why software must change if the cars already drive in the dark. The practical answer appears to be reliability and scale: Tesla has held back mass expansion until more of the v15 stack is merged, citing the need for higher confidence before putting thousands of unoccupied vehicles on streets around the clock.
If the next module arrives on the timetable Elluswamy sketched, 24-hour service could begin in October 2026 in at least some markets.
That would mark a shift from a daytime-bounded pilot to a service that can run whenever demand exists, including the late-night hours that have so far remained out of reach.




