News
SpaceX’s first Falcon Heavy launch in three years eyes late-October liftoff
For the second time in 2022, SpaceX’s Falcon Heavy rocket has a firm launch date for the first time in more than three years.
Cursed by a seemingly relentless flood of delays impacting almost every one of the rocket’s payloads, Falcon Heavy made it within three or four months of ending its launch drought as recently as June 2022. At the time, the rocket was more or less ready to begin assembly, but NASA announced late that month that the Jet Propulsion Laboratory (JPL) and supplier Maxar had failed to finish qualifying software needed to power its Psyche spacecraft. Designed to journey to and enter orbit around the asteroid 16 Psyche, the complex trajectory required to reach it constrained the mission to a launch window sometime between August and October.
When JPL and Maxar were unable to properly test the spacecraft’s software in time for that window, they were forced to stand down and wait until the next earliest window, which begins in July 2023. That left Falcon Heavy with three more possible payloads to launch in 2022, but all three were chronically delayed and there was little reason to believe that even one of them would be ready to launch before 2023. However, Falcon Heavy’s single most delayed payload appears to have made a breakthrough, giving the most powerful rocket currently in operation at least one more shot at a 2022 launch.
Continuing an excellent series of reports tracking Falcon Heavy’s never-ending US military payload delays, Spaceflight Now broke the news with an official statement from the US Space Force, which confirmed that an unspecified industry partner had finally resolved payload problems that have delayed the military’s USSF-44 mission by two years. More importantly, the USSF spokesperson revealed a specific target of October 28th.
The US military has repeatedly offered implausible launch targets for USSF-44 with little to no official explanation for the mission’s delays, making it reasonable to appraise any specific launch date much like a boy crying wolf. But this particular target, announced within the same month as its date, is a bit more believable on its own.
Thankfully, it’s not on its own. On October 7th, SpaceX sent out an email confirming that Falcon Heavy is scheduled to launch USSF-44 sometime in October and asking members of the media to register for press site access and remote camera setup opportunities. It’s possible that the rocket or USSF-44 satellites will run into issues and trigger additional delays, but a press accreditation email is about as close as one can get to a believable guarantee that a secretive US military payload is on track for a SpaceX launch scheduled more than a week or so in the future.
The mission’s next major step forward will be the assembly of Falcon Heavy inside SpaceX’s main hangar at its NASA Kennedy Space Center LC-39A pad. Photos SpaceX shared last month and earlier this month of preparations for Crew-5, Falcon 9’s eighth successful astronaut launch, show that at least two of the four main stages that make up Falcon Heavy are already inside that hangar. One of two new Falcon Heavy side boosters was clearly spotted on September 30th.
-
The rocket’s expendable upper stage was also clearly visible in a September 23rd photo. Ordinarily, Falcon upper stages are nearly indistinguishable from each other, but the upper stage stored behind the Crew-5 upper stage in the foreground features a unique grey band around the bottom of its airframe. In July 2019, SpaceX tested another Falcon 9 upper stage with the same grey band, which a spokesperson explained was meant to improve the rocket’s longevity in orbit.
Long orbital coasts of six or more hours are necessary for some of the most challenging launch trajectories. Direct-to-geostationary launches are the most common type of mission to require long coast capabilities and are often demanded by the US military. The grey band’s purpose is to increase the amount of heating absorbed from sunlight to warm the liquid kerosene (RP-1) fuel contained within that part of the rocket. When it gets too cold, kerosene – which freezes at a much higher temperature than Falcon’s liquid oxygen oxidizer – becomes viscous and slush-like before it freezes solid. If ingested, slushy fuel would likely prevent ignition or destroy the upper stage’s Merlin engine.
USSF-44 will be SpaceX’s first direct geostationary launch attempt, explaining why the grey band has reappeared more than three years after its first test. Coincidentally, Falcon Heavy’s third and latest launch occurred in June 2019, just one month before that upper stage test. 40 months later, the rocket might finally launch again, and it will do so by attempting what is likely SpaceX’s most difficult customer mission to date. To enable the high performance required for the mission, USSF-44 will also intentionally expend a Falcon Heavy booster for the first time. The rocket’s two new side boosters will boost back to Florida and land side by side at LZ-1 and LZ-2, but its new center core will be expended after a single flight.
SpaceX has already finished converting Pad 39A’s mobile transporter/erector, which was previously set up for single-core Falcon 9 rockets. The T/E will eventually roll inside the pad’s integration hangar, confirming that Falcon Heavy has been fully assembled and is about to be installed on the structure. The rocket will then be rolled out to the pad and brought vertical for static fire testing, a process that will likely begin at least a week before the current October 28th launch target.
If testing is successful, Falcon Heavy will return to the hangar, have its fairing and USSF-44 payload installed, and roll out to the pad one last time. Stay tuned for updates on that ongoing process.
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
