News
SpaceX wants to boost Hubble Space Telescope’s orbit with Dragon spacecraft
NASA and SpaceX have signed a Space Act Agreement to study the feasibility of boosting the orbit of the iconic Hubble Space Telescope, potentially ensuring that the highly successful observatory will remain operable well into the middle of this century.
Thanks to three servicing missions completed in the 1990s and 2000s, Hubble remains highly productive more than 32 years after its launch. NASA believes that that will remain the case until at least the late 2020s or 2030s. However, many components of the telescope have spent decades in the unforgiving environment of space, raising unsurprising concerns about their longevity.
More importantly, the inexorable march of time, gravity, and Earth’s atmosphere mean that Hubble is guaranteed to eventually reenter that atmosphere and burn up without intervention. That demise could come as early as the mid-2030s, but SpaceX thinks it could help extend the telescope’s viability into the 2050s.
NASA and SpaceX will spend the next six or so months discussing whether it’s possible to use Dragon to boost the telescope’s orbit back to a nominal 600 kilometers (~372 mi). Both parties say that the agreement will also investigate the possibility of Dragon servicing missions, which could be even more significant for Hubble. While a boost that large would likely keep it in orbit for decades to come, there’s no guarantee the telescope would remain functional to take full advantage of the extra time it would have.
During the fifth and final Space Shuttle servicing mission, NASA astronauts installed a docking adapter (Soft Capture Mechanism) on the Hubble Telescope. Although no concrete plans existed for any additional servicing missions, the forward-facing installation of that adapter has made this feasibility study possible.
In theory, that docking adapter could make boosting Hubble’s orbit far more feasible, safe, and affordable than a Shuttle-style crewed servicing mission. SpaceX’s Cargo Dragon 2 spacecraft has the same autonomous docking capabilities its crewed sibling has and costs less to launch and operate, so it’s not inconceivable that an uncrewed Dragon could autonomously dock with Hubble and boost its orbit. Jessica Jensen, SpaceX’s Vice President of Customer Operations and Integration, says that an uncrewed option will be studied alongside crewed servicing and orbit-boost alternatives.
According to Patrick Crouse, NASA’s Hubble Space Telescope project manager, without a reboost, NASA would need to consider a separate mission to ensure a controlled deorbit of the massive telescope by “the end of the decade.” The study’s targeted boost of “40 to 70 kilometers,” meanwhile, could extend the longevity of Hubble’s orbit by “15 to 20 years,” or well into the 2050s. But as a feasibility study, there’s a chance that it will conclude that using Dragon – crewed or uncrewed – to boost or service HST isn’t feasible. Ordinarily, the most likely outcome would be a conclusion that the project is feasible from a technical perspective but out of reach from a financial perspective.
Enter billionaire and private astronaut Jared Isaacman, who was directly involved in the September 29th press conference. In September 2021, Isaacman – alongside four others – became the first all-private astronaut mission in history to reach orbit. After the spectacular success of Inspiration4, Isaacman’s relationship with SpaceX has become even closer. In early 2022, the pair announced a new endeavor – the Polaris Program – that intends to conduct at least two or three more private astronaut launches over the next few years.
-
Expanding the scope of their joint ambitions, the Polaris Program intends to debut the world’s first privately developed EVA spacesuit, test spacecraft-to-spacecraft communications using Starlink’s network of space lasers, and culminate in the first crewed launch of SpaceX’s next-generation Starship rocket. On its own, the decision to privately fund and develop an EVA suit and pursue the ability to conduct EVAs out of Crew Dragon represents a major leap forward for SpaceX and private spaceflight if realized.
But crucially, when asked about the synergies between the Polaris Program, SpaceX, and NASA, Isaacman revealed that he and SpaceX are willing to undertake a sixth Hubble servicing mission more or less pro bono, “with little or no potential cost to the government.” According to Isaacman, it’s possible that “the study could result in [a Hubble servicing mission] becoming the second [Polaris Program] mission.”
Polaris Dawn, the program’s first mission, was recently delayed from a late-2022 launch target to March 2023. The four private astronauts assigned to the mission (including Isaacman himself) recently began training for the historic private EVA, which will see two of four astronauts attempt to briefly exit their Crew Dragon spacecraft in new SpaceX-designed suits. With a targeted apogee of 1400 kilometers (~870 mi), the mission will also attempt to break the record for the highest Earth orbit reached by astronauts, and the spacewalk attempt will also occur at a record-breaking altitude of 700 kilometers (~435 mi)
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
