News
SpaceX Starship eyes Tuesday launch after FAA communication breakdown causes delays
Two new sourced reports suggest that SpaceX’s fast-moving approach to Starship development and a shocking level of naivety and ineptitude on behalf of the FAA’s regulatory responsibilities combined to delay the latest Starship test flight.
As previously discussed on Teslarati, SpaceX was clearly and publicly targeting a Starship launch as early as 12pm to 5pm on Monday, March 29th after unknown issues delayed a Friday attempt. Those plans were writ large on SpaceX’s own website and via CEO Elon Musk’s tweets a full three days before launch and confirmed by road closures, notices to mariners, and the FAA’s own flight restrictions and advisories 24-48 hours prior. Around 11am CDT Monday, Musk revealed that SpaceX had been forced to call off the day’s launch attempt because an FAA-required inspector was “unable to reach” Boca Chica in time.
Now, per reports separately corroborated by The Verge reporter Joey Roulette and Washington Post reporter Christian Davenport, a clearer picture of what exactly transpired is available.
Roulette first broke the news, offering a better look at a portion of the debacle. Per “a source,” SpaceX had apparently told the FAA inspector – who had been waiting all week for Starship SN11’s launch debut – that plans for a Monday recycle had been canceled. The inspector then flew home to Florida. However, as things often do and have, the situation rapidly changed and SpaceX suddenly found itself in a position to launch on Monday.
According to the apparent FAA-side source, SpaceX dropped that change of plans on the agency’s lap late on Sunday, leading the inspector to “[scramble]” onto a Monday flight that was somehow too late to arrive before the 5pm CDT end of Starship’s test window. In a statement, the FAA chided SpaceX, stating that the company “must provide adequate notice of its launch schedule to allow for a safety inspector to travel to Boca Chica.”
Under that description of events, it would be hard not to find SpaceX clearly in the wrong. Mere hours of notice – and only offered late on Sunday evening – would make it difficult for anyone to abruptly arrange a 1300-mile, multi-stop flight. At the same time, though, someone capable of singlehandedly scrubbing an entire rocket launch attempt on a whim (or an accident) is obviously not just “anyone” and a functional regulatory apparatus probably wouldn’t leave the entirety of that substantial responsibility up to a single employee.
As it so happened, Roulette’s source only offer part of the picture. According to Christian Davenport and his sources, SpaceX (or someone) did tell the FAA inspector that it was safe to head home on Friday because the company was struggling to secure road closures from Cameron County for a Monday launch attempt. Apparently, the issue was so extreme that SpaceX wasn’t sure if a launch on any day of the next week would be possible.
However, sometime early on Sunday morning, SpaceX secured a road closure for a Monday Starship launch attempt. According to Davenport, SpaceX emailed the FAA inspector but he “didn’t see the email,” which presumably served as a notice of plans for a Starship launch attempt. Logically, SpaceX then began attempting to call the FAA (inspector?) but didn’t get an answer or call back until “late Sunday night.”
Via Cameron County’s explicitly public road closure announcement website, Monday’s road closure was granted no later than 11am CDT. Assuming SpaceX emailed the FAA inspector around then, that email effectively served as a notice of launch plans more than 24 hours before the window was scheduled to open. If SpaceX didn’t somehow forget to email until hours later, Davenport’s description implies that it took SpaceX hours of constant phone calls before the FAA finally responded.
If that series of events is accurate, as it seems to be, it’s a searing indictment of systematic ineptitude and laziness on behalf of the FAA. Having changed SpaceX’s Starship launch license to necessitate the presence of an FAA inspector mere weeks ago, thus giving a single person the power to scrub an entire launch attempt, the regulatory agency appears to have entrusted the entirety of that responsibility to a single “inspector.” Knowing full well that SpaceX works continuously with multiple shifts after almost two years of managing Starhopper and Starship tests, hops, and launches, the FAA then failed to ensure that some kind of communications infrastructure was in place to keep SpaceX appraised about the availability of a single inspector it now fully hinged on for all future Starship launches.
If, as the phrasing in both reports suggests, the FAA allotted a single government inspector to preside over all future Starship launches, that alone would bely a ridiculous level of ineptitude and naivete (or ignorance). To then trust that single person with nearly all of the responsibility of maintaining contact with SpaceX, day and night, would be akin to the FAA consciously guaranteeing that a disruptive breakdown in communications like this one would happen.
All told, SpaceX likely also needs to do some recalibration to better mesh and coexist with the FAA’s glacial reaction time and pace of work. However, the FAA is not going to be winning any favors if it continues to manage SpaceX’s Starship licensing in a manner as inept and cavalier as it has been. Far more importantly, if the FAA – one of the largest, best-funded regulatory bodies responsible for ensuring the safety of some of the most complex systems and vehicles on Earth – is unable to perform tasks as rudimentary as scheduling and contingency planning, it’s difficult to imagine how that same office could be trusted to regulate – and make safer – systems as extraordinarily complex as launch vehicles.
With any luck, the FAA will prove that the last four months have been minor bumps in the road to reliably and professionally licensing and regulating SpaceX’s Starship launch vehicle. However, after two separate demonstrations of systematic mismanagement over a mere four Starship launch attempts, it’s becoming harder and harder to soundly argue that the FAA still deserves the benefit of the doubt.
Assuming the FAA inspector is on schedule, Starship SN11’s next launch attempt is now scheduled between 7am and 3pm CDT (UTC-5) on Tuesday, March 30th.
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
