Connect with us

News

SpaceX Starship launch delayed to Tuesday by poor FAA planning

Starship SN10, March 2nd. (SpaceX)

Published

on

Update: CEO Elon Musk says that SpaceX’s fourth high-altitude Starship launch has been delayed from Monday to Tuesday after an FAA inspector – recently required to be onsite for launches – was inexplicably more than six hours late.

While the smallest grain of salt is warranted given Musk’s recently vitriolic relationship with the FAA, the CEO has every reason not to lie about a federal regulatory agency that SpaceX almost fundamentally depends on. As such, the implication is that a lone FAA inspector – only recently required by the FAA itself to be onsite for SpaceX Starship launches – was somehow more than four or five hours away from Boca Chica, Texas by 11am CDT, March 29th.

The only possible explanation for such a delay is that a single inspector – lacking virtually any of the resources afforded to large government agency – missed a flight on a public airline, had a flight canceled at the last second, or was somehow stranded in the middle of nowhere by car issues. As any sane human familiar with air or car travel would know, those issues happen and should always be anticipated. Knowing full well that it had just changed SpaceX’s Starship launch license just two weeks prior to prevent flights without an inspector present, the FAA does not appear to have prepared for those issues in even the most basic sense, failing to ensure alternate methods of transport or two redundant inspectors.

In essence, due either to severe underfunding, general ineptitude, some childish attempt to assert dominance, or some combination of all three, the FAA has explicitly disrespected the hundreds of (possibly 1000+) SpaceX employees working around the clock for weeks to launch Starship SN11 as quickly as possible. Given that the FAA itself distributed Temporary Flight Restrictions (TFRs) for SN11’s Monday launch on Saturday and noted plans for the launch more than a day prior, the giant regulatory agency had no less than 24-48 hours of prior warning even if they’d somehow ignored or missed SpaceX’s own CEO announcing a delay to March 29th on March 26th.

If a regulatory agency like the FAA is incapable of ensuring that an inspector can stand around at a launch the agency itself required an inspector be present for days prior, the same apparatus assuredly should not and cannot be trusted to regulate systems as complex as modern aircraft, spacecraft, and rockets. If the FAA is, in fact, up to the challenge of responsibly regulating those systems with the public’s best interest in mind, then failing a task as simple as ensuring its own inspector is transported, on time, from Point A to Point B is a conscious decision or mistake. Either way, something clearly needs to change.

CEO Elon Musk says that SpaceX has delayed Starship serial number 11’s (SN11) high-altitude launch debut from Friday to Monday to best ensure that the company can “land & fully recover” the 50-meter-tall steel rocket.

Advertisement

First and foremost, the weekend will allow SpaceX times time for “additional checkouts” and scour Starship SN11 and the data it’s produced during testing for any red flags or minor issues. While plans for a same-day static fire and launch didn’t pan out on Friday, March 26th, SpaceX did manage the first half, firing up just one of Starship’s three Raptors to verify the health of the replacement engine after a Thursday Raptor swap. The test marked the first time SpaceX has intentionally fired up just one of the Raptors installed on a three-engine Starship prototype, so the delay will provide extra time to ensure that all three are still looking good.

The weather in Boca Chica, Texas has also taken a turn for the worse in the last few days, so the extra few days will also (hopefully) allow time for wind, visibility, and precipitation conditions to improve. According to Musk, Starship SN11 is now scheduled to fly as early as Monday “afternoon” and, as usual, SpaceX will offer live coverage of the fourth high-altitude launch and landing attempt beginning a few minutes before liftoff.

With a little luck, the Starship prototype will be able to continue a trend of iterative improvement and one-up Starship SN10 with a slightly softer landing and no explosion minutes after touchdown. Stay tuned for updates both here and on SpaceX’s social media platforms to catch the official webcast.

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

News

Tesla Full Self-Driving (Supervised) v14.1.7 real-world drive and review

