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.
Tesla AI lead Ashok Elluswamy said this week that 24-hour Robotaxi service is close. Replying on X to a rider who wanted Cybercab trips all night, he wrote that the capability would arrive “next month or so” once “the next tech to merge on the v15 plan” is ready.
The comment landed on September 4, one day after Tesla opened public Cybercab rides in Austin. It is the clearest near-term timeline yet for overnight unsupervised operation. Tesla’s paid Robotaxi network currently runs from 6 a.m. to 10 p.m. seven days a week across Austin, Dallas, Houston, Miami, Orlando, and Tampa.
next month or so. the next tech to merge on the v15 plan will enable it.
— Ashok Elluswamy (@aelluswamy) September 4, 2026
That 16-hour window is shorter than the 6 a.m. to 2 a.m. schedule the company used for much of the prior year.
Elluswamy did not name the specific feature or say whether the change would apply first to purpose-built Cybercabs, the existing Model Y fleet, or both. He also offered no city-by-city rollout list. The link to Full Self-Driving v15 is nevertheless significant.
Tesla has described v15 as a step-change architecture with seven parallel improvement tracks and roughly ten times more parameters than earlier builds. Early versions of that software already operate on the Robotaxi fleet and contain about 40 percent of the planned gains.
By July 2026, the unsupervised fleet had logged more than 380,000 miles across six cities in two states with what the company called an impeccable safety record and no notable incidents caused by the vehicles themselves. Tesla has repeatedly argued that camera-based end-to-end neural networks, rather than extra sensors, are the core of the solution.
Overnight service would test that claim in lower-light conditions and would also raise vehicle utilization, a key variable for Robotaxi unit economics. The company has already begun using public Superchargers at night and is building dedicated Robotaxi charging sites.
Riders have asked why software must change if the cars already drive in the dark. The practical answer appears to be reliability and scale: Tesla has held back mass expansion until more of the v15 stack is merged, citing the need for higher confidence before putting thousands of unoccupied vehicles on streets around the clock.
If the next module arrives on the timetable Elluswamy sketched, 24-hour service could begin in October 2026 in at least some markets.
That would mark a shift from a daytime-bounded pilot to a service that can run whenever demand exists, including the late-night hours that have so far remained out of reach.
Tesla is beginning to roll out Full Self-Driving Supervised v14.3.9 with a new active safety layer that can take control even when the driver is operating the car manually.
Tesla AI said the software can activate FSD on the driver’s behalf when an imminent collision is detected and Automatic Emergency Braking may not be enough. It may also engage if the system detects heavy distraction or an accidental FSD disengagement.
FSD Supervised v14.3.9 starting to roll out shortly
This release includes a new active safety feature set: FSD Supervised can now activate on your behalf when an imminent collision is detected and Automatic Emergency Braking (AEB) may not be enough.
It may also engage if we…
— Tesla AI (@Tesla_AI) September 4, 2026
The capability is essentially Automatic Collision Evasion. However, unlike conventional AEB, which mainly applies the brakes in a straight line, this feature can use steering, braking, and acceleration together if the car calculates that stopping alone will not prevent impact and a safer path exists. The system may change lanes or move toward a shoulder when conditions allow, then continue driving after the immediate threat is handled rather than simply coming to a stop.
The intervention is meant as a last-resort safety net, not a replacement for attentive driving.
Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident
Tesla’s own description still frames FSD as supervised assistance. Secondary reports on internal release notes say the feature can fire while the car is being driven manually if cabin-camera monitoring suggests the driver is not sufficiently attentive, such as reaching toward the back seat, or if FSD appears to have been turned off unintentionally.
After the emergency maneuver, the car is expected to alert the driver and request a return to manual control.
The safety case is straightforward. Many collisions happen in the last second because a driver is looking away, fumbles a control, or faces an obstacle that braking cannot fully solve. A system that can both recognize that AEB is insufficient and execute a coordinated evasive path can reduce those remaining high-severity events.
Re-engaging after accidental disengagement also addresses a practical failure mode: a small steering nudge that drops FSD at the worst moment. The advantage is a background safety net that uses the same vision stack already running in v14, instead of leaving the car solely to emergency braking once the driver is no longer in command.
The feature still depends on FSD being enabled and, according to reports, an active FSD purchase or subscription. It does not make the vehicle unsupervised. Drivers remain responsible, and Tesla has not published how often the system is expected to intervene or how it will handle false positives.
If the rollout is conservative and the false-alarm rate stays low, the update is a meaningful step: FSD is no longer only a feature the driver turns on. In the rare moments when disaster is already forming, it can step in.
Tesla launched the all-electric, steering wheel-less, and pedal-less Cybercab last night at a quiet and small event in downtown Austin, Texas.
The launch, which marked the beginning of unsupervised ride-hailing for Tesla’s Robotaxi platform with Cybercab, has already caught the attention of the National Highway Traffic Safety Administration (NHTSA) who has more questions.
NHTSA opened an Audit Query (AQ) into the Cybercab’s Federal Motor Vehicle Safety Standards (FMVSS) certification that Tesla gave the vehicle. Manufacturers self-certify vehicles much of the time to avoid excessive regulatory delays.
Tesla Cybercab interior, note the lack of steering wheel and pedals. (Credit: @niccruzpatane/X< /a>)
However, the agency needs more information; it said in a summary:
“On September 3, 2026, Tesla began commercial deployment with a small number of its Cybercab vehicles in Austin, Texas. Tesla notified the Agency that it certified those Cybercab vehicles as compliant with all applicable Federal Motor Vehicle Safety Standards (FMVSS). Tesla also notified the Agency that it plans to gradually expand commercial deployment of the Cybercab to include additional vehicles and locations.”
It also went on to state that the Cybercab lacks traditional automotive controls, which is a groundbreaking move. The process is entirely new to the NHTSA, which gives the agency some leverage to put Tesla’s launch under a microscope:
“The vehicles lack permanently attached, conventional manual controls, such as a brake pedal, gas pedal, steering wheel, and mirrors. NHTSA is opening this AQ to examine the process and technical data on which Tesla relied when certifying the Cybercab and related issues. Among other things, NHTSA will consider the extent to which Tesla’s certification depended on determinations that certain FMVSS are inapplicable to the Cybercab.”
Tesla has added 45 Cybercab units to its fleet of Robotaxi-enabled cars in Austin, according to public documents the company submitted to the State of Texas over the past week. Enabling this level of self-driving is something Tesla has worked toward for many years, and now that it is finally here, it seems more than reasonable that regulatory agencies will have some questions.
Many outlets might try to frame this as a negative, but it is truly an agency looking to gain more information about groundbreaking tech that Tesla has been developing for years.
In an effort to keep riders, pedestrians, and property safe, any and all data accumulated from these first days, weeks, and months of rides will likely be shared with the NHTSA to enable broader rollout strategies across the United States and more in the future.
Tesla Robotaxi will be a 24/7 service: here’s when
Tesla Full Self-Driving will now overtake manual driving to avoid disaster
