News
SpaceX Crew Dragon switches ports to make room for Boeing’s Starliner do-over
Update: For the second time, a SpaceX Crew Dragon spacecraft has successfully swapped International Space Station (ISS) docking ports in orbit – this time to make way for Boeing’s planned Starliner Orbital Test Flight do-over.
If Starliner’s second orbital flight test is more successful than the first, which failed almost immediately after launch, the Boeing spacecraft will launch no earlier than July 30th, rendezvous and dock with the ISS, and spend approximately five days at the station before attempting to return to Earth. Once Starliner departs, freeing up the forward docking port, SpaceX and NASA will likely have to perform a second Crew-2 port relocation, moving Dragon back to its original port to set the stage for the CRS-23 Cargo Dragon resupply mission scheduled in late August.
SpaceX and NASA are on track for the Crew-2 Dragon spacecraft currently docked to the International Space Station (ISS) to perform a “port relocation” maneuver early Wednesday, effectively opening the door for Boeing’s Starliner flight test do-over.
Scheduled to launch on a United Launch Alliance (ULA) Atlas V rocket no earlier than (NET) July 30th, Boeing’s Starliner will be flying for the first time since the spacecraft’s near-catastrophic Orbital Flight Test (OFT) debut in December 2019. During Starliner’s inaugural test flight, a combination of inept Boeing software development, shoddy quality control, and inexplicably lax NASA oversight allowed the spacecraft to launch with inoperable software.
As a result, things went wrong mere seconds after Atlas V – which performed nominally – deployed Starliner. Almost as simple as using the wrong clock, the first software fault – something that would have been instantly caught with even the most rudimentary integrated systems test – caused Starliner to think it was in a different part of the OFT mission and waste much of its fuel with thousands of unnecessary thruster firings.
Aside from pushing Starliner’s maneuvering thrusters beyond their design limits, those unplanned and unexpected misfirings also threw the spacecraft off course, obfuscating Boeing and NASA’s ability to communicate and command the spacecraft and troubleshoot the situation at hand. Eventually, the company regained control of Starliner, but not before it had burned through most of its propellant reserves – precluding plans for to rendezvous and dock with the ISS.
Less than three hours before reentry, Boeing also uncovered a separate thruster-related software issue that could have caused the Starliner capsule to lose stability and re-impact its expendable trunk section after separation.
Ultimately, with so many issues and a failure to gather any kind of data related to operations at and around the ISS, NASA thankfully forced Boeing to plan to repeat OFT with Orbital Flight Test 2 (OFT-2). Scheduled to launch in December 2020 as of the second half of that year, OFT-2 ultimately slipped – both for scheduling and technical reasons – to March, June, and finally July 30th, 2021.
More than 19 months after Starliner’s ill-fated debut, NASA and Boeing are now almost ready for the spacecraft’s critical do-over. For unknown reasons, though, NASA and/or Boeing apparently need (or prefer) Starliner to use a specific docking port – the same port SpaceX’s second operational Crew Dragon spacecraft is currently docked to. According to NASA and Boeing, Starliner needs to use that forward docking port because it has not been qualified for zenith docking, which is a bit more complex. As a result, SpaceX and NASA have scheduled a port relocation maneuver around 7am EDT (UTC-4) on Wednesday, July 21st.
SpaceX’s first relocation occurred in early April to prepare for the arrival of a second Crew Dragon later that month. When Crew-1 Dragon departed a few weeks after the maneuver, it would leave the station’s zenith (space-facing) port free for a Cargo Dragon 2 spacecraft scheduled to arrive around one month later. Due to the station’s geometry and port layout, only the zenith port allows its robotic Canadarm2 arm to unload unpressurized cargo from Dragon’s trunk.
Already at the forward port, the Crew-2 Dragon will thus be moving to the zenith port for Starliner’s brief 1-2 week stay at the ISS. However, as may have become clear, Crew Dragon will then have to re-relocate to the forward port for any future Cargo Dragon missions – one of which happens to be scheduled to launch with an important unpressurized payload as early as August 29th.
Regardless of why, it’s hard to ever complain about seeing Dragons fly. Tune in around 6:30 am EDT (10:30 UTC) to watch Crew Dragon C206 maneuver around an orbital space station.
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 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.
FSD Supervised v14.3.9 starting to roll out shortly
This release includes a new active safety feature set: FSD Supervised can now activate on your behalf when an imminent collision is detected and Automatic Emergency Braking (AEB) may not be enough.
It may also engage if we…
— Tesla AI (@Tesla_AI) September 4, 2026
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.
Tesla crosses major Unsupervised Self-Driving milestone
Tesla Robotaxi will be a 24/7 service: here’s when
