News
SpaceX fires up Starship rocket twice in 30 hours ahead of next big tests
SpaceX has successfully fired up a full-scale Starship rocket for the second time in barely 30 hours and removed the ship’s Raptor engine to perform an additional suite of “cryo testing”.
Around 7pm CDT on May 6th, SpaceX technicians began loading the fourth full-scale Starship with liquid oxygen and methane, filling up a large portion of its massive propellant tanks. Just the latest in a line of several tests involving wet dress rehearsals (WDR) completed in the days prior, this test would soon become exceptional. About an hour and a half after work began, Starship SN4’s lone Raptor engine ignited and burned for ~3 seconds, marking the first time in history a next-generation SpaceX rocket truly came alive with one of the engines designed to take it all the way to orbit.
In line with tests performed with Starhopper – a low-fidelity, subscale tested that flew twice with Raptor – last year, it would have been business as usual if SpaceX had called it a day and moved on to something else with Starship SN4. Instead, Starship performed another WDR and fired up its Raptor engine for a second time in just 30 hours after SpaceX teams inspected the rocket and cleared it for another round. It’s unknown why two back-to-back static fires were performed but, to be clear, every step Starship SN4 takes forward is a step into uncharted territory. Already, the ship’s next steps could come as soon as Friday, May 8th.
According to CEO Elon Musk, SpaceX’s second Starship SN4 static fire test was completed successfully and actually marked the operational debut of a critical aspect of the next-generation launch vehicle and spacecraft. Known as header tanks, Starship needs two smaller secondary propellant tanks to complement its main tanks, a need driven mainly by the challenges of landing such a large and mobile spacecraft. Smaller header tanks will also make it dramatically easier for SpaceX to insulate cryogenic propellant and ensure it remains liquid over long-duration cruises in space, but safe and reliable landings are a more pressing concern for these early prototypes.
During landing operations, the main benefits smaller header tanks offer are relative ease of pressurization (needed to safely feed Raptor engines) and a much lower risk of issues from sloshing, which can introduce bubbles and voids that can obliterate rocket engines if ingested. Impressively, per Musk, Starship SN4 completed its second static fire test using its internal liquid methane header tank – a sort of bubble attached to the bottom of the main methane tank dome.
Starship’s liquid oxygen header tank is situated at the tip of the conical nose section, a part that all full-scale ships have been tested without thus far. However, the use of the fuel header tank on May 7th means that Starship SN4 already has a functional, plumbed header tank installed, verifying the partial functionality of a critical part of the next-generation launch vehicle. A second static fire will have also provided SpaceX a wealth of extra data about Raptor’s performance while installed on Starship, invaluable at such an early stage of integrated testing.
Two Starship static fires now under its belt, SpaceX removed SN4’s Raptor engine around 12 hours after its second test and returned it to storage at the company’s nearby factory facilities. According to public notices provided by Cameron County, Texas officials, SpaceX’s next Starship SN4 activity is expected to occur on May 8th with backup windows on the 9th and 10th and will involve “cryo testing”.
The most obvious conclusion is that SpaceX – having completed enough static fire testing to verify Starship SN4’s performance – now wants to really put the rocket through its paces with another cryogenic test. Completed on April 26th, the ship’s first cryogenic ‘proof’ test maxed out at around 4.9 bar (70 psi), enough for low-stress hop tests but well short of the sustained pressure needed for orbital spaceflight. While testing singular propellant tanks in the first few months of 2020, Musk revealed that SpaceX was targeting a minimum of 6 bar (~90 psi) for orbital Starship flights – ~8 bar (115 psi) with a 25% safety factor.
The company actually achieved 8.4 bar with one of its Starship test tanks, the same processes of which were used to build Starship SN4, but a full-scale ship has yet to demonstrate those pressures. Now, SpaceX already has a fifth full-scale prototype (Starship SN5) likely just a week or so away from pad readiness, meaning that Starship SN4’s potential destruction during pressure testing wouldn’t have a big impact on plans for a series of imminent flight tests. If SN4 survives pressure testing, it would likely have its Raptor engine reinstalled and move on to a 150m (500 ft) hop test.
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
