Connect with us

News

SpaceX’s Crew Dragon abort test gets closer to launch with SuperDraco static fires

A pair of Crew Dragon's upgraded SuperDraco abort engines perform a static fire test. (SpaceX)

Published

on

SpaceX has posted a video showing the static fire test of a pod of Crew Dragon SuperDraco abort thrusters, indicating that the complex system has been successfully redesigned (“upgraded”) to fix the faults that caused a Dragon capsule to explode in April 2019.

This progress keeps SpaceX on track for two critical Crew Dragon milestones, both of which are now expected to occur sooner than later.

Published just a few hours prior, CNBC journalist Michael Sheetz reported that SpaceX is planning to static fire the Super Draco abort thrusters of Crew Dragon capsule C205 as early as November 2nd.

Capsule C205 – along with an expendable trunk – were reassigned to support Crew Dragon’s crucial In-Flight Abort (IFA) test after flight-proven capsule C201 was destroyed just prior to a SuperDraco static fire test on April 20th. Having just successfully completed Crew Dragon’s first uncrewed orbital launch, space station docking, and ocean recovery (Demo-1), the plan was to reuse C201 to perform the IFA test.

Crew Dragon C205 would support Demo-2 – the spacecraft’s first NASA astronaut launch – and C206 would support Post-Certification Mission 1 (PCM-1), meaning Dragon’s first operational delivery of astronauts to the ISS.

Crew Dragon capsule C205 and Falcon 9 booster B1046 arrived in Florida around October 3rd ahead of SpaceX’s critical In-Flight Abort (IFA) test. (SpaceX)
Excluding Falcon 9, all pieces of SpaceX’s first astronaut-rated Crew Dragon spacecraft are visible in this one frame: capsule C206, a heat shield, and what looks like a nearly finished trunk. (Teslarati – Pauline Acalin)

Instead, Crew Dragon C201 suffered a catastrophic explosion just prior to a SuperDraco static fire test at SpaceX’s Cape Canaveral Air Force Station (CCAFS) Landing Zone (LZ) facilities. Capsule C205 was diverted to support the In-Flight Abort, while C206 was moved up to support Demo-2. Had C201’s static fire been successful, SpaceX could have been ready to launch Crew Dragon’s IFA mission as early as May or June.

As Michael Sheetz reported, SpaceX now plans to perform a similar static fire test of the IFA Crew Dragon capsule as early as November 2nd. It’s unclear if this static fire would have been performed had C201 not exploded, but CNBC suggests that NASA and a number of other parties will be watching the results of this test closely.

SpaceX’s first spaceworthy Crew Dragon capsule prepares for its first Falcon 9-integrated static fire and a post-recovery test fire three months later. (SpaceX)

Whether that’s true or not, it’s unclear just how relevant a SuperDraco static fire of a factory-fresh Crew Dragon spacecraft (C205) is to C201’s failure. The latter spacecraft had completed months of testing (much of it fueled), spent a week in orbit, reentered Earth’s atmosphere, and splashed down in saltwater barely a month and a half prior to the fated test.

Regardless, it looks like SpaceX and NASA understandably want to perform a (relatively) similar static fire test to verify that – at a minimum – the Dragon capsule’s abort thrusters are in working order. As SpaceX’s static fire video illustrates, SuperDraco thrusters – as well as each integrated pair of engines – are all static fired in McGregor, Texas as part of routine acceptance testing. If all goes as planned during the November 2nd static fire, as well as the Falcon 9 rocket’s own static fire, Crew Dragon’s In-Flight Abort mission could launch as early as late-November.

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

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

News

Tesla Full Self-Driving will now overtake manual driving to avoid disaster

Published

on

Credit: Tesla

Tesla is beginning to roll out Full Self-Driving Supervised v14.3.9 with a new active safety layer that can take control even when the driver is operating the car manually.

Tesla AI said the software can activate FSD on the driver’s behalf when an imminent collision is detected and Automatic Emergency Braking may not be enough. It may also engage if the system detects heavy distraction or an accidental FSD disengagement.

The capability is essentially Automatic Collision Evasion. However, unlike conventional AEB, which mainly applies the brakes in a straight line, this feature can use steering, braking, and acceleration together if the car calculates that stopping alone will not prevent impact and a safer path exists. The system may change lanes or move toward a shoulder when conditions allow, then continue driving after the immediate threat is handled rather than simply coming to a stop.

The intervention is meant as a last-resort safety net, not a replacement for attentive driving.

Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident

Tesla’s own description still frames FSD as supervised assistance. Secondary reports on internal release notes say the feature can fire while the car is being driven manually if cabin-camera monitoring suggests the driver is not sufficiently attentive, such as reaching toward the back seat, or if FSD appears to have been turned off unintentionally.

After the emergency maneuver, the car is expected to alert the driver and request a return to manual control.

The safety case is straightforward. Many collisions happen in the last second because a driver is looking away, fumbles a control, or faces an obstacle that braking cannot fully solve. A system that can both recognize that AEB is insufficient and execute a coordinated evasive path can reduce those remaining high-severity events.

Re-engaging after accidental disengagement also addresses a practical failure mode: a small steering nudge that drops FSD at the worst moment. The advantage is a background safety net that uses the same vision stack already running in v14, instead of leaving the car solely to emergency braking once the driver is no longer in command.

The feature still depends on FSD being enabled and, according to reports, an active FSD purchase or subscription. It does not make the vehicle unsupervised. Drivers remain responsible, and Tesla has not published how often the system is expected to intervene or how it will handle false positives.

If the rollout is conservative and the false-alarm rate stays low, the update is a meaningful step: FSD is no longer only a feature the driver turns on. In the rare moments when disaster is already forming, it can step in.

Continue Reading