News
SpaceX outfits Starship, Super Heavy with dozens of Raptor engines
New photos shared by SpaceX show that the company has nearly finished installing a total of 39 upgraded Raptor engines on a new Starship and its Super Heavy booster.
Those prototypes – known as Ship 24 and Booster 7 – could be tasked with supporting Starship’s first orbital launch attempt sometime later this year if both make it through upcoming test campaigns without major issues. Whether that’s a probable outcome is still uncertain but recent progress suggests that it won’t take long for the prospects of both prototypes to shift into clearer focus.
After several rounds of proof testing and two trips to and from SpaceX’s Starbase, Texas orbital launch site (OLS) in March, April, and May, Super Heavy Booster 7 (B7) made its third trip to the pad on June 23rd.
“SpaceX used the six weeks Booster 7 spent back in a factory assembly bay to finish installing aerocovers, surfaces known as chines or strakes, car-sized grid fins, Starlink internet dishes, and – most importantly – 33 upgraded Raptor V2 engines. Combined, Booster 7 could produce up to 7600 metric tons (~16.8M lbf) of thrust at or before liftoff. Crucially, SpaceX also finished installing most of Booster 7’s Raptor heat shield in the same period, completing in six weeks work that took Booster 4 closer to half a year. With its heat shield and all 33 Raptors mostly in place, Booster 7 should be ready to kick off static fire testing almost as soon as it’s installed on Starbase’s orbital launch mount.”
Teslarati.com – June 24th, 2022
Building, qualifying, shipping, and installing 33 new Raptor 2 engines on Super Heavy B7 was already an impressive achievement and produced the most (potentially) powerful rocket booster ever assembled. On July 2nd, a pair of photos published by SpaceX showed off Booster 7’s nearly-finished engine section and simultaneously revealed that the company has finished installing all six of Starship S24’s Raptor engines – and even part of the ship’s aft thermal protection.
Differences are already visible between Ship 24 and Ship 20, the only other Starship prototype to have six Raptors installed. The most notable change is the addition of a metal framework that covers the entire breadth of the ship’s aft – most likely destined to support flat sections of insulation and thermal protection that will partially seal off sensitive engine, plumbing, pressure vessels, and avionics components located inside Starship’s aft. That extra shielding should help limit the extreme conditions that hardware will be subjected to during ground testing and, perhaps, in flight.
Super Heavy Booster 7 has already completed a significant amount of testing, including four cryogenic proofs (cryoproofs) and one Raptor thrust simulation test. Since its third return to the pad, SpaceX has several more ambiguous tests, none of which appeared to involve cryogenic propellant loading. It’s possible that those tests focused more on Booster 7’s pressurization system, perhaps filling its tanks with the hot oxygen and methane gases it will eventually use to pressurize its tanks. It’s likely that SpaceX wants to put Booster 7 through at least one successful wet dress rehearsal – using real liquid methane and oxygen propellant – before attempting to static fire any of its 33 Raptors. Booster 7’s aft thermal protection system also isn’t entirely complete, so technicians will need to finish installing several more panels before any static fire testing.
Alongside B7, Starship S24 has completed a good amount of cryoproof and Raptor thrust simulation testing, which it survived without any irreperable issues. The ship was then returned to an assembly bay on June 9th, where where workers have been installing heat shield tiles, finalizing the ship’s engine section, and completing dozens of other less visible closeout tasks. SpaceX also recently finished modifying one of its two suborbital test and launch mounts for Starship static fire testing, leaving the other mount semi-permanently modified for cryoproof and thrust simulation testing of future prototypes.
SpaceX has requested permission for road closures – each a potential 12-hour test window – on July 5th, 6th, 7th, 11th, and 12th.
Elon Musk
Tesla Cybercabs narrowly miss deadly Amazon cargo plane crash
An Amazon cargo plane crash near Miami’s airport stopped feet from dozens of Tesla Cybercabs.
An Amazon Prime Air Boeing 767 cargo jet overran the runway at Miami International Airport on Sunday afternoon, killing five people and injuring five more. The jet, operated by North Carolina based carrier 21 Air as Flight 7598, touched down around 2 p.m. after arriving from San Juan, Puerto Rico, then crossed the airport perimeter, plowed across NW 67th Avenue and struck multiple vehicles before catching fire, according to the Associated Press.
Photos and video from the scene show the aircraft’s nose stopped within meters of a fenced staging lot holding dozens of gold painted Tesla Cybercabs, the steering wheel free robotaxi Tesla began putting on public roads in Austin last week. Miami-Dade Fire Rescue has confirmed the plane struck “multiple vehicles” but has not said whether any Cybercabs were among them, and neither Tesla nor airport officials have addressed the fleet directly.
The Cybercabs had not yet entered commercial service in Miami. Tesla’s existing Robotaxi operation there runs on modified Model Y vehicles and has been unsupervised since Ashok Elluswamy confirmed the detail on X in July.
Footage of the plane crash from earlier today | #ONLYinDADE pic.twitter.com/iGoOtnd6cD
— ONLY in DADE (@ONLYinDADE) September 6, 2026
Elon Musk offered the briefest of reactions. Replying to a Zero Hedge post about the Cybercabs sitting so close to the wreckage, he wrote a single word: “Weird.” He has not commented further, and Tesla has not issued a statement.
The timing puts Tesla’s newest vehicle near an unrelated but highly visible tragedy just days after its Austin debut, a launch that had already drawn scrutiny from federal regulators. The National Highway Traffic Safety Administration opened an audit how Tesla certified the Cybercab as compliant with federal vehicle safety standards, a process Teslarati covered after the vehicle’s September 3 launch event. That inquiry concerns the car’s lack of a steering wheel and pedals, not the Miami crash.
Investigators from the FAA and NTSB are focused on the plane, not the parking lot beside it. Flight data reviewed by outlets including Simple Flying show the 767 touched down around 170 knots, well above the 135 to 140 knot range typical for the aircraft, though investigators have not determined a cause. Amazon said it is working with authorities and that its priority is the safety of everyone affected.
Whether any Cybercabs were damaged, and what Tesla plans for the fleet parked near one of the country’s busiest airports, remain open questions.
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 Cybercabs narrowly miss deadly Amazon cargo plane crash
Tesla crosses major Unsupervised Self-Driving milestone
