News
SpaceX’s Crew Dragon spaceship marches towards launch with vacuum chamber test
SpaceX has published the latest photo of its next-generation Crew Dragon spacecraft, showing the crewed vehicle preparing to be put through its paces inside a NASA thermal vacuum chamber located in Cleveland, Ohio. If the tests are completed without issue, the Dragon’s next destination will be Cape Canaveral, Florida, where it will prepare for an inaugural launch targeted for the fourth quarter of 2018.
In the photo released on June 20th, SpaceX’s DM-1 Crew Dragon capsule (C202 in shorthand: [C]apsule, Dragon [2], serial number [02]) is seen being craned by SpaceX technicians into the thermal vacuum chamber at NASA’s Plum Brook testing facilities. Located in Ohio, Plum Brook’s vacuum chamber is unique because of both its size and its ability to fairly accurate replicate the actual environment faced by satellites and spacecraft once in space. Most importantly, this includes the extreme thermal conditions those vehicles are subjected to by constant ~90-minute day-night cycles in low Earth orbit (LEO).
Without Earth’s cozy atmosphere to act as both a heat sink and insulating blanket once on orbit, there is simply nothing there to protect spacecraft like Crew Dragon from the absolute extremes of direct solar radiation (sunlight), total darkness, and a complete lack of cooling by conduction and convection. In order to avoid overheating, Crew Dragon thus needs to bring along its own means of cooling in the form of onboard radiators to shed excess heat. The use of white paint on spacecraft further aids this process by selectively preventing the absorption of solar radiation while simultaneously efficiently emitting in infrared wavelengths.
- SpaceX’s Demo Mission-1 Crew Dragon seen preparing for vacuum tests at a NASA-run facility, June 2018. (SpaceX)
- The DM-1 Crew Dragon testing inside SpaceX’s anechoic chamber, May 2018. (SpaceX)
- An overview of Crew Dragon’s main features, all of which can be seen in the real-life photos. The Cargo Dragon version will likely remove seats and windows. (SpaceX)
How to prep your Dragon
Crew Dragon’s primary radiators are elegantly integrated into vertical panels installed on the cylindrical bottom segment, known as the trunk, while the craft’s power source – solar panels in this case – are installed in a curved array on the opposite side of the trunk. Intriguingly, the trunks displayed in the two most recent photos of the DM-1 Crew Dragon appear to be almost completely different, and the trunk at Plum Brook does not appear to have its solar arrays or radiators installed. Nominally, SpaceX would use the thermal vacuum capabilities of the Ohio facility to fully vet Crew Dragon’s ability to maintain optimal temperatures on orbit, but the particularly tests planned for the DM-1 capsule and trunk may be of a slightly different type.
- On February 28, SpaceX completed a demonstration of their ability to recover the crew and capsule after a nominal water splashdown in the Atlantic Ocean, just off the coast of Florida. (SpaceX)
- Astronaut Bob Behnken examines a sample of Crew Dragon docking and crew transfer hardware, the mechanisms that will allow the spacecraft to dock with the International Space Station and allow crew to enter the orbital outpost. Taken March 2017. (SpaceX)
Regardless, after testing at Plum Brook is completed, the DM-1 Crew Dragon capsule will be shipped to a newly-constructed processing facility in Cape Canaveral, Florida, while it’s understood that the trunk installed in SpaceX’s June 20th photo will be returned to the Hawthorne, CA factory to be outfitted with flight hardware (presumably including cameras, radiators, solar arrays, and a healthy amount of insulation). It’s unclear when the two segments of DM-1 will part ways and head on to their next destinations, but it’s likely that testing at Plum Brook will last for at least a handful of weeks.
Birds of a feather
In the meantime, several additional Crew Dragon capsules/trunks and the Falcon 9 Block 5 rockets that will launch them are in a variety of states of fabrication and assembly at SpaceX’s Hawthorne factory. B1051, the Block 5 booster assigned to the first uncrewed Demo-1 launch of Crew Dragon, was reported by NASA to be undergoing propellant tank integration in March 2018, implying that the rocket should be at or near the final stages of integration, and will likely ship to McGregor, Texas for static fire testing late this summer.
As of June 15th, SpaceX’s third Falcon 9 Block 5 booster was vertical on the Texas test stand, likely nearing its own static fire test before being shipped to SpaceX’s Vandenberg Air Force Base launch facilities for the July 20th launch of Iridium-7. While possible that a booster slipped past the watchful eyes and ears of SpaceX enthusiast observers, it’s probable that the rocket currently in McGregor is B1048, implying that a minimum of two additional booster shipments and Texas test programs remain before B1051 can be prepped to launch SpaceX’s first Crew Dragon mission. At the current marginally accelerated booster production and shipment schedule (~ 30-day cadence), B1051 would be expected to leave Hawthorne for Texas no earlier than (NET) late August or early September. This meshes with a recent comment from Commercial Crew astronaut Suni Williams:
“I think we’re going to get the [uncrewed[ demo flights probably by the end of the year, maybe a little after that . . . and then the crew demo missions next year.”
- Falcon 9 Block 5 completed its first launch on May 11, carrying the Bangabandhu-1 communications satellite to geostationary transfer orbit. (Tom Cross)
- SpaceX’s second Block 5 booster was spotted vertical at the company’s McGregor, TX testing facilities. That booster has since been shipped to Florida for a mid-July launch, with B1048 now in its place as of June 15. (Aero Photo)
- A matte-silver Block 5 Merlin 1D rocket engine seen preparing to leave SpaceX’s Hawthorne factory for testing in Texas. (SpaceX)
Anticipating acceptance and prelaunch testing that is far more extensive and time-consuming than typically seen with SpaceX’s commercial missions, it’s safe to bet that the first uncrewed Crew Dragon mission – DM-1 – will launch from Kennedy Space Center in November or December 2018. While those operations proceed over the course of the rest of this year, SpaceX expects roughly 10 additional Falcon 9 and Falcon Heavy launches to occur. It’s gonna be a busy H2.
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
News
Tesla Full Self-Driving v14.3.6 review: a rare regression, but some bright spots
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
Musk’s massive Terafab project will get final location soon
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.”
News
Elon Musk reveals SpaceX performed secret Starship test on Flight 13
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.









