News
SpaceX Crew-1 launch set for Sunday, ULA successfully launches spy satellite
On Friday evening, Nov. 13, NASA and SpaceX announced that the first operational Commercial Crew Program mission of the Crew Dragon would be delayed 24 hours to Sunday, Nov. 15, at 7:27 pm EST (0027 GMT 11/16). During a Crew-1 pre-launch news conference, SpaceX’s senior director of the Human Spaceflight Programs, Benji Reed, stated that the delay was driven by impacts on recovery efforts caused by tropical storm Eta, which had plagued Florida for days.
Just prior to the news conference, United Launch Alliance(ULA) successfully launched its Atlas V rocket after suffering delays of its own earlier in the week. The NROL-101 mission carried a classified payload for the National Reconnaissance Office of the U.S. government and successfully launched from Space Launch Complex 41 (SLC-41) at Cape Canaveral Air Force Station at 5:32 pm EST.
Florida weather caused multiple launch delays
Weather, especially that caused by tropical storm Eta, has caused a domino effect of delays for SpaceX and ULA over the last few weeks. The ULA Atlas V 531 rocket stacked with the secretive NROL-101 payload, initially set to liftoff on Nov. 3, was first delayed by damage sustained to environmental control system hardware of the upper stage.
According to company CEO, Tory Bruno, as the rocket was transported from ULA’s vertical integration facility (VIF) to the launchpad of SLC-41, very high winds caused damage to a duct that controlled the flow rate of an upper payload environmental control system. As a result, the rocket was returned to the VIF to have the duct replaced. A launch attempt scheduled for the following day on Wednesday, Nov. 4, was called off due to an unrelated problem with ground support equipment.
The NROL-101 mission was then set to launch on Sunday, Nov. 8, but that attempt was eventually called off due to the impending weather that would be brought across the Florida peninsula by then hurricane Eta. On Friday, Nov. 6, the Atlas V 531 rocket and payload for the National Reconnaissance Office was once again returned to the VIF for protection from the storm.
A final launch attempt was identified for Friday, Nov. 13, just 22 hours before the scheduled launch of the SpaceX, NASA Crew-1 mission from nearby Launch Complex 39A at the Kennedy Space Center. Fortunately, the weather held out long enough for the ULA Atlas V 531 rocket to liftoff. Following liftoff and successful payload deployment the mission was later declared a full success by ULA.
Florida weather also caused offshore recovery delays, impacting crewed launch
Similarly, the SpaceX and NASA Crew-1 mission has also suffered setbacks due to inclement weather, although not at the launch site. Following the successful launch and landing of the B1062 Falcon 9 of the recent GPSII-SV04 mission on Thursday, Nov. 5, SpaceX recovery teams battled unsettled seas to return the booster and the recovery droneship, Of Course I Still Love You (OCISLY), safely back to Port Canaveral.
After securing B1062 safely aboard OCISLY, the SpaceX recovery vessel GO Quest took refuge at the Port of Morehead City in North Carolina. The recovery crew would wait there to assist with the recovery of the B1061 Falcon 9 of the Crew-1 mission, rather than return to Port Canaveral in Florida. The droneship Just Read The Instructions (JRTI) was intended to meet the crew of GO Quest at the Crew-1 booster recovery zone prior to the end of the week.
Due to high winds and rough seas churned up by tropical storm Eta, the OCISLY droneship took an exceptionally tedious 7-day journey hugging the eastern coast of the United States to return to Port Canaveral. The delay caused the crew transfer process from OCISLY to JRTI to be delayed which in turn hindered the departure of the JRTI droneship.
As tropical storm Eta moved out and away from Florida the waters of the Atlantic remained too rough for the JRTI droneship to make up for the lost time. Following the conclusion of SpaceX’s Crew-1 preflight launch readiness review on Friday, Nov. 13, it was announced that the delay in getting the recovery droneship to the B1061 landing zone would delay the Crew-1 launch attempt by 24 hours.
Recovering the Falcon 9 booster, of any mission, is a secondary mission objective. However, the recovery of the Crew-1, B1061 Falcon 9 is important to both NASA and SpaceX – enough so to delay a launch attempt. NASA and SpaceX have already designated this booster to be reused on the next Crew Dragon mission, Crew-2, targeted for no earlier than March 30, 2021. In order to reuse a booster to save on launch costs, it must first be successfully recovered.
If all goes to plan, three NASA astronauts and one astronaut from the Japan Aerospace Exploration Agency will climb aboard the Crew Dragon Resilience on Sunday, Nov. 15, and blast off to the International Space Station precisely at 7:27 pm EST (0027 11/16) from LC-39A at the Kennedy Space Center.
NASA and SpaceX will provide a hosted live broadcast of all Crew-1 events beginning at 3:15 pm EST on Sunday, Nov. 15, on NASA TV and on the SpaceX website.
Check out Teslarati’s newsletters for prompt updates, on-the-ground perspectives, and unique glimpses of SpaceX’s rocket launch and recovery processes.
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
