News
SpaceX sends Starship’s first vacuum Raptor engine to Boca Chica
For the first time, SpaceX has shipped a vacuum-optimized Raptor engine to its Boca Chica, Texas Starship factory days after the company’s present reiterated plans for an inaugural orbital launch attempt as early as July.
Back in March 2021, CEO Elon Musk confirmed that he’d set SpaceX a goal of attempting Starship’s first orbital launch no later than the end of July – around four and a half months distant at the time. Fifteen weeks later, though the prospects of an orbital launch attempt happening in July have practically shrunk to zero, SpaceX COO and President Gwynne Shotwell – best known for acting as a more grounded foil to Musk’s often impractical schedule estimates – reiterated that the company is still “shooting for July” for Starship’s first orbital launch attempt.
As of late June, hitting that target would require SpaceX to string together numerous extraordinary feats of engineering and rocketry in record time or attempt some extremely unorthodox corner-cutting.
The launch pad and launch vehicle hardware needed for Starship’s first space shot are currently far from ready for flight. On June 24th, Musk unexpectedly revealed that the Super Heavy booster prototype SpaceX is now in the late stages of assembly isn’t actually the booster that will carry Starship on its first space launch attempt. In other words, though dozens of rings in various states of work are strewn about SpaceX’s Boca Chica factory, the company has yet to begin assembling the massive 65m (~215 ft) tall booster required for the first orbital launch attempt.
Using Super Heavy Booster 3 (B3) as a ruler, assembly could easily take 9-10 weeks – starting whenever the process actually begins. If SpaceX started stacking Booster 4 today, in other words, it’s unlikely that the rocket would even be complete by the end of August. Barring SpaceX taking unprecedented shortcuts, completing the booster is just part of the process of preparing for flight and B4 would still need to be qualified for flight, likely involving at least one cryogenic proof and static fire test.
In a best-case scenario where SpaceX begins assembly today, manages to halve Booster 4 assembly time in one fell swoop, the sneaks the second Super Heavy ever completed through qualification testing in a single week, the orbital flight test booster still wouldn’t be ready for Starship installation (likely another unprecedented first) before mid-August.
That would then leave SpaceX five or six weeks to fully assemble Starship S20, a process that has yet to begin. Like Starship SN15, which Musk said sported “hundreds of improvements”, Musk has also stated that Ship 20 and all after it will feature another batch of upgrades needed to take Starship orbital. Starship SN15 was very gradually stacked and assembled over the course of almost four months, though that slow assembly can likely be blamed on the fact that SpaceX is busy testing Starships SN8 through SN11 and was effectively waiting to see if any other major changes might be required.
While most of S20’s upgrades are a mystery, the ship’s thrust dome – spotted in work at Boca Chica earlier this month – has already confirmed that the prototype will be the first with the necessary hardware for Raptor Vacuum engine installation. That likely means that S20 will also be the first Starship to attempt to static fire six Raptor engines*, potentially producing more thrust than a Falcon 9 booster. On June 27th, one such vacuum-optimized Raptor (RVac) arrived in Boca Chica for the first time ever, making it clear that the comparatively brand new engine may already be ready to start integrated Starship testing.
*Update: SpaceX CEO Elon Musk says that the Raptor Vacuum delivered to Boca Chica on June 27th is, in fact, meant for Starship S20, seemingly confirming that the prototype will fly with a full six Raptor engines.
Of course, beyond Starship and Super Heavy, SpaceX also has a great deal of work left to get the rocket’s first orbital-class launch facilities partially operational. SpaceX will need to complete and activate at least one or two more custom-built propellant storage tanks, sleeve those three or four tanks with three or four massive thermos-like ‘shells,’ complete thousands of feet of insulated plumbing and wiring, finish a massive ‘launch table,’ install that table on a six-legged ‘launch mount;’ outfit that table and mount with an array of power, avionics, hydraulics, and fueling equipment and plumbing; complete a ~145m (~475 ft) ‘integration tower,’ and perform the first fit checks and shakedown tests with a real booster or Starship.
Only then will SpaceX be able to attempt Starship’s first space launch. All told, it might not be literally impossible for SpaceX to complete all the above work in less than five weeks, but it’s safe to say that the odds of that happening could probably make a lottery ticket blush. Regardless, if Starship reaches orbit at any point before the end of 2021, it would beat out simpler “next-generation” rockets like Ariane 6, ULA’s Vulcan, and Blue Origin’s New Glenn despite beginning concerted development years later and with a far less certain funding situation.
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
