News
SpaceX’s recent Starship testing challenges don’t worry Elon Musk
In his latest burst of tweets, SpaceX CEO Elon Musk says he isn’t all that worried about a duo of recent Starship prototype failures and talked next steps for the next few Starships.
Aside from SpaceX’s South Texas rocket factory, Musk also touched on progress being made on the cutting-edge Raptor engine set to power Starships and their boosters, revealing a small production milestone in the process. The CEO says that SpaceX has already begun building its 26th Raptor engine, a sign that Raptors may actually be waiting on Starships in a turn of events. Back when SpaceX was busy testing its low-fidelity Starhopper testbed, the ship actually had to wait several months for the full-scale Raptor engine’s design to mature enough to support 15-30+ second hop tests.
Now, Musk’s Raptor SN26 reveal implies that SpaceX is slowly but surely ramping up production of the new engine back at its Hawthorne, California headquarters.
From August to December 2019, SpaceX completed one Raptor engine every ~17 days, on average. With Musk’s confirmation that SpaceX is currently building (or already testing) SN26, the company is completing an engine every 12-14 days – an overall improvement of 20-40%. In other words, SpaceX’s growing engine production capacity is almost perfectly positioned to support a fleet of suborbital Starship prototypes, which is about where the company’s Boca Chica, Texas factory is today.
Obviously, following two recent full-scale Starship prototype failures spaced barely a month apart, rocket production has a ways to go before it will need the volume of Raptor engines SpaceX appears to already be capable of producing. For the time being, three Raptor engines – having already completed production in Hawthorne and acceptance testing in McGregor, Texas – are quite literally sitting around and gathering dust as they wait for the first Starship prototype qualified to host them.
Once a Starship passes proof testing, SpaceX will be able to install either one or all three engines for an inaugural static fire test, following by a small Starhopper-class hop (no higher than 150m or 500 ft).
However, once SpaceX has explored the full range of testing available to suborbital Starship prototypes, things will change. Likely ending with the first one or several successful ‘skydiver-style’ rocket landing tests, SpaceX will finally be able to seriously think about its first orbital flight tests. To reach orbit and still be capable of returning to Earth and landing softly, Starship will need a Super Heavy booster – set to be the largest rocket booster ever developed by a large margin.
Although Musk has stated that early orbital flight tests will likely launch with far fewer engines, a single Super Heavy booster could eventually require 37 Raptor engines – a full 42% more engines than SpaceX has managed to build in the entire 15+ month history of full-scale Raptor production.
Thankfully, SpaceX’s engine production HQ likely has at least 6-12 months to ramp up production to support fully-outfitted Super Heavy boosters – let alone several. For the time being, each suborbital Starship only needs 3 sea level-optimized Raptor engines, although it’s possible that SpaceX will eventually perform suborbital tests with a full compliment of six engines – including three with much larger vacuum-optimized nozzles.
Ultimately, Musk explained that his lack of concern about recent Starship prototype failures – potentially including any anomalies that follow SN4’s test campaign – comes from the fact that he believes that producing Starships is a much more challenging and pressing concern. Indeed, if your factory can churn out functioning building-sized spacecraft for pennies on the dollar, losing a few during testing is little more than an annoyance. The first failed prototypes can thus be considered learning experiences, helping SpaceX improve designs and optimize the factory and production strategies. SpaceX does still need to prove that its existing approach really can build functioning rockets, but that should (in theory) come with enough trial and error.
Depending on how initial tests go with Starship Serial Number 4 (SN4), likely days away from wrapping up production, Musk says that the first few suborbital Starship tests will likely involve short, low-velocity hops. Those flights will be slow enough that the ship (or ships) wont require aerodynamic control surfaces to complete them, instead relying entirely on smaller thrusters and the thrust vector control (TVC) provided by their three main Raptor engines.
If Starship SN4 testing – including wet dress rehearsals, Raptor static fires, and short hops – goes perfectly, Musk says that Starship SN5 could be the first new ship to have fully-functional flaps installed. If things don’t go quite as well, that milestone could shift to Starship SN6, while SN7 and beyond are obviously on the table in the event of even less forgiving SN4/SN5 testing scenarios. For now, Starship SN4 could be ready to move to the launch pad and kick off a series of critical proof tests a handful of days from now.
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
