News
SpaceX repairing upgraded Starship prototype after first test
SpaceX workers have been spotted repairing the company’s newest Starship prototype in the days after the rocket’s first partial test.
Starship S24 was transported to SpaceX’s Starbase, Texas orbital launch site (OLS) on May 26th after about two and a half months of assembly, marking the first time SpaceX transported a new Starship prototype to a test stand since August 2021. Less than 24 hours later, after attaching Ship 24 to a new test bay located beside the actual ‘orbital launch mount,’ the Starship prototype came to life and began its first proof test.
Unfortunately, while it’s impossible to judge with certainty without official confirmation, Ship 24 either failed to complete that test or did not make it through unscathed.
Known as an ambient or pneumatic proof test, the main goal is to pressurize a Starship or Super Heavy prototype with nonflammable, ambient-temperature nitrogen gas to ensure that the rocket and all its plumbing are structurally sound and working as expected. A successful test would likely require a prototype to reach and sustain flight pressures – up to 8.5 bar (~125 psi) as of 2020 – without exhibiting any significant leaks or problems.
For a while, Ship 24’s first ambient proof test went about as expected, with lots of small vents from its main liquid oxygen (LOx) and methane (LCH4) tanks. No activity was visible at the ship’s nose, where vents and plumbing attach to a pair of small landing (header) propellant tanks. Ship 24 is the first Starship with an upgraded version of those tanks after SpaceX decided to remove the methane header tank from the main methane tank and relocate it directly under the oxygen header tank, which takes up the tip of Starship’s nose.
After an hour or two of testing, a muffled bursting noise different from previous vents was heard, followed by a quieter ‘whoosh’ more akin to a long vent. At the same time as the loud noise was heard, a good dozen or so of S24’s thousands of heat shield tiles were knocked off the section of the hull between the Starship’s main tanks and nose cone. SpaceX depressurized Ship 24 soon after and within a few hours, workers could be seen extracting a pipe from the ship that appeared to have been bent almost in half.

Three days later, workers were spotted guiding apparent replacement pipes into Ship 24. Altogether, it appears that some small section of Ship 24’s internal piping failed catastrophically after it was pressurized during the vehicle’s first pneumatic proof test, knocking tiles loose and possibly damaging other adjacent plumbing. Given the location of that piping inside Ship 24’s nose section, there’s a nonzero chance that the failure occurred when SpaceX attempted to pressurize the Starship’s new header tanks, which would have started by pressurizing the propellant and gas lines leading to them. That would explain the first muffled burst, the subsequent venting sound that slowly faded to nothing, and the loss of heat shield tiles.
It would also explain why SpaceX decided to leave Starship in place and conduct repairs at the pad. Super Heavy Booster 7, which suffered a dramatic plumbing failure during an early proof test, was moved back to one of Starbase’s covered assembly bays for repairs. Had Ship 24’s incident been severe, it would have likely left the pad as well. The fact that Ship 24 did not move indicates that the failure was fairly minor and contained, only impacting some easily-replaceable plumbing.

Additionally, SpaceX appears to have moved Raptor heat shield components and a missing cover for one of Ship 24’s four flaps to the pad since the incident. On top of the team that has been working all weekend to repair the Starship, other sets of workers have set about closing out Ship 24’s ‘raceway’, which protects hundreds of feet of smaller plumbing and cables and a flight termination system that runs from the top to the bottom of the ship’s tanks; and some have begun preparing to fill gaps in Ship 24’s heat shield. Most of that work can be classified as ‘finishing touches’ and none of it would be prioritized if Ship 24 was not in decent shape.
Still, even minor damage is a setback. Ship 24’s next opportunity for redemption is a 10am to 10pm CDT window on Wednesday, June 1st, with backup windows available on Thursday and Friday.
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.
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.