News
NASA head calls out SpaceX CEO Elon Musk over Starship event in bizarre statement
Roughly 24 hours before SpaceX CEO Elon Musk was scheduled to present an update on the company’s Starship launch vehicle development, NASA administrator Jim Bridenstine tweeted a bizarre and wholly unprovoked statement on the subject.
Seemingly equating SpaceX’s recent Crew Dragon delays with the distribution of Elon Musk’s public attention, the NASA administrator’s comment was almost universally criticized by the spaceflight community at large – and rightfully so.
First, some context. Created in 2010 and first supported with serious funding some 12-24 months later, NASA’s Commercial Crew Program (CCP) exists to replace the astronaut transport capabilities once offered by Space Shuttle and now achieved with contracts for seats on Russian Soyuz launches. Primarily the result of inept bureaucracy in NASA and Congress, the Space Shuttle was “retired” in 2011 in full knowledge that the US would have to rely on Russia to get NASA astronauts to the ISS until 2015 (at the absolute earliest).
Congress shut down multiple 2010 proposals to continue Shuttle flights until the late 2010s, choosing instead to kill the Shuttle and divert its associated funding to the expendable Ares V rocket (now the Space Launch System, SLS) and Orion crew capsule. More on that later...
Retweeted by Bridenstine’s official Twitter account, above is the absolute best-case interpretation of the NASA administrator’s comment. Although Eric Berger means well, the interpretation gives NASA far too much credit. Specifically, Bridenstine (or whoever fed him the statement) went out of his way to make it entirely one-sided in its focus on SpaceX. By all appearances, it would have never been posted if not for Elon Musk’s plans to present on Starship. Bridenstine additionally notes that “Commercial Crew is years behind schedule” and indicates that “NASA expects to see the same level of enthusiasm focused on [its] investments”.
Altogether, it’s simply impossible to interpret it as anything less than Bridenstine scolding SpaceX – and SpaceX alone – for not falling to the floor, kissing NASA’s feet, and pretending that Crew Dragon and Falcon 9 are the only things in existence. Absent from Bridenstine’s criticism was NASA’s other (and even more delay-complicit) Commercial Crew Partner, Boeing, who has yet to complete a pad abort or orbital flight test of its Starliner spacecraft. SpaceX completed Crew Dragon’s pad abort in 2015 and completed a flawless orbital flight test in March 2019.
In essence, Bridenstine is publicly implying that SpaceX needs to stop being (or appearing to be) distracted by Starship and focus 100% on Crew Dragon. Boeing was not mentioned, despite being a minimum of six months behind SpaceX and dramatically more ‘distracted’ in the Bridenstine-style interpretation of the word. For reference, Boeing is a publicly-traded company with 150,000 employees, annual revenue of more than $100B, and a market cap of $206B. Boeing has 14 subsidiaries, a handful of which are involved in spaceflight, and has no less than one or two dozen products that are each more fiscally important to shareholders and board members than Starliner.
Compared to Boeing’s annual ~$100B revenue, the entirety of the Starliner development program – from the drawing board in 2010 to crewed, orbital spaceflight sometime in 2020 – is ~$4.8B. On the scale of corporate focus, Starliner has likely been a blip at most in 2019, with the company probably far more focused on the systematic organizational failures that lead to the deaths of hundreds of people in two near-identical 737 MAX crashes. Alas, NASA administrator Jim Bridenstine did not release a statement publicly implying that Boeing needs to devote the “same level of enthusiasm” to Starliner after the second fatal 737 MAX crash in March 2019. Nor did Bridenstine release a statement charging Boeing with a lack of focus after continuous reports of issues with the company’s KC-46 Pegasus tanker program, nor Boeing’s recent $9.2B US Air Force trainer jet contract, or myriad other corporate focuses.
On the other hand, as Musk noted in his relatively subtle September 28th responses to Bridenstine’s implicitly derisive comment, something like 50-80% of the entirety of SpaceX’s workforce and resources are focused on Crew Dragon, the Falcon 9 rockets that will launch it, or a combination of both. At present, Starship is – at most – a side project, even if its strategic importance to SpaceX is hard to exaggerate. The same is largely true for Starlink, SpaceX’s ambitious internet satellite constellation program. It may be true that Starship will eventually make Crew and Cargo Dragon (as well as Falcon 9 and Falcon Heavy) wholly redundant, but that is likely years away and SpaceX will support NASA – as it is contractually required to – for as long as the space agency has vested interest in using Crew Dragon.
At the same time, NASA has explicitly and publicly chosen to prioritize safety over schedule with the Commercial Crew Program, accepting the possibility of delays and cost overruns to ensure that SpaceX and Boeing can build the safest spacecraft possible.
In a September 28th interview with CNN, Musk bluntly noted that the hardware was – at this point in time – more or less ready for flight and will be on-site at SpaceX’s Pad 39A Florida launch site within the next two months. According to Musk, from then on, any additional launch delays can almost entirely be attributed to the paperwork and reviews NASA must complete before giving SpaceX the go-ahead. If Bridenstine wants SpaceX to launch astronauts sooner, one – and possibly the only – solution is to tackle the roadblocks created by NASA’s own self-enforced red tape. The question, then, is whether Bridenstine wants to cut away red tape that may (or may not) be there for good reason.
When the pot calls the kettle black
Detached from whining about a contractor’s CEO presenting about a non-NASA program, complaining about Commercial Crew delays is at least slightly more reasonable. Originally intended to launch as early as 2015, Congress systematically underfunded the Commercial Crew Program by more than 50% for over half a decade, dispersing $2.4B of the $5.8B NASA requested from 2011 to 2016. Unsurprisingly, this completely upended Boeing and SpaceX development schedules. By September 2014, SpaceX aimed to have Crew Dragon certified by NASA for astronaut transport before the end of 2017, but even then, NASA already saw that schedule as overly optimistic.
It would be another two years before Congress began to seriously fund Commercial Crew at its requested levels, beginning in FY2016. In response to Bridenstine, former NASA deputy administrator Lori Garver noted that over the ~5 years Congress consistently withheld hundreds of millions of dollars of critical funds from Commercial Crew, NASA’s SLS rocket and Orion spacecraft were just as consistently overfunded above and beyond their budget requests. From 2011 to 2016 alone, SLS and Orion programs requested $11B and received an incredible $16.3B (148%) from Congress, while Commercial Crew requested $5.8B and received $2.4B (41%).
Ironically, despite literally receiving almost seven times as much funding as Crew Dragon and Starliner, SLS and Orion are arguably just as – if not more – delayed than their commercial brethren. Originally intended to launch an uncrewed test flight in 2017, there is now little to no chance that that mission (known then as EM-1 and now as Artemis-1) will launch before 2022, a delay of roughly half a decade. The cost of the SLS/Orion program recently crested $30B, a figure likely to grow to ~$40B before it has conducted a single launch. Of that funding, approximately a third has gone to Boeing, the primary contractor responsible for NASA’s comically-delayed SLS Core Stage – the orange booster pictured above.
The Commercial Crew development program will likely cost NASA $8B total over 9-10 years and produce two clean-sheet, high-performance, (relatively) low-cost crewed spacecraft. After their demonstration launches are completed, NASA will transition to fixed-price service contracts with SpaceX and Boeing to routinely send astronauts to the ISS several times per year.
Put simply, if Bridenstine actually cared about defending “the investments of the American taxpayer” more than wielding their sanctity as a political weapon, he wouldn’t have folded like a house of cards at the slightest resistance to his attempts to cull SLS/Orion delays and cost overruns, and he certainly wouldn’t be wasting breath complaining about what SpaceX’s CEO is or isn’t talking about.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
-
Tesla released Full Self-Driving version 14.3.6 last week, and after what was potentially one of the best FSD releases in v14.3.5, there has been a bit of a regression. While there are some bright spots, the changes made to v14.3.6 seem to have backtracked some behaviors.
Overall, it is hard to really complain about FSD in any sense; it has revolutionized how I travel literally anywhere. According to my self-driving app, the last time I went a day without using it was 59 days ago.
However, I think it’s also important to recognize when things are just plain bad with FSD. There are times it does truly mind-boggling things, and I’ll dive into those here. Additionally, I only had these issues on local roads, not on highways. Highway operation, generally, is always incredible other than the occasional complaint about speed or left lane camping.
With those things being said, my personal experience may not represent others’ experiences. A handful of people have said they have had a similar experience on v14.3.6, while others have said it is more than normal.
Turning Hesitancy, Inaccuracy
I’ve noticed more inaccuracy turning into multi-lane stretches of road than in any version I can remember. I’ve had at least three instances of FSD turning into a stretch of roadway that has two or more lanes, and not selecting a lane confidently as it has in past versions.
I think Tesla FSD v14.3.6 is a regression from previous .3 branches
This version in particular has been incredibly hesitant, jerky, and indecisive at times. There’s actually been two drives that I have decided to not used FSD for the remainder of the trip. These were local trips… pic.twitter.com/YobHDOKRS6
— TESLARATI (@Teslarati) July 26, 2026
Instead, the car will drive over one of the dashed road lines, and the steering wheel will jerk back and forth before picking the lane. It should be said that it has always picked the correct lane when choosing based on the navigation, but it is still very indecisive. The steering wheel jerking is reminiscent of some of the later versions of v13.
I admit I really hate to see the steering wheel jerking come back. However, I think when Tesla releases v14.3.7, it won’t be present. When there are occurrences of it in FSD versions, it is usually resolved by the following release.
FSD Disregards Manual Turn Signals
This is my biggest bone to pick with FSD other than Navigation issues, but this one seems like it would be such an easy fix.
If Tesla is going to put the word “Supervised” on the end of “Full Self-Driving,” then when I tell the car to do something, it should do it. If I input an increase in speed by pressing the accelerator, the car will immediately respond. It does not disregard my input because it feels it is traveling at the right speed.
FSD should never disobey and turn off turn signals that the driver inputs. Trying to direct the car into the correct lane, I had initiated the left turn signal not once, not twice, but three times, with the car turning it off all three times and continuing in a lane that would end in just one block. The only solution at this point would be to zipper merge.
This goes back to the fact that self-driving’s biggest bottleneck might be rider preference. A zipper merge might have been more than reasonable, might have saved me time that I spent sitting through an additional light cycle, and might be something many drivers would do. I was in no hurry, I traditionally do not try to zipper merge because it feels inconsiderate, and lastly, the car should have just followed my input.
This caused me to disengage and drive manually the rest of the way home. Sometimes I just do not need FSD to try to pass every car it can at intersections.
Bird Braking is a Thing of the Past
The big complaint with recent versions of Full Self-Driving has been what we’ve coined as “bird braking,” which is when the car will brake suddenly as a bird flies past.
There have been zero issues with this so far in v14.3.6, which is an excellent improvement.
FSD Might Already Be Taking Note of Driver Preferences
Another thing I have noticed over the past few days is that v14.3.6 seems to already be taking my preferences with navigation into account.
This is something that is supposed to be rolling out with the Summer Update, but I have a hunch it’s already present and might have been included in this v14.3.6 build. On Friday, FSD pulled into an entrance to a local convenience store that it had never attempted to go into before.
Typically, I manually pull into this entrance because it avoids heavy cross traffic at the main entrance. FSD has always chosen that congested main entrance.
I don’t want to get anyone excited but my Tesla running FSD v14.3.6 just:
✅ Pulled into an entrance at my local Sheetz that I routinely pull into manually but FSD never has entered
✅ Pulled into my assigned parking space at home despite many other spots being vacant https://t.co/ZUShvknTWO pic.twitter.com/83O5a2S0eh
— TESLARATI (@Teslarati) July 24, 2026
Additionally, FSD has pulled into my assigned parking spot at my townhouse community on multiple occasions with this release. This is something that used to happen ocassionally, but not consistently.
It also navigated back to the same convenience store last night, drove through crazy cars scrambling to gas pumps, navigated out of the parking lot correctly, drove me home, and, once again, parked in my assigned spot.
As previously stated, this release just seems to have a few things that need to be brought to Tesla’s attention, and also to make others who use FSD aware of some things that I’ve experienced. I look forward to the next release that will remedy these issues, just as Tesla has always done in the past.
Elon Musk’s massive Terafab project, which will be the first true conglomeration between each of his major entities, is set to get its final location soon, the CEO said on Tesla’s recent earnings call.
“The Terafab, we expect to announce a location soon, and provide more details about our plans in that regard. We’ll leave that to the product, the launch announcement rather than try to squeeze it into an earnings call,” Musk said last Wednesday.
Tesla Terafab set for launch: Inside the $20B AI chip factory that will reshape the auto industry
Terafab was announced by Musk back in March and was essentially a massive, vertically integrated semiconductor manufacturing project that would provide all the chips the three companies needed for their AI initiatives without needing third-party companies.
The plant will produce over 1 terawatt of AI compute each year, and will help back up projects like Optimus, Full Self-Driving, and other AI-based projects that Musk’s companies are working on.
In April, less than a month after the project was launched, Intel announced it would join the project, contributing manufacturing expertise and consulting to Terafab as a whole. Intel is one of three chip manufacturers that produce sub-5 nanometer chips at scale. TSMC and Samsung are the other two.
However, there was no true indication of where Terafab would end up, but most believe it will likely be somewhere in Texas. Business Insider has reported that SpaceX plans to build out Terafab in Grimes County, Texas, but this is unconfirmed.
Musk confirmed recently that it would not be on Giga Texas property, as it is simply too large.
The sheer scale of TERAFAB is going to be insane.
Elon said it wouldn’t be suitable for anywhere on Giga Texas property because it’s too big:
“We couldn’t possibly fit the Terafab on the GigaTexas campus. It will be far bigger than everything else combined there.
Several… pic.twitter.com/79GbhNNuf4
— TESLARATI (@Teslarati) March 23, 2026
Terafab holds much of Musk’s grand ambitions for the future within its construct. It holds so much responsibility for the future and the biggest projects that Musk’s companies can imagine.
“I think this is a very big announcement and it deserves to have its own day in the spotlight and not be squeezed into an earnings call,” he said. “I do think Terafab is going to be an amazing initiative and a necessary one, and one without which we will be constrained in our ability to scale Optimus production, because we simply won’t have enough AI chips.”
He continued by stating that Terafab is necessary for scaling Optimus, which Musk said could be the biggest product of any kind of all time. “It’s crucial to solve that, and we’ll have to solve memory, logic, and packaging in order to scale Optimus.”
SpaceX performed a secret test on a specific portion of Starship with its recent 13th test flight last week, CEO Elon Musk revealed.
Starship’s 13th test flight took place last Friday, and in many aspects, it was one of the most overwhelmingly successful launches in the project’s history.
All of the mission objectives were met without incident, both the Super Heavy Booster and Ship managed to perform safe splashdowns in the Gulf of America and the Indian Ocean, respectively, and the deployment of Starlink satellites came and went without any complications.
— Elon Musk (@elonmusk) July 25, 2026
However, there was more on the agenda for SpaceX with Flight 13. Musk revealed an internal test of the ship’s heat shield tiles, as the space exploration company wanted to push them to the limits after previous issues.
Many noticed that Starship’s initial launch seemed to be more accelerated than normal, and that was not a mistake. Musk revealed that SpaceX decided to give Flight 13 an intentionally aggressive acceleration rate in an effort to test how well the tiles would remain attached to the ship:
This flight intentionally had much higher acceleration to test how well the heat shield tiles would remain attached at high dynamic pressure.
Test was successful.
— Elon Musk (@elonmusk) July 25, 2026
SpaceX had issues with some of the heat shield tiles remaining attached early on in the Starship program. The first six test flights presented some kind of anomaly with them, so the company’s big focus with them was to figure out a way to keep them intact through the duration of the flight.
Things truly improved as Flight 10 showed that ceramic tiles generally stayed attached to the ship far better due to refined attachment, as SpaceX utilized pins instead of adhesives. Flights 10 through 13 truly showed some clear progress with the heat shield tiles, and this latest test seems to be where some real progress was noticed, especially by Musk.
The 13th Starship launch last Friday was the second with Starship V3, SpaceX’s latest and greatest iteration of the spacecraft. Goals and ambitions are getting even grander as the project continues to progress. Musk has already hinted that SpaceX will likely try to catch Starship with Flight 14.
Tesla Full Self-Driving v14.3.6 review: a rare regression, but some bright spots
Musk’s massive Terafab project will get final location soon
