Connect with us

News

SpaceX rolls Raptor Vacuum engines to launch pad for Starship’s next tests

A Raptor Vacuum engine is pictured among sea-level siblings inside a Starbase hangar. (SpaceX)

Published

on

For the second time, SpaceX is gearing up to install a full six Raptor engines on the first orbital-class Starship prototype.

This time around, though, there’s reason to believe that the preparations SpaceX is making aren’t a false start and could culminate in one or several record-breaking Starship static fires as early as next week.

SpaceX installed Raptors on Starship S20 for the first time in early August, outfitting the 50m (165 ft) tall prototype with a full six engines as part of a fit test that ultimately saw it installed on top of a Super Heavy booster. Ship 20 only spent an hour on top of Booster 4, though, and was quickly returned to Starbase build site for Raptor removal and final outfitting. Ship 20 was then rolled back to the launch site and installed on one of two suborbital launch mounts and test stands in mid-August, where it has sat ever since.

Between September 4th and 10th, SpaceX then appeared to install three sea-level-optimized Raptor Center (RC) engines and one Raptor Vacuum (RVac) engine on Starship S20 before the prototype had completed any proof testing. Whether that set of installs was a fit test or an aborted attempt at full installation, SpaceX seemingly paused at three or four Raptors and ultimately removed the lone RVac and one or more of S20’s sea-level engines. Another sea-level Raptor was (re)installed on September 15th.

After a frenetic month of back and forth with no obvious rhyme or reason, all of Ship 20’s Raptors were removed and a series of hydraulic rams used to simulate engine thrust – removed, unused, back in August – were reinstalled. Starship then completed pneumatic and cryogenic proof tests in the last few days of September.

Starship S20 fires up for the first time with Super Heavy B3 and B4 in the rafters. (NASASpaceflight – bocachicagal)

After another ten or so days of unusual downtime, SpaceX began reinstalling Raptors on Ship 20 – one sea-level and one vacuum – around October 10th for a static fire test campaign that began about a week later. Finally, on October 21st, SpaceX fired up the orbital-class prototype for the first time, also completing the first test of a Raptor Vacuum engine installed on a Starship. Barely an hour later, Starship S20 performed a second test, simultaneously firing up both RVac and RC engine in another first.

Barely a full day after that successful back-to-back static fire test, SpaceX rolled two more sea-level Raptors to the suborbital pad and installed them on Ship 20. Another unusual week of downtime later and, on October 28th, SpaceX has rolled two more Raptor Vacuum engines from the build site to the launch pad and staged them beside Starship. Once installed, Starship S20 will, for the second time, be fully outfitted with six Raptors. Having already fired up two of those engines without needing either replaced, though, there’s a decent chance that all six will actually be used before Ship 20’s next bout of engine removal/installation deja vu.

Advertisement
-

SpaceX has never fired more than three engines at a time on a Starship prototype or at its suborbital test site, so a number of firsts potentially lay before Ship 20 as it nears a second round of static fire testing. There is some uncertainty as to whether the suborbital test stands can actually handle the stress from static fires with more than three Raptors, but if they can, then S20 will likely be the first prototype to ignite more 4+ engines and could become the first Starship to fire all six engines at once.

SpaceX currently has one possible test window scheduled from 10am to 6pm CDT on Monday, November 1st, though it could be another week or more before Starship S20’s next static fire attempt if past trends continue.

Eric Ralph is Teslarati's senior spaceflight reporter and has been covering the industry in some capacity for almost half a decade, largely spurred in 2016 by a trip to Mexico to watch Elon Musk reveal SpaceX's plans for Mars in person. Aside from spreading interest and excitement about spaceflight far and wide, his primary goal is to cover humanity's ongoing efforts to expand beyond Earth to the Moon, Mars, and elsewhere.

Advertisement
Comments

Elon Musk

Elon Musk rips ABC News over fatal NYC Tesla crash report

