News
SpaceX Falcon 9 crushes next-gen ULA Vulcan rocket on cost in first competition
The United Launch Alliance’s (ULA) next-generation Vulcan Centaur rocket appears to have made it through what could be described as its first real competition with SpaceX and its Falcon 9 workhorse.
The US Space Force (or Air Force) awarded both rockets two launch contracts each on March 9th, marking the second award under “Phase 2” of a new National Security Space Launch (NSSL; formerly Evolved Expendable Launch Vehicle or EELV) agreement. The culmination of a multi-year competition, NSSL Phase 2 calcified in late 2020 when the US military ultimately chose ULA and SpaceX as its primary launch providers for the better part of the next decade.
The final Phase 2 agreement followed Phase 1, in which the USAF committed up to $2.3 billion to assist Blue Origin, Northrop Grumman, and ULA in their efforts to develop future military launch capabilities. SpaceX submitted a proposal but didn’t win funds. Even though the ULA-SpaceX dichotomy was already a more or less fixed outcome before the competition even began, the US military still managed to dole out almost $800 million to Blue Origin and Northrop Grumman before announcing that neither provider had been selected for Phase 2.
Notably, as part of Phase 1, ULA is on track to receive nearly $1 billion in USSF/USAF aid to develop its next-generation Vulcan Centaur rocket and ensure that it meets all of the military’s exacting, unique requirements. SpaceX, on the other hand, received a sum total of $0 from that opaque slush fund to meet the exact same requirements as ULA.
For Phase 2, the US military arbitrarily split the roughly two-dozen launch contracts up for grabs into a 60/40 pile. Even more bizarrely, the USAF did everything in its power to prevent two of the three rockets it had just spent more than $1.7 billion to help develop from receiving any of those two or three-dozen available launch contracts – all but literally setting $800M of that investment on fire. Short of comical levels of blind ineptitude, verging on criminal negligence, the only possible explanation for the US military’s behavior with NSSL Phase 1 and Phase 2 is a no-holds-barred effort to guarantee that ULA and its Vulcan Centaur rocket would have zero real competition.
The arbitrary 60:40 split of the final Phase 2 contract ‘lot’ further supports that argument. A government agency objectively interested in securing the best possible value and redundancy for its taxpayer-provided money would logically exploit a $1.7B investment as much as possible instead of throwing two-thirds of its ultimate value in the trash. On its own, a block-buy scenario – even with a leading goal of selecting two providers – is fundamentally inferior to an open competition for each of the dozens of launch contracts at hand.
Further, selecting the block-buy option and failing to split those contracts 50:50 makes it even clearer that the USAF’s only steadfast NSSL Phase 2 goal was to guarantee ULA enough Vulcan launch contracts for the company to be comfortable and (most likely) not lose money on a rocket that has yet to demonstrate an ability to compete on the commercial launch market.
Amazingly, despite multiple handicaps in the form of a 60:40 contract split and what amounts to a $1B subsidy that explicitly disadvantages its only competitor, ULA’s Vulcan rocket still appears to be ~40% more expensive than SpaceX’s Falcon 9. In the latest round of NSSL Phase 2 contracts, seemingly the first in which ULA’s Vulcan Centaur rocket was selected, SpaceX’s Falcon 9 received two East Coast launch contracts worth slightly less than $160M, averaging out to less than $80M each.
Outfitted with four of a possible zero, two, four, or six strap-on solid rocket boosters (SRBs), Vulcan Centaur received two launch contracts for $224M – an average of $112M each. Assuming ULA wins exactly 60% (~15) of the Phase 2 launch contracts up for grabs and receives no more than $1 billion in USAF development funding through NSSL Phase 1, some $67 million will have to be added to the cost of each announced Vulcan launch contract to get a truly accurate picture. In the case of the rocket’s first two contracts, the real average cost of each Vulcan Centaur launch could thus be closer to $179M ($112M+$67M).
According to ULA CEO Tory Bruno, both Vulcan missions are to “high-energy orbits,” whereas a USAF official told Spaceflight Now that SpaceX’s two Falcon 9 contracts were to “lower-energy orbits.” In Vulcan’s defense, if Bruno’s “high-energy orbit” comment means a circular geostationary orbit (GEO) or a very heavy payload to an elliptical geostationary transfer orbit (GTO), it’s possible that SpaceX would have had to use Falcon Heavy to complete the same contracts. Against Falcon Heavy’s established institutional pricing and excluding ULA’s $1B Phase 1 subsidy, Vulcan Centaur is reasonably competitive.
Ultimately, even with several significant cards stacked against it, SpaceX appears likely to continue crushing entrenched competitors like ULA and Arianespace on cost while still offering performance and results equivalent to or better than even than their “next-generation” rockets.
Tesla CEO Elon Musk teased the insane capabilities of the next major Full Self-Driving update just hours after the company rolled out version 14.2 to owners.
Tesla Full Self-Driving v14.2 had some major improvements from the previous iteration of v14.1.x. We were on v14.1.7, the most advanced configuration of the v14.1 family, before Tesla transitioned us and others to v14.2.
However, Musk has said that the improvements coming in the next major update, which will be v14.3, will be where “the last big piece of the puzzle finally lands.”
14.3 is where the last big piece of the puzzle finally lands
— Elon Musk (@elonmusk) November 21, 2025
There were some major improvements with v14.2, most notably, Tesla seemed to narrow in on the triggers that caused issues with hesitation and brake stabbing in v14.1.x.
One of the most discussed issues with the past rollout was that of brake stabbing, where the vehicle would contemplate proceeding with a route as traffic was coming from other directions.
We experienced it most frequently at intersections, especially four-way stop signs.
Elon Musk hints at when Tesla can fix this FSD complaint with v14
In our review of it yesterday, it was evident that this issue had been resolved, at least to the extent that we had no issues with it in a 62-minute drive, which you can watch here.
Some owners also reported a more relaxed driver monitoring system, which is something Tesla said it was working on as it hopes to allow drivers to text during operation in the coming months. We did not test this, as laws in Pennsylvania prohibit the use of phones at any time due to the new Paul Miller’s Law, which took effect earlier this year.
However, the improvements indicate that Tesla is certainly headed toward a much more sentient FSD experience, so much so that Musk’s language seems to be more indicative of a more relaxed experience in terms of overall supervision from the driver, especially with v14.3.
Musk did not release or discuss a definitive timeline for the release of v14.3, especially as v14.2 just rolled out to Early Access Program (EAP) members yesterday. However, v14.1 rolled out to Tesla owners just a few weeks ago in late 2025. There is the potential that v14.3 could be part of the coming Holiday Update, or potentially in a release of its own before the New Year.
Tesla rolled out Full Self-Driving version 14.2 yesterday to members of the Early Access Program (EAP). Expectations were high, and Tesla surely delivered.
With the rollout of Tesla FSD v14.2, there were major benchmarks for improvement from the v14.1 suite, which spanned across seven improvements. Our final experience with v14.1 was with v14.1.7, and to be honest, things were good, but it felt like there were a handful of regressions from previous iterations.
While there were improvements in brake stabbing and hesitation, we did experience a few small interventions related to navigation and just overall performance. It was nothing major; there were no critical takeovers that required any major publicity, as they were more or less subjective things that I was not particularly comfortable with. Other drivers might have been more relaxed.
With v14.2 hitting our cars yesterday, there were a handful of things we truly noticed in terms of improvement, most notably the lack of brake stabbing and hesitation, a major complaint with v14.1.x.
However, in a 62-minute drive that was fully recorded, there were a lot of positives, and only one true complaint, which was something we haven’t had issues with in the past.
The Good
Lack of Brake Stabbing and Hesitation
Perhaps the most notable and publicized issue with v14.1.x was the presence of brake stabbing and hesitation. Arriving at intersections was particularly nerve-racking on the previous version simply because of this. At four-way stops, the car would not be assertive enough to take its turn, especially when other vehicles at the same intersection would inch forward or start to move.
This was a major problem.
However, there were no instances of this yesterday on our lengthy drive. It was much more assertive when arriving at these types of scenarios, but was also more patient when FSD knew it was not the car’s turn to proceed.
Can report on v14.2 today there were ZERO instances of break stabbing or hesitation at intersections today
It was a significant improvement from v14.1.x
— TESLARATI (@Teslarati) November 21, 2025
This improvement was the most noticeable throughout the drive, along with fixes in overall smoothness.
Speed Profiles Seem to Be More Reasonable
There were a handful of FSD v14 users who felt as if the loss of a Max Speed setting was a negative. However, these complaints will, in our opinion, begin to subside, especially as things have seemed to be refined quite nicely with v14.2.
Freeway driving is where this is especially noticeable. If it’s traveling too slow, just switch to a faster profile. If it’s too fast, switch to a slower profile. However, the speeds seem to be much more defined with each Speed Profile, which is something that I really find to be a huge advantage. Previously, you could tell the difference in speeds, but not in driving styles. At times, Standard felt a lot like Hurry. Now, you can clearly tell the difference between the two.
It seems as if Tesla made a goal that drivers should be able to tell which Speed Profile is active if it was not shown on the screen. With v14.1.x, this was not necessarily something that could be done. With v14.2, if someone tested me on which Speed Profile was being used, I’m fairly certain I could pick each one.
Better Overall Operation
I felt, at times, especially with v14.1.7, there were some jerky movements. Nothing that was super alarming, but there were times when things just felt a little more finicky than others.
v14.2 feels much smoother overall, with really great decision-making, lane changes that feel second nature, and a great speed of travel. It was a very comfortable ride.
The Bad
Parking
It feels as if there was a slight regression in parking quality, as both times v14.2 pulled into parking spots, I would have felt compelled to adjust manually if I were staying at my destinations. For the sake of testing, at my first destination, I arrived, allowed the car to park, and then left. At the tail-end of testing, I walked inside the store that FSD v14.2 drove me to, so I had to adjust the parking manually.
This was pretty disappointing. Apart from parking at Superchargers, which is always flawless, parking performance is something that needs some attention. The release notes for v14.2. state that parking spot selection and parking quality will improve with future versions.
Any issues with parking on your end? 14.1.7 didn’t have this trouble with parking pic.twitter.com/JPLRO2obUj
— TESLARATI (@Teslarati) November 21, 2025
However, this was truly my only complaint about v14.2.
You can check out our full 62-minute ride-along below:
Elon Musk
SpaceX issues statement on Starship V3 Booster 18 anomaly
The incident unfolded during gas-system pressure testing at the company’s Massey facility in Starbase, Texas.
SpaceX has issued an initial statement about Starship Booster 18’s anomaly early Friday. The incident unfolded during gas-system pressure testing at the company’s Massey facility in Starbase, Texas.
SpaceX’s initial comment
As per SpaceX in a post on its official account on social media platform X, Booster 18 was undergoing gas system pressure tests when the anomaly happened. Despite the nature of the incident, the company emphasized that no propellant was loaded, no engines were installed, and personnel were kept at a safe distance from the booster, resulting in zero injuries.
“Booster 18 suffered an anomaly during gas system pressure testing that we were conducting in advance of structural proof testing. No propellant was on the vehicle, and engines were not yet installed. The teams need time to investigate before we are confident of the cause. No one was injured as we maintain a safe distance for personnel during this type of testing. The site remains clear and we are working plans to safely reenter the site,” SpaceX wrote in its post on X.
Incident and aftermath
Livestream footage from LabPadre showed Booster 18’s lower half crumpling around the liquid oxygen tank area at approximately 4:04 a.m. CT. Subsequent images posted by on-site observers revealed extensive deformation across the booster’s lower structure. Needless to say, spaceflight observers have noted that Booster 18 would likely be a complete loss due to its anomaly.
Booster 18 had rolled out only a day earlier and was one of the first vehicles in the Starship V3 program. The V3 series incorporates structural reinforcements and reliability upgrades intended to prepare Starship for rapid-reuse testing and eventual tower-catch operations. Elon Musk has been optimistic about Starship V3, previously noting on X that the spacecraft might be able to complete initial missions to Mars.
Tesla CEO Elon Musk teases insane capabilities of next major FSD update
Tesla Full Self-Driving v14.2 – Full Review, the Good and the Bad
