News
SpaceX prepares Starship, Super Heavy for milestone Raptor static fire tests
SpaceX has scheduled a full week with as many as 30 hours of road and beach closures for Starship and Super Heavy testing and is working hard to prepare the first orbital-class ship and booster for several major challenges.
First rolled to SpaceX’s Starbase orbital launch site more than six weeks ago and stacked together for the first time on August 6th, the company has spent the last month putting the finishing touches on Starship 20 (S20) and Super Heavy Booster 4 (B4) – ranging from heat shield installation to plumbing and wiring. Perhaps most importantly, SpaceX has also installed some or all of the Raptor engines that are expected to support the ship and boosters’ first static fire qualification tests.
For a number of reasons, those static fires – and a few additional tests expected to precede them – could be huge milestones for SpaceX’s Starship program.

Earlier this month, after rolling Starship S20 to the launch pad for the second time and installing it on one of two suborbital launch/test mounts, SpaceX began the process of installing Raptor engines (again for the second time) on the rocket. Beginning with two center sea level-optimized Raptors, SpaceX then installed a Raptor Vacuum engine on Ship 20. The implication: when S20 fires up for the first time, it might be doing so with two kinds of Raptor engines – a first for the Starship program.
Since Raptor Vacuums first began static fire testing at SpaceX’s McGregor, Texas development campus around Q4 2020, the company has yet to fire up an RVac engine on a Starship prototype. Starship’s current design features three gimballing sea-level Raptors and three vacuum-optimized variants with much larger nozzles – all in close proximity inside a 9m-wide (30 ft) skirt.


As such, the first Starship static fire with any combination of Raptor Center and Raptor Vacuum engines will be a significant milestone for SpaceX. Eventually, that will likely culminate in the first static fire(s) of a Starship (likely S20) with all six Raptors installed – a test that will effectively qualify that prototype for its first orbital launch attempt.
Meanwhile, things are arguably even more complex for Super Heavy. Aside from a single three-engine static fire completed by Super Heavy Booster 3 (B3), Starship’s first stage has never come close to a full-up static fire with all 29-33 Raptor engines installed. Whenever that occurs, Super Heavy will likely become the most powerful rocket ever tested and – like with Starship – will be more or less qualified for its first flight if the test goes according to plan.


SpaceX already installed a full 29 Raptor engines on Super Heavy B4 last month. After returning to Starbase, those engines were removed and eventually reinstalled a few weeks later – albeit with a number of replacements. Now, having spent the last 11 days sitting on the orbital pad’s launch mount, SpaceX has begun to replace at least one of Booster 4’s 29 installed engines. It’s unclear why but the fact that SpaceX is replacing engines at the launch pad – instead of rolling Super Heavy back to the build site for the third time – is an encouraging sign that B4 is nearly ready for its first proof and static fire tests.
Due to all the recent activity, it’s almost impossible to tell whether Starship S20 or Super Heavy B4 will be first onto the figurative saddle for ambient pressure, cryogenic, and static fire proof testing. What is clear, though, is that SpaceX has five six-hour testing windows scheduled every day next week. Stay tuned for updates on the next steps for SpaceX’s first orbital-class ship and booster pair.
News
Tesla Robotaxi will be a 24/7 service: here’s when
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.
News
Tesla Full Self-Driving will now overtake manual driving to avoid disaster
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.
News
Tesla Cybercab launch catches NHTSA’s attention who wants to know more
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.