News
SpaceX Starship outfitted with Tesla battery packs and motors
Following in the footsteps of the late Mk1 vehicle, SpaceX’s latest Starship prototype has been outfitted with several Tesla battery packs and motors over the last few weeks.
CEO Elon Musk has confirmed in the past that SpaceX intends to try to use Tesla batteries to power Starship rockets and Tesla motors to drive the ships’ large aerodynamic control surfaces. By all appearances, a Tesla Model S motor’s appearance on the exterior of a Starship prototype recently moved to the launch pad is a first for SpaceX. However, in 2019, SpaceX at one point planned to use and even installed battery packs on Starship Mk1 components before the ship was prematurely destroyed during testing. The nosecone those battery packs were installed in still sits in the middle of SpaceX’s growing Boca Chica rocket factory.
For Starship SN3, the purpose of its ~200 kWh of battery power is rather self-explanatory. The purpose of the Tesla Model S motor recently installed on its side is much less clear.
SpaceX is in the midst of preparing Starship SN3 for its first tests after assembling the rocket from next to nothing in less than a month. SpaceX transported the building-sized prototype a mile down the road to its Boca Chica launch site on March 29th, where dozens of workers have been poring over it day and night ever since. SpaceX originally wanted to attempt the ship’s first two tests yesterday, April 1st, but the scheduled times have come and gone while work continues. Several backup windows are ready on April 2nd, beginning shortly before this article went live (1am CDT, 06:00 UTC).
Regardless, with any rocket prototype, test schedules can be extremely fluid and are always liable to change. While SpaceX relies heavily on agile development strategies, beginning with a minimum viable product and iterating to something approaching feature-complete, there is some value in not turning the “move fast and break stuff” dial to 100%. In the case of Starship, the equivalent of tens to hundreds of thousands of work hours and several million dollars of hardware go into each prototype – incredibly cheap on the scale of aerospace development norms but still a significant chunk of change and effort. A few days or weeks of delays are an annoyance that can be suffered if it better guarantees a successful test, versus the alternative of potentially rushing and cutting corners.
SpaceX is now up to roughly five days of delays while preparing Starship SN3 for testing. Originally scheduled as early as April 1st, SpaceX has moved a planned Raptor engine static fire test to no earlier than (NET) April 6th, to be followed no fewer than several days later by a 150m (500 ft) hop test. Of course, before it can safely attempt its first static fire (or hop), SpaceX needs to verify that Starship SN3 – finished just days ago – is up to the task.
Enter Tesla hardware. During ground testing, Starship will likely be continuously connected to ground power sources. It’s also possible that SpaceX has chosen to use its Tesla battery packs as the main power source to insulate it from local outages. Either way, if or when Starship SN3 makes it to flight tests, the battery packs would power the ship’s onboard avionics, landing legs, and any other necessary equipment. That latter category may be where Starship’s apparent Model S motor comes in.
While it could simply be an early implementation test of the Tesla motors SpaceX wants to use to actuate Starship flaps and fins, there are no signs that SN3 will be outfitted with updated flaps and aerodynamic control surfaces more generally. For low-velocity testing, they’re simply unnecessary. Instead, it’s more likely that this Tesla motor is somehow involved in Starship’s autogenous pressurization system, a method of pressurizing tanks with the liquids they contain. Autogenous pressurization relies on a small portion of propellant (liquid oxygen and methane for Starship) being siphoned off and heated until it turns to gas. That oxygen or methane gas is then fed back into the tank it came from, keeping it at the pressure needed to feed Starship’s Raptor engines.
Autogenous pressurization is significantly more complex than the far more common use of helium or nitrogen pressurization systems. An electric pump could potentially be useful at several points throughout the process. Pump mystery aside, tune in to LabPadre’s 24/7 livestream below to follow along as SpaceX prepares to put Starship SN3 to the test for the first time.
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