On an hour-long drive, we tested v14.1.7 and tested its new capabilities, which are mostly overall performance and smoothness fixes rather than integrations of new features that are unknown to routine FSD users.

Published

on

tesla interior operating on full self driving
Credit: TESLARATI

Tesla started rolling out its Full Self-Driving (Supervised) v14.1.7 suite last night to owners, and there are several improvements to note within the new update that are at least the start of fixes to highly-mentioned issues.

On an hour-long drive, we tested v14.1.7 and tested its new capabilities, which are mostly overall performance and smoothness fixes rather than integrations of new features that are unknown to routine FSD users. However, there are a handful of shortcomings that are still present within the suite, which are not something that will be fixed within the span of a single update.

For what it is, Full Self-Driving does an excellent job of navigating — once you get it on its correct path. Our issues tend to be confined to navigation, routing, and the decision-making process that has to do with the way the car wants to get you to your destination. There were five things that happened on our first drive with v14.1.7 that are worth mentioning. The full drive will be available at the bottom of this article.

Navigation and Routing Still Seems to Be a Major Challenge

In past content, we’ve discussed the issues with routing and navigation, and how a Tesla chooses its path. Most noticeably, these issues occur in the same areas; for me, it’s my local Supercharger. My 2026 Model Y with AI4 continues to pick less-than-optimal routes out of the Supercharger, and in this instance, it actually chose to turn down a road, pull over, and give me the wheel, essentially asking, “Hey, can you get me on the right track here?”

This is still my biggest bone to pick with FSD, even more so than some of the bonehead moves it’s made in tougher scenarios (mostly parking lots with very limited visibility due to shrubs being planted in the worst possible locations). It’s rare that it happens, but this particular Supercharger has been a true thorn in the side of my Tesla.

This is not an issue that is confined to v14.1.7, or even v14 in general. Unfortunately, it is an issue that has persisted throughout my ownership experience, as well as during Demo Drives.

Stuttering and Hesitation at Intersections was Non-Existent

There was some confusion regarding my language in a recent article where I stated Tesla is confronting the issues that have been reported regarding the “stabbing” with braking.

“Tesla began the v14.1.4 launch last night, which included minor improvements and addressed brake-stabbing issues many owners have reported. In my personal experience, the stabbing has been awful on v14.1.3, and is a major concern.

However, many things have improved, and only a couple of minor issues have been recurring. Many of the issues v13 addressed are no longer an issue, so Tesla has made significant progress.”
It has undoubtedly improved, but it is not resolved.

With that being said, I did not feel a single example of hesitation, stabbing, or stuttering at a single intersection or instance when it has been present in the past. CEO Elon Musk said it would be fixed with v14.2, so it seems like Tesla is well on its way to resolving it.

Proper Handling of Crosswalks

It’s crazy how many people still do not stop for pedestrians at clearly-marked crosswalks. I had two instances of it happen during the drive, with FSD stopping for those pedestrians both times.

Human drivers did not stop either time:

Handled Merging onto a Highway with an Inconsiderate Driver Well

Routinely, drivers will get over into the left lane, if they are able, to allow merging traffic to safely enter the freeway. It does not always happen this way, and it’s not required by law.

Not exclusive to v14.1.7, as many past iterations would have done this as well, but it was nice to watch the vehicle slow down to let that traffic pass. It then entered the freeway safely, and the entire maneuver was well done.

Took an Appropriate Move with Oncoming Foot Traffic and Debris in a Tight Alleyway

This was probably the most on-edge I was during the drive because: 1) FSD chose to take an unnecessary alleyway, and 2) there was a box and oncoming pedestrians.

The car was aware of everything that was going on. In order to avoid the box, it would have had to turn toward the pedestrians, and in order to avoid the pedestrians, it would have had to turn into the box.

It chose to wait patiently, and after the pedestrians were past the car, FSD chose to proceed.

Closing Thoughts

