News
SpaceX just finished Starship’s 100th Raptor engine
SpaceX says its Hawthorne, California rocket factory and headquarters has completed the assembly of Starship and Super Heavy’s 100th Raptor engine.
SpaceX began developing Raptor behind the scenes as far back as 2012 and 2013, when a small team successfully tested a full-scale Raptor preburner – a small but important subcomponent – at NASA’s Stennis Space Center (SSC) facilities. Three years later, in September 2016, CEO Elon Musk revealed the first integrated static fire of a Raptor prototype – though it would later become clear that that prototype was a subscale engine about the same size as Falcon 9’s Merlin 1D.
After two and a half years of subscale testing that helped SpaceX refine startup and shutdown sequences and the general operation of what quickly became the world’s most thoroughly tested full-flow staged combustion engine, SpaceX graduated to full-scale testing. Designed to produce about twice the thrust (~200 tons/440,000 lbf) of its subscale predecessors, the first full-scale Raptor engine shipped to SpaceX’s McGregor, Texas test facilities and completed its first static fire days later on February 3rd, 2019.
Notably, the very first full-scale Raptor prototype (SN1) not only survived its first test but lived long enough to complete several more, ultimately reaching SpaceX’s minimum thrust target four days after its first static fire. A vibration issue would soon require several months of troubleshooting and iterative build-test-fail cycles but Raptor was ultimately ready to support its first brief Starhopper hop tests in July and August.
Approximately 15 months after Raptor’s first flight, Starship prototype SN8 successfully lifted off with three engines, one of which performed a near-flawless four-minute burn to apogee. Eventually, six months after SN8’s successful ascent but failed landing, Starship SN15 successfully landed, demonstrating Raptor’s ability to reignite mid-flight. Since SN15’s May 2021 success, SpaceX appears to have completed anywhere from 20 to 35+ new Raptors as part of a dramatic acceleration in production to meet the needs of at least two imminent orbital Starship test flights – both of which will need approximately 35 engines each.
For additional information on Booster 3's engine placement. Refer to this diagram below!
Massive thanks to @StarshipGazer for providing super high resolution and detailed pictures which allowed me to figure these positions out. pic.twitter.com/j1s5qHoGJ2— Artzius (@artzius) July 21, 2021
Per its label, RB16 – now better known as the 100th Raptor engine overall – is the 16th Raptor Boost engine built by SpaceX. “Boost” refers to the particular variant – in this case, a Raptor engine specifically designed for an outer ring of 20 engines on each Super Heavy booster. Unlike Raptor Center (RC) engines, the outer ring of Raptor Boost engines are fixed in place against the rocket’s skirt and aren’t designed to vector their thrust (i.e. gimbal). According to Musk, all sea level-optimized Raptor engines will ultimately produce approximately 230 tons (~510,000 lbf) of thrust.
Relative to almost any other large-scale engine development program in the last half-century, Raptor’s 29-month 100-engine milestone is an extraordinary achievement. The closest comparable engine is Blue Origin’s BE-4, which is expected to produce up to ~240 tons (~540,000 lbf) of thrust, uses an efficient (albeit slightly less so) combustion cycle, and relies on the same methane and oxygen propellant. Full-scale BE-4 testing began 16 months before Raptor in October 2017 and Blue Origin has reportedly only built and tested nine prototypes in the almost four years since. According to Musk, as of May 2021, SpaceX is now building more than a dozen Raptors – including prototypes and flight engines – every month.
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
