Connect with us

News

SpaceX’s Pacific rocket recovery fleet heads to sea for Western Block 5 debut

Published

on

SpaceX drone ship Just Read The Instructions was spotted by Teslarati photographer Pauline Acalin departing Port of Los Angeles on the evening of July 22, while fairing catcher Mr Steven completed final checkouts and full installation of his massive new net, hopefully just days away from the first successful fairing catch. Their call to action, Iridium NEXT-7, is scheduled to launch NET 04:39 PDT/11:39 UTC, July 25th.

Over the course of July, both vessels have been undergoing significant maintenance and upgrades. Mr Steven’s was perhaps the most extreme – his original arm and net apparatus was removed in its entirety and replaced with a massively upgraded system of arms, booms, and a brand new net, well and truly expanding the vessel’s catching area by a factor of four.

With a new net and arm span stretching at least 60 meters by 60 meters, Mr Steven’s improved fairing catching mechanism is now almost the same size as the landing area aboard SpaceX’s two autonomous spaceport drone ships – roughly 200ft x 300ft (60m x 90m). While presumably a pure coincidence, the size parallels apparently necessary to recover two very different components of Falcon 9 – the booster rocket and the payload fairings – is rather satisfying.

Mr Steven captured just minutes after his upgraded net was fully lifted and tensioned, July 22. (Pauline Acalin)

A last hurrah?

Intriguingly, ASDS Just Read The Instructions has stoically remained at SpaceX’s Port of San Pedro, CA berth for more than nine months, wholly unused despite the fact that the company has completed four additional missions since its last tasked booster recovery (October 2017, Iridium-3). It’s not a coincidence that all four of those Vandenberg AFB missions featured boosters that had already successfully launched and landed once before – SpaceX made a habit over the last four months of intentionally expending Falcon 9 boosters after their second missions, even when the launch conditions would allow for booster recovery.

This mission will thankfully bring an end to that understandable but still-painful practice, thanks to Iridium-7’s new Block 5 booster, B1048. Many of the months JRTI spent at berth were without the pod thrusters the drone ship needs to keep itself at the proper landing point once at sea, but JRTI departed the port with a full complement of four blue thrusters on the evening of July 22. However, it’s unclear how much SpaceX will need the vessel within just a month or two from today.

 

At long last, SpaceX’s planned, built, and now-patiently-waiting West Coast landing zone is finally finished, permitted, and in the green to begin supporting Falcon 9 return-to-launch-site (RTLS) recoveries at Vandenberg Air Force Base. Effectively a basic copy of SpaceX’s now well-worn landing zone pair in Cape Canaveral, Florida, the company’s VAFB LZ-1 has been hinted at in two FCC launch permits for launches as early as the first and last weeks of September. Aside from Iridium launches, of which just one will remain after Iridium-7, nearly all of SpaceX’s West Coast launches are for fairly lightweight payloads that should easily allow Falcon 9 RTLS recoveries.

Advertisement
-

Environmental conditions mean that JRTI will still be needed regularly for a handful of months (March through June) to avoid disrupting baby seals (pups, technically), but the vessel’s recovery efforts this week may be one of the last ‘off-season’ examples for months or even years to come. On the plus side, RTLS recovery at SpaceX’s VAFB landing zone will be an absolute dream for recovery technicians, as the LZ is directly beside the launch pad and hangar, where recovered Block 5 boosters can likely be refurbished or at least easily packaged and shipped to the Hawthorne factory.

For more sneak peeks and exclusive behind-the-scenes footage of SpaceX’s rocket recovery fleet, including drone ship Just Read The Instructions, be sure to subscribe to our exclusive membership program!

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

Advertisement
Comments

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.

Published

on

By

Photorealistic depiction of the Amazon Prime plane crash in Miami on Sep 3, 2026 near a fleet of Tesla Cybercab
Photorealistic depiction of the Amazon Prime plane crash in Miami on Sep 3, 2026 near a fleet of Tesla Cybercab

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.


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.

Advertisement
-

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.

Continue Reading

News

Tesla crosses major Unsupervised Self-Driving milestone

Published

on

Credit: Tesla

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.

Advertisement
-

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.

Continue Reading

News

Tesla Robotaxi will be a 24/7 service: here’s when

Published

on

Credit: @AdanGuajardo/X

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.

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.

Advertisement
-

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.

Advertisement
-
Continue Reading