Musk pushed back on NYC Tesla crash coverage, pointing to a pattern of premature blame.

Published

on

By

Elon Musk pushed back overnight against media framing of a fatal Tesla crash in Midtown Manhattan, telling a user on X that “it wasn’t the car” and that the vehicle’s Autopilot system had nothing to do with the wreck.

The crash happened just before 3 a.m. Wednesday, when a 2024 Tesla Model Y struck a sidewalk shed outside 315 Madison Ave., a bus stop pole and a mailbox on East 42nd Street, according to the NYPD. The car kept moving several more blocks before stopping near Second Avenue. Both women inside, each 27, were taken to Bellevue Hospital, where the passenger was pronounced dead. The driver was charged with vehicular manslaughter, driving while ability impaired and leaving the scene of an accident.

Police have not attributed the crash to Autopilot or Full Self-Driving in any public statement. The charges point to impairment, not software. Musk’s response followed a since-deleted ABC News post that he said mischaracterized the incident. Replying to a user on X, Musk wrote that if Autopilot had been engaged, “they would not have crashed,” and added that “the legacy media will never forgive Tesla for failing to advertise with them,”

It’s a familiar cycle for Tesla. In June, headlines from several national outlets described a fatal crash in Katy, Texas, as happening while the car was “on autopilot,” based on the driver’s own account to police after his Model 3 struck a home and killed a 76-year-old woman. Tesla’s data told a different story when Ashok Elluswamy, Tesla’s head of AI, said the driver had pressed the accelerator to 100% and reached 73 mph in a residential zone. Harris County prosecutors later confirmed the human override and the driver was charged with manslaughter.

Florida Gov. Ron DeSantis pointed to that same Katy crash last month to argue that outlets routinely name Tesla in crash headlines while leaving other automakers unnamed, even after a driver’s own actions are shown to be the cause. A similar pattern played out in 2024, when Musk had to clarify that FSD was never even downloaded onto the Model 3 involved in a fatal Colorado DUI crash, despite a passenger’s claim that an “auto drive feature” was in use.

Tesla has not issued a separate statement on the Manhattan crash beyond Musk’s posts on X. The NYPD’s investigation is ongoing, and no cause for the driver losing control has been released.

Continue Reading

News

Tesla’s two defunct flagship models are getting a big upgrade

Published

on

Tesla’s two recently-defunct flagship models, the Model S and Model X, are getting a big upgrade, according to the company’s Head of AI, Ashok Elluswamy.

Older Hardware 3 Model S and Model X vehicles have been the last major holdouts in Tesla’s Full Self-Driving v14 Lite rollout, and that wait now appears to be ending.

Tesla brings closure to flagship ‘sentimental’ models, Musk confirms

At Tesla’s Cybercab launch, AI chief Ashok Elluswamy told Ryan McCaffrey that he thought the S and X build “was supposed to go out last week.” Evidently, Elluswamy expects the suite to be rolled out to those HW3 Model S and Model X very soon:

Those cars are not the current Model S and Model X, which already ship with Hardware 4. They are the pre-refresh flagships built around Tesla’s older Autopilot computer, often called HW3 or AI3.

Tesla stopped putting that computer in new vehicles years ago, which is why owners treat these S and X cars as a closed generation. Model 3 and Model Y vehicles on the same computer began receiving v14 Lite in late June 2026 and saw a wider North American expansion in July. South Korea followed as an early international market. The S and X versions of the same software never joined that wave.

v14 Lite is Tesla’s way of squeezing the current v14 driving stack onto hardware that cannot run the full AI 4 model. The company describes the process as distillation: behaviors learned on the newer computer, including reinforcement learning and offline models, are compressed so the older chip and cameras can use them as a guide.

Early descriptions put the distilled network at roughly 15 percent of the original size. The result is still supervised Level 2 driving. Tesla has been clear that HW3 cannot support unsupervised Full Self-Driving or robotaxi operation because of memory and bandwidth limits.

