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.
Elon Musk
Elon Musk reveals date of Tesla Full Self-Driving’s next massive release
Initially planned for a January or February release, v14.3 aims to add some reasoning and logic to the decisions that Full Self-Driving makes, which could improve a lot of things, including Navigation, which is a major complaint of many owners currently.
Tesla CEO Elon Musk revealed the date of Full Self-Driving’s next massive release: v14.3.
For months, Tesla owners with Hardware 4 have been utilizing Full Self-Driving v14.2 and subsequent releases. Currently, the most up-to-date FSD version is v14.2.2.5, which has definitely brought out mixed reviews. With releases, some things get better, and other things might regress slightly.
For the most part, things are better in terms of overall behavior.
However, many owners have been looking forward to the next release, which is v14.3, about which Musk has said many great things. Back in November, Musk said that v14.3 “is where the last big piece of the puzzle lands.”
He added:
“We’re gonna add a lot of reasoning and RL (reinforcement learning). To get to serious scale, Tesla will probably need to build a giant chip fab. To have a few hundred gigawatts of AI chips per year, I don’t see that capability coming online fast enough, so we will probably have to build a fab.”
Initially planned for a January or February release, v14.3 aims to add some reasoning and logic to the decisions that Full Self-Driving makes, which could improve a lot of things, including Navigation, which is a major complaint of many owners currently.
Tesla Full Self-Driving v14.2 is a considerable improvement from early versions of the suite, but we have written about the somewhat confusing updates that have come with recent versions.
Tesla Full Self-Driving v14.2.2.5 might be the most confusing release ever
They’ve been incredibly difficult to gauge in terms of progress because some things have gotten better, but there seems to be some real regression on a handful of things, especially with confidence and assertiveness.
Musk confirmed today on X that Tesla is already testing v14.3 internally right now. It will hit a wide release “in a few weeks,” so we should probably expect it by late April.
It’s in testing right now. Wide release in a few weeks.
— Elon Musk (@elonmusk) March 19, 2026
Overall, there are high hopes that v14.3 could be a true game changer for Tesla Full Self-Driving, as many believe it could be the version that Robotaxis in Austin, Texas, some of which are driverless and unsupervised, are running.
It could also include some major additions, including “Banish,” also referred to as “Reverse Summon,” which would go find a parking spot after dropping occupants off at their destination.
What Tesla will roll out, and when exactly it arrives, all remain to be seen, but fans have been ready for a new version as v14.2.2.5 has definitely run its course. We have had a lot of readers tell us their biggest request is to fix Navigation errors, which seem to be one of the most universal complaints among daily FSD users.
Cybertruck
Chattanooga Charge: Tesla and EV fans ready for the Southeast’s wildest Tesla party
From Cybertruck Convoys to Kid-Friendly Fun Zones: The Chattanooga Charge Has Something for Everyone
Hundreds of like-minded Tesla and EV enthusiasts are descending on Chattanooga Charge this weekend for the largest Tesla meet in the Southeast. Taking place on March 20–22, 2026 at the stunning Tennessee Riverpark.
If you were there last year, you’ll know that it’s the ultimate experience to see the wildest Teslas in action, see the best in EV tech, and arguably the most fun – finally put a name to the face and connect with those social media buddies IRL! Oh, and that epic night time Tesla light show is a once-in-a-lifetime experience that will transform the Riverpark into something out of a sci-fi film that’s remarkably unforgettable and must be seen in person.
This year’s event takes everything up a notch, with over 100 Cybertrucks expected to be on display, many sporting jaw-dropping modifications and custom wraps that push the boundaries of what these stainless steel beasts can look like.
Whether you’re a diehard Tesla fan, EV supporter, or just EV-mod-curious, the sheer spectacle is worth the drive.
The Chattanooga Charge doesn’t wait until Saturday morning to get started. The weekend technically kicks off Friday, March 20th, and the venue sets the tone immediately. Come share roadtrip stories over drinks at the W-XYZ Rooftop Bar on the top floor of the Aloft Chattanooga Hamilton Place Hotel, with sunset views over the city.
Come morning, nurse your hangover with a some good coffee, and convoy with hundreds of other Tesla and EV drivers through Chattanooga to the event for some morning meet and greets before the speaker panel starts and the food trucks fire up.
Tesla owner clubs travel from across the country to be here, not just to show off their vehicles,, but to connect, share, and celebrate a shared passion for the future of driving.
Sounds like a plan to me. See you there, guys. Don’t miss it. Get your tickets at ChattanoogaCharge.com and join the charge. 🔋⚡
Chattanooga Charge is a premier Tesla and EV gathering inspired by the X Takeover, known as one of the largest Tesla event gatherings. What began as a bold idea from the team at DIY Wraps/TESBROS, hosted in their hometown of Chattanooga, Tennessee, the event quickly became a movement across social media. The first annual Chattanooga Charge united over 16 Tesla clubs from 16 states, proof that the EV community was hungry for something big in the South. Year after year, the event has grown in scale, ambition, and heart.
News
Tesla Full Self-Driving gets latest bit of scrutiny from NHTSA
The analysis impacts roughly 3.2 million vehicles across the company’s entire lineup, and aims to identify how the suite’s degradation detection systems work and how effective they are when the cars encounter difficult visibility conditions.
The National Highway Traffic Safety Administration (NHTSA) has elevated its probe into Tesla’s Full Self-Driving (Supervised) suite to an Engineering Analysis.
The analysis impacts roughly 3.2 million vehicles across the company’s entire lineup, and aims to identify how the suite’s degradation detection systems work and how effective they are when the cars encounter difficult visibility conditions.
The step up into an Engineering Analysis is often required before the NHTSA will tell an automaker to issue a recall. However, this is not a guarantee that a recall will be issued.
🚨 The NHTSA said it was upgrading a probe into Tesla’s Full Self-Driving (Supervised) platform to an “engineering analysis”
It will examine 3.2 million vehicles and aims to determine its effectiveness in evaluating degraded road conditions pic.twitter.com/2dkrv1mR8o
— TESLARATI (@Teslarati) March 19, 2026
The NTHSA wants to examine Tesla FSD’s ability to assess road conditions that have reduced visibility, as well as detect degradation to alert the driver with sufficient time to respond.
The Office of Defects Investigation (ODI) will evaluate the performance of FSD in degraded roadway conditions and the updates or modifications Tesla makes to the degradation detection system, including the timing, purpose, and capabilities of the updates.
Tesla routinely ships software updates to improve the capabilities of the FSD suite, so it will be interesting to see if various versions of FSD are tested. Interestingly, you can find many examples from real-world users of FSD handling snow-covered roads, heavy rain, and single-lane backroads.
However, there are incidents that the NHTSA has used to determine the need for this probe, at least for now. The agency said:
“Available incident data raise concerns that Tesla’s degradation detection system, both as originally deployed and later updated, fails to detect and/or warn the driver appropriately under degraded visibility conditions such as glare and airborne obscurants. In the crashes that ODI has reviewed, the system did not detect common roadway conditions that impaired camera visibility and/or provide alerts when camera performance had deteriorated until immediately before the crash occurred.”
It continues to say in its report that a review of Tesla’s responses revealed additional crashes that occurred in similar environments showed FSD “did not detect a degraded state, and/or it did not present the driver with an alert with adequate time for the driver to react. In each of these crashes, FSD also lost track of or never detected a lead vehicle in its path.”
The next steps of the NHTSA Engineering Analysis require the agency to gather further information on Tesla’s attempts to upgrade the degradation detection system. It will also analyze six recent potentially related incidents.
The investigation is listed as EA26002.
Elon Musk reveals date of Tesla Full Self-Driving’s next massive release
Chattanooga Charge: Tesla and EV fans ready for the Southeast’s wildest Tesla party
