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 is bolstering its Cybercab fleet with the State of Texas’s regulatory bodies ahead of the planned launch of the all-electric ride-hailing vehicle this Thursday.
Seven purpose-built Tesla Cybercabs have been added to Texas’s official automated vehicle registry, appearing in the Texas Motor Carrier Credentialing System (TxMCCS) public lookup just three days before Tesla’s invite-only Cybercab launch event in Austin on September 3.
The records, visible through TxDMV’s Motor Carrier and Automated Motor Vehicle Operator Lookup, list seven 2026 Tesla Cybercabs under Tesla Robotaxi, LLC. Their VINs begin with the 5YJA prefix, distinct from the 7SAYG Model Y robotaxis that already dominate Tesla’s Texas fleet.
Community trackers that scrape the same public database recorded the new entries on August 31, bringing Tesla’s authorized Texas robotaxi total to 276 vehicles: 269 Model Ys and the seven Cybercabs:
🚨 There are now SEVEN Tesla Cybercabs registered with the state of Texas
We are just three days from Cybercab! pic.twitter.com/ndwhuFYsep
— TESLARATI (@Teslarati) August 31, 2026
Texas Senate Bill 2807, which took effect in late May 2026, created a self-certification framework for commercial Level 4 operations. Operators file through TxMCCS, attest to SAE Level 4 capability, maintain insurance, and keep an active vehicle list.
Tesla completed that process months earlier for its existing Model Y Robotaxi service, which has carried paying passengers in Austin, Dallas, Houston and other markets. Adding the Cybercabs to the same authorization means the new two-seat, steering-wheel-free vehicles are now legally recognized for commercial use on Texas roads.
The timing is deliberate as Tesla scheduled the September 3 event at its Austin campus after sending invitations to selected Robotaxi riders and other guests. The company has described the evening as a chance to “experience the future of full autonomy” and plans to livestream it.
Production Cybercabs, which lack pedals and a steering wheel, have been rolling off the Giga Texas line for months; some earlier examples still carried temporary driver controls for data collection. Registering a small fleet of the finished design immediately before the public event signals that Tesla intends to move the purpose-built vehicle from factory and test tracks into the same Robotaxi app already used by Model Y passengers.
The seven units remain a tiny fraction of Tesla’s overall Texas authorization and far smaller than competing fleets. Registration does not automatically equal unsupervised public rides; it is the legal prerequisite.
Still, the sudden appearance of Cybercab VINs in the state’s lookup system, after a year of Model Y-only listings, is the clearest official confirmation yet that Tesla’s dedicated robotaxi hardware is entering the regulatory pipeline at the same moment the company is preparing to show it to invited guests and a global livestream audience.
Whether those seven vehicles appear at the September 3 event or begin carrying passengers shortly afterward, their presence in TxMCCS marks a concrete regulatory step that has been anticipated since the Cybercab concept was first revealed.
Tesla has expanded the operational geofence for its driverless Robotaxi service in Austin, Texas, marking the first such increase in some time. The updated Service Area for Robotaxi in Austin now spans about 288 square miles and is roughly 9 percent larger than the previous boundary.
This incremental growth adds approximately 24 square miles of coverage, bringing the prior zone of roughly 264 square miles into a broader footprint that better serves northern suburbs.
The expansion extends the geofence northward toward Pflugerville along the US 183 corridor, incorporating additional neighborhoods north of the Domain and areas such as Mesa Park. These additions include higher-end residential and commercial districts that previously sat just outside the allowed operating zone.
Riders can now request unsupervised trips that begin or end in these newly included locations, provided the entire route remains inside the digital boundary:
Tesla has just expanded its Robotaxi service area in Austin, Texas for the first time in 10 months.
The new service area is roughly 9% larger than the old one, and is about 288 square miles in total. pic.twitter.com/i4oBM1KfWS
— Sawyer Merritt (@SawyerMerritt) August 31, 2026
Tesla first launched public Robotaxi operations in Austin in mid-2025 with a modest initial zone of about 20 square miles. Subsequent enlargements in 2025 and early 2026 steadily grew the map until it covered much of the metropolitan area.
After the last major update roughly ten months earlier, the company held the boundary steady while it collected additional miles and refined the FSD suite.
The modest nine percent increase still matters for daily utility. Longer trips become possible, more residents gain access, and the fleet can accumulate more diverse real-world data across new road types and traffic patterns. Observers note that the added territory aligns with existing Tesla service infrastructure, which could support more efficient vehicle staging in the North end of Austin.
Although the geofence has grown, Tesla continues to operate a relatively small unsupervised fleet in the city. The company has emphasized safety and software readiness over rapid geographic scaling. This latest map update signals that Tesla remains committed to expanding Robotaxi availability in its home market as it prepares for further software improvements and potential Cybercab deployments.
The 288-square-mile zone now gives Austin riders one of the larger driverless service areas currently available in the United States.
Tesla’s 2026 Summer Update turns Grok from a talking companion into a true in-car controller, with considerably expanded capabilities. Where the assistant once answered questions and handled navigation, it can now operate hardware and software through ordinary speech, including several requests at the same time.
Grok has become incredibly robust over the past few quarters, and this new ability that Tesla has included with its Summer Update is perhaps the clearest sign of just how capable it has become.
You can issue many commands to Grok at once, and each will be taken care of: anything from headlight control to climate adjustments to mirror folding can now all be taken care of with a simple sentence spoken toward Grok:
This is cool, you can now give Grok a ton of commands at once in your Tesla and it’ll do them all together.
The commands I gave:
• Fold mirrors
• Turn on wipers to fastest setting
• Change temp to 65°
• Open self-driving app
• Open gloveboxComes with Tesla’s 2026 Summer… pic.twitter.com/drZxoHrknv
— Sawyer Merritt (@SawyerMerritt) August 26, 2026
Here’s another example I used in my Model Y:
🚨 Using Grok to control the cabin temperature and turn on headlights in 2026 Model Y on FSD v14.3.8 and 2026.26.6.5 pic.twitter.com/7clgQkGABk
— TESLARATI (@Teslarati) August 27, 2026
Tesla’s official Release Notes list the core powers of Grok’s new capabilities: Grok can place phone calls from a paired phone, search a streaming service and queue music, adjust climate, and search the Controls panel. Drivers can also ask it questions about the vehicle or the latest features included in a recent software update.
It can also take care of driving settings, dynamics, and other relevant preferences that deal with how the car operates and handles.
Tesla Summer Update begins rolling out: a look at the new features
It’s also more of a use case than a novelty feature. Grok was great for learning about something that was being pondered while Full Self-Driving was taking care of the major automotive responsibilities, but it did have some useful functionality when it came to navigation.
Another less-noted improvement is the swift transition that Grok has from thinking of its answer to giving you one. In the past, it would take a few seconds for Grok to truly come up with a valuable response. It now seems that it is improving, at least slightly.
Tesla Cybercab fleet grows in Austin ahead of launch event
Tesla expands driverless Robotaxi geofence in Austin
