News
SpaceX’s first orbital Starship prototype prepares for proof tests
Several days after SpaceX’s first orbital-class Starship prototype took a second trip to a nearby launch site, the rocket is on its way to one of two suborbital launch mounts.
Once installed on the steel structure, Starship prototype 20 (S20) will finally be ready for – at minimum – two crucial tests: a cryogenic proof and static fire. According to highway closures filed by SpaceX late last week, the first of those tests could apparently begin as early as Thursday, August 19th, potentially setting Starship S20 up to attempt at least one major milestone next week.
On August 13th, SpaceX rolled Starship S20 back to the launch site a week after the rocket was sent to the pad to be briefly stacked on top of a Super Heavy booster – an event that appears to have been something like 50% photo opportunity, 50% test objective. Neither the booster or ship were fully complete at the time and both ultimately required at least another week or two of outfitting and plumbing to be ready for ground testing – let alone flight. Aspirationally, the same pair – Ship 20 and Booster 4 – could be the first to attempt a true orbital Starship launch sometime later this year.
Since its second rollout, Ship 20 has more or less stayed in one place as workers continuously swarmed about the rocket on boom and scissor lifts. Over the last four days, not much has visually changed save for the installation of a handful of heat shield tiles, but the focus clearly centered around the Starship’s ‘raceway’ – a clutch of plumbing and wiring that runs most of the length of the vehicle’s back. Virtually all rockets have them and Starship is no different with a raceway packed with avionics wire runs, plumbing for propellant loading, and smaller lines for pressurization and hydraulics.
While it’s not entirely clear what specific work has been done over the last few days or why it wasn’t done back at the build site, where CEO Elon Musk himself has said such tasks are more easily done, it’s clear that Starship S20 does have a more refined raceway than any ship before it. In recent days, SpaceX has also begun to install structural elements that strongly imply that S20 will be the first Starship to receive a raceway aerocover – not unlike those on Falcon boosters – to protect its external wiring and plumbing in flight.

Regardless, once Starship S20 is installed on one of SpaceX’s two suborbital launch mounts, the vehicle will most likely be prepared for a routine cryogenic proof test. To pass, Starship will need to survive significant thermal and mechanical stress as its tanks are filled with supercool liquid nitrogen and pressurized to at least 6 bar (~90 psi). At this point, a Starship prototype hasn’t failed a cryo proof in more than a year, so the test should be fairly routine.
Curiously, after spending weeks modifying Mount B with a series of hydraulic rams meant to simulate the thrust of Ship 20’s six Raptor engines during its cryo proof(s), SpaceX removed all of that extra hardware just prior to the Starship’s second rollout and now-imminent installation on said mount. Regardless of why, that decision likely means that Starship S20 will move directly to static fire testing once it passes cryo proofing. Given that Ship 20 appears to be on track to be the first Starship prototype of any kind to fire more than three Raptors at a time, that static fire campaign will likely be somewhat cautious, possibly beginning with just 1-3 engines and then moving to four, five, or straight to six.
SpaceX could also throw caution to the wind (not implausible as evidenced by the removal of Pad B’s unused thrust rams) and install and attempt to fire all six Raptors immediately after Ship 20 completes a cryo proof. Based on road closures filed by SpaceX, that testing could begin as early as 5pm to 11pm CDT on Thursday, August 19th. A backup window is also scheduled from 6am to 12pm CDT on August 20th.
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.
News
Tesla Full Self-Driving will now overtake manual driving to avoid disaster
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.