News
SpaceX Starbase construction takes priority as next orbital Starship, Super Heavy pair come together
As SpaceX teams slowly prepare the first orbital-class Starship and Super Heavy booster for the next-generation rocket’s first full-stack launch, the company has simultaneously begun assembling a second ship/booster pair. However, it’s clear that orbital pad construction remains a priority.
Known as Ship 20 and Booster 4, the two stages of the first orbital-class Starship first arrived at the launch site in early August. Only eight weeks later has Starship S20 finally become the first of the pair to attempt and complete one of two crucial proof tests, opening the door for one or several Raptor static fires in the coming week or two. Meanwhile, Booster 4 has had all 29 of its Raptor engines installed, uninstalled, and reinstalled and twice been placed on and removed from Starbase’s orbital launch mount in the same time frame but has yet to attempt any proof testing.
Despite the apparent delays and challenges slowing Ship 20 and Booster 4’s test debuts and two plodding FAA reviews that appear all but guaranteed to preclude an orbital launch attempt in 2021, though, SpaceX has recently begun assembling a second two-stage Starship.
Save for Starhopper back in 2019, no Starship or Super Heavy prototype has spent nearly as long at the launch site without a single test as Ship 20 and Booster 4 have. To an extent, there have likely been some technical delays while assembling, outfitting, and working with two first-of-their-kind prototypes. Still, the difference between past vehicles like Starship SN15 and Super Heavy Booster 3 are so stark that some portion of the testing delays almost has to be a conscious decision made by SpaceX.
To be able to fully proof and static fire test Super Heavy B4, SpaceX first needs to plumb, wire, and outfit Starbase’s orbital launch mount and complete a majority of the orbital pad’s massive tank farm. However, the orbital pad and its many unfinished systems are situated just a thousand (~300m) east of the suborbital launch site and Starship test facilities, which are complete and ready for testing. To test a Starship at those facilities, SpaceX has to entirely clear the pad of personnel – now several hundred people at the peak of construction – for 6-12+ hours.
The implication is that SpaceX management effectively chose to rip off the bandage now rather than later, sacrificing timely testing of Starship S20 to allow a near-total focus on orbital pad construction and activation over the last ~8 weeks. It’s hard to say if that’s paid off but the fact that SpaceX has chosen this particular moment to begin assembling the next orbital-class Starship and Super Heavy suggests that a clearer plan is starting to come together.
B4/S20, meet B5/S21
Parts of Starship S21 and Super Heavy B5 have been floating around Starbase’s build site for weeks. There was a multi-week period, for example, where the site’s massive high bay was effectively unused – clearly a conscious choice given SpaceX’s history of Starship prototype production earlier this year and late last. Parts of Super Heavy B5 were likely ready for assembly (i.e. stacking) by mid to late August. The ‘mid bay’ used for Starship tank section assembly has been similarly underutilized for even longer – only recently accepting its first Starship S21 section after supporting assembly of the orbital pad’s final storage tank.
Instead, Booster 5 stacking began around September 15th. At the current rate of assembly, which has slowed down considerably in the last week, SpaceX’s second flightworthy Super Heavy could reach its full 69m (~225 ft) height as early as mid-October. Starship S20 likely won’t be far behind. Further, thanks to SpaceX’s preferred style of continuous improvement, Booster 5 and Ship 21 production already appear well on track to outpace Booster 4 and Ship 20. With B5, rather than installing a range of external equipment (avionics, wiring, plumbing) after assembly is finished, SpaceX appears to be completing some of those subsystems during stacking, potentially speeding up final assembly by 1-2+ weeks. With S21, SpaceX has begun outfitting the Starship’s nose cone with heat shield tiles far earlier in the assembly process than it did with S20.
Given that it has taken SpaceX the better part of a month to finish and spot-fix Starship S20’s heat shield since the prototype’s second trip to the test site, taking those lessons learned to heart and getting Starship S21’s heat shield installation right on the first try could cut weeks from final assembly.
In the meantime, after completing Ship 20’s first cryoproof test on September 29th, SpaceX will hopefully be able to kick off the first six-engine Raptor static fire test campaign within the next week or so. With any luck, the start of B5/S21 assembly also means that the orbital launch pad is nearly ready to support Super Heavy B4’s first proof tests, even if static fires with anything close to a full set of 29 Raptors appear to be weeks away. Regardless, it looks like it won’t be long before SpaceX will be juggling two pairs of orbital-class Starships and Super Heavy boosters.
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
