News
SpaceX set to launch NASA astronauts first after Boeing narrowly avoids catastrophe in space
SpaceX is set to become the first private company to launch NASA astronauts as few as three months from now, all but guaranteed after Boeing’s competing Starliner spacecraft narrowly avoided a catastrophe in space on its orbital launch debut.
The ultimate purpose of NASA’s Commercial Crew Program (CCP) is to ensure that the US is once again able to launch its own astronauts into orbit and to the International Space Station (ISS) – a capability the country has not possessed since it prematurely canceled the Space Shuttle in 2011. In a logical step, NASA decided to fund two independent companies to ensure that astronaut launch capabilities would be insulated against any single failure, ultimately awarding contracts to Boeing and SpaceX in 2014. Boeing did actually try to have Congress snub SpaceX back in 2014 and solely award the contract to Starliner, but the company thankfully failed.
As a result, SpaceX beating Boeing on the (not-a-) race to launch NASA astronauts to the International Space Station (ISS) would represent an immense and deeply embarrassing upset in the traditional aerospace industry – essentially a case of David and Goliath. For the better part of a decade, Congress, most industry officials, and Boeing itself have argued ad nauseum the Starliner spacecraft was clearly a far safer bet than anything built by SpaceX – Boeing, obviously, has far more experience (“heritage”) in the spaceflight industry. However, multiple “catastrophic” failures during Boeing’s recent Starliner ‘Orbital Flight Test’ (OFT) paint a far uglier picture.
As its PR team and executives will constantly remind anyone within earshot, Boeing helped build the first stage of the Saturn V rocket, while a company it bought years after the fact (Rockwell) did technically buy the company (North American) that built the spacecraft (Apollo CSM) that carried NASA astronauts from the Earth to the Moon (and back). Rockwell (acquired by Boeing) also built all five of NASA’s Space Shuttle orbiters.
In the 1990s, Boeing – set to lose a competition to build an expendable rocket for the US military – acquired McDonnell Douglas at the last second, slapping a Boeing sticker on the Delta IV rocket – designed and built by MD. Boeing then conspired to steal trade secrets from Lockheed Martin (bidding Atlas V) and used that stolen info to mislead the USAF about the real cost of Delta IV, thus securing the more lucrative of two possible contracts. This is all to point out the simple fact that Boeing has far less real experience designing spacecraft than it tends to act like it does.
As such, it’s substantially less surprising than it might otherwise be that Boeing’s Starliner spacecraft has had such a rocky orbital launch debut. Preceded just a matter of weeks by a quality assurance failure that prevented one of Starliner’s four parachutes from deploying after an otherwise-successful pad abort test, a second Starliner spacecraft launched atop an Atlas V rocket on its orbital launch debut (OFT) on December 20th, 2019. Atlas V performed flawlessly but immediately after Starliner separated from the rocket, things went very wrong.
Bad software ultimately caused the spacecraft to perform thousands of uncommanded maneuvering thruster burns, depleting a majority of its propellant before Boeing was able to intervene. Starliner managed to place itself in low Earth orbit (LEO), but by then it had nowhere near enough propellant left to rendezvous and dock with the ISS – one of the most crucial purposes of the uncrewed flight test. Unable to complete that part of the mission, Boeing instead did a few small tests over the course of 48 hours in orbit before commanding the spacecraft’s reentry and landing on December 22nd.
But wait, there’s more!
As it turns out, although both NASA and Boeing inexplicably withheld the information from the public for more than two months, Boeing’s OFT Starliner spacecraft reportedly almost suffered a second major software failure just hours before reentry. According to NASA and Boeing comments in a press conference held only after news of that second failure broke after an advisory panel broached the issue in February 2020, a second Starliner software bug – caught only because the first failure forced Boeing to double-check its code – could have had far more catastrophic consequences.
NASA officials stated that had the second bug not been caught, some of Starliner’s thruster valves would have been frozen, either entirely preventing or severely hampering the spacecraft’s detached trunk from properly maneuvering in orbit. Apparently, that service module (carrying fuel, abort engines, a solar array, and more) could have crashed into the crew module shortly after detaching from it. Unsurprisingly, that ‘recontact’ could have severely damaged the Starliner crew capsule, potentially making reentry impossible (or even fatal) if its relatively fragile heat shield bore the brunt of that impact.
SpaceX has undeniably suffered its own significant failures, most notably when flight-proven Crew Dragon capsule C201 exploded moments before a static fire test, but the company has already proven that it fixed the source of the failure with the spacecraft’s second successful launch on a Falcon 9 rocket. Ultimately, it’s becoming nearly impossible to rationally argue that Boeing’s Starliner will be safer than SpaceX’s Crew Dragon – let alone worth the 40% premium Boeing is charging NASA and the US taxpayer.
According to Ars Technica’s Eric Berger, Crew Dragon’s inaugural astronaut launch is now tentatively scheduled as early as late-April to late-May 2020. Paperwork – not technical hurdles – is currently the source of that uncertainty, and all Demo-2 mission hardware (Falcon 9 and Crew Dragon) is either already in Florida or days away from arriving.
Due to the combination of similar software failures Starliner suffered during its first and only launch, Boeing now has to review the entirety of the spacecraft’s software – more than a million lines of code – before NASA will allow the company to launch again. There’s also a very good chance that Boeing will now have to repeat the Orbital Flight Test, potentially incurring major delays. In short, it would take nothing less than a miracle – or NASA making a public mockery of itself for Boeing’s benefit – for Starliner to launch astronauts before SpaceX.
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
