News
SpaceX begins filling Starship’s orbital launch site with rocket propellant
Less than a year after tank farm assembly began in South Texas, SpaceX has begun the painstaking process of filling Starship’s first orbital launch site with thousands of tons of rocket propellant.
Comprised of seven giant custom-built tanks, the last of which SpaceX installed and ‘sleeved’ in mid-October, Starbase’s first orbital-class tank farm is a bit like the pad’s circulatory system and needs to store, chill, and distribute all the propellant needed for a rocket launch. To support Starship and Super Heavy, both the largest individual rocket stages and the largest integrated rocket ever built, its launch site and tank farm have to be equally immense. In classic SpaceX fashion, the company has strived to keep the costs of that tank farm low and its speed of construction high, resulting in a setup that’s fairly unique as far as launch pads go.
Perhaps nothing emphasizes the scale of Starship’s first orbital-class tank farm than the process of filling it with the supercool propellant and fluids its designed to hold.
In mid-September, SpaceX began delivering cryogenic fluids to Starbase’s orbital tank farm for the first time ever. Instead of propellant, dozens of tanker trucks delivered liquid nitrogen to one or two of the farm’s tanks between mid-September and mid-October. Altogether, around 40-60 truckloads was delivered – only enough to partially fill one tank. That liquid nitrogen also appeared to be piped into two of the farm’s three liquid oxygen tanks, meaning that it may have only been used to clean and proof test them.
Combined, the farm’s seven main tanks should be able to store roughly 2400 tons (5.3M lb) of liquid methane (LCH4), 5400 tons (12M lb) of liquid oxygen (LOx), and 2600 tons (5.7M lb) of liquid nitrogen (LN2). LCH4 and LOx are Starship’s propellant, while LN2 is needed to ‘subcool’ that propellant below its boiling point, significantly increasing its density and the mass of propellant Starships can store.
In recent weeks, LN2 deliveries have picked back up at the orbital tank farm, suggesting that more tanks are being cleaned and proofed. SpaceX may have also begun filling one or both of the farm’s dedicated LN2 tanks, though it’s hard to say for sure. More importantly, around October 17th, SpaceX began filling Starship’s orbital tank farm with liquid oxygen – real propellant – for the first time. Rather than a slow and cautious process, deliveries have streamed in almost daily ever since. As of November 4th, at least 74 tanker trucks have delivered LOx to the farm in 18 days.
Based on Department of Transportation (DOT) regulations that limit the gross weight of cryogenic tanker trucks to about 37 tons (~81,000 lb), each of those trucks has likely delivered around 20 tons (~45,000 lb) of LOx to Starbase. Altogether, that amounts to around 1500 tons (3.3M lb) delivered in less than three weeks – enough to fill about 80% of one of the farm’s three LOx tanks or a quarter of its total LOx storage capacity.
Based on data from AI-based tracker Starbase Deliveries, which can only count daytime deliveries, at least 134 tankers have delivered LCH4, LOx, or LN2 to Starbase’s orbital and suborbital launch sites between October 4th and November 4th – an average of 4.3 per day. At that rate, even if every delivery went to the orbital pad, it would take SpaceX nearly four months just to fill the orbital tank farm. Put simply, the facilities and logistics required to support even a single orbital Starship launch are gargantuan.
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 launched the all-electric, steering wheel-less, and pedal-less Cybercab last night at a quiet and small event in downtown Austin, Texas.
The launch, which marked the beginning of unsupervised ride-hailing for Tesla’s Robotaxi platform with Cybercab, has already caught the attention of the National Highway Traffic Safety Administration (NHTSA) who has more questions.
NHTSA opened an Audit Query (AQ) into the Cybercab’s Federal Motor Vehicle Safety Standards (FMVSS) certification that Tesla gave the vehicle. Manufacturers self-certify vehicles much of the time to avoid excessive regulatory delays.
Tesla Cybercab interior, note the lack of steering wheel and pedals. (Credit: @niccruzpatane/X< /a>)
However, the agency needs more information; it said in a summary:
“On September 3, 2026, Tesla began commercial deployment with a small number of its Cybercab vehicles in Austin, Texas. Tesla notified the Agency that it certified those Cybercab vehicles as compliant with all applicable Federal Motor Vehicle Safety Standards (FMVSS). Tesla also notified the Agency that it plans to gradually expand commercial deployment of the Cybercab to include additional vehicles and locations.”
It also went on to state that the Cybercab lacks traditional automotive controls, which is a groundbreaking move. The process is entirely new to the NHTSA, which gives the agency some leverage to put Tesla’s launch under a microscope:
“The vehicles lack permanently attached, conventional manual controls, such as a brake pedal, gas pedal, steering wheel, and mirrors. NHTSA is opening this AQ to examine the process and technical data on which Tesla relied when certifying the Cybercab and related issues. Among other things, NHTSA will consider the extent to which Tesla’s certification depended on determinations that certain FMVSS are inapplicable to the Cybercab.”
Tesla has added 45 Cybercab units to its fleet of Robotaxi-enabled cars in Austin, according to public documents the company submitted to the State of Texas over the past week. Enabling this level of self-driving is something Tesla has worked toward for many years, and now that it is finally here, it seems more than reasonable that regulatory agencies will have some questions.
Many outlets might try to frame this as a negative, but it is truly an agency looking to gain more information about groundbreaking tech that Tesla has been developing for years.
In an effort to keep riders, pedestrians, and property safe, any and all data accumulated from these first days, weeks, and months of rides will likely be shared with the NHTSA to enable broader rollout strategies across the United States and more in the future.
Tesla Robotaxi will be a 24/7 service: here’s when
Tesla Full Self-Driving will now overtake manual driving to avoid disaster