The feature list is what made the wait so frustrating for S and X owners, as plenty of new features are to be shipped with it.

Official notes for the first Lite build, firmware 2026.20.5.1, added parking, unparking, and reversing; arrival options for a parking lot, street, driveway, or curbside; speed profiles that stay available at all times; and start-from-park engagement. Tesla also claimed better handling of merges, forks, pedestrians, traffic lights, and cut-ins, plus fewer false slowdowns and smoother lane centering.

A mid-July follow-on build, 2026.20.6.10, added more of the Hardware 4 interface, including a standalone Self-Driving app and the ability to start a trip from Park without a brake-pedal confirmation.

Elluswamy called that version the one “likely going to wide release.”

That wide release already reached most other HW3 cars in the United States and Canada. International timing still depends on regional validation and regulatory approval. For S and X owners, the remaining work appears to be model-specific validation rather than a new software stack.

There is no official Tesla changelog or build number for those two models yet, only Elluswamy’s offhand timeline. Some HW3 drivers who already have Lite report large gains over v12.6; others have described new indecision or phantom braking. The next test will be whether the same software lands cleanly on the older flagships that have waited the longest.

Continue Reading

Cybertruck

This tiny Tesla Cybertruck adjustment has big advantages

Published

on

Credit: Wes Morrill | X

Yesterday, we reported on Tesla Cybertruck getting some major adjustments from a manufacturing standpoint in an effort to make the all-electric pickup more cost-effective, more reliable, more serviceable, and more easily produced.

Tesla Cybertruck engineer reveals new changes in ‘constantly evolving’ pickup

One of those changes was the addition of a self-reinforcing polypropylene aero shield that sits underneath the truck. Previously, Tesla utilized aluminum for this, but the self-reinforcing polypropylene was more durable while also being cheaper and lighter.

Tesla has revealed another small change it made to the Cybertruck, and it has to do with the side repeater cameras.

Tesla does not wait for a new model year to improve its vehicles. On September 8, Cybertruck lead engineer Wes Morrill posted side-by-side photos of an updated side repeater camera housing now rolling off the line at Gigafactory Texas.

The triangular camera pod mounted on the front fender looks almost identical at first glance. A closer look reveals a revised contour that uses the air already flowing around the truck to keep the lens clearer in rain and road spray.

The side repeater cameras sit in an exposed position on the Cybertruck’s angular stainless-steel body.

In wet weather, they readily collect water droplets that can degrade the image Autopilot and Full Self-Driving use for lane changes and blind-spot monitoring. Early production trucks sometimes left owners wiping lenses by hand or accepting temporary restrictions on driver-assistance features.

Tesla has added washers to cameras on certain other models and on Cybercab prototypes, but those active systems add cost, complexity, and extra potential leak points.

The new housing solves the problem with passive geometry. Subtle changes in the surround create localized airflow disturbances as the vehicle moves. Those eddies physically push water droplets away from the optical surface. Morrill called the result “pure vision improvement” achieved at “no cost penalty.” Once the production mold is updated, every subsequent part costs the same as the original.

The advantages compound quickly. Clearer cameras in rain improve the reliability of driver-assistance features precisely when they are needed most. The design consumes no extra energy and introduces no new failure modes.

New Cybertrucks built after the tooling changeover receive the updated part automatically. Some owners of trucks delivered as late as June 2026 have already confirmed they received the revised housing. Retrofit questions have appeared in replies, and the cameras appear electrically compatible, though Tesla has not announced an official service program.

A few millimeters of reshaped housing will not make headlines the way a new battery pack does, but these changes are incremental and increase the Cybertruck’s effectiveness as a vehicle over time.

This improvement illustrates how Tesla continues to refine the Cybertruck after volume production began. Better wet-weather vision, zero added cost, and no extra hardware add up to a meaningful gain in everyday usability and safety.

Continue Reading