News
SpaceX’s next Starship gets frosty to prepare for first launch
One week after the rocket was rolled from the factory to the launch pad, SpaceX appears to have successfully put Starship serial number 9 (SN9) through two routine pre-launch tests.
On December 22nd, significantly less than two weeks after Starship SN9 suffered a significant handling or production accident that caused it to tip several degrees and impact the walls of its production facility, SpaceX wrapped up speedy repairs and transported the rocket about 1.5 miles down the road.
In some combination of a minor miracle and Starship’s exceptionally sturdy design, the rocket – standing ~50 meters (~165 ft) tall and weighing around 75 to 100 metric tons (175,000-220,000 lb) – tipped sideways onto two of its four pre-installed flaps. Despite being subjected to off-nominal forces, the far stronger structural mechanisms connecting those flaps to Starship’s main airframe were seemingly unharmed and SpaceX was able to remove and replace the crumpled control surfaces mere days after the incident.
On December 28th, that work began in earnest with what is generally known as an ambient temperature pressure test, filling Starship SN9’s propellant tanks with benign air-temperature nitrogen gas. Used to check for leaks, verify basic vehicle valve and plumbing performance, and ensure a basic level of structural integrity, SN9 appeared to pass its ambient proof test without issue – albeit late in the window.
Testing wrapped up on Monday shortly after the ambient proof and was followed by the main event – a cryogenic proof test – a bit less than a day later on Tuesday. The exterior of Starship SN9 began to develop a coating of frost after SpaceX started loading its oxygen and methane tanks with liquid nitrogen around 2:30 pm CST (UTC-6). While used similarly to verify structural integrity like an ambient pressure test, a ‘cryo proof’ adds the challenge of thermal stresses to ensure that Starship can safely load, hold, and offload supercool liquids.
In SN9’s case, it’s unclear if SpaceX fully or only partially loaded the rocket’s main propellant tanks with liquid nitrogen, while a lack of frost at the tip of its nose implies that the Starship’s smaller liquid oxygen ‘header’ tank wasn’t filled as part of the test. Altogether, Starship should be capable of holding roughly 1200 metric tons of liquid nitrogen if fully loaded.
The lack of SN9’s LOx header tank participation in Tuesday cryo proof testing is intriguing on its own, as it implies that SpaceX will either perform a second cryo proof later this week or is confident enough in LOx header tank and transfer tube performance to forgo any testing. In the latter case, SpaceX would likely just use the build-up to Starship SN9’s first Raptor static fire test as a wet dress rehearsal (WDR) and a cryo proof for the smaller tank system.
According to NASASpaceflight’s managing editor, if Monday and Tuesday’s ambient and cryo proof tests were as uneventful and successful as they seemed, SpaceX may move directly on to triple-Raptor static fire preparations. In a first, Starship SN9 was transported to the launch pad last week with two of three central Raptor engines already installed and had that missing third engine installed within a few days of arrival. SN9 is also the first Starship to attempt its first proof tests with any Raptor – let alone three – installed.
If SpaceX does move directly from cryo proof testing to a three-engine static fire, that will mark another first for the Starship program and signal growing confidence and a desire for speedier preflight tests – both of which will help accelerate flight testing. As of now, SpaceX has yet to cancel a road closure scheduled on Wednesday, December 30th but it’s far more likely that a trio of 8 am to 5 pm CST closures requested on January 4th, 5th, and 6th will host Starship SN9’s first static fire attempt(s). According to NASASpaceflight.com, Starship SN9 is expected to attempt a 12.5 km (~7.8 mi) launch similar or identical to SN8’s as early as a few days after that static fire. Stay tuned for updates!
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
