Connect with us

News

Musk calls out SpaceX rival for receiving billion dollar subsidy, ULA head fires back

Published

on

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.

Advertisement
-->

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.

 

Advertisement
-->

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.

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.

Advertisement
-->

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.

Advertisement
Comments

Elon Musk

SpaceX Starship Version 3 booster crumples in early testing

Photos of the incident’s aftermath suggest that Booster 18 will likely be retired.

Published

on

Credit: SpaceX/X

SpaceX’s new Starship first-stage booster, Booster 18, suffered major damage early Friday during its first round of testing in Starbase, Texas, just one day after rolling out of the factory. 

Based on videos of the incident, the lower section of the rocket booster appeared to crumple during a pressurization test. Photos of the incident’s aftermath suggest that Booster 18 will likely be retired. 

Booster test failure

SpaceX began structural and propellant-system verification tests on Booster 18 Thursday night at the Massey’s Test Site, only a few miles from Starbase’s production facilities, as noted in an Ars Technica report. At 4:04 a.m. CT on Friday, a livestream from LabPadre Space captured the booster’s lower half experiencing a sudden destructive event around its liquid oxygen tank section. Post-incident images, shared on X by @StarshipGazer, showed notable deformation in the booster’s lower structure.

Neither SpaceX nor Elon Musk had commented as of Friday morning, but the vehicle’s condition suggests it is likely a complete loss. This is quite unfortunate, as Booster 18 is already part of the Starship V3 program, which includes design fixes and upgrades intended to improve reliability. While SpaceX maintains a rather rapid Starship production line in Starbase, Booster 18 was generally expected to validate the improvements implemented in the V3 program.

Tight deadlines

SpaceX needs Starship boosters and upper stages to begin demonstrating rapid reuse, tower catches, and early operational Starlink missions over the next two years. More critically, NASA’s Artemis program depends on an on-orbit refueling test in the second half of 2026, a requirement for the vehicle’s expected crewed lunar landing around 2028.

Advertisement
-->

While SpaceX is known for diagnosing failures quickly and returning to testing at unmatched speed, losing the newest-generation booster at the very start of its campaign highlights the immense challenge involved in scaling Starship into a reliable, high-cadence launch system. SpaceX, however, is known for getting things done quickly, so it would not be a surprise if the company manages to figure out what happened to Booster 18 in the near future.

Continue Reading

News

Tesla FSD (Supervised) is about to go on “widespread” release

In a comment last October, Elon Musk stated that FSD V14.2 is “for widespread use.”

Published

on

Tesla has begun rolling out Full Self-Driving (Supervised) V14.2, and with this, the wide release of the system could very well begin. 

The update introduces a new high-resolution vision encoder, expanded emergency-vehicle handling, smarter routing, new parking options, and more refined driving behavior, among other improvements.

FSD V14.2 improvements

FSD (Supervised) V14.2’s release notes highlight a fully upgraded neural-network vision encoder capable of reading higher-resolution features, giving the system improved awareness of emergency vehicles, road obstacles, and even human gestures. Tesla also expanded its emergency-vehicle protocols, adding controlled pull-overs and yielding behavior for police cars, fire trucks, and ambulances, among others.

A deeper integration of navigation and routing into the vision network now allows the system to respond to blocked roads or detours in real time. The update also enhances decision-making in several complex scenarios, including unprotected turns, lane changes, vehicle cut-ins, and interactions with school buses. All in all, these improvements should help FSD (Supervised) V14.2 perform in a very smooth and comfortable manner.

Elon Musk’s predicted wide release

The significance of V14.2 grows when paired with Elon Musk’s comments from October. While responding to FSD tester AI DRIVR, who praised V14.1.2 for fixing “95% of indecisive lane changes and braking” and who noted that it was time for FSD to go on wide release, Musk stated that “14.2 for widespread use.”

FSD V14 has so far received a substantial amount of positive reviews from Tesla owners, many of whom have stated that the system now drives better than some human drivers as it is confident, cautious, and considerate at the same time. With V14.2 now rolling out, it remains to be seen if the update also makes it to the company’s wide FSD fleet, which is still populated by a large number of HW3 vehicles. 

Advertisement
-->
Continue Reading

News

Tesla FSD V14.2 starts rolling out to initial batch of vehicles

It would likely only be a matter of time before FSD V14.2 videos are posted and shared on social media.

Published

on

Credit: Grok Imagine

Tesla has begun pushing Full Self-Driving (Supervised) v14.2 to its initial batch of vehicles. The update was initially observed by Tesla owners and veteran FSD users on social media platform X on Friday.

So far, reports of the update have been shared by Model Y owners in California whose vehicles are equipped with the company’s AI4 hardware, though it would not be surprising if more Tesla owners across the country receive the update as well. 

Based on the release notes of the update, key improvements in FSD V14.2 include a revamped neural network for better detection of emergency vehicles, obstacles, and human gestures, as well as options to select arrival spots. 

It would likely only be a matter of time before FSD V14.2 videos are posted and shared on social media.

Following are the release notes of FSD (Supervised) V14.2, as shared on X by longtime FSD tester Whole Mars Catalog.

Advertisement
-->

Release Notes

2025.38.9.5

Currently Installed

FSD (Supervised) v14.2

Full Self-Driving (Supervised) v14.2 includes:

  • Upgraded the neural network vision encoder, leveraging higher resolution features to further improve scenarios like handling emergency vehicles, obstacles on the road, and human gestures.
  • Added Arrival Options for you to select where FSD should park: in a Parking Lot, on the Street, in a Driveway, in a Parking Garage, or at the Curbside.
  • Added handling to pull over or yield for emergency vehicles (e.g. police cars, fire trucks, ambulances.
  • Added navigation and routing into the vision-based neural network for real-time handling of blocked roads and detours.
  • Added additional Speed Profile to further customize driving style preference.
  • Improved handling for static and dynamic gates.
  • Improved offsetting for road debris (e.g. tires, tree branches, boxes).
  • Improve handling of several scenarios including: unprotected turns, lane changes, vehicle cut-ins, and school busses.
  • Improved FSD’s ability to manage system faults and improve scenarios like handling emergency vehicles, obstacles on the road, and human gestures.
  • Added Arrival Options for you to select where FSD should park: in a Parking Lot, on the Street, in a Driveway, in a Parking Garage, or at the Curbside.
  • Added handling to pull over or yield for emergency vehicles (e.g. police cars, fire trucks, ambulances).
  • Added navigation and routing into the vision-based neural network for real-time handling of blocked roads and detours.
  • Added additional Speed Profile to further customize driving style preference.
  • Improved handling for static and dynamic gates.
  • Improved offsetting for road debris (e.g. tires, tree branches, boxes).
  • Improve handling of several scenarios, including unprotected turns, lane changes, vehicle cut-ins, and school buses.
  • Improved FSD’s ability to manage system faults and recover smoothly from degraded operation for enhanced reliability.
  • Added alerting for residue build-up on interior windshield that may impact front camera visibility. If affected, visit Service for cleaning!

Upcoming Improvements:

  • Overall smoothness and sentience
  • Parking spot selection and parking quality
Continue Reading