News
SpaceX’s Raptor engine nears flight-readiness for BFR spaceship hop tests
In a presentation that revealed plans for a private mission to the Moon in as early as 2023, SpaceX CEO Elon Musk dedicated a couple minutes to BFR’s booster and spaceship rocket engine of choice, Raptor. Musk had nothing but praise for SpaceX’s propulsion engineers and technicians, stating that he was “really excited” about the propulsion system’s advanced design.
SpaceX has completed over 1,200 seconds of firing across 42 main Raptor engine tests. pic.twitter.com/EhxbPjd8Cj
— SpaceX (@SpaceX) September 29, 2017
Judging from a total of 1200 seconds of hot-fires completed just under a year ago, it’s safe to assume that Raptor has soared beyond that measure. Most recently, photos captured earlier this summer showed that a new prototype was installed on SpaceX’s horizontal Raptor test stand in McGregor, Texas, looking nearly identical to the deep black Raptor nozzle shown in Monday’s presentation. Previous Raptor prototypes seen during testing or at the test stand appeared to have a nozzle closer to SpaceX’s silver Merlin 1Ds, whereas this newest iteration’s nozzle doesn’t seem to reflect the powerful spotlights surrounding it.
Perhaps not a coincidence, SpaceX’s propulsion engineering lead Tom Mueller stated in May 2018 that flight-ready Raptors were already “in work”, with the implication being that the finalized Raptor design had been completed and that manufacturing work was beginning in earnest. Barring an unexpected shift in testing strategies, SpaceX will optimize and verify Raptor’s flight design over the course of several hundred seconds of static fire tests, eventually leading into the same practices used for Falcon 9.
-
- A September 2018 render of Starship (then BFS) shows one of the vehicle’s two hinged wings/fins/legs. (SpaceX)
-
- In 2018, Musk decided to sidestep vacuum engines entirely, moving to 7 SL Raptors. (SpaceX)
“This is a stupidly hard problem and SpaceX engineering has done a great job with this design.” In a May 2018 tweet, Musk added that “this engine is something special.” – Elon Musk, 09/17/18
-
Prior to being installed on any BFR prototypes, all Raptors will thus go through acceptance testing in Texas, potentially followed by a full-up static fire of the first completed BFR spaceships. Falcon 9 boosters – capable of roughly 7600 kN (1.7 million lbf) of thrust – are routinely tested in McGregor, while a full BFR spaceship with 2017-grade Raptors (1700 kN at sea level) would produce 12,000 kN (2.7 million lbf) of thrust with all Raptors firing. However, due to the sheer difficulty of transporting something 9 meters in diameter by road, it’s more likely that SpaceX will need to build up a dedicated static fire and hop test facility near the coast of Texas, at a spot called Boca Chica.
An immense liquid oxygen (LOX) tank just arrived at @SpaceX's prospective Boca Chica, TX facility, likely to be dedicated to BFR & BFS testing. @NASASpaceflight forum user "Nomadd" caught some of the first detailed photos, as well as the tank's arrival at SpaceX land on July 11. pic.twitter.com/hr7SeA6BGw
— Eric Ralph (@13ericralph31) July 12, 2018
Getting to hop tests
As it turns out, massive propellant storage tanks (vacuum insulated) have already begun arriving at SpaceX’s Boca Chica facilities, currently dedicated to a duo of tracking and communications radars to be used for Crew Dragon communications. Over the course of the next 12 or so months, SpaceX is thus likely to expand and develop its Boca Chica facilities, culminating – if all goes well – sometime late next year with the first shipment of a prototype BFR spaceship from Port of Los Angeles, through the Panama Canal, to Port of Brownsville, Texas.
“I’m really excited about this engine design, I think the SpaceX propulsion team has done an amazing job – the SpaceX structures and aero team has done a phenomenal job in the design of this.”
“Even others in the aerospace industry don’t know what question to ask – once we could frame the question [with precision], the answers [for Raptor and BFR R&D] flowed.” – Elon Musk, 09/17/18
SpaceX has already completed the first composite segment (both a section of the fuselage and of a propellant tank) of the first BFR spaceship prototype, and Musk further stated that BFR’s structural engineers and technicians would begin fabricating the spaceship prototype’s propellant tank domes and engine section “soon”. A vast amount of work remains to be completed before that prototype will begin to look anything like an actual spaceship, and the exact fidelity SpaceX is hoping to achieve with it is unclear.
If the company tries to get as close as possible to a finished product (within reason, of course) before beginning propulsive hop tests in Texas, a very late-2019 debut of that test campaign could be a practical goal. It’s not a perfect comparison, but Falcon 9 is perhaps the best prior example of SpaceX’s speed of development, moving from structural fabrication and testing (albeit with Falcon 5 in mind) in 2006 and 2007 to a full-up orbital launch of the first Falcon 9 in mid-2010, with milestones like the first static fire of a booster octaweb and nine Merlin 1C engines 6-12 months prior.
-
For prompt updates, on-the-ground perspectives, and unique glimpses of SpaceX’s rocket recovery fleet check out our brand new LaunchPad and LandingZone newsletters!
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
