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 released Full Self-Driving version 14.3.7 yesterday, and after about 90 miles of testing today, it is evident there are some definite fixes from version 14.3.6, which I wrote about last week and called a regression.
Within the first 40 minutes of my drive on v14.3.7, it saved me from getting into an accident with an unaware Dodge Charger driver, and some of the things Tesla seemed to miss in v14.3.6 were definitely improved. All in all, the release so far has some really great performance, and I’m looking forward to testing it further.
For now, here’s everything I noticed with v14.3.7:
Overall Improvement
Just generally speaking from a ride perspective, this was a really great experience. A lot of the hesitancy I experienced on v14.3.6 was gone. There were no instances of brake-stabbing, wheel-jerking, or any uncertain or unconfident movements. It was void of anything that I felt made it timid with v14.3.6.
The one thing I do hope to see down the road is a smaller need to adjust Speed Profiles so often. Because Tesla calls FSD “Supervised,” I’m okay with needing to hit the scroll wheel a few times a drive.
However, I hope that things can be incrementally improved upon with speed. Sometimes it’s too fast; other times it’s too slow. It’s a difficult thing to hone in and refine, but I hope it eventually gets there.
I didn’t notice any significant left lane camping or any behaviors that were completely out of line. I am hopeful that this opinion does not change, but after driving a few days with this version and putting it in a variety of different situations, you are exposed to more behaviors, some of which are not necessarily what I’d prefer.
The big things to notice, at least in my experience thus far, are that the major issues with previous versions — meaning the braking stabbing and wheel jerking — simply weren’t there. That’s enough to already consider this progress compared to .6.
Manual Signal Override is More Responsive
On .6, I had quite a few issues with FSD ignoring my manually input turn signals. If Tesla wants to call it “Supervised,” then the car should not ignore any input the driver gives. If I touch the accelerator on FSD, the car speeds up.
🚨 Tesla FSD v14.3.7 obeying manual turn signals https://t.co/6eqToXpQfC pic.twitter.com/vHBlFQ4PDV
— TESLARATI (@Teslarati) August 2, 2026
The car did a great job of obeying my turn signals when I wanted it to change lanes, which is welcome.
Parking Lot Performance
Before .6, I traditionally took over in nearly every parking lot my car entered, because I knew it would not park somewhere that I wanted, and usually, it was just a tad too timid in this setting.
The one bright spot of .6 was how well it handled parking lots. This continued with v14.3.7:
I’m always really happy to see progress at all, but once parking preferences come to FSD, as long as this performance is still around, that could potentially be the biggest improvement I’ve seen in FSD in the year I’ve been using it personally on a daily basis.
Full Self-Driving Averts Disaster
A Dodge Charger changed into my lane without checking if I was there, running me off the road. FSD made the initial avoidance maneuver; I grabbed the wheel out of instinct, looked in my side mirror to ensure I had nobody following closely behind, hit the brake, and straightened the car back up to avoid a curb:
🚨 Guys this is why you all NEED to stay vigilant behind the wheel, even on Tesla Full Self-Driving
Human drivers are UNHINGED and have no idea what they’re doing anymore. This was a kid obviously younger than 20 years old with zero awareness.
First drive with v14.3.7 https://t.co/1vTbCMpCn8 pic.twitter.com/lz7KKEF6bj
— TESLARATI (@Teslarati) August 2, 2026
There have been quite a few responses to this video stating that I should never have grabbed the wheel. To be honest, I really wish I had not done so, because I do believe FSD would have avoided any sort of collision with anything, including the car or the curb.
However, this was the first time I had ever been this close to being hit while using FSD. My natural reaction was to take over. I think if I had had something like this happen before, my reaction might have been different.
Hitting the brake avoided hitting the curb, while FSD swerved to avoid the car. My concern after the car was clear of my front end was the curb. All in all, I’m really happy with how things turned out, and I think anyone could be a critic of how I handled it. I only had a split second to really make a decision, and thankfully, any damage was avoided.
It is clear FSD managed to avoid the car coming down before I was able to. I truly credit FSD for avoiding the collision.
What Needs to Improve
Better Recognition of Potholes, Uneven Roads, Sharp Changes in Roadway/Bumps
On Friday, my Fianceè and I were in the car, and FSD was driving us. We crossed over a roadway that has a traffic light, and FSD was traveling at 40 MPH on Standard, 5 MPH over the speed limit. Everything was more than reasonable.
However, the road we were crossing at the light has a major bump both as you start and finish crossing it. Without a speed reduction, your car can go airborne. The Tesla did just this on Friday on v14.3.6; it was an uncomfortable bounce that pretty much confirmed I would not ever let FSD go over again unless we were sitting at that intersection when there is a red light.
I even tried scrolling down into Sloth quickly, but I ended up just taking over:
This is that big bounce that I mentioned in the quoted post.
It’s just a tad too drastic to take at the speed FSD wants to go over it. You can see me quickly swipe down into Sloth, but I intervened. https://t.co/K20PK9ysBg pic.twitter.com/81Oc82ZJcZ
— TESLARATI (@Teslarati) August 2, 2026
A few people have said it remains related to the vision-based approach and its difficulty comprehending 3D. This is a huge issue because this can cause serious damage at certain speeds.
Navigation
Nothing new here. I still turn off “Online Routing” quite frequently to get the car to take logical routes from time to time.
Auto Wipers
Auto Wipers are just plain bad. I really hope Tesla just uses a rain sensor. I thought they had improved at one point, but I still get dry wipes, Speed 4 on a drizzle, and Speed 2 on a steady rain. In reality, these should be switched.
You can watch our full review of Tesla Full Self-Driving v14.3.7 below:
🚨 Tesla Full Self-Driving v14.3.7 saved me from an accident! FULL REVIEW: https://t.co/1vTbCMpCn8 pic.twitter.com/9mHmKVoMVA
— TESLARATI (@Teslarati) August 2, 2026
SpaceX will report second quarter results after the market closes on Tuesday, August 4, marking the first time the company has opened its books to the public since its record IPO in June. Management will host a live audio only webcast at 4:30 p.m. ET, streamed on X, with no dial in option.
The debut carries more weight than a typical first quarter as a public company. Two trading days after the release, on August 6, the first tranche of SpaceX’s lockup expires, freeing roughly 911.5 million insider and employee shares, worth well over $100 billion at current prices and the largest such release in Wall Street history. A second, larger tranche tied to the stock trading 30 percent above its $135 IPO price never triggered, since shares have spent most of July trading below that price.
Wall Street’s models point to revenue near $6.9 billion for the quarter, up sharply from the $4.69 billion SpaceX reported in the first quarter, with a narrower per share loss than the $1.27 posted three months earlier, according to estimates compiled by Motley Fool. Those numbers will be the first look at how SpaceX’s three segments, Starlink, launch and AI, are performing independently.
SpaceX scores another massive Pentagon deal to support military satellites
Investors heading into the call have a specific list of questions. How many net new Starlink subscribers did SpaceX add after ending March with 10.3 million, and is average revenue per user holding up as the service expands into lower income markets. How much of the AI segment’s revenue reflects contract signings with Anthropic, Google and Reflection AI this year, deals that combined could annualize to nearly $28 billion if fully ramped. Whether capital expenditures, which nearly doubled in the AI segment alone between 2024 and 2025, are still accelerating or starting to plateau. And whether management offers any forward guidance at all, something SpaceX has never done publicly.
The report will also land days after Elon Musk publicly denied a Wall Street Journal report describing internal planning to separate Tesla’s China business ahead of a potential Tesla-SpaceX merger. Whether Musk or SpaceX executives address that speculation on the call, even indirectly, maybe something investors will be listening for on Tuesday.
As Teslarati reported after Musk’s own warning to short sellers last week, the CEO has made clear he expects skeptics to be proven wrong over time. Tuesday will be the first chance for the numbers themselves to make that case.
Elon Musk
SpaceX’s Starship just got filmed by its own cargo
SpaceX released new footage of Starship in space captured by the Starlink satellites it deployed.
SpaceX released a new video Friday evening showing Starship from an angle showcased by its own Starlink satellites, watching the rocket drift away in orbit.
The 65 second clip, posted on X, stitches together footage from four cameras mounted on a single Starlink V3 satellite. It opens with a close view of Starship’s 171 foot upper stage, still catching sunlight, then pulls back as the two spacecraft separate.
The footage comes from Starship’s 13th flight test, which launched July 24 from Starbase after a scrubbed attempt and an abort caused by an engine issue the week before. When Flight 13 finally flew, it carried the first batch of functional Starlink V3 satellites Starship has ever deployed, twenty of them, with six equipped with cameras meant to scan the ship’s heat shield during reentry.
View of Starship in space from a Starlink V3 satellite on Flight 13.
This composite is made of imagery from four separate cameras on a single satellite. Six of the satellites were equipped with cameras to scan Starship’s heat shield and transmit imagery down to operators to… pic.twitter.com/sNTHHz5vLr
— SpaceX (@SpaceX) July 31, 2026
Flight 13 checked most of its boxes. Starship deployed all 20 satellites, relit a Raptor engine in space, and splashed down softly in the Indian Ocean off Western Australia. Musk’s longer term plan calls for a Starlink V3 constellation of 100,000 satellites, according to a recent FCC filing, with Starship as the only vehicle capable of launching them at the volume that requires. Each Starship flight is designed to carry up to 60 V3 satellites once the vehicle reaches routine service, well beyond what Falcon 9 can carry in a single mission.
Starship is next expected to fly with an attempt at catching the ship itself with the launch tower’s mechanical arms, a maneuver SpaceX has so far reserved for the Super Heavy booster.
Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident
SpaceX’s biggest test yet arrives this week and it’s not a rocket launch
