News
SpaceX has finally begun filling Starship’s orbital launch site fuel tanks
Almost five months after SpaceX began the process of filling and testing the first custom-built propellant storage system for Starship, the largest rocket ever built, the company has finally begun to fill the fuel half of the ‘tank farm’.
SpaceX began delivering truckloads of liquid nitrogen (LN2) to the LN2 and liquid oxygen (LOx) sections of the tank farm in mid-September 2021, well before the farm was anywhere close to completion. In about a month, SpaceX accepted ~60 LN2 deliveries – enough to partially fill one of the farm’s seven cryogenic tanks. Instead of some operational purpose, that LN2 was likely used to clean and partially proof the farm’s three LOx tanks. Just two weeks later, the orbital tank farm received its first LOx deliveries.
At the time, mere days after the basic structure of the main tank farm storage system was effectively completed, most figured that it would take SpaceX about as long to clean, proof, and begin filling the farm’s two liquid methane tanks. That would not be the case.
SpaceX installed the second of the farm’s two vertical SpaceX-built cryogenic liquid methane (LCH4) tanks in mid-October 2021. All seven cryogenic tanks had ‘sleeves’ – designed to be filled with foam insulation – installed by the end of the month, effectively completing the farm’s basic structure half a year after assembly began. However, around the same time, SpaceX also installed two horizontal tanks that were also identified as LCH4 storage – giving the overall tank farm far more fuel storage than its oxidizer (LOx) tanks could match. Starship’s Raptor engines burn about 3.55 kilograms of LOx for every 1 kilogram of LCH4.
As work on the vertical LCH4 tanks appeared to slow to a crawl, it took until December 2021 for SpaceX to begin cleaning and proofing the farm’s horizontal LCH4 tanks with liquid nitrogen. By that time, a rough unofficial narrative had been constructed to explain the lack of progress on the farm’s fuel half. Namely, in an excellent Twitter thread, CSI Starbase made a strong case that SpaceX appeared to have designed the first orbital-class Starship tank farm – a compact and pleasingly symmetric set of eight vertical storage tanks – without taking into consideration rudimentary Texas regulations for the storage of liquid natural gas and methane. By all appearances, that conclusion was correct, as the farm was visibly violating several rules – namely the requirements that all LCH4 storage be surrounded by six-foot-tall retaining walls and that all associated plumbing not be situated under power cabling.
As it exists, the LCH4 side of the vertical tank farm violates both of those rules and it’s not obvious that there is actually enough space between the two vertical methane tanks to build a retaining wall with two feet of horizontal clearance. It’s possible that the situation is more complex and that SpaceX intentionally broke those rules or was pursuing an exception to them but the end result was that those vertical LCH4 tanks have yet to be finished, let alone cleaned or proof tested. Instead, SpaceX appears to have fully refocused on horizontal tanks and most recently tore down a dirt berm beside them and began preparing foundations for at least two or three more.
Those horizontal tanks appear to store about 1000 cubic meters (~35,000 ft^3) of LCH4, while the vertical tanks would have stored about 1800 m^3. To fully replace them, SpaceX will need approximately four horizontal tanks – two more in addition to the two already installed. Thankfully, SpaceX has finally begun filling the already installed tanks while it works to expand the methane farm, beginning with three truckloads on the very first day – February 13th, 2022.
To fill the two existing tanks, which may store enough methane to fuel a stacked Starship and Super Heavy about 4/5ths of the way, SpaceX will need around 40-50 more tanker deliveries. Since last November, SpaceX has completed more than 320 liquid nitrogen and 200 liquid oxygen deliveries – equivalent to about 6700 tons (~14.8M lb) of LN2 and 4200 tons (~9.3M lb) of LOx. If SpaceX maintains that average and focuses entirely on LCH4, the two horizontal tanks could be filled to the brim before the end of February.
Having a substantial amount of LCH4 stored at the orbital tank farm will finally allow SpaceX to attempt the first major wet dress rehearsals (WDRs) and, more importantly, the first full static fires with flightworthy Super Heavy booster prototypes. Of course, a tank farm with full supplies of LOx, LCH4, LN2, and their gaseous equivalents is also a necessity for the first orbital Starship launch attempt, which has most recently slipped from a target of mid-2021 to no earlier than (NET) Q2 2022, pending regulatory approval.
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
