Connect with us

News

SpaceX set to launch reused Dragon on a new Falcon 9 as NASA requests delay

Falcon 9 B1050 lifts off during the first Block 5 launch of Cargo Dragon.(Tom Cross)

Published

on

An electrical fault aboard the International Space Station (ISS) has forced NASA to delay SpaceX’s CRS-17 Cargo Dragon launch from May 1st to May 3rd, giving the station’s crew more time to fix the issues at hand.

A new Falcon 9 Block 5 booster is tasked with launching the spacecraft and completed a static fire test at SpaceX’s LC-40 pad on April 27th. The Cargo Dragon capsule, however, completed its first orbital resupply mission (CRS-12) in September 2017 and has since been refurbished for a second launch. After CRS-17, three launches remain on SpaceX’s CRS1 NASA contract between now and early 2020, after which Dragon 2 (i.e. Crew Dragon) is expected to take over. However, a recent failure during a Crew Dragon test have thrown those plans into question.

Cargo Dragon’s 17th mission

Known as C113, the CRS-12 capsule is the last Dragon 1 manufactured by SpaceX, leaving a fleet of five flight-proven spacecraft for SpaceX to complete the eight remaining ISS resupply missions under its Commercial Resupply Services 1 (CRS1) contract. CRS-17 is the latest installment in SpaceX’s ISS resupply saga and is manifested with ~2500 kg (5500 lb) of cargo.

Along for the ride are NASA’s Orbiting Carbon Observatory-3 (OCO-3) and the multi-experiment STP-H6 investigation, two large pieces of hardware that will be delivered to the ISS in Dragon’s unpressurized trunk. After being berthed to the ISS, astronauts will unpack dozens of packages stored inside Cargo Dragon’s cabin. Sometime later, the station’s Canadarm2 will be used to grab OCO-3 and STP-H6 and install each on the outside of the space station, where they will hopefully live long and scientifically fruitful lives.

SpaceX and NASA have assigned a new Falcon 9 Block 5 booster – likely B1056 – to launch CRS-17. To preserve the scene of Crew Dragon C201’s April 20th explosion, the booster will attempt to land around 20 miles (32 km) offshore aboard drone ship Of Course I Still Love You (OCISLY). Originally scheduled for April 25th, CRS-17 was delayed to the 26th, 30th, 1st, and now May 3rd, most of which were requested by NASA for ISS scheduling purposes.

The latest delay – from May 1st to no earlier than (NET) May 3rd – was triggered by an unexpected electrical fault aboard the ISS, cutting the redundancy of its Canadarm2 (SSRMS) control systems from two strings to one. In other words, Canadarm2 – used to ‘grapple’ and berth spacecraft like Cargo Dragon and Cygnus to the station – is now just one electrical fault away from being rendered inoperable. CRS-17 will stay grounded until two-string (i.e. single fault) redundancy is returned to Canadarm2 and additional impacted systems.

In the event that ISS astronauts and NASA ground control are able to repair the electrical systems in a timely fashion, CRS-17 is scheduled to launch at 3:11 am EDT (07:11 UTC) on May 3rd.

The International Space Station was captured in October 2018 during a Soyuz fly-around. (NASA/Roscosmos)

In the shadow of Crew Dragon

A recent catastrophic failure of Crew Dragon (i.e. Dragon 2) raises serious questions about SpaceX’s follow-up CRS2 contract, but the nominal plan involves retiring Dragon 1 after CRS-20 and flying all future cargo missions with flight-proven Crew Dragon spacecraft. In the likely event that Crew Dragon C201’s failure delays SpaceX’s CRS2 schedule by several months, there are contingency plans to continue flying refurbished Dragon 1 spacecraft.

However, each Dragon 1 was designed for a maximum of three orbital missions, meaning that SpaceX’s current capsule fleet can support no more than six additional resupply missions before they reach the end of their usable lifespans. SpaceX thus has two potential buffer missions – CRS-21 and CRS-22 – that could theoretically account for up to a year of Dragon 2 delays. Beyond that, additional Dragon 2 delays could create a gap where NASA would have to supply the ISS without SpaceX’s services.

In a best-case scenario, SpaceX and NASA will quickly uncover an unequivocal culprit of C201’s catastrophic explosion, fix the technical and organizational failures that allowed it to happen, and be back on their feet in no time. In reality, it’s likely that the failure will delay future Crew Dragon (and thus Dragon 2) launches by a minimum of 6-12 months. SpaceX will likely need to change up the launch order of its capsules, reassigning DM-2’s Crew Dragon to the in-flight abort (IFA) test and the US Crew Vehicle 1 (USCV-1) Crew Dragon to SpaceX’s first crewed demonstration mission (DM-2). After such a serious and potentially fatal failure, it’s even possible that NASA will require an additional uncrewed orbital launch before permitting SpaceX to fly astronauts on Crew Dragon.

Given that SpaceX’s nominal CRS2 plan involved lightly modifying and reusing Dragon 2s after crewed missions, the future (and schedule) of the company’s Cargo and Crew contracts are intimately intertwined. With any luck, SpaceX and NASA will be able to solve the technical, organizational, and logistical problems now facing them and ensure a stable future for Dragon 2. In the meantime, Cargo Dragon’s CRS-17 mission offers SpaceX a chance to partially verify that Cargo Dragon C201’s issues are are relegated to Dragon 2 and Dragon 2 alone.

Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.

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.

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.

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.

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.

Continue Reading