News
SpaceX’s Starship comes to life for the first time in lead-up to launch debut
For the first time ever, SpaceX has pressurized Starship Mk1’s building-sized propellant tanks, a critical test that culminated in the rocket prototype essentially taking its first ‘breaths’.
An anthropomorphization sometimes used to describe the venting launch vehicles often exhibit while during and after fueling, Starship Mk1’s so-called ‘breaths’ occurred around 5:59 pm CST (23:59 UTC). Those first vents came after roughly an hour or two spent performing several different pressurization cycles, observable due to the fact that Starship’s stainless steel tanks visibly smoothed out as pressure increased.
Due to the typical distances Starship is viewed from and the nature of the mirror-finished stainless steel SpaceX has chosen to build the next-generation launch vehicle out of, the exterior of Starship prototypes can produce a reflection that looks bumpy and disjointed. This has lead many a layperson to incorrectly assume that SpaceX’s Starship prototypes are thus shoddily built. In reality, viewed from afar, the tiniest hint of surface heterogeneity on a mirror can dramatically change what is reflected on its surface.
Even at the thinness of Starship Mk1’s liquid oxygen and methane tanks, stainless steel is still extremely strong, but pressurizing the vehicle’s tanks can clearly counteract a significant portion of the slight imperfections in their curvature.
Although it’s now clear that SpaceX did in fact perform some kind of pressurization test with Starship Mk1, it remains to be seen what exactly the nature of that testing was. First and foremost, SpaceX did establish significant roadblocks almost six hours before testing began, and company workers vacated the launch site several hours before visible Starship pressurization and venting. Fairly soon after that vent, workers returned to the pad and may or may not have been present during additional (but more subdued) venting activity.
Most importantly, November 18th’s testing featured a sum total of zero visible activity at SpaceX’s nearby flare stack, a mechanism used to burn waste methane gas to prevent dangerous buildups at worksites (or launch pads). This almost certainly means that methane (gaseous or liquid) played no role in pressurizing Starship Mk1’s propellant tanks.
Altogether, that likely means that Monday’s proof test was not a wet dress rehearsal (WDR), a term used to describe the process of testing a launch vehicle by fully fueling it and performing a countdown identical to a real launch – but without engine ignition or liftoff. Instead, SpaceX likely began the day’s testing by pressurizing Starship several times with a neutral gas like nitrogen or helium, while gaseous oxygen is also a possibility but is significantly less likely. Simply by using pressure sensors on Starship and knowing the volume of gas that is being loaded, SpaceX could likely determine whether the prototype has any leaks.
The major vent around 6 pm local time could have simply been Starship venting that pressurant gas, which would explain why there was just a single large, observable vent. When dealing with cryogenic liquid propellant, those supercool liquids gradually heat up, causing a portion to boil and turn into gas, gas that launch vehicles then vent intermittently to prevent overpressure events (i.e. explosions). Starship Mk1 only visibly vented once, although there may have also been some additional venting even after technicians returned to the launch site (another sign that the pressurant was neither toxic or combustible).
Oddly, shortly after SpaceX workers returned to the launch pad, they appeared to begin spraying down Starship Mk1 with a large volume of water or foam, producing clouds of mist as large as Starship itself. This came as a total surprise and why it’s being done is entirely unclear. Possible explanations include simply rinsing Starship (but why and why now?), checking its tanks for leaks, applying industrial quantities of WD40 (used to protect stainless steel from rust), or maybe even testing how Starship stands up to ice (extremely unlikely as it would need to be filled with a cryogenic liquid to be cold enough).
Perhaps the morning light will bring some answers. All things considered, as long as the mysterious spraying is not indicative of any serious issues or concerns with Starship Mk1, SpaceX may now be ready to put the prototype through a true propellant loading test, potentially filling its tanks with as much as 1200 metric tons (2.65 million pounds) of liquid oxygen and methane. If or when Starship passes that test, it’s next trial will be the very first triple-Raptor-engine static fire test. For now, we wait.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
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
