News
SpaceX's "Christmas tree" is a Raptor engine for the holidays
SpaceX CEO Elon Musk showed off a holiday-themed Raptor engine “Christmas tree” with its very own star on top. Musk noted via a tweet that the company’s Starship propulsion team is “making great progress” building, testing, and refining the Raptor engines that will one day propel the next-generation rocket to Earth orbit and beyond.
On December 13th, Musk revealed that SpaceX is preparing to ship the 17th completed Raptor engine to the company’s McGregor, Texas rocket test and development facilities, the site of several dedicated test stands for the Starship engine. Likely one of the most complex rocket engines ever designed, built, or tested, Raptor relies on an exotic combustion cycle, referring to the specifics of how engines turn their propellant into meaningful thrust.
Raptor uses what is known as full-flow staged combustion (FFSC) and is the first FFSC engine to graduate beyond ground testing and actually fly, thus far having completed two flight tests in July and August 2019 as part of SpaceX’s Starhopper test campaign. In simple terms, the FFSC cycle aims to extract as much energy from a rocket’s propellant as efficiently as possible, resulting in what is theoretically the most efficient possible chemical propulsion from a given fuel and oxidizer combination.
Due to the sheer complexity required to achieve full-flow staged combustion, the engine type is incredibly rare and only two other (once) functional examples exist – one developed by Soviet engineers in the 20th century and the other built, tested, and inexplicably scrapped by NASA in the 2000s. In fact, the Soviet RD-270 engine’s thrust-to-weight ratio is likely second only to SpaceX’s own Merlin 1D engine, an absolutely spectacular achievement for a propulsion bureau operating in the late 1960s.
RD-270 had major development challenges and would likely have taken years of additional hardware-rich (i.e. destructive trial and error) testing to produce an engine actually capable of reliable flight. Before the program was cancelled in 1970, 22 engines were tested and no single RD-270 survived to perform a fourth static fire, a testament to the immense challenge of FFSC engines.
SpaceX appears to have had a much better go of it with Raptor, although many, many engines have definitely been destroyed or irreparably damaged since the full-scale engine’s February 2019 static fire debut. SpaceX CEO Elon Musk says that the 17th completed Raptor engine is almost ready to head to McGregor, Texas to kick off development and acceptance testing.
It remains to be seen when exactly Raptor engines will be mature and reliable enough to perform the 3-10 minute burns needed to send a Starship to orbit, let alone the Moon or Mars, but Musk appears confident that SpaceX is making great progress along those lines.
Per photos and info posted by NASASpaceflight.com earlier today, Raptor engine SN15 is already installed on a recently-reactivated McGregor test stand ahead of its first rocket-related test in almost half a decade.
Formerly used to test Falcon 9 first stages before SpaceX built a new stand for Falcon 9 and Heavy, that tripod stand has been reactivated for the sole purpose of supporting vertical Raptor engine static fire testing, which Musk says will simplify and expedite development by making test conditions much more flight-like. As of now, all subscale and full-scale Raptor engine static fire testing has been performed at horizontal test stands in McGregor, apparently resulting in wear and behavior that would not likely appear if engines were tested vertically.
SpaceX has gone through the same process with its Merlin engine programs, beginning with horizontal testing (far easier and simpler) but ultimately building a number of dedicated vertical test bays to ensure that engine acceptance and development tests can be performed under more flight-like conditions.
According to NASASpaceflight, SpaceX may have already fired up Raptor SN15 on its reactivated tripod test stand earlier this week, kicking off Raptor’s first Starhopper-free vertical static fire testing. It’s now unclear where the twin horizontal Raptor test bays will fit into future engine testing given Musk’s comments. More importantly, every completed Starship and Super Heavy rocket will require several dozen new Raptor engines and every one of those engines will likely need to pass acceptance testing (including static fires) in McGregor before they can be installed on a launch vehicle.
SpaceX’s Falcon 9 rocket already requires 10 engines per new booster and upper stage, a test burden SpaceX has only managed with the help of two Merlin 1D stands and one Merlin Vacuum stand, all vertical. In other words, it’s safe to say that the reactivated tripod stand is likely just the first of several vertical Raptor test stands to come.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
A new report from Reuters claims that a transport authority in Sweden is pushing back against the approval of Tesla’s Full Self-Driving suite because it will travel over speed limits.
The report says the Swedish Transport Administration (TRV) recommends the European Union votes against FSD’s approval. TRV believes it should not be approved until Tesla disables FSD’s ability to speed.
TRV sent a letter to the European Union’s Technical Committee on Motor Vehicles (TCMV), which is set to meet on June 30 to discuss the potential approval of the Tesla FSD suite in the country. Tesla, which has received various approvals in Europe over the past two months, has not provided a comment.
Teslas operating on FSD do travel over the speed limit, depending on the Speed Profile that is chosen. Drivers have the ability to disengage FSD at any point; Tesla specifically states that those supervising the suite are responsible for its actions.
Let’s cut to the chase: humans operating any vehicle speed almost daily in the United States. Realistically, speed limits in the U.S. are more frequently treated as speed minimums. However, other countries are different, and driving behaviors are less aggressive.
TRV believes that “allowing automated systems to systematically exceed legal speed limits…risks undermining both the legal framework and the expected safety benefits of vehicle automation,” the report stated. It’s surprising that Tesla has not received this claim from other countries previously.
This could be a good argument to bring Max Speed back, the setting that previously allowed the driver to choose the absolute fastest the car would travel.
This would still put the responsibility of supervision in the hands of the driver. It would allow the driver to choose whether the car would travel over the speed limit or not, acknowledging that they set the speed, and if they get pulled over, there would be no ability to argue it.
However, it does not seem as if this is something Tesla will do, especially considering many U.S. drivers have requested the feature in an effort to eliminate speeding or at least tone it down. The company has not shown any interest in bringing it back.
Tesla has approvals for FSD in Europe in Estonia, Lithuania, Denmark, the Netherlands, and Belgium.
Tesla is going to let you guide Full Self-Driving with Grok in 3 months, CEO Elon Musk confirmed on X.
The response from Musk, which revealed Tesla plans to allow drivers to effectively control the car and its navigation more explicitly using Grok, puts the feature for about September.
A Tesla owner said that Full Self-Driving is great, but owners should be able to “converse with Grok like we can with an Uber driver.” She then used examples like, “Grok, turn right here,” and “Drop us off right here, we’ll walk due to traffic,” and finally,” Drop at entrance first, then park far away.”
Coincidentally, the final piece of dialogue would also mean features like Banish are potentially on the way soon.
This functionality will be there in about 3 months or so
— Elon Musk (@elonmusk) June 18, 2026
Banish is also referred to as “Reverse Summon,” and would enable the car to self-park while dropping occupants off at their destination.
This would be a great way to improve the overall experience while supervising FSD. Navigation is already a major painpoint that many owners complain about. Manual overrides when a maneuver is requested or canceled (like using the turn signal stalk to override a navigation route), do not always work.
The feature could be especially useful in street parking scenarios in a city, where spots are sometimes tough to come by. Many of us who grab dinner in a more populated area will park a street or two over from wherever we’re going, because sometimes you know that’s the best you will get. If a driver using FSD could say, “Hey Grok, turn right here on Queen St. and park in that open spot on the right,” it could save a lot of confusion FSD might have on its own.
Musk teased that a similar feature was “coming” back in February:
Tesla Full Self-Driving set to get an awesome new feature, Elon Musk says
It is certainly surprising that Tesla is doing it at this point. The company’s more recent moves have been more evident of taking control and inputs away from humans and putting them in the AI’s hands more frequently. The biggest example of this was taking away Max Speed in AI4 cars, giving us Speed Profiles, and not having any input on the fastest speed the car will travel.
Of course, giving navigation preferences to Grok is availble already in Teslas, but not at the drop of a hat. Instead, you can suggest a certain route at the beginning of your drive.
Here’s an example of that from December:
🚨🏈 I am taking my parents and Fiancee to the @Ravens game next weekend and asked @Grok to help me route my @Tesla through a specific neighborhood to reach the correct Lot we will park in.
This is a great example of the new @grok nav integration with the Tesla Holiday Update: pic.twitter.com/rPp4I7q8Yv
— TESLARATI (@Teslarati) December 13, 2025
Finally, the original post that Musk responded to mentioned a parking preference after dropping off the occupants, which describes the Banish feature that Tesla has teased for years.
We’re not sure if Musk was responding more to the ability to guide the car with Grok, or whether he also was including Banish in the three-month prediction timeframe.
A close-up image of a Cybercab engineering vehicle in Peabody, Massachusetts, reveals a compact triangular side repeater camera housing equipped with an integrated washer mechanism.
This seemingly small hardware addition could prove to be one of the most critical components for achieving reliable, unsupervised Full Self-Driving (FSD) — not just for the dedicated Robotaxi but potentially for existing AI4-equipped vehicles as well.
The washer system’s importance cannot be overstated in Tesla’s vision-only autonomy approach. Cameras are the sole sensory input for the neural networks powering FSD, constantly interpreting the environment for safe navigation. In real-world conditions, however, lenses quickly accumulate rain, snow, mud, dust, or road spray.
Many of us Tesla owners, especially those who deal with any sort of winter weather at all, know the all-too-common alert that pops up when cameras are obstructed:
Even brief obstructions can drop perception confidence, trigger safety disengagements, or force the vehicle to pull over, although these are relatively rare. Instead, most of the time, the camera will need a wipe from the owner next time they stop the car.
But unlike human drivers who can manually clear their view, a Robotaxi operating 24/7 without a steering wheel or mirrors must maintain pristine vision autonomously. The Cybercab’s side repeater washer delivers targeted cleaning bursts precisely where needed for merging, lane changes, and blind-spot monitoring — functions that demand uninterrupted visibility from the external cameras:
And this is how the side camera and washer look like on a Cybercab. This is from an Engineering vehicle in Peabody MA. pic.twitter.com/Re8VknpmLM
— Tobias Goebel (Unsupervised) (@tpgoebel) June 17, 2026
This hardware directly tackles a known pain point in current FSD deployments. Owners frequently report camera-related alerts during inclement weather, which is understandable, but needs to be solved for a true autonomous experience.
For a production Robotaxi fleet aiming for high utilization and minimal downtime, robust washer systems represent a foundational reliability upgrade; essentially, they’re a must-have. Early sightings suggest the design may extend to rear cameras as well, creating a comprehensive cleaning architecture that keeps the entire vision suite operational in harsh environments.
Without it, even the most advanced neural nets struggle when their “eyes” are compromised.
What Does This Mean for AI4 Cars?
This Cybercab detail raises timely questions for AI4 cars already on the road. While Hardware 4 delivers superior compute and camera resolution compared to earlier versions, production models typically lack dedicated side and rear washers. Tesla has included them on Model Y robotaxis that it is using in the fleet:
Tesla Robotaxi has a highly-requested hardware feature not available on typical Model Ys
As Tesla refines unsupervised FSD for broader release, the gap in environmental resilience becomes evident. Software improvements can help mitigate issues, but they cannot fully replace physical cleaning in heavy rain or muddy conditions. Analysts and owners increasingly speculate that AI4 vehicles may eventually require similar washer retrofits — or a future AI4.5 variant — to match the Cybercab’s all-weather readiness and support the same level of autonomy.
As testing progresses, the Cybercab’s washer mechanism highlights Tesla’s pragmatic focus on real-world robustness. It may well become the hardware piece that determines how quickly and reliably FSD scales from prototypes to everyday vehicles.
Tesla faces Full Self-Driving pushback in EU over ‘speeding’
Tesla teases greater Grok FSD integration and ‘Banish’ feature ‘in about 3 months’
