News
Musk calls out SpaceX rival for receiving billion dollar subsidy, ULA head fires back
Following an intriguing SpaceX testimony before Senate committees in Washington D.C., Musk took to Twitter to share some thoughts on the state of the launch marketplace and SpaceX’s place within it. It didn’t take long for him to relate a somewhat common critique of the United Launch Alliance, SpaceX’s only American competition.
Sorry. That is simply not true. There is no "billion dollar subsidy". Amazing that this myth persists.
— Tory Bruno (@torybruno) July 14, 2017
Other orgs shd also develop reusable orbital rockets. If an airplane co had reusable airplanes, buying single use airplanes wd seem crazy. pic.twitter.com/OJotlGmPHt
— Elon Musk (@elonmusk) July 13, 2017
Tory Bruno, President and Chief Executive of ULA, responded with gloves off just a few hours later, deeming the implied existence of such a subsidy nothing more than a “[persistent] myth”. He spent fifteen or so minutes replying to skeptical and inquisitive followers on Twitter, stating that the Wikipedia paragraph on the subject was incorrect. Bruno was steadfast in his response saying that he had publicly testified on the public procurement process before Congress (he did, and he did not defer on the term “subsidy”), and he adamantly refused to back down on his statement that such a subsidy only existed in mythology.
For better or for worse, Bruno is correct to a large extent. In fact, he published a full editorial on the controversial subject in the canonical SpaceNews Magazine. The ELC (EELV (Evolved Expendable Launch Vehicle) Launch Contract) is the source of this controversy, and while not quite a full billion dollars, the FY2016 ELC contract was for $860 million.
-
SpaceX has admittedly been chronically doubted and mistreated in the realm of government contracting, and ULA has been less than perfectly civil in the past. Simply by existing, SpaceX in effect disrupted what was a American launch industry monopoly held between Boeing and Lockheed Martin. Those two companies merged their space endeavors approximately 11 years ago and have since been the United Launch Alliance. For reasons that do make a bit of sense but are still mildly obtuse, the United States Air Force chose to purchase ULA launch vehicles and the services that make the launch of those vehicles possible separately. The main given reason for this choice, as explored in Bruno’s editorial, is to give the Air Force added flexibility.
As discussed in the 2016 ELC contract itself, another large need for this type of funding lies in the maintenance of a large workforce, and the constant depreciation of both the Atlas and Delta families of launch vehicles. The Delta family, known mainly for the large Delta IV Heavy, is almost never utilized at this point in time, with Atlas being both more cost effective and more reliable. Regardless, due to contracting, ULA is required to maintain both the workforce and facilities necessary to produce and launch Delta vehicles, in spite of having nearly no “business” thanks to Atlas V. Maintaining a workforce and set of facilities that is in part or whole redundant is not efficient or cost-effective, but it is contractually required. So, while the ELC contract Musk deemed a nearly pointless subsidy does have some major flaws, inefficiencies, and illogical aspects, it is not technically correct to label it a subsidy.
-
- Operated by the same company responsible for the F-35, Atlas 5 is a highly reliable and equally expensive rocket. (ULA)
-
- Delta IV Heavy, the only current American heavy lift launch vehicle in service. Once operational, Falcon Heavy will be capable of launching nearly double the payload to GTO. (USAF/ULA, 2013)
Without the actual contract information, it is also difficult to know if ULA would still receive this contractual payment in lieu of conducting actual launches. Bruno frames it in such a way that it sounds like the U.S. government modifies the payment size based on the number and type of required launches for a given year. If the multi-year agreement means that launches delayed many months or more can still be swapped out at no additional charge, then this does indeed make a certain amount of sense. The array of discussion on the subject nevertheless fails to explore the consequences of launch provider-side issues, the likes of which ULA and Atlas 5 experienced earlier this year, resulting in some amount of delays.
We do that too, but for free
— Elon Musk (@elonmusk) July 13, 2017
While there can be no doubt that the actual gritty details of the ELC contracts deal explicitly with such possible outcomes, the lack of transparency (be that as a result of publicly inaccessible contract details or highly obtuse and lingo-heavy contract language) ultimately frames ELC contracts and the vehemence with which ULA defends them as a wasteful, overly complex, and unnecessary alternative to simply offering a fixed product with services inherently included, as SpaceX does.
-
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
