News
SpaceX’s Crew Dragon preps for debut as race to return astronauts to US craft nears final stages
After spending two weeks testing in a specialized NASA-run facility, SpaceX’s first flightworthy Crew Dragon spacecraft was shipped from Ohio to Florida, where it will now spend a number of months preparing for its first (uncrewed) launch into Earth orbit.
Known as Demonstration Mission 1 (DM-1), this critical milestone must be passed before the capsule will be certified to carry NASA astronauts to the International Space Station (ISS) sometime in 2019. While DM-1 will not sport a human crew, the spacecraft is nevertheless expected to demonstrate all life and mission-critical components, ranging from Crew Dragon’s complex array of avionics and ground/orbital communications equipment to craft’s ability to safely return passengers to Earth with a soft ocean landing.
SpaceX’s Crew Dragon spacecraft has been in the serious hardware development phase for approximately five years, although the concept itself dates back about as early as its Cargo Dragon predecessor – 2005 to 2006, publicly. Over the course of roughly two weeks of testing at NASA’s Plum Brook Station, Crew Dragon was likely subjected to a suite of environmental conditions the spacecraft will need to routinely survive to make it through initial launch and successfully operate under the rigors of microgravity and thermal vacuum conditions.
Crew Dragon arrived in Florida this week ahead of its first flight after completing thermal vacuum and acoustic testing at @NASA’s Plum Brook Station in Ohio. https://t.co/xXJE8TjcTr pic.twitter.com/lr0P95zzIK
— SpaceX (@SpaceX) July 12, 2018
Given the DM-1 capsule and trunk’s fairly quick jaunt at the huge Plum Brook vacuum chamber and equally quick arrival in Florida, those test results were likely quite favorable. Still, a major amount of work lies ahead before the first full Crew Dragon is ready for its launch atop Falcon 9. Most significantly, the craft’s trunk did not follow its fellow capsule to Florida, but rather returned to SpaceX’s Hawthorne, CA factory to be outfitted with critical flight hardware, particularly radiators and solar arrays. Once that outfit is complete, the module will also be shipped to Florida before being integrated with the DM-1 Crew Dragon capsule.
Of note, the DM-1 capsule has been constructed from the start to support a plan to use the vehicle in an in-flight abort test meant to ensure that the craft can wrest its passengers from harm’s way even at the most intense point of launch, where aerodynamic pressures are at their peak. In order to properly support both the DM-1 orbital mission and the in-flight abort test to follow, the capsule has been outfitted with a fair amount (hundreds of pounds) of hardware that will be unique to the pathfinder spacecraft. This understandably adds its own complexity to the already intense program’s first orbital mission, although it will hopefully not translate into additional delays.
-
-
- NASA Astronaut Suni Williams, fully suited in SpaceX’s spacesuit, interfaces with the display inside a mock-up of the Crew Dragon spacecraft in Hawthorne, California, during a testing exercise on April 3. (SpaceX)
-
- SpaceX’s Demo Mission-1 Crew Dragon seen preparing for vacuum tests at a NASA-run facility, June 2018. (SpaceX)
-
- Crew Dragon parachute tests are likely to continue into the summer to ensure NASA certification in time for DM-1. (SpaceX)
SpaceX competitor’s crewed spacecraft and rocket take shape
It’s worth noting that SpaceX is effectively operating at a distinct – albeit partially self-wrought – financial handicap when compared with Boeing’s Starliner spacecraft program, one of two vehicles funded by NASA to accomplish the same task of safely and reliably transporting astronauts to and from the ISS.
“NASA awarded firm-fixed-price contracts in 2014 to Boeing and Space Exploration Technologies Corporation (SpaceX) [of] up to $4.2 billion [for Boeing] and $2.6 billion [for SpaceX] for the development of crew transportation systems.” (GAO-18-476)
-
- Boeing’s DM-2 Starliner undergoes integration in Florida earlier this year. (Boeing)
-
- The ULA Atlas V rocket that will launch Boeing’s DM-1 Starliner spacecraft captured at ULA’s Decatur, AL factory, October 2017. (ULA)
-
- The United Launch Alliance (ULA) dual engine Centaur upper stage of the Atlas V rocket in the final stages of production and checkout, May 2018. (ULA)
In other words, Boeing requested and received a full 60% more than SpaceX to – quite literally – accomplish an identical task. Alongside the storied and brutally expensive history of crewed American spaceflight, both contracts are an absolute steal for two modernized, crew-capable spacecraft, but a 60% premium is a 60% premium. Foreseeable but slight cost overruns caused, among other things, by additional contractual requirements from NASA have followed a similar trend, roughly proportional to each company’s slice of the original $6.8b Commercial Crew contract.
“As of April 2018, NASA requirement changes had increased the value of contract line item 001 for Boeing by approximately $191 million and for SpaceX by approximately $91 million.” (GAO-18-476)
Still, Boeing’s progress towards its own DM-1 and DM-2 demo flights and a pad-abort test are impressive, although it very likely is more of a demonstration of a different approach to public communications than of any actual step up on SpaceX. In the last few weeks, Boeing has released a number of photos showing off the progress made building its own Starliner capsules and service modules (trunks), three of which are currently in varied states of assembly and integration in the company’s Florida-based facility. Additionally, United Launch Alliance CEO Tory Bruno has shared off-and-on updates and photos of the launch contractor’s own progress assembling the rockets that will launch Boeing’s spacecraft.
The two engine Centaur is getting ready and excited for #StarLiner. pic.twitter.com/WIf3H8k9yq
— Tory Bruno (@torybruno) July 2, 2018
Regardless, a huge amount of work lies ahead before both Boeing and SpaceX’s crewed spacecraft are able to conduct their first uncrewed and crewed launches into orbit. Now very outdated, NASA has stated several times recently that the presently available targets of NET August 31 will likely be updated later this month, pushing DM-1 debuts into NET Q4 2018 and the first commercial crewed demo missions to 2019.
-
Stay tuned, as the Block 5 Falcon 9 tasked with launching SpaceX’s own DM-1 Crew Dragon will likely be the next of a recent flood of finished rockets to leave the company’s Hawthorne factory, where it will head to McGregor, Texas to complete acceptance wet dress rehearsals and static fire tests before shipping to SpaceX’s Pad 39A in Florida.
Follow us for live updates, peeks behind the scenes, and photos from Teslarati’s East and West Coast photographers.
Teslarati – Instagram – Twitter
Tom Cross – Twitter
Pauline Acalin – Twitter
Eric Ralph – Twitter
-
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 Full Self-Driving v14.3.6 review: a rare regression, but some bright spots
Musk’s massive Terafab project will get final location soon
