News
SpaceX’s orbital Starship prototype sheds tiles, comes to life during first tests
After weeks of mostly invisible – albeit slow and steady – work at Starbase’s suborbital launch and test facilities, SpaceX has finally kicked off the first orbital Starship prototype’s first test campaign.
Almost two months ago, Starship 20 (S20) departed the factory it was built in for the first time and was rolled a few miles down a South Texas highway to Starbase’s nascent orbital launch site. There, SpaceX briefly installed Ship 20 on top of Super Heavy Booster 4 (B4) – an important first and one done with the same ship and booster pair CEO Elon Musk says could eventually support the rocket’s inaugural orbital launch attempt. Mere hours after that August 6th photo opportunity and fit test, Ship 20 was rolled back to the Starbase build site for another week of work before again returning to the launch site.
This time around, Starship S20 headed for one of two suborbital launch and test stands and ultimately spent the better part of the next six weeks sitting in place as workers swarmed around the 50m (~165 ft) tall spacecraft and upper stage to prepare it for the next steps. In theory, those steps were simple enough, beginning with the completion of two basic qualification tests – the same tests that a half-dozen prototypes preceding Ship 20 completed without issue.
Effectively SpaceX’s first Starship or Super Heavy test of any kind in more than two months, it thankfully didn’t take long for things to get interesting. Before the pad had even been cleared of the last few remaining workers, Starship S20 violently shed a good dozen or so fragile heat shield tiles. CEO Elon Musk quickly confirmed speculation that Starship S20 had effectively jetted the tiles off its nose during a brief test of high-pressure cold gas maneuvering thrusters, coincidentally around the same time as SpaceX began to pressurize the rocket for its first tests.
Going into what was believed to be Starship S20’s first ambient-temperature pressure test and cryogenic proof test, the loss of some heat shield tiles was almost universally expected. In a structure as large as Starship, even just the thermal contraction of steel at supercool temperatures (and expansion as it warms back up) could change the rocket’s diameter an inch or so, potentially causing tiles to scrape or press against each other. About the size of a dinner plate and the thickness of an average paperback book, Starship’s ceramic heat shield tiles have proven to be very fragile, with dozens routinely chipping, cracking, and shattering during and after installation on Ship 20.
One unique (and no less unproven) aspect of Starship is SpaceX’s decision to mount its heat shield directly to the thin steel propellant tanks and skin that make up the rocket’s entire airframe. SpaceX’s first stab at the problem involves studs/pins welded – by robot – directly to the exterior of Starship’s tanks and skin. By embedding small metal plates inside each cast tile, they can be easily installed by aligning the tile and pressing it against each set of three barb-like pins, which then irreversibly lock in place. Over most of Starship’s hull, SpaceX then tacks on blankets of off-the-shelf ceramic wool insulation before tiles are installed on top of that steel and blanket sandwich. Compared to the Space Shuttle and Russia’s Buran, the only other orbital spacecraft to fly with non-ablative heat shields, Starship’s thermal protection system (TPS) is incredibly simple. Of course, the challenges imposed on heat shields by mechanical stresses during launch/landing, orbital reentry, and a need for rapid reusability are anything but simple.
As such, to see tiles blown off Starship S20 by cold gas maneuvering thrusters that were simply placed too close to adjacent TPS was an unexpected route to an expected outcome. During Monday’s nine-hour test window, SpaceX appeared to partially or fully pressurize Starship S20 at ambient temperatures before aborting a cryogenic proof test either before or just after it began. While an ambient-temperature proof was the easier of the two tests on the docket, it’s still encouraging to see no obvious tile loss caused by the actual mechanical stresses involved in the test.
Most importantly, compared to losing dozens of tiles to regular mechanical or thermal stresses, fixing an issue with thruster impingement is much easier and should only require a few design tweaks to one specific Starship component. The real nail-biting moments will come during Starship S20’s seemingly imminent cryogenic proof and static fire debuts, major TPS issues during either of which could necessitate vehicle-wide design changes and cause delays.
With any luck, whatever forced SpaceX to abort Starship S20’s first cryogenic proof test can be easily rectified, opening the door for additional attempts. Two more test windows are scheduled later this week from 5pm to 11pm CDT on Tuesday and Wednesday. Rewatch today’s brief testing below.
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
