News
SpaceX talks Moon mission as strategic stepping stone for Mars colony
Josh Brost, Senior Director of SpaceX’s Government Business Development was in attendance at a civil spaceflight conference in Washington D.C. yesterday, January 18, and provided a number of interesting details about SpaceX’s upcoming activities in 2018. Perhaps most intriguingly, he reiterated SpaceX’s interest in enabling exploration of the Moon and Mars, while also clarifying that the upcoming Falcon 9 upgrade will be the last major change to the vehicle for the indefinite future.
Although the audience may have been more focused on SpaceX’s potential lunar prospects, Brost provided a vision similar to CEO Elon Musk’s common-knowledge goal of Martian (and interplanetary) colonization. This lunar focus was in part evidenced by a pointed question from an audience member that triggered Brost’s subsequent suggestion that the Moon could be a more logical starting place for the company as it ramps up its deep space efforts and gradually slips beyond Earth orbit. This strategic and calculated extension of the aspirations of the launch company’s famous founder is a rational attempt to position SpaceX in ways that allow the company to derive as much value as possible from the US government’s recently revived interest in returning the US and its astronauts to the Moon.
- SpaceX’s 2017 BFS (now Starship) delivers cargo to a large lunar base. (SpaceX)
- Starship and a Martian city, circa 2017. (SpaceX)
To a large extent, his comments mesh with the vision Elon Musk reiterated at 2017’s September IAC.
SpaceX’s next-generation heavy-lift rocket and spaceship (BFR and BFS) are being designed to carry 150 metric tons into low Earth orbit while still recovering both the first and second stages, and will be purpose-built for rapid and complete reusability. BFR and BFS are also being intentionally designed to be relatively destination-agnostic. In other words, BFS will be capable of transporting cargo and eventually crew to a number of destinations in the solar system, be it the Moon, Mars, or beyond. The outer planets are almost certainly off limits for crew due to the sheer length of any journey beyond the orbit of Mars, but BFR, as it was discussed last year, would be capable of transporting unprecedented amounts of cargo almost anywhere in the solar system. Reusability is, of course, paramount to SpaceX’s operational intent with BFR/BFS; unless a very lucrative offer is made, it is highly unlikely that SpaceX will even consider expendable missions, thus partially limiting what the next-gen vehicle will be capable of.
Still, it will be an incredibly capable rocket even with full reusability. Add in the potential promise of mature in-situ resource utilization (ISRU), more simply the production of methane and oxygen propellant at the destination, and it will open a hundred entirely new worlds to serious scientific, exploratory, and economic prospecting throughout the solar system.
What’s next?
The question, then, is “when?” While Brost did not specifically provide any sort of timeline for BFR, aside from a brief statement on its readiness in “a few years,” he did describe in some detail the imminent end of serious Falcon 9 upgrades. A continual stream of upgrades and modifications has been one of the only real constants with SpaceX’s Falcon 9 rocket: the original Falcon 9 is in almost every respect a completely different rocket when compared to the Falcon 9 Full Thrust (FT/1.2) of the present. However, one final leap is expected for Falcon 9, this time almost exclusively intended to improve the vehicle’s reliability and reusability as SpaceX rapidly approaches its first flights of Crew Dragon and dreams of rapid and repeated booster reuse.
While it was a small detail in an obscure sentence of one of several hour-long discussions, Brost specifically stated this:
Brost: with Block 5, goal it to lock down the design and fly the vehicle at very high flight rates. Innovation will focus on designing and testing BFR.
— Jeff Foust (@jeff_foust) January 18, 2018
This is arguably the most exciting tidbit provided to us by SpaceX. While it was undeniably vague and rather less than crystal-clear, it can be interpreted as something like this: once Block 5 has been introduced and begun to fly and refly both regularly and successfully, the vast majority of SpaceX’s launch vehicle development expertise will begin to focus intensely on the development and testing of BFR and BFS.
Statements from just last week made by SpaceX President Gwynne Shotwell strengthen this intuitive leap considerably, because BFR and BFS are liable to require a considerable amount of attention as they proceed through design maturation and eventually begin physical hardware testing in Texas.
Shotwell’s comments implied that SpaceX’s Boca Chica launch facilities, currently under construction, would be ready to support “vehicle tests” as early as late 2018/early 2019. Comments from earlier in 2017 indicate that SpaceX (and Shotwell) perceive Boca Chica as a near-perfect location for BFR launches (and thus BFR testing, as well). Finally, Brost’s implication that SpaceX’s exceptional team of brilliant and innovative launch vehicle engineers would be refocused on BFR soon after Block 5 was stable also meshes with this rough timeline. If Falcon 9 Block 5 does indeed debut within the “next few months” as Brost stated, it will have likely reached some level of design and operational maturity by the end of 2018, assuming SpaceX’s expected launch cadence.
- SpaceX’s Falcon 9 ahead of the launch of Zuma. (Tom Cross/Teslarati)
- A Falcon 9 lifts off from LC-40 carrying the highly secretive Zuma spacecraft. Hispasat 30W will launch from the same pad in just a few days. (Tom Cross)
- Falcon 9 1035 conducts its second landing after successfully launching CRS-13 on December 15. Improved reusability will be a huge focus of SpaceX in 2018. (NASA)
As of right now, SpaceX is already looking at a very busy February, and currently has as many as three commercial launches scheduled within a period of maybe three weeks (GovSat-1, PAZ, and Hispasat), maybe even four if Falcon Heavy completes its first static fire later this weekend. Musk estimated that SpaceX would complete 30 missions in 2018, and a cadence anywhere near three launches per month (let alone four) would easily push SpaceX past that goal and provide the company dozens of opportunities to test, launch, recover, and relaunch their new Block 5 version of Falcon 9. As such, while BFR is probably not going to reach fully integrated hardware development or testing in 2018, it is certainly a distinct possibility, and 2019 is far more promising for the company’s interplanetary aspirations.
For now, SpaceX’s 2018 focus is quite explicitly centered on ensuring the reliability of its Crew Dragon – set to debut NET August 2018 – and Falcon 9 as it strives to complete the development of both vehicles. Up next on the company’s busy schedule is another attempt at Falcon Heavy’s inaugural static fire on Saturday afternoon, as well as the flight-proven launch of GovSat-1/SES-16, currently NET January 30.
Follow along live as launch photographer Tom Cross and I cover these exciting proceedings live from both coasts.
Teslarati  –  Instagram – Twitter
Tom Cross – Instagram
Eric Ralph – Twitter
News
Tesla briefly offered this Robotaxi part for your personal car
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.
News
Tesla Robotaxi gets sweeping but polarizing change
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.
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.







