News
SpaceX may have signed a fairing agreement with ULA supplier RUAG (Update: no agreement)
According to unverified and speculative comments reportedly made to a member of the space industry by a RUAG spokesperson, the prominent aerospace supplier may have reached an agreement with SpaceX to manufacture a handful of larger payload fairings for future Falcon 9 and Heavy launches.
In the likely event that SpaceX is one of two contractors awarded a portion of several dozen US military launch contracts next year, the company will need to be able to cater to niche requirements, including accommodating unusually tall military satellites. Those satellites can be so tall that SpaceX’s own payload fairing – generally middle-of-the-pack relative to competitors’ offerings – may be too short, meaning that SpaceX will have to find ways around that minor shortcoming.
Update: Tim Chen has retracted his earlier comments and has stated that there is actually no agreement currently in place with SpaceX for RUAG to produce taller fairings out of its new Decatur, AL factory.
Additionally, ULA CEO Tory Bruno clarified that the company’s “[new fairing] has [ULA] intellectual property in its design and manufacture … [and] is currently planned only for use on Atlas and Vulcan”, meaning that any cooperation between SpaceX and RUAG would likely require a new production facility and a somewhat different fairing design.
“ULA’s new fairing, which is built in our factory in Decatur, has our intellectual property in its design and manufacture. This fairing is currently planned only for use on Atlas and Vulcan. You would want to ask RUAG about business they might have with their other customers.”
Tory Bruno, August 14th, 2019
Regardless of the veracity of these recent claims, it appears that SpaceX has three obvious responses at its disposal: design and build an entirely new variant of its universal Falcon fairing, purchase the necessary fairings from an established supplier, or bow out of launch contract competitions that demand it. The latter option is immediately untenable given that it could very well mean bowing out of the entire US military competition, known as Phase 2 of the National Security Space Launch program’s (NSSL; formerly EELV) Launch Services Procurement (LSP).
For dubious reasons, the US Air Force (USAF) has structured the NSSL Phase 2 acquisition in such a way that – despite there being four possible competitors – only two will be awarded contracts at its conclusion. The roughly ~30 launch contracts up for grabs would be split 60:40 between the two victors, leaving two competitors completely emptyhanded. In short, bowing out of the Phase 2 competition could mean forgoing as many as one or two-dozen contracts worth at least $1-2B, depending on the side of the 60:40 split.
According to a handful of recent comments and developments, SpaceX has likely sided with the option of procuring taller fairings from an industry supplier. As it turns out, European company RUAG has effectively cornered the Western rocket fairing market, with SpaceX being the only Western launch company currently building its own fairings. RUAG builds fairings for both Arianespace’s Ariane 5 and Vega rockets and ULA’s Atlas V. Additionally, RUAG will build and supply fairings for both companies’ next-gen rockets – Arianespace’s Ariane 6 and ULA’s Vulcan – and builds fairings for a number of smallsat launch companies.
Comments made in June by a RUAG official confirmed that there was some semblance of a relationship between SpaceX and RUAG for the purpose of satisfying USAF needs for taller fairings, although the phrasing suggested that the cooperation was in its early stages and nothing had been solidified.
“In a June 12 letter to Smith, the company’s CEO Peter Guggenbach makes the case that legislation forcing access to suppliers is unnecessary in this case because RUAG does not have an exclusive arrangement with ULA and is willing to work with SpaceX or any other launch providers.
“For this competition, we are in the process of submitting or have submitted proposals to multiple prime contractors regarding launch vehicle fairings. In those agreements, we share technical data to support a prime contractor’s bid while protecting our intellectual property.”
RUAG vice president Karl Jensen told SpaceNews the company has a “significant partnership” with ULA but is looking to work with others too. “We have an offer to SpaceX,” he said. “We don’t know if they’ll accept it.”
SpaceNews, 06/13/2019
Interestingly, although ULA’s RUAG-built Atlas V fairing is slightly narrower than SpaceX’s 5.2m (17 ft) diameter fairing, Atlas V’s largest fairing is significantly taller, supporting payloads up to 16.5m (54 ft) tall compared to 11m (36 ft) for Falcon 9 and Heavy. Given that just a tiny portion of military spacecraft actually need fairings that tall, SpaceX is apparently not interested in simply modifying its own fairing design and production equipment to support a 20-30% stretch.
This likely relates in part to the fact that one of SpaceX’s three NSSL Phase 2 competitors – Northrop Grumman (Omega), Blue Origin (New Glenn), and ULA (Vulcan) – are guaranteed to receive hundreds of millions of dollars of development funding after winning one of the two available slots (60% or 40% of contracts). SpaceX, on the other hand, will receive no such funding while still having to meet the same stringent USAF requirements compete in LSP Phase 2. Of note, Congressman Adam Smith managed to insert a clause into FY2020’s defense authorization bill that could disburse up to $500M to SpaceX in the event that the company is one of Phase 2’s two winners.
Despite this potential influx of infrastructure-focused funds, SpaceX may still be pursuing taller Falcon fairings from RUAG as a backup in the event that the company is not one of the two Phase 2 winners or is unable to use some of the $500M secured by Rep. Smith to develop its own stretched fairing.
On August 12th, SpaceX – along with Blue Origin, ULA, and NGIS – submitted bids for NSSL Phase 2 launch services, confirming that all four companies will indeed be in the running for contracts. The USAF is not expected to announce the results of this competition until Q2 2020.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
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
