News
SpaceX fires Falcon Heavy’s 27 booster engines ahead of “most difficult launch ever”
For the third time ever, SpaceX has successfully performed a critical static-fire test of an integrated Falcon Heavy, briefly igniting all 27 of its Merlin 1D engines to verify the health and readiness of the rocket.
Per SpaceX’s official confirmation, a “quick-look” inspection of static fire telemetry has indicated that the company’s Falcon Heavy rocket is ready for its second launch in less than three months, a milestone that could also allow both flight-proven side boosters to tie SpaceX’s own record for booster turnaround. Falcon Heavy Flight 3 is now scheduled to launch the US Air Force’s Space Test Program 2 (STP-2) mission no earlier than 11:30 pm ET (03:30 UTC), June 24th. According to SpaceX CEO Elon Musk, the mission will unequivocally be the company’s “most difficult launch ever”.
Coincidentally, on top of being Falcon Heavy’s first scheduled night launch, STP-2 has now also marked the massive rocket’s first nighttime static fire. During this critical test, Falcon Heavy briefly ignites all 27 of its three boosters’ Merlin 1Ds and throttles the engines up to full thrust, much like airliners sometimes set their brakes and throttle up before attempting to take off. The difference between Falcon Heavy and passenger aircraft is nevertheless rather significant, given that Falcon Heavy produces ~15x the thrust of an A380 – the world’s most powerful mass-produced passenger aircraft – at liftoff: 22,820 kN (5.1M lbf) to the massive jet’s meager 1,440 kN (0.3M lbf).
Despite all of that thrust, Falcon Heavy is held down during static fire by eight accurately-named hold-down clamps, themselves a part of a massive transport/erector, which is itself anchored directly to Pad 39A’s concrete foundation. In short, Falcon Heavy (and especially Falcon 9) is not going anywhere until those hold-down clamps are explicitly released. Thanks to SpaceX’s avoidance of the solid rocket boosters used by almost every other modern launch vehicle, Falcon 9 and Heavy rockets can abort at any point prior to clamp release, offering a uniquely broad abort capability.
As such, not only does SpaceX’s dedicated pre-launch static fire fully test the rocket’s health, but the same procedure is essentially repeated in the seconds before clamp release during an actual orbital launch attempt. If at any point Falcon 9’s autonomous onboard computer decides that it doesn’t like any of the thousands of channels of telemetry it’s constantly analyzing, it can command an engine shutdown and total launch abort even if all first stage engines have already ignited and reached full thrust. If routine McGregor, TX acceptance testing – also involving a full static fire – is accounted for, every single Falcon 9 booster technically completes three fully-integrated static fires before its inaugural liftoff. Falcon Heavy is slightly different, as each booster is independent test-fired in Texas but the integrated rocket can only perform static fires at Pad 39A.
After those three critical tests, flight-proven Falcon boosters are subjected to the less stringent few-second static fires SpaceX performs at the launch pad 3-7 days before a given launch. With Falcon Heavy Flight 3, the rocket’s center core, upper stage, and payload fairing are all brand new, fresh from either SpaceX’s Hawthorne factory or McGregor acceptance testing. However, both side cores – Block 5 boosters B1052 and B1053 – are flight-proven, having successfully completed their first launches and landings on April 11th, less than 70 days ago.
Set by regular old Falcon 9 boosters, SpaceX’s current record for booster turnaround time (time between two launches) is 71 days (set in June 2018), while the Block 5 upgrade’s record stands at 74 days (set in October 2018). If Falcon Heavy’s STP-2 launch holds strong on June 24th, B1052 and B1053 will simultaneously tie SpaceX’s Block 5 turnaround record. This would be accomplished despite the added pressure from the US Air Force’s decision to use STP-2 as a sort of dress rehearsal for certifying all flight-proven commercial rockets, an honor (and burden) that likely added extra work, oversight, and scrutiny to the process of refurbishing and relaunching B1052 and B1053.
“[T]he US Air Force has decided that STP-2 presents an excellent opportunity to begin the process of certifying flight-proven SpaceX rockets for military launches. The STP-2-related work is more of a preliminary effort for the USAF to actually figure out how to certify flight-proven commercial rockets, but it will still be the first time a dedicated US military mission has flown on a flight-proven launch vehicle. Down the road, the processes set in place thanks – in part – to STP-2 and Falcon Heavy may also apply to aspirational rockets like Blue Origin’s New Glenn and ULA’s “SMART” proposal for Vulcan reuse.”
— Teslarati.com, 06/16/2019
In a last-second surprise, SpaceX updated Falcon Heavy center core B1057’s planned drone ship landing site from a brief 40 km (25 mi) to more than 1240 km (770 mi) off the coast of Florida. SpaceX set its current record for recovery distance less than three months ago during Falcon Heavy’s commercial launch debut, in which Block 5 center core B1055 landed nearly 970 km (600 mi) offshore on drone ship Of Course I Still Love You (OCISLY). If all goes well, B1057 – the second finished Block 5 center core – will absolutely crush its predecessor’s record, implying that the booster will likely be subjected to SpaceX’s most difficult reentry and recovery yet.
For more on what CEO Elon Musk describes as “[SpaceX’s] most difficult launch ever”, check out these previous articles on an unexpected ultra-fast booster reentry and the extraordinary challenge facing Falcon upper stage.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
Tesla briefly offered one Robotaxi part in its Parts Catalog for your personal car, only to remove it just a short time after it was first noticed.
Tesla’s Robotaxi camera washer apparatus was briefly available for purchase on the company’s Online Parts Catalog. The camera washer was first noticed on Model Y Robotaxi vehicles about six months ago in Austin.
🚨 Tesla looks to have installed Camera Washers on the side repeater cameras on Robotaxis in Austin
pic.twitter.com/xemRtDtlRR— TESLARATI (@Teslarati) January 23, 2026
First noticed by Not a Tesla App, the Camera Washer entries appeared for the new “Juniper” Model Y under a category called “Halo,” which has also now disappeared. Interestingly, Halo probably is related to Tesla’s internal “Project Halo,” which was a project that aimed to retrofit customer-owned Model Ys into functional Robotaxis.
This hardware addition would likely be required for the vehicle to operate as a Robotaxi, as the Camera Washer seems to be a non-negotiable part of the vision-based system Tesla utilizes for self-driving efforts.
However, this part has since been removed and is no longer visible on the EPC.
Now the true question lingers: Why would Tesla add this Camera Washer to the Model Y parts catalog? Is it planning to make it available for owners to utilize on their own cars for personal use, or will it become a prerequisite for Robotaxi operation in customer-owned cars?
While discussing the upgrade options for Hardware 3 vehicles during the Q1 Earnings Call, Tesla CEO Elon Musk had said that the company could establish small, satellite shops that would upgrade cameras and self-driving computers. Perhaps this same strategy could be utilized for vehicles that want to be included in Robotaxi but do not have the correct hardware.
AI4 is currently represented as capable of unsupervised self-driving, and the same was said about HW3 at one point, only for Tesla to admit last quarter that it would, unfortunately, not be possible. Perhaps AI4 vehicles might need this camera washer as a prerequisite, just as HW3 cars will need that camera and computer upgrade.
This could be the first hint of that’s where we are headed.
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.
Tesla briefly offered this Robotaxi part for your personal car
Tesla Robotaxi gets sweeping but polarizing change
