News
SpaceX delays Starhopper’s first flight a few days despite Raptor preburner test success
SpaceX has (partially) ignited Starhopper’s freshly-installed Raptor engine, successfully verifying that the engine is ready for its next major test: a full ignition and static firing. Although successful, SpaceX still has some work to do before the vehicle is ready for its first untethered flight(s).
July 15th’s progress is just the latest in a several day-series of preflight tests designed to reduce the likelihood that Starhopper is destroyed over the coming days and (hopefully) weeks. If all goes planned during the awkward Starship prototype’s first foray into hover tests, SpaceX CEO Elon Musk has stated that he will provide an official presentation updating the public on the status of the company’s ever-changing next-generation rocket.
The past week or so of Starhopper preflight testing began with Raptor serial number 6 (SN06) completing the last of a series of acceptance test fires in McGregor, Texas on June 10th. Even on its own, this was a major milestone for the new SpaceX engine: Raptor SN06 was the first of the new, full-scale engines to pass the acceptance test program with flying colors. According to Musk, for the engine to complete those tests so successfully, SpaceX had to solve a challenging bug in which some sort of mechanical resonance (i.e. vibration) damaged or destroyed Raptors SN01-05.
Hours later, the engine began a short ~450 mi (720 km) journey south to Starhopper, located in Boca Chica, Texas. The engine arrived on July 11th and was fully installed on Starhopper by the following evening (July 12th), at which point SpaceX put Starhopper and Raptor through some mild but valuable thrust vector controller (TVC) tests, wiggling the car-sized engine to ensure it can accurately steer the prototype rocket.
Around two days after the above ‘wiggle’ test was successfully completed, SpaceX moved into the next stage, partially fueling Starhopper with liquid methane and oxygen propellant and helium pressurant in what is known in rocketry as a wet dress rehearsal (WDR). The (implicitly) successful WDR was capped off with a duo of what can now safely be concluded were some sort of Raptor test preceding even pre-ignition operations. Whatever the tests were, they appear to have been completed successfully.
That appears to be the case because less than 24 hours after their completion, on July 15th, SpaceX once again began loading Starhopper with propellant and pressurant for a second round of wet testing. This time around, SpaceX got right into more critical Raptor tests once enough propellant was loaded, igniting the engine’s interwoven oxygen and methane preburners.
Previously discussed 24 hours ago in a Teslarati article focused on Raptor wiggles and other miscellaneous tests, Raptor is an extremely advanced rocket engine based on a cycle (i.e. how propellant is turned into thrust) known as full-flow staged combustion.
“In a staged-combustion engine like Raptor, getting from the supercool liquid oxygen and methane propellant to 200+ tons of thrust is quite literally staged, meaning that the ignition doesn’t happen all at once. Rather, the preburners – essentially their own, unique combustion chambers – ignite an oxygen- or methane-rich mixture, the burning of which produces the gas and pressure that powers the turbines that bring fuel into the main combustion chamber. That fuel then ignites, producing thrust as they exit the engine’s bell-shaped nozzle.
Unintuitively, conditions inside the preburner – hidden away from view – are actually far more intense than the iconic blue, purple, and pink flame that visibly exists Raptor’s nozzle. Much like hot water will cool while traveling through pipes, the superheated gaseous propellant that Raptor ignites to produce thrust will also cool (and thus lose pressure) as it travels from Raptor’s preburner to its main combustion chamber. If the pressure produced in the preburners is too low, Raptor’s thrust will be (roughly speaking) proportionally limited at best. At worst, low pressure in the preburners can trigger a “hard start” or shutdown that could destroy the engine. According to Elon Musk, Raptor’s oxygen preburner thus has the worst of it, operating at pressures as high or higher than 800 bar (11,600 psi, 80 megapascals).”
In full-flow staged combustion (FFSC), even more complexity is added as all propellant that touches the engine must necessarily end up traveling through the main combustion chamber to eke every last ounce of thrust out of the finite propellant a rocket lifts off with. As such, FFSC engines can be about as efficient as the laws of physics allow any given chemical rocket engine to be, at the cost of exceptional complexity and brutally difficult development.
Additionally, FFSC physically requires two separate preburners and then makes things even harder by making each separate preburner (methane and oxygen) depend on each other’s operation for the engine to fully ignite. This means that no individual preburner can be used to kickstart Raptor – instead, SpaceX must somehow spin the turbopumps that feed propellant into each preburner with some separate system. This is all just to emphasize the fact that Raptor’s ignition sequence is a spectacularly complex orchestra of valves, spark plugs, sensors, and magic. This is why it’s valuable for Raptor to test its preburner system independently of an actual ignition test, at least as long as the engine is still in the development stages.
According to NASASpaceflight.com managing editor Chris Bergin, what this practically translates to is a minor Starhopper hover test delay of 1-2 days, while the static fire has also been pushed roughly 24 hours from July 15th to July 16th. If that full static fire produces lots of happy data, Starhopper could be cleared for a hover test debut attempt as early as Wednesday or Thursday (July 17/18).
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
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.
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,”
The legacy media will never forgive Tesla for failing to advertise with them
— Elon Musk (@elonmusk) September 9, 2026
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.
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:
For my @Tesla friends – and specifically Model S & X owners with HW3 who are waiting on FSD v14 Lite – I spoke to @aelluswamy at the Cybercab launch, & when I asked for an ETA on v14 Lite for S/X owners, he said, “Oh, I thought it was supposed to go out last week.”
So: soon! 🙌
— Ryan McCaffrey (@DMC_Ryan) September 7, 2026
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.
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 camera was updated – the version on the left is the newer part which uses passive geometry to create airflow disturbance that better keep water off the lens while driving. No cost penalty, just pure vision improvement. pic.twitter.com/wAbXtcL1Jf
— Wes (@wmorrill3) September 8, 2026
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.
Elon Musk rips ABC News over fatal NYC Tesla crash report
Tesla’s two defunct flagship models are getting a big upgrade
