News
SpaceX to put custom Starship propellant storage tanks through first trial
In the latest twist in the saga of SpaceX’s custom-built Starship launch pad propellant storage tanks, the company appears to have retroactively decided to build small prototype meant solely for testing.
Known as a ‘test tank,’ the relatively small steel structure was fairly rapidly assembled from parts of an older Ground Support Equipment (GSE) tank scrapped in July over the last week or so. SpaceX completed the first Starship-derived propellant storage tank in April 2021 and rapidly rolled that tank (GSE1) and a second (GSE2) from the build site to the orbital launch pad just a few weeks apart. Less than a month after that, SpaceX also completed GSE tank #3, though things seemingly devolved into chaos immediately thereafter.
Only three months later would GSE3 finally be transported to – and installed on a concrete mount at – Starship’s first orbital launch site, and only after a number of structural modifications and in the footsteps of GSE tanks #5 and #6. Little is known about why SpaceX’s custom GSE tank production faltered so soon after it began, why none of the five Starship-sized tanks installed at the orbital pad have been fully plumbed or subjected to any kind of testing, or why structural modifications were seemingly required after the fact. However, it’s safe to say that SpaceX’s brand new GSE ‘test tank’ is now at the center of the mystery.
Thankfully, at minimum, the rapid appearance of SpaceX’s first GSE test tank returns some level of familiarity to the brief but chaotic history of Starship’s orbital launch pad propellant tanks. Test tanks are nothing new and have been an integral part of Starship development since Test Tank 1 first headed to SpaceX’s suborbital launch (and test) facilities in January 2020. In the 20 months since, SpaceX has built and tested seven small test tanks, several of which didn’t survive.
Whether intentionally destroyed or not, each test tank explicitly helped SpaceX qualify new manufacturing techniques, different materials, and different skin thickness and generally gather data more quickly and cheaply than full-scale prototypes would allow. Most recently, for example, SpaceX seemingly successfully tested a Super Heavy booster test tank, subjecting the prototype to cryogenic liquid nitrogen and using hydraulic rams to simulate the thrust of nine Raptor engines on an unproven disk-like thrust structure.
Now, almost as if SpaceX snapped out of a trance and remembered the utility of test tanks, the company has assembled a subscale GSE prototype presumably meant to verify that its custom-built propellant storage tanks can handle a set of conditions significantly different from the Starships they’re derived from. In this case, that GSE tank was quite literally built from scrapped sections of GSE tank #4. In fact, the top half (forward dome section) was quite literally cut off of GSE4 after the tank was scrapped last month for unknown reasons.
Over the last several months, while GSE tank production and installation took an unexpected hiatus, SpaceX workers slowly but surely welded steel rings (stiffeners) to the exterior of GSE1, GSE2, and GSE3. When GSE5 and GSE6 eventually headed to the pad, they left with those stiffeners already installed, implying that whatever tripped SpaceX up was likely structural. The GSE4 test tank also includes external stiffeners along each circumferential weld (where rings were stacked or domes joined).
At the same time as SpaceX was (or wasn’t, for several months) building its own GSE tanks, contractors normally tasked with assembling water towers and storage tanks in situ built eight massive 12m (~40 ft) wide tanks of their own. Deemed “cryo shells,” much like their name suggests, those tanks are meant to fully enclose SpaceX’s GSE tanks. SpaceX will use those shells to insulate their thin, single-walled steel propellant tanks, thus keeping their cryogenic contents cryogenic for as long as possible. How they’ll be insulated is unclear, though.
Based on the seemingly retroactive decision to strengthen the exterior of those GSE tanks, the general consensus as of late is that SpaceX wants to pull at least a partial vacuum in the gap between shell and tank. It’s also possible that SpaceX will do the opposite and pressurize that gap (as much as possible) with an insulative gas like nitrogen. Extra confusion comes from the fact that Starship tanks are technically designed to support a literal spacecraft (operating in a near-total vacuum) without the need for external stiffeners.
Additionally, it’s fairly clear that SpaceX hasn’t built a custom subscale cryoshell or concrete installation pad for its GSE4 test tank, meaning that it will really only be useful for testing some of the loads operational GSE tanks will experience inside their sleeves. Additionally, given that SpaceX has already completed six of the orbital pad’s seven GSE tanks and all seven of their cryosleeves, the discovery of any significant issues during GSE4 testing could easily trigger months of rework and delays. With any luck, though, GSE4 will sail through an imminent test campaign, clearing the way for SpaceX to finish plumbing, sleeving, and activating Starship’s first orbital launch site tank farm.
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
