News
SpaceX ships Starship’s 200th upgraded Raptor engine
A day after revealing the completion of the 200th Falcon upper stage and Merlin Vacuum engine, SpaceX has announced that it also recently finished building Starship’s 200th upgraded Raptor engine.
Starship – and Raptor, by extension – has yet to reach orbit and is likely years away from scratching the surface of the established success and reliability of the Falcon upper stage and MVac. But compared to MVac, Raptor is more complex, more efficient, more than twice as powerful, experiences far more stress, and is three times younger.
And Raptor 2 isn’t the first version of the engine. Before SpaceX shipped its first Raptor 2 prototype, it manufactured 100 Raptor 1 engines between the start of full-scale testing in February 2018 and July 2021. By late 2021 or early 2022, when Raptor 2 took over, the total number of Raptor 1 engines produced likely reached somewhere between 125 and 150 – impressive but pale in comparison to SpaceX’s Raptor 2 ambitions.
From the start, Raptor 2’s purpose was to make future Raptors easier, faster, and cheaper to manufacture. The ultimate goal is to eventually reduce the cost of Raptor 2 production to $1000 per ton of thrust, or $230,000 at Raptor 2’s current target of 230 tons (~510,000 lbf) of thrust. As of mid-2019, Musk reported that each early Raptor 1 prototype cost “more” than $2 million for what would turn out to be 185 tons of thrust (~$11,000 per ton). It’s not clear if that ever appreciably changed.
In response, SpaceX strived to make Raptor 2 simpler wherever possible, removing a large part of the maze of primary, secondary, and tertiary plumbing. In 2022, CEO Elon Musk confirmed that SpaceX had even removed a complex torch igniter system for Raptor 2’s main combustion chamber. All that simplification made Raptor 2 much easier to build in theory, and SpaceX’s production figures have more than confirmed that theory. Despite those simplifications, SpaceX was also able to boost Raptor 2’s thrust by 25% by sacrificing just 1% of Raptor 1’s efficiency.
Beginning with its first delivery in February 2018, SpaceX produced the first 100 Raptor 1 engines in about 36 months. In the first 11 to 12 months of Raptor 2 production, SpaceX has delivered 200 engines. That translates to at least six times the average throughput, but the true figure is even higher. In June 2019, Musk stated that SpaceX was “aiming [to build a Raptor] engine every 12 hours by end of year.” As is usually the case, that progress took far longer to realize. But in October 2022, a senior NASA Artemis Program official revealed that SpaceX recently achieved sustained production of one Raptor 2 engine per day for a full week.
Such a high rate – likely making Raptor one of the fastest-produced orbital-class rocket engines in history – is required because SpaceX’s next-generation Starship rocket needs a huge amount of engines. The Starship upper stage currently requires three sea-level-optimized Raptors and three vacuum-optimized Raptors, and SpaceX has plans to increase that to nine engines total. Starship’s Super Heavy booster is powered by 33 sea-level Raptors.
Orbital-class versions of Starship and Super Heavy have never flown, let alone demonstrated successful recovery or reuse, so SpaceX has to operate under the assumption that every orbital test flight will consume 39 Raptors. Even after the reuse of Super Heavy boosters or Starships becomes viable, taking significant strain off of Raptor demand, SpaceX wants to manufacture a fleet of hundreds or even thousands of Starships and a similarly massive number of boosters. To outfit that massive fleet, SpaceX would have to mass-produce orbital-class Raptor engines at a scale that’s never been attempted.
But it will likely be years – if not a decade or longer – before SpaceX is in a position to attempt to create that mega-fleet. If the Raptor 2 engines SpaceX is already building are modestly reliable and reusable, and it doesn’t take more than 5-10 orbital test flights to begin reusing Starships and Super Heavy boosters, a production rate of one engine per day is arguably good enough to support the next few years of realistic engine demand.
SpaceX’s first orbital Starship launch attempt could occur as early as December 2022, although Q1 2023 is more likely. SpaceX currently has permission for up to five orbital Starship launches per year out of its Starbase, Texas facilities and will likely try to take full advantage of that with several back-to-back test flights in a period of 6-12 months.
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
