News
SpaceX wiggles Starhopper’s Raptor engine, tests parts ahead of hover test debut
On the evening of July 12th, SpaceX technicians put Starhopper’s freshly-installed Raptor – serial number 06 (SN06) – through a simple but decidedly entertaining test, effectively wiggling the engine in circles.
Designed to verify that Raptor’s thrust vectoring capabilities are in order and ensure that Starhopper and the engine are properly communicating, the wiggle test is a small but critical part of pre-flight acceptance and a good indicator that the low-fidelity Starship prototype is nearing its first hover test(s). Roughly 48 hours after a successful series of wiggles, Starhopper and Raptor proceeded into the next stage of pre-flight acceptance, likely the final more step before a tethered static fire.
Routine for all Falcon rockets, SpaceX’s exceptionally rigorous practice of static firing all hardware at least once (and often several times) before launch has unsurprisingly held firm as the company proceeds towards integrated Starhopper and Starship flight tests. Despite the fact that Raptor SN06 completed a static fire as recently July 10th, SpaceX will very likely put Starhopper and its newly-installed Raptor through yet another pre-flight static fire, perhaps its fourth or fifth test this month.
Although it would undoubtedly be easier, cheaper, and faster to skip that post-delivery static fire, it will simultaneously lower the risk of Raptor failing mid-flight and verify that Starhopper itself is healthy and ready for untethered hovering. Although SpaceX could likely live without Starhopper in the event that it’s lost during flight-testing, any failure capable of destroying the vehicle itself is at least as capable of severely damaging or completely destroying the spartan but still expansive test and launch facilities the company built over the course of several months.
Would you like some testing with your testing?
Follow July 12th’s nighttime Raptor wiggle test, July 13th was mainly quiet and filled with inspections of Starhopper, Raptor, and other various work. The day after, however, SpaceX proceeded through several hours of propellant loading, ending with what looked like less energetic versions of the Raptor preburner ignition tests Starhopper previously performed with Raptor SN02.
In a staged-combustion engine like Raptor, getting from the supercool liquid oxygen and methane propellant to 200+ tons of thrust is quite literally staged, meaning that the ignition doesn’t happen all at once. Rather, the preburners – essentially their own, unique combustion chambers – ignite an oxygen- or methane-rich mixture, the burning of which produces the gas and pressure that powers the turbines that bring fuel into the main combustion chamber. That fuel then ignites, producing thrust as they exit the engine’s bell-shaped nozzle.
Although the fireworks are so subtle that they are easily missed, the conditions inside the preburner – hidden away from view – are actually far more intense than the iconic blue, purple, and pink flame that exists Raptor’s nozzle. This is because the preburners have to nurture the conditions necessary for the pumps they power to fuel the main combustion chamber. Much like hot water will cool while traveling through pipes, the superheated gaseous propellant that Raptor ignites to produce thrust will also cool (and thus lose pressure) as it travels from Raptor’s preburner to the main combustion chamber.
Thus, if the head pressure produced in the preburners is too low, Raptor’s thrust will be (roughly speaking) proportionally limited at best. At worst, low pressure in the preburners can completely prevent Raptor from starting and running stably and can even trigger a “hard start” or shutdown that could damage or destroy the engine. As such, to preburners fundamentally have to operate at higher chamber pressures (and thus higher temperatures) than the main combustion chamber (the big firey bit at the end). According to Elon Musk, Raptor’s oxygen preburner has the worst of it, operating at pressures as high or higher than 800 bar (11,600 psi, 80 megapascals).
Coincidentally, this is roughly equivalent to the pressure at the bottom of the Pacific Ocean.
In short, preburner testing is no less critical than full-on static fire testing with an engine like Raptor. July 14th’s test was also made doubly efficient due to the fact that preburner testing requires liquid propellant, which effectively makes the whole test a wet dress rehearsal (WDR) even before any engine ignition or partial ignition is involved. Per SpaceX moving from propellant loading to preburner/turbine testing, Starhopper is almost certainly healthy and operating as expected, an excellent sign that the ungainly vessel may be ready for a static fire of Raptor as early as 2pm CT, July 15th.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
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.
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.
Tesla is beginning to roll out Full Self-Driving Supervised v14.3.9 with a new active safety layer that can take control even when the driver is operating the car manually.
Tesla AI said the software can activate FSD on the driver’s behalf when an imminent collision is detected and Automatic Emergency Braking may not be enough. It may also engage if the system detects heavy distraction or an accidental FSD disengagement.
FSD Supervised v14.3.9 starting to roll out shortly
This release includes a new active safety feature set: FSD Supervised can now activate on your behalf when an imminent collision is detected and Automatic Emergency Braking (AEB) may not be enough.
It may also engage if we…
— Tesla AI (@Tesla_AI) September 4, 2026
The capability is essentially Automatic Collision Evasion. However, unlike conventional AEB, which mainly applies the brakes in a straight line, this feature can use steering, braking, and acceleration together if the car calculates that stopping alone will not prevent impact and a safer path exists. The system may change lanes or move toward a shoulder when conditions allow, then continue driving after the immediate threat is handled rather than simply coming to a stop.
The intervention is meant as a last-resort safety net, not a replacement for attentive driving.
Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident
Tesla’s own description still frames FSD as supervised assistance. Secondary reports on internal release notes say the feature can fire while the car is being driven manually if cabin-camera monitoring suggests the driver is not sufficiently attentive, such as reaching toward the back seat, or if FSD appears to have been turned off unintentionally.
After the emergency maneuver, the car is expected to alert the driver and request a return to manual control.
The safety case is straightforward. Many collisions happen in the last second because a driver is looking away, fumbles a control, or faces an obstacle that braking cannot fully solve. A system that can both recognize that AEB is insufficient and execute a coordinated evasive path can reduce those remaining high-severity events.
Re-engaging after accidental disengagement also addresses a practical failure mode: a small steering nudge that drops FSD at the worst moment. The advantage is a background safety net that uses the same vision stack already running in v14, instead of leaving the car solely to emergency braking once the driver is no longer in command.
The feature still depends on FSD being enabled and, according to reports, an active FSD purchase or subscription. It does not make the vehicle unsupervised. Drivers remain responsible, and Tesla has not published how often the system is expected to intervene or how it will handle false positives.
If the rollout is conservative and the false-alarm rate stays low, the update is a meaningful step: FSD is no longer only a feature the driver turns on. In the rare moments when disaster is already forming, it can step in.
Tesla crosses major Unsupervised Self-Driving milestone
Tesla Robotaxi will be a 24/7 service: here’s when
