News
SpaceX sets Dragon reuse record, debuts drone ship on first launch in two months
Update #2: After a 24-hour weather delay, conditions were far more favorable on August 29th, allowing a SpaceX Falcon 9 rocket to lift off for the first time in almost two months and send a cargo-filled Dragon spacecraft on its way to the International Space Station (ISS).
Aside from marking the end of SpaceX’s longest launch hiatus in two years, CRS-23’s successful liftoff also means that the company has smashed the world record for fastest orbital space capsule reuse. As part of Cargo Dragon 2’s first reuse ever, SpaceX launched Dragon C208 just seven and a half months (227d) after its first orbital reentry and splashdown, handily beating the previous record of 328 days. Additionally, flying for the fourth time, Falcon 9 booster B1064 became the first rocket to land on brand new SpaceX drone ship A Shortfall of Gravitas (ASOG) after sending Dragon C208 on its way to the ISS.
Getting a nice view of CRS-23's trunk as it separates, confirming no trunk cargo on this flight. pic.twitter.com/ZeJjviKqFE— Jonathan McDowell (@planet4589) August 29, 2021
Update: Although the weather forecast has worsened, SpaceX remains on track to attempt its first launch in eight weeks – a mission that will also smash one of the company’s orbital spacecraft reusability records.
While mostly mundane, a system preceding Tropical Storm Ida is producing conditions less than optimal for rocket launches, raising the risk of in-flight lightning strikes and the chances of Falcon 9 and Dragon flying through clouds containing precipitation (rain/ice/etc). Ultimately, that means that there’s just a 40% chance (down from 50% in the last few days) that weather conditions will be favorable for SpaceX to launch CRS-23. Regardless, barring a surprise announcement in the next few hours, it appears that there’s enough of a chance that SpaceX and NASA will still make an attempt.
If all goes according to plan, a flight-proven Falcon 9 rocket will send an upgraded Cargo Dragon on the way to orbit for the second time in seven months – almost twice as fast a turnaround as SpaceX’s ~340-day record for orbital spacecraft reuse. Tune in below around 3:20am EDT (07:20 UTC) to catch the hopeful launch live.
For the first time in more than nine weeks, SpaceX has completed a routine Falcon 9 preflight test known as a static fire and verified that the rocket is ready to launch later this week.
Save for at least one booster qualification test completed at SpaceX’s McGregor, Texas development facilities, Falcon 9’s August 25th static fire is the first since June 22nd. The upgraded Cargo Dragon space station resupply mission the rocket will support will also be SpaceX’s first launch since June 30th – the company’s longest hiatus between launches since a three-month pause that began two years ago.
Now, just a few days before that drought is expected to end, a SpaceX executive has partially explained why the company hasn’t launched a single Falcon rocket in ~60 days after completing a record 20 orbital launches in the first half of 2021.
-
Speaking at the 2021 Space Symposium on August 24th, SpaceX President and COO Gwynne Shotwell revealed that the company had chosen to pause Starlink missions (representing the vast majority of its 2021 launches) and focus on preparing a new generation of satellites for flight. Believed to be called Starlink V1.5, those new satellites represent a relatively small design change save for one crucial addition: multiple lasers.
All the way back in mid-2018, SpaceX launched its very first pair of Starlink prototype satellites – spacecraft that largely functioned as expected and provided a wealth of data but were almost nothing like the Starlink V0.9 and V1.0 spacecraft SpaceX would eventually start launching in 2019. Nevertheless, they did carry sets of small lasers generally known as optical intersatellite links or OISLs for short. Not radically dissimilar to the hundreds of thousands of miles of fiber optic cables that make up the backbone of the internet, lasers operating in the vacuum of space can effectively mirror the extraordinary bandwidth and performance offered by fiber connections – but wirelessly.
Instead of carefully insulated cables filled with tiny threads of glass, which really just serve as a controlled environment for light-based communications, OISLs enable a similar feat by replacing cables with extraordinarily precise mechanisms capable of aiming lasers with sub-millimeter precision from dozens or hundreds of miles away. As a result, laser interlinks are fairly complex and expensive devices – not something currently economical to install on thousands of satellites mainly focused on affordability.
SpaceX, of course, has wanted to install unprecedentedly affordable laser interlinks on thousands of Starlink satellites for as long as the constellation has been publicly discussed. If realized, it would create an extraordinary orbital mesh network that would allow Starlink to self-route a large portion of user communications without the need for a colossal network of tens of thousands of ground stations covering every inch of Earth – land, sea, ice, and all. A Starlink constellation with near-universal laser interlinks could also potentially allow the constellation to not only match – but beat by a large margin – the latency of best-case terrestrial fiber-optic connections.
After effectively completing Starlink’s first ‘shell’ of satellites earlier this year, SpaceX shifted its focus to preparing for polar Starlink launches from both its west and east coast facilities. While the first shell lacked interlinks entirely, SpaceX appears to have decided that all polar Starlink satellites will be launched with its own custom-built space lasers, even if that means delaying Starlink launches until those lasers are ready for action. Due to the fact that the vast majority of SpaceX’s launches as of late have been its own Starlink missions, the company’s Falcon rockets simply haven’t had anything to launch.
That should change on August 28th, when a thrice-flown Falcon 9 booster launches a refurbished spacecraft on its second orbital space station resupply – a first for SpaceX’s upgraded Cargo Dragon 2 vehicle. A Shortfall of Gravitas (ASOG), SpaceX’s newest drone ship, will also be supporting its first Falcon landing ever as part of CRS-23, hopefully recovering Falcon 9 booster B1064 for a fifth launch later this year.
Tune in around 3:20am (07:20 UTC) on Saturday, August 28th to watch SpaceX’s first launch in two months live.
-
Tesla released Full Self-Driving version 14.3.6 last week, and after what was potentially one of the best FSD releases in v14.3.5, there has been a bit of a regression. While there are some bright spots, the changes made to v14.3.6 seem to have backtracked some behaviors.
Overall, it is hard to really complain about FSD in any sense; it has revolutionized how I travel literally anywhere. According to my self-driving app, the last time I went a day without using it was 59 days ago.
However, I think it’s also important to recognize when things are just plain bad with FSD. There are times it does truly mind-boggling things, and I’ll dive into those here. Additionally, I only had these issues on local roads, not on highways. Highway operation, generally, is always incredible other than the occasional complaint about speed or left lane camping.
With those things being said, my personal experience may not represent others’ experiences. A handful of people have said they have had a similar experience on v14.3.6, while others have said it is more than normal.
Turning Hesitancy, Inaccuracy
I’ve noticed more inaccuracy turning into multi-lane stretches of road than in any version I can remember. I’ve had at least three instances of FSD turning into a stretch of roadway that has two or more lanes, and not selecting a lane confidently as it has in past versions.
I think Tesla FSD v14.3.6 is a regression from previous .3 branches
This version in particular has been incredibly hesitant, jerky, and indecisive at times. There’s actually been two drives that I have decided to not used FSD for the remainder of the trip. These were local trips… pic.twitter.com/YobHDOKRS6
— TESLARATI (@Teslarati) July 26, 2026
Instead, the car will drive over one of the dashed road lines, and the steering wheel will jerk back and forth before picking the lane. It should be said that it has always picked the correct lane when choosing based on the navigation, but it is still very indecisive. The steering wheel jerking is reminiscent of some of the later versions of v13.
I admit I really hate to see the steering wheel jerking come back. However, I think when Tesla releases v14.3.7, it won’t be present. When there are occurrences of it in FSD versions, it is usually resolved by the following release.
FSD Disregards Manual Turn Signals
This is my biggest bone to pick with FSD other than Navigation issues, but this one seems like it would be such an easy fix.
If Tesla is going to put the word “Supervised” on the end of “Full Self-Driving,” then when I tell the car to do something, it should do it. If I input an increase in speed by pressing the accelerator, the car will immediately respond. It does not disregard my input because it feels it is traveling at the right speed.
FSD should never disobey and turn off turn signals that the driver inputs. Trying to direct the car into the correct lane, I had initiated the left turn signal not once, not twice, but three times, with the car turning it off all three times and continuing in a lane that would end in just one block. The only solution at this point would be to zipper merge.
This goes back to the fact that self-driving’s biggest bottleneck might be rider preference. A zipper merge might have been more than reasonable, might have saved me time that I spent sitting through an additional light cycle, and might be something many drivers would do. I was in no hurry, I traditionally do not try to zipper merge because it feels inconsiderate, and lastly, the car should have just followed my input.
This caused me to disengage and drive manually the rest of the way home. Sometimes I just do not need FSD to try to pass every car it can at intersections.
Bird Braking is a Thing of the Past
The big complaint with recent versions of Full Self-Driving has been what we’ve coined as “bird braking,” which is when the car will brake suddenly as a bird flies past.
There have been zero issues with this so far in v14.3.6, which is an excellent improvement.
FSD Might Already Be Taking Note of Driver Preferences
Another thing I have noticed over the past few days is that v14.3.6 seems to already be taking my preferences with navigation into account.
This is something that is supposed to be rolling out with the Summer Update, but I have a hunch it’s already present and might have been included in this v14.3.6 build. On Friday, FSD pulled into an entrance to a local convenience store that it had never attempted to go into before.
Typically, I manually pull into this entrance because it avoids heavy cross traffic at the main entrance. FSD has always chosen that congested main entrance.
I don’t want to get anyone excited but my Tesla running FSD v14.3.6 just:
✅ Pulled into an entrance at my local Sheetz that I routinely pull into manually but FSD never has entered
✅ Pulled into my assigned parking space at home despite many other spots being vacant https://t.co/ZUShvknTWO pic.twitter.com/83O5a2S0eh
— TESLARATI (@Teslarati) July 24, 2026
Additionally, FSD has pulled into my assigned parking spot at my townhouse community on multiple occasions with this release. This is something that used to happen ocassionally, but not consistently.
It also navigated back to the same convenience store last night, drove through crazy cars scrambling to gas pumps, navigated out of the parking lot correctly, drove me home, and, once again, parked in my assigned spot.
As previously stated, this release just seems to have a few things that need to be brought to Tesla’s attention, and also to make others who use FSD aware of some things that I’ve experienced. I look forward to the next release that will remedy these issues, just as Tesla has always done in the past.
Elon Musk’s massive Terafab project, which will be the first true conglomeration between each of his major entities, is set to get its final location soon, the CEO said on Tesla’s recent earnings call.
“The Terafab, we expect to announce a location soon, and provide more details about our plans in that regard. We’ll leave that to the product, the launch announcement rather than try to squeeze it into an earnings call,” Musk said last Wednesday.
Tesla Terafab set for launch: Inside the $20B AI chip factory that will reshape the auto industry
Terafab was announced by Musk back in March and was essentially a massive, vertically integrated semiconductor manufacturing project that would provide all the chips the three companies needed for their AI initiatives without needing third-party companies.
The plant will produce over 1 terawatt of AI compute each year, and will help back up projects like Optimus, Full Self-Driving, and other AI-based projects that Musk’s companies are working on.
In April, less than a month after the project was launched, Intel announced it would join the project, contributing manufacturing expertise and consulting to Terafab as a whole. Intel is one of three chip manufacturers that produce sub-5 nanometer chips at scale. TSMC and Samsung are the other two.
However, there was no true indication of where Terafab would end up, but most believe it will likely be somewhere in Texas. Business Insider has reported that SpaceX plans to build out Terafab in Grimes County, Texas, but this is unconfirmed.
Musk confirmed recently that it would not be on Giga Texas property, as it is simply too large.
The sheer scale of TERAFAB is going to be insane.
Elon said it wouldn’t be suitable for anywhere on Giga Texas property because it’s too big:
“We couldn’t possibly fit the Terafab on the GigaTexas campus. It will be far bigger than everything else combined there.
Several… pic.twitter.com/79GbhNNuf4
— TESLARATI (@Teslarati) March 23, 2026
Terafab holds much of Musk’s grand ambitions for the future within its construct. It holds so much responsibility for the future and the biggest projects that Musk’s companies can imagine.
“I think this is a very big announcement and it deserves to have its own day in the spotlight and not be squeezed into an earnings call,” he said. “I do think Terafab is going to be an amazing initiative and a necessary one, and one without which we will be constrained in our ability to scale Optimus production, because we simply won’t have enough AI chips.”
He continued by stating that Terafab is necessary for scaling Optimus, which Musk said could be the biggest product of any kind of all time. “It’s crucial to solve that, and we’ll have to solve memory, logic, and packaging in order to scale Optimus.”
SpaceX performed a secret test on a specific portion of Starship with its recent 13th test flight last week, CEO Elon Musk revealed.
Starship’s 13th test flight took place last Friday, and in many aspects, it was one of the most overwhelmingly successful launches in the project’s history.
All of the mission objectives were met without incident, both the Super Heavy Booster and Ship managed to perform safe splashdowns in the Gulf of America and the Indian Ocean, respectively, and the deployment of Starlink satellites came and went without any complications.
— Elon Musk (@elonmusk) July 25, 2026
However, there was more on the agenda for SpaceX with Flight 13. Musk revealed an internal test of the ship’s heat shield tiles, as the space exploration company wanted to push them to the limits after previous issues.
Many noticed that Starship’s initial launch seemed to be more accelerated than normal, and that was not a mistake. Musk revealed that SpaceX decided to give Flight 13 an intentionally aggressive acceleration rate in an effort to test how well the tiles would remain attached to the ship:
This flight intentionally had much higher acceleration to test how well the heat shield tiles would remain attached at high dynamic pressure.
Test was successful.
— Elon Musk (@elonmusk) July 25, 2026
SpaceX had issues with some of the heat shield tiles remaining attached early on in the Starship program. The first six test flights presented some kind of anomaly with them, so the company’s big focus with them was to figure out a way to keep them intact through the duration of the flight.
Things truly improved as Flight 10 showed that ceramic tiles generally stayed attached to the ship far better due to refined attachment, as SpaceX utilized pins instead of adhesives. Flights 10 through 13 truly showed some clear progress with the heat shield tiles, and this latest test seems to be where some real progress was noticed, especially by Musk.
The 13th Starship launch last Friday was the second with Starship V3, SpaceX’s latest and greatest iteration of the spacecraft. Goals and ambitions are getting even grander as the project continues to progress. Musk has already hinted that SpaceX will likely try to catch Starship with Flight 14.
Tesla claims supplier is holding Cybertruck production hostage
Tesla Full Self-Driving v14.3.6 review: a rare regression, but some bright spots
