News
SpaceX installs Starship Mk1 rocket’s flaps for the second time in build-up to flight debut
A little over a month after SpaceX CEO Elon Musk presented an update on Starship in Boca Chica, Texas and technicians dressed the rocket up for the show, SpaceX has begun to install Starship Mk1’s flaps for the second time.
This time, with any luck, those flaps are here to stay until Starship Mk1’s inaugural launch debut, an ambitious flight test with a target altitude of 20 km (12 mi).
Around the second half of September, SpaceX technicians appeared to begin working around the clock to fully assemble Starship, outfitting the exterior with the beginnings of plumbing, power lines, and avionics harnesses, stacking the Mk1 prototype’s two halves, and installing the vehicle’s large fore and aft flaps. During SpaceX CEO Elon Musk’s September 28th Starship update, what looked to be the largely finished Starship Mk1 served as the main backdrop – an undeniably impressive one, at that.
As would soon become clear, SpaceX’s September 2019 Starship Mk1 integration was actually more of a mock-assembly – all the parts involved appear to genuinely be real flight hardware, but almost all of it was only temporarily attached to Starship to give the partial appearance of a finished ship. By October 1st, technicians began removing Starship Mk1’s four flaps, flap shrouds, and leg shrouds, finally culminating in the separation of the rocket prototype’s upper and lower halves.
The fact that neither Musk or SpaceX spokespersons noted that Starship wasn’t actually complete is at least a little unsavory, although it’s admittedly unsurprising given CEO Elon Musk’s known affinity for grand gestures and events. On a positive note, Starship’s mock-assembly likely served as an excellent learning experience for the Boca Chica team and thankfully only seems to have caused a week or two of delay.
Rapid progress in Boca Chica
Despite the mild disruption of dressing Starship Mk1 up for Musk’s presentation, SpaceX Boca Chica has made a huge amount of progress in the five weeks since. Barely three weeks after the rocket’s forward flaps (canards) were removed, SpaceX technicians began the reinstallation process with one major visible difference: a massive motorcycle-sized actuator.
On the first round of installations-for-show, Starship Mk1’s flaps featured no such mechanism, confirming suspicions that much of the hardware installed at the last second was not quite finished or was only being installed for Musk (and practice). The appearance of a previously unseen actuator mechanism on the first reinstalled canard suggests that this time around, SpaceX is installing Starship’s flaps with their final purpose of controlling Starship’s free-fall in mind.
Instead of copying Falcon 9’s proven method of vertical launch and vertical landing, SpaceX is taking a more radical approach with Starship that will see the spacecraft reenter Earth’s atmosphere belly-first, slow its forward speed to near-zero, and fall directly down for approximately 25 km (15.5 mi), using its flaps like a skydiver’s limbs. Perhaps just a few hundred meters above the ground, Starship will finally perform an aggressive flip maneuver, igniting its Raptors while sideways, swerving to neutralize that horizontal velocity, and finally landing on six small legs.
In this sense, although they certainly look the part, Starship’s aerodynamic control surfaces are very explicitly not wings and are instead meant to interact with the atmosphere at an almost 90-degree angle of attack (AoA). In line with that strategy, they only have to actuate with a single degree of freedom, drastically simplifying Starship’s control surfaces.
Similar to Starship Mk1’s newly filled-out canard actuators, SpaceX technicians have installed two massive hinges/mounts for Starship’s larger after flaps. Aft flap installation will likely start as soon as SpaceX technicians have installed the bulk of Starship Mk1’s external plumbing and wiring, a milestone that appears to be fast approaching.
Starship Mk1’s lower half was unexpectedly moved about a mile to SpaceX’s nearby launch facilities prior to the installation of its nose section, meaning that SpaceX will likely have to transport the nose to the launch pad for final mating. It’s unclear what tests SpaceX specifically plans to kick off Starship Mk1’s pre-flight preparations with, but it’s safe to assume that the most imminent milestone is a wet dress rehearsal (WDR), possibly preceded by a tank proof test.
The latter procedure would be designed to prove that Starship Mk1’s pressure vessel is both leakproof and structurally sound and would nominally involve filling the spacecraft’s tanks with a neutral fluid (likely water or liquid nitrogen). A WDR would see SpaceX load Starship as if preparing for launch (requiring liquid oxygen, methane, nitrogen, and helium) but stopping just prior to the engine ignition and liftoff that would otherwise follow. Although unlikely, a WDR could result in a massive fire or explosion if Starship were to lose structural integrity during the test, which is why the aforementioned neutral testing is typically performed first when handling brand new launch vehicles.
Finally, assuming Starship Mk1 successfully passes the above tests, SpaceX will use the vehicle to perform Raptor’s first triple-engine static fire test. That static fire will likely be the final major test activity before SpaceX readies Starship Mk1 for its 20-km flight debut, which will serve as a more or less full-fidelity test of Starship’s exotic skydiver-like landing.
Regardless of how exactly Starship Mk1’s imminent test campaign will play out, SpaceX has road closures scheduled on November 7th, 8th, and 12th. Right now, it’s anyone’s guess what is planned for Thursday and Friday, but it could potentially involve a tank proof test, launch pad checkouts, propellant loading, or something more benign, like transporting Starship’s nose section to the pad for final installation. Stay tuned!
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
Tesla has started rolling out a broader change to the ride experience for its Robotaxi fleet by silencing turn signals, but the change is certainly polarizing.
Tesla has generally made it clear that its purpose-built ride-hailing platform, Robotaxi, will cater to the rider in nearly every way possible. This includes having climate preferences, music, and other personal settings loaded up in the car as the rider enters.
But Tesla is taking it a step further by muting turn signal chimes altogether, a change that appears to be a way to make the ride more peaceful:
Tesla has finally turned off the blinker/turn signal noises in their Model Y Robotaxis.
This is a small update, but will definitely be noticeable for riders. It didn’t really make much sense to leave the turn signal sound on when it’s Unsupervised. pic.twitter.com/ITwx60PAMO
— Sawyer Merritt (@SawyerMerritt) July 27, 2026
However, there are a handful of people who are not thrilled about this change. Turn signals are a conditioned part of the human mind for those who ride in a car regularly.
Taking a turn without one feels strange and odd, and not hearing it click while activated could set off some alarms for riders, who might use the noise as confirmation that other drivers know of their intention to turn.
I kind of like it being on, threw me off when riding with Zoox who has had it disabled
— Dan Burkland (@DBurkland) July 27, 2026
Turn signal noises are still audible in customer cars, so if you use FSD in your personal vehicle, you will still hear the turn signal.
The move is certainly one that is unique, but not one that separates it from other ride-sharing services. In a normal car, the clicking sound confirms to the driver that the blinker is active. In a fully driverless Robotaxi, that feedback serves no purpose for passengers, other than peace of mind.
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.”
Tesla silences Robotaxi turn signals in sweeping but polarizing change
Tesla claims supplier is holding Cybertruck production hostage