Overall, we’re very impressed with v14.1.7, and we think this is Tesla’s best iteration of the FSD suite yet, as it should be since it’s the newest version available. Tesla’s attention to detail regarding the brake stabbing is really well done, and it seems evident that a complete fix is on its way.

Other than the navigation issue at the very beginning, which was not an intervention, at least in my opinion, this was a really successful drive.

Continue Reading

Elon Musk

Elon Musk debunks report claiming xAI raised $15 billion in funding round

xAI also responded with what appeared to be an automated reply, stating, “Legacy Media Lies.”

Published

on

Credit: xAI

Elon Musk has debunked a report claiming his AI startup xAI had raised $15 billion from a funding round. Reports of the alleged funding round were initially reported by CNBC, which cited sources reportedly familiar with the matter.

CNBC’s report

The CNBC story cited unnamed sources that claimed that the new capital injection would help fund GPUs that xAI needs to train its large language model, Grok. The news outlet noted that following the funding round, xAI was valued at $200 billion. 

Artificial intelligence startups have been raising funds from investors as of late. OpenAI raised $6.6 billion in October, valuing the startup at a staggering $500 billion. Reuters also reported last month that OpenAI was preparing for an IPO with a valuation of $1 trillion. Elon Musk’s xAI is looking to catch up and disrupt OpenAI, as well as its large language model, ChatGPT, which has become ubiquitous.

Elon Musk and xAI’s responses

In his response on X, Elon Musk simply stated that the CNBC story was “false.” He did not, however, explain if the whole premise of the publication’s article was fallacious, or if only parts of it were inaccurate. 

Amusingly enough, xAI also issued a response when asked about the matter by Reuters, which also reported on the story. The artificial intelligence startup responded with what appeared to be an automated reply, which read, “Legacy Media Lies.”

Advertisement

xAI, founded in July 2023 as an alternative to OpenAI and Anthropic, has aggressively built out infrastructure to support its flagship products, including Grok and its recently launched Grokipedia platform. The company is developing its Colossus supercomputer in Memphis, which is heralded as one of the world’s largest supercomputer clusters.

Continue Reading

News

Tesla reportedly testing Apple CarPlay integration: report

Citing insiders reportedly familiar with the matter, Bloomberg News claimed that CarPlay is being trialed by the EV maker internally.

Published

on

Credit: Tesla

Tesla is reportedly testing Apple’s CarPlay software for its vehicles, marking a major shift after years of resisting the tech giant’s ecosystem. 

Citing insiders reportedly familiar with the matter, Bloomberg News claimed that CarPlay is being trialed by the EV maker internally. The move could help Tesla gain more market share, as surveys have shown many buyers consider CarPlay as an essential feature when choosing a car.

Not the usual CarPlay experience

Bloomberg claimed that Tesla’s tests involve a rather unique way to integrate CarPlay. Instead of replacing the vehicle’s entire infotainment display, Tesla’s integration will reportedly feature a CarPlay window on the infotainment system. This limited approach will ensure that Tesla’s own software, such as Full Self-Driving’s visuals, remains dominant. 

The feature is expected to support wireless connectivity as well, bringing Tesla in line with other luxury automakers that already offer CarPlay. While plans remain fluid and may change before public release, the publication’s sources claimed that the rollout could happen within months. 

A change of heart

Tesla has been reluctant to grant Apple access to its in-car systems, partly due to Elon Musk’s past criticism of the tech giant’s App Store policies and its poaching of Tesla engineers during the failed Apple Car project. Tesla’s in-house software is also deemed by numerous owners as a superior option to CarPlay, thanks to its sleek design and rich feature set.

Advertisement

With Apple’s retreat from building cars and Elon Musk’s relationship with Apple for X and Grok, however, the CEO’s stance on the tech giant seems to be improving. Overall, Tesla’s potential CarPlay integration would likely be appreciated by owners, as a McKinsey & Co. survey last year found that roughly one-third of buyers considered the lack of such systems a deal-breaker.

Continue Reading

Trending