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 CEO Elon Musk revealed today on the social media platform X that legacy automakers, such as Ford, General Motors, and Stellantis, do not want to license the company’s Full Self-Driving suite, at least not without a long list of their own terms.
“I’ve tried to warn them and even offered to license Tesla FSD, but they don’t want it! Crazy,” Musk said on X. “When legacy auto does occasionally reach out, they tepidly discuss implementing FSD for a tiny program in 5 years with unworkable requirements for Tesla, so pointless.”
I’ve tried to warn them and even offered to license Tesla FSD, but they don’t want it! Crazy …
When legacy auto does occasionally reach out, they tepidly discuss implementing FSD for a tiny program in 5 years with unworkable requirements for Tesla, so pointless. 🤷♂️
🦕 🦕
— Elon Musk (@elonmusk) November 24, 2025
Musk made the remark in response to a note we wrote about earlier today from Melius Research, in which analyst Rob Wertheimer said, “Our point is not that Tesla is at risk, it’s that everybody else is,” in terms of autonomy and self-driving development.
Wertheimer believes there are hundreds of billions of dollars in value headed toward Tesla’s way because of its prowess with FSD.
A few years ago, Musk first remarked that Tesla was in early talks with one legacy automaker regarding licensing Full Self-Driving for its vehicles. Tesla never confirmed which company it was, but given Musk’s ongoing talks with Ford CEO Jim Farley at the time, it seemed the Detroit-based automaker was the likely suspect.
Tesla’s Elon Musk reiterates FSD licensing offer for other automakers
Ford has been perhaps the most aggressive legacy automaker in terms of its EV efforts, but it recently scaled back its electric offensive due to profitability issues and weak demand. It simply was not making enough vehicles, nor selling the volume needed to turn a profit.
Musk truly believes that many of the companies that turn their backs on FSD now will suffer in the future, especially considering the increased chance it could be a parallel to what has happened with EV efforts for many of these companies.
Unfortunately, they got started too late and are now playing catch-up with Tesla, XPeng, BYD, and the other dominating forces in EVs across the globe.
Tesla is backtracking on a strange adjustment it made to its in-car Navigation feature after numerous complaints from owners convinced the company to make a change.
Tesla’s in-car Navigation is catered to its vehicles, as it routes Supercharging stops and preps your vehicle for charging with preconditioning. It is also very intuitive, and features other things like weather radar and a detailed map outlining points of interest.
However, a recent change to the Navigation by Tesla did not go unnoticed, and owners were really upset about it.
For trips that required multiple Supercharger stops, Tesla decided to implement a naming change, which did not show the city or state of each charging stop. Instead, it just showed the business where the Supercharger was located, giving many owners an unwelcome surprise.
However, Tesla’s Director of Supercharging, Max de Zegher, admitted the update was a “big mistake on our end,” and made a change that rolled out within 24 hours:
The naming change should have happened at once, instead of in 2 sequential steps. That was a big miss on our end. We do listen to the community and we do course-correct fast. The accelerated fix rolled out last night. The Tesla App is updated and most in-car touchscreens should…
— Max (@MdeZegher) November 20, 2025
The lack of a name for the city where a Supercharging stop would be made caused some confusion for owners in the short term. Some drivers argued that it was more difficult to make stops at some familiar locations that were special to them. Others were not too keen on not knowing where they were going to be along their trip.
Tesla was quick to scramble to resolve this issue, and it did a great job of rolling it out in an expedited manner, as de Zegher said that most in-car touch screens would notice the fix within one day of the change being rolled out.
Additionally, there will be even more improvements in December, as Tesla plans to show the common name/amenity below the site name as well, which will give people a better idea of what to expect when they arrive at a Supercharger.
News
Dutch regulator RDW confirms Tesla FSD February 2026 target
The regulator emphasized that safety, not public pressure, will decide whether FSD receives authorization for use in Europe.
The Dutch vehicle authority RDW responded to Tesla’s recent updates about its efforts to bring Full Self-Driving (Supervised) in Europe, confirming that February 2026 remains the target month for Tesla to demonstrate regulatory compliance.
While acknowledging the tentative schedule with Tesla, the regulator emphasized that safety, not public pressure, will decide whether FSD receives authorization for use in Europe.
RDW confirms 2026 target, warns Feb 2026 timeline is not guaranteed
In its response, which was posted on its official website, the RDW clarified that it does not disclose details about ongoing manufacturer applications due to competitive sensitivity. However, the agency confirmed that both parties have agreed on a February 2026 window during which Tesla is expected to show that FSD (Supervised) can meet required safety and compliance standards. Whether Tesla can satisfy those conditions within the timeline “remains to be seen,” RDW added.
RDW also directly addressed Tesla’s social media request encouraging drivers to contact the regulator to express support. While thanking those who already reached out, RDW asked the public to stop contacting them, noting these messages burden customer-service resources and have no influence on the approval process.
“In the message on X, Tesla calls on Tesla drivers to thank the RDW and to express their enthusiasm about this planning to us by contacting us. We thank everyone who has already done so, and would like to ask everyone not to contact us about this. It takes up unnecessary time for our customer service. Moreover, this will have no influence on whether or not the planning is met,” the RDW wrote.
The RDW shares insights on EU approval requirements
The RDW further outlined how new technology enters the European market when no existing legislation directly covers it. Under EU Regulation 2018/858, a manufacturer may seek an exemption for unregulated features such as advanced driver assistance systems. The process requires a Member State, in this case the Netherlands, to submit a formal request to the European Commission on the manufacturer’s behalf.
Approval then moves to a committee vote. A majority in favor would grant EU-wide authorization, allowing the technology across all Member States. If the vote fails, the exemption is valid only within the Netherlands, and individual countries must decide whether to accept it independently.
Before any exemption request can be filed, Tesla must complete a comprehensive type-approval process with the RDW, including controlled on-road testing. Provided that FSD Supervised passes these regulatory evaluations, the exemption could be submitted for broader EU consideration.
Tesla CEO Elon Musk sends rivals dire warning about Full Self-Driving
Tesla backtracks on strange Nav feature after numerous complaints
