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.
News
Tesla (TSLA) receives “Buy” rating and $551 PT from Canaccord Genuity
He also maintained a “Buy” rating for TSLA stock over the company’s improving long-term outlook, which is driven by autonomy and robotics.
Canaccord Genuity analyst George Gianarikas raised his Tesla (NASDAQ:TSLA) price target from $482 to $551. He also maintained a “Buy” rating for TSLA stock over the company’s improving long-term outlook, which is driven by autonomy and robotics.
The analyst’s updated note
Gianarikas lowered his 4Q25 delivery estimates but pointed to several positive factors in the Tesla story. He noted that EV adoption in emerging markets is gaining pace, and progress in FSD and the Robotaxi rollout in 2026 represent major upside drivers. Further progress in the Optimus program next year could also add more momentum for the electric vehicle maker.
“Overall, yes, 4Q25 delivery expectations are being revised lower. However, the reset in the US EV market is laying the groundwork for a more durable and attractive long-term demand environment.
“At the same time, EV penetration in emerging markets is accelerating, reinforcing Tesla’s potential multi‑year growth runway beyond the US. Global progress in FSD and the anticipated rollout of a larger robotaxi fleet in 2026 are increasingly important components of the Tesla equity story and could provide sentiment tailwinds,” the analyst wrote.
Tesla’s busy 2026
The upcoming year would be a busy one for Tesla, considering the company’s plans and targets. The autonomous two-seat Cybercab has been confirmed to start production sometime in Q2 2026, as per Elon Musk during the 2025 Annual Shareholder Meeting.
Apart from this, Tesla is also expected to unveil the next-generation Roadster on April 1, 2026. Tesla is also expected to start high-volume production of the Tesla Semi in Nevada next year.
Apart from vehicle launches, Tesla has expressed its intentions to significantly ramp the rollout of FSD to several regions worldwide, such as Europe. Plans are also underway to launch more Robotaxi networks in several more key areas across the United States.
News
Waymo sues Santa Monica over order to halt overnight charging sessions
In its complaint, Waymo argued that its self-driving cars’ operations do not constitute a public nuisance, and compliance with the city’s order would cause the company irreparable harm.
Waymo has filed a lawsuit against the City of Santa Monica in Los Angeles County Superior Court, seeking to block an order that requires the company to cease overnight charging at two facilities.
In its complaint, Waymo argued that its self-driving cars’ operations do not constitute a public nuisance, and compliance with the city’s order would cause the company irreparable harm.
Nuisance claims
As noted in a report from the Los Angeles Times, Waymo’s two charging sites at Euclid Street and Broadway have operated for about a year, supporting the company’s growing fleet with round-the-clock activity. Unfortunately, this has also resulted in residents in the area reportedly being unable to sleep due to incessant beeping from self-driving taxis that are moving in and out of the charging stations around the clock.
Frustrated residents have protested against the Waymos by blocking the vehicles’ paths, placing cones, and “stacking” cars to create backups. This has also resulted in multiple calls to the police.
Last month, the city issued an order to Waymo and its charging partner, Voltera, to cease overnight operations at the charging locations, stating that the self-driving vehicles’ activities at night were a public nuisance. A December 15 meeting yielded no agreement on mitigations like software rerouting. Waymo proposed changes, but the city reportedly insisted that nothing would satisfy the irate residents.
“We are disappointed that the City has chosen an adversarial path over a collaborative one. The City’s position has been to insist that no actions taken or proposed by Waymo would satisfy the complaining neighbors and therefore must be deemed insufficient,” a Waymo spokesperson stated.
Waymo pushes back
In its legal complaint, Waymo stated that its “activities at the Broadway Facilities do not constitute a public nuisance.” The company also noted that it “faces imminent and irreparable harm to its operations, employees, and customers” from the city’s order. The suit also stated that the city was fully aware that the Voltera charging sites would be operating around the clock to support Waymo’s self-driving taxis.
The company highlighted over one million trips in Santa Monica since launch, with more than 50,000 rides starting or ending there in November alone. Waymo also criticized the city for adopting a contentious strategy against businesses.
“The City of Santa Monica’s recent actions are inconsistent with its stated goal of attracting investment. At a time when the City faces a serious fiscal crisis, officials are choosing to obstruct properly permitted investment rather than fostering a ‘ready for business’ environment,” Waymo stated.
News
Tesla FSD v14.2.2 is getting rave reviews from drivers
So far, early testers have reported buttery-smooth drives with confident performance, even at night or on twisty roads.
Tesla Full Self-Driving (Supervised) v14.2.2 is receiving positive reviews from owners, with several drivers praising the build’s lack of hesitation during lane changes and its smoother decision-making, among others.
The update, which started rolling out on Monday, also adds features like dynamic arrival pin adjustment. So far, early testers have reported buttery-smooth drives with confident performance, even at night or on twisty roads.
Owners highlight major improvements
Longtime Tesla owner and FSD user @BLKMDL3 shared a detailed 10-hour impression of FSD v14.2.2, noting that the system exhibited “zero lane change hesitation” and “extremely refined” lane choices. He praised Mad Max mode’s performance, stellar parking in locations including ticket dispensers, and impressive canyon runs even in dark conditions.
Fellow FSD user Dan Burkland reported an hour of FSD v14.2.2’s nighttime driving with “zero hesitations” and “buttery smooth” confidence reminiscent of Robotaxi rides in areas such as Austin, Texas. Veteran FSD user Whole Mars Catalog also demonstrated voice navigation via Grok, while Tesla owner Devin Olsen completed a nearly two-hour drive with FSD v14.2.2 in heavy traffic and rain with strong performance.
Closer to unsupervised
FSD has been receiving rave reviews, even from Tesla’s competitors. Xpeng CEO He Xiaopeng, for one, offered fresh praise for FSD v14.2 after visiting Silicon Valley. Following extended test drives of Tesla vehicles running the latest FSD software, He stated that the system has made major strides, reinforcing his view that Tesla’s approach to autonomy is indeed the proper path towards autonomy.
According to He, Tesla’s FSD has evolved from a smooth Level 2 advanced driver assistance system into what he described as a “near-Level 4” experience in terms of capabilities. While acknowledging that areas of improvement are still present, the Xpeng CEO stated that FSD’s current iteration significantly surpasses last year’s capabilities. He also reiterated his belief that Tesla’s strategy of using the same autonomous software and hardware architecture across private vehicles and robotaxis is the right long-term approach, as it would allow users to bypass intermediate autonomy stages and move closer to Level 4 functionality.
Tesla (TSLA) receives “Buy” rating and $551 PT from Canaccord Genuity
Waymo sues Santa Monica over order to halt overnight charging sessions
