Connect with us

News

SpaceX, NASA schedule back-to-back astronaut recovery and launch after delays

Published

on

Poor winter weather on Florida’s East Coast and across the Atlantic Ocean has forced NASA and SpaceX to flip the nominal sequence of events for the imminent back-to-back launch and recovery of two Crew Dragons.

Contrary to preference, SpaceX and NASA’s four Crew-2 astronauts are now scheduled to undock from the International Space Station (ISS) and return to Earth before their replacements (Crew-3) launch to the station. As a result, there will be no on-orbit handoff, meaning that only one NASA astronaut – Mark Vande Hei – will be left alongside cosmonauts Anton Shkaplerov and Pyotr Dubrov to crew and operate the US segment of the ISS until Crew-3’s arrival.

After several delays from an initial October 30th target, Crew-3 astronauts Raja Chari, Thomas Marshburn, Matthias Maurer, and Kayla Barron are scheduled to ride Falcon 9 and Crew Dragon to orbit no earlier than (NET) 9:03pm EST, Wednesday, November 10th (02:03 UTC 13 Nov) – two days after Crew-2 is expected to splash down.

Crew-3 astronauts Matthias Maurer, Thomas Marshburn, Raja Chari, and Kayla Barron have been (mostly) ready for flight since late October. (SpaceX)

Save for a one-day delay from October 30th to October 31st needed to give SpaceX and NASA time to qualify a fixed plumbing leak for crewed spaceflight, all subsequent delays into November have been caused by poor weather – a rather common late fall and winter occurrence in the Atlantic Ocean and southern US. The weather isn’t entirely to blame, though. Crew Dragon, SpaceX, and NASA are also partly responsible due to the extremely strict and narrow range of weather conditions the spacecraft has been certified to operate in.

Worse, a large portion of Dragon’s weather constraints are for hypothetical abort scenarios rather than the nominal launch – not “is it safe to launch?” but “is it safe to launch if something fails catastrophically and Dragon aborts and has to splash down anywhere in a several-dozen-mile corridor stretching the entire length of the Atlantic?” In the case of Crew-3’s launch, the main condition making that vast abort zone a no-go for launch is surface winds.

While aborting an expensive, time-sensitive rocket launch due to ground winds might bring to mind some kind of storm with vast swells and torrential rain, the reality is that NASA has only rated Crew Dragon to splash down when surface winds are less than 8-11 mph (13-18 km/h). In other words, the conditions causing 10+ days of delays and leading NASA to leave a skeleton crew at the space station’s US segment amounts to a firm breeze. There are likely many reasons (most hopefully good) for that highly conservative limit but ultimately, it means that NASA’s Crew Dragon missions will almost always be at risk of weather delays both going up and coming down.

Crew-2 astronauts Shane Kimbrough, Megan McArthur, Akihiko Hoshide, and Thomas Pesquet check out their Dragon ahead of one last ride home. (Thomas Pesquet)

As if to emphasize that fact, winds in the Gulf of Mexico, on the opposite side of Florida, also caused NASA to delay SpaceX’s Crew-2 departure and splashdown from November 6th/7th to November 8th, raising the risk of more Crew-3 delays or another complex schedule conflict if conditions force another change. A minor issue with Dragon’s toilet discovered during Inspiration4 and fixed on Crew-3’s ride to space will preclude its use during Crew-2’s 11-hour trip home, but that change should be barely noticeable to professional astronauts that are required to wear diapers as a precaution regardless. Otherwise, throughout the delays, Falcon 9 B1067, Crew-3 Dragon C210, and Crew-2 Dragon C206 have all thankfully remained healthy and ready to go.

Crew-2 is scheduled to undock from the ISS around 2pm EST (17:00 UTC) on November 8th and could splash down as early as 10:33 pm (03:33 UTC) – less than nine hours later.

Advertisement
-

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