News
Elon Musk says SpaceX’s orbital Starship debut headed for FAA faceoff in a few weeks
CEO Elon Musk says that SpaceX’s first completed Starship rocket could be ready for its orbital launch debut just “a few weeks” from now – far sooner than most expected.
On August 6th, SpaceX very stacked that same vehicle – Starship 20 (S20) and Super Heavy Booster 4 (B4) – to its full height for the first time ever, briefly creating the largest rocket ever assembled. However, the feat was equally a symbolic photo opportunity. SpaceX did install an unprecedented number of Raptor engines on Booster 4 and Ship 20 in a spectacularly short timeframe and both stages are technically meant for flight, but Starship S20 was demated less than an hour later and shipped back to the factory shortly thereafter.
Though they’d had Raptors installed and been stacked to their full ~120m (~390 ft) height, neither booster or ship were truly complete and at least 20% of their engines had yet to be qualified at SpaceX’s McGregor, Texas test campus. Both needed a week or two of additional work – mostly just wiring avionics and installing secondary and tertiary plumbing. Curiously, on August 13th, Starship S20 was once again rolled to SpaceX’s Boca Chica launch site in a partial state of completion, where it now sits beside the orbital launch mount for unknown reasons.
After several days of delays, SpaceX also removed Super Heavy B4 from the orbital launch mount and returned it to the build site on August 11th, where teams are still working to finish its secondary plumbing and avionics. Like Ship 20, all of its Raptors were removed soon after its return, freeing both to complete cryogenic proof testing without risking dozens of potentially flightworthy rocket engines.
Like all previous Starship prototypes, those ‘cryo proof’ tests will involved loading Ship 20 and Booster 4 with supercool liquid nitrogen (LN2), simulating the weight and extreme thermal stress of real liquid oxygen (LOx) and methane (LCH4) propellant without the risk of a catastrophic fire or explosion in the event of anomalies.
For more than a month, SpaceX also gradually outfitted one of two suborbital launch mounts with special hydraulic rams that would have simulated the thrust of Ship 20’s three sea level and three vacuum-optimized Raptor engines – the first Starship prototype with such a configuration. The same was true for Booster 4 and SpaceX had outfitted a new test jig with nine hydraulic rams labeled “B4” – clearly meant to simulate the thrust of nine engines pushing against the Super Heavy’s thrust puck. Additionally, a far larger structural test tool unofficially nicknamed the ‘can crusher’ has been more or less finished after ~6 weeks of work, leading many to assume that Booster 4 would be the first Super Heavy to be subjected to the immense simulated thrust of 29 Raptor engines.
However, earlier this week, SpaceX completely disassembled the six hydraulic rams installed on Mount B and removed all nine rams from the apparent Booster 4 jig. Starship S20 was then rolled back to spot beside the orbital launch mount – not the suborbital mount that had been carefully prepared for its test campaign mere days prior. At the time, the only practical explanation – save for some kind of catastrophic miscommunication – was that SpaceX had cancelled clear plans to cryo proof Ship 20 and Booster 4 with simulated Raptor thrust.
-
Up to now, every single major design change implemented on Starship’s engine section has resulted in the first prototype – and often one or several test tanks – being subjected to cryo proof testing with a complex series of hydraulic rams used to simulate thrust. That most recently peaked with SpaceX’s lone BN2.1 Super Heavy test tank, which seemingly passed a cryo proof, pressure test, and a jig capable of simulating the thrust of up to eight Raptor engines. However, SpaceX has never tested Super Heavy’s new nine-engine thrust puck and has certainly never subjected a Super Heavy booster skirt to the combined thrust of 20 outer engines and 9 center engines.
The fact that complex custom test stands and jigs had already been assembled and installed for Ship 20 and Booster 4 before they were removed or disassembled without use strongly implies that someone at SpaceX – presumably Elon Musk himself – has either decided that those tests are unnecessary or that skipping them is worth the substantial risk. Indeed, for Musk’s subsequent August 15th claim that Ship 20 and Booster 4 could be stacked and ready for flight just “a few weeks” from now to come true, 14-21 days is simply nowhere close to enough time to cryo proof, thrust sim, and static fire both vehicles; integrate the stages; and perform the first true integrate testing of a Starship stack – possibly up to and including some combination of a full-stack cryo proof, wet dress rehearsal, or static fire.
And, as Musk himself notes, that complex ballet of first-of-their-kind rocket prototypes might not even be the long straw for Starship’s orbital launch debut. Technically, short of some kind of major legal intervention, there is actually no way for Starship to launch in the next “few weeks.” In an absolute best-case scenario, the Federal Aviation Administration (FAA) would release a draft environmental review of SpaceX’s orbital Starship launch site today, accept public comments for the required 30 days, instantly clear Starbase with environmental approval within a few days of the public comment window, and then approve Starship’s South Texas orbital launch license as soon as the necessary environmental permissions are in hand.
In other words, the best-case ETA of regulatory approvals for Starship’s first orbital test flight is arguably late September and going off of FAA precedent, that optimistic scenario is also a fairy tale. In reality, a bare minimum of 2-3 months after the FAA releases its draft environmental impact statement is a more realistic best-case scenario for SpaceX. On the opposite end, it’s possible that the FAA will decide that SpaceX needs to complete an entirely new environmental review for its Starbase launch site, easily delaying Starship’s orbital launch debut by 6-12+ months. That doesn’t even account for the potential looming challenges SpaceX might have to surmount to secure an orbital Starship launch license.
Given the challenges SpaceX had in securing even a watered-down suborbital launch license for its medium-altitude Starship flight tests, it’s not out of the question that the FAA could attach some extremely onerous limitations to that license. Ultimately, only time (and the slightest hint of actual movement or urgency at the FAA) will tell and there is arguably nothing that would better apply pressure in the right places than the largest, most powerful, most ambitious rocket ever built sitting – ready for flight – at a brand new launch pad, waiting solely on regulatory approval.
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
