Connect with us

News

SpaceX aborts several Starship static fire attempts, rolls test tank to the pad

Still plagued by aborts and delays, Starship SN9 sits to the right of test tank SN7.2 on January 20th. (NASASpaceflight - bocachicagal)

Published

on

Accidentally producing the polar opposite of Starship serial number 9 (SN9) completing a trio of Raptor ignition tests in four hours last week, SpaceX has now suffered three back-to-back static fire aborts on January 20th.

On January 13th, Starship SN9 somewhat successfully ignited its Raptor engines three separate times with zero hands-on human intervention or inspection. While an impressive feat, SpaceX CEO Elon Musk soon revealed that two of the rocket’s three engines were damaged during the test campaign. NASASpaceflight.com later reported that the company had detected an issue with one Raptor after the first three-engine static fire, ultimately firewalling it and performing the next two static fires with only two engines.

SpaceX initially allotted five days to replace the two damaged Raptors (SN44 & SN46), scheduling road closures (a telltale sign of test plans) on January 18th, 19th, and 20th. Windows on the 18th and 19th went by with zero attempts. Finally, on the 20th, SpaceX kicked off Starship SN9’s first real test attempt since the engine swap around 2pm but it was aborted by 3pm.

After an extremely brisk recycle, Starship likely made it less than a minute away from ignition but the second attempt was ultimately aborted around 3:40 pm.

Two hours later, after SpaceX extended the end of its road closure from 5pm to 8pm, Starship SN9’s third Raptor static fire attempt was also aborted – once again just a minute or less away from ignition.

SpaceX held Starship SN9 for another hour or so after the third abort but ultimately began final detanking and depressurization around 6:50 pm, marking the end of the day’s attempts.

Advertisement
-

It’s impossible to say what caused Wednesday’s back-to-back-to-back aborts or if the three instances were connected. While potentially frustrating to watch from the sidelines, it’s crucial to remember that the public is getting a truly unprecedented continuous view of SpaceX’s process of developing and refining a world-class launch vehicle. Additionally, every abort Starship suffers should theoretically produce volumes of valuable data that both Starship and Raptor teams can use to better understand how to design, build, test, and operate the cutting-edge vehicle and its engines.

More likely than not, SpaceX is leaning towards caution (and thus cautious hardware and software limits) while attempting to prepare Starship SN9 for its true data-gathering purpose – an SN8-style high-altitude launch and landing attempt.

Starship SN8’s launch and (explosive) landing debut. SN9’s goal is to replicate the feat without the last-second explosion. (Richard Angle)

SpaceX is currently scheduled to try again with another series of Starship SN9 static fire attempts between 8am and 5pm CST (UTC-6) on Thursday, January 21st.

Meanwhile, prior to SN9’s multiple Wednesday aborts, SpaceX rolled the latest in a series of Starship ‘test tanks’ from the factory to the launch pad. A team rapidly strapped the tank to the concrete pad and connected it to ground support equipment in preparation for a series of tests that will likely end with SpaceX intentionally pressurizing the tank until its bursts. If successful, it will open the door for future Starships to save weight by cutting steel skin thickness from 4mm to 3mm.

Stay tuned for updates on both active test campaigns.

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