News
SpaceX Starship prototype speeding towards launch pad for first Raptor engine tests
SpaceX continues to build full-scale Starship hardware at a jaw-dropping pace, testing the limits of rocket production to complete the fifth full-scale prototype in three months and prepare the ship for its first Raptor engine ignition tests.
This time around, SpaceX CEO Elon Musk is fairly confident that the latest Starship prototype – known as serial number 3 (SN3) – has the best chance yet of becoming the first full-scale ship to pass acceptance tests and kick off a Raptor engine static fire campaign. A step further, if said static fires go according to plan, Starship SN3 could become the first full-scale vehicle of its kind to perform controlled flight tests.
Starship SN3 will thus attempt to follow in the footsteps of Starhopper and hopefully avoid an unintentional launch debut similar to the one that destroyed Starship SN1 earlier this month. A successful Starship flight test powered by three Raptor engines would be a major bode of confidence in the upgraded rocket factory SpaceX is building in South Texas. Musk recently made it clear that setting up the machine that builds the machine is currently just as important as individual Starship tests. Thankfully, given that SpaceX is already managing to build colossal rocket prototypes in a matter of weeks for what has to be pennies on the dollar, all with a team of just a few hundred people, the next Starship test campaign is likely just a week or two away.

On March 9th, Musk revealed that the Starship SN2 prototype – an incomplete tank repurposed for specific testing – had passed a proof test with flying colors. SN2’s brief test campaign managed to prove that SpaceX had already fixed the weak point believed to have destroyed Starship SN1 less than two weeks prior. Featuring a redesigned engine section and thrust structure (or “thrust puck,” per Musk), the Starship SN2 test tank survived pressure testing and even made it through engine thrust simulations with the help of an industrial-scale hydraulic jack.

While the tank passed its tests looking no worse for wear, the last-second design changes SpaceX had to make to rapidly perform thrust structure verification testing made it impossible to repurpose for any alternative use. Starship SN2 has thus been relegated to the scrapyard, a technical necessity but also a sign of both the program’s high rate of progress and low prototype cost. SpaceX’s Boca Chica factory has already more or less completed a new engine section for Starship SN3 and is probably just a day or two away from integrating it with the rest of the steel vehicle.
Less than three days after SpaceX’s brand new vehicle assembly building (VAB) had a single, small Starship section sat inside it, two additional sections of Starship SN3’s tank section departed their fabrication tents and were stacked on March 18th. Less than a day later, the third segment of the rocket’s tank section capped off the two that were stacked the day before. Once those three stacked sections are fully welded together to form a single, cohesive piece of steel, it will need to be stacked atop the aft tank dome and thrust structure to effectively complete Starship SN3’s tank section.




After all four sections are joined, technicians will need to install a few internal parts, but most remaining work mainly involves running wiring and plumbing for power, communications, propellant management, and pressurization. More likely than not, SpaceX replicate its Starship Mk1 and SN1 testing strategy and bring Starship SN3’s tank section to the launch pad for proof testing as soon as outfitting is complete. If the rocket passes proof testing, SpaceX can – for the first time – install functional Raptor engines on a full-scale Starship prototype and begin a crucial wet dress rehearsal (WDR) and static fire test campaign.
At the current rate of progress, SpaceX could easily be ready to transport Starship SN3 to the pad within the next week, give or take. Stay tuned for updates as the company works to quickly finish SN3 integration and move onto the testing phase.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
News
Tesla crosses major Unsupervised Self-Driving milestone
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.
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.