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.

Advertisement

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.

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.

Advertisement

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

News

Tesla to open source Model S and Model X designs and software

Published

on

Credit: Tesla

In a move echoing its earlier commitment to open innovation, Tesla CEO Elon Musk announced recently that the company plans to make the design and software of its Model S and Model X fully open source.

This follows the same approach Tesla took with its original Roadster, releasing all available design, engineering, and diagnostic materials in November 2023 so that “whatever we have, you now have.”

The Model S, introduced in 2012, was Tesla’s first mass-produced vehicle and a groundbreaking luxury electric sedan. It offered impressive range, rapid acceleration, and over-the-air software updates that redefined expectations for electric cars.

The Model X, launched in 2015, built on that foundation as a high-performance electric SUV notable for its distinctive falcon-wing doors, spacious interior, and advanced safety features. Both models served as flagships that helped establish Tesla as a leader in the EV industry and popularized long-range battery-electric vehicles.

Production of the Model S and Model X was wound down earlier in 2026, with manufacturing ending in the second quarter. Tesla redirected the Fremont factory space previously used for these vehicles toward higher-priority projects, including Optimus humanoid robots and the Cybercab autonomous vehicle.

By the time of Musk’s open-source announcement, custom orders had closed and only remaining inventory was available.

Open-sourcing the designs and software offers several clear advantages. Owners of these aging but still capable vehicles gain better access to technical documentation, diagnostic tools, and software resources, making independent repairs and modifications easier and more affordable.

Independent repair shops and third-party specialists can support the large existing fleet without relying solely on Tesla’s service network. Enthusiasts and engineers can study real-world implementations of Tesla’s battery, powertrain, and software systems, potentially accelerating broader industry progress in electric mobility.

The step aligns with Tesla’s 2014 patent pledge and its overall mission to advance sustainable transport by sharing hard-won knowledge rather than locking it behind proprietary walls.

By releasing these materials now that the models have left production, Tesla ensures continued support for its early adopters while freeing internal resources for future technologies. The open-source release of the original Roadster already enabled simulations, community projects, and deeper technical understanding.

Extending that practice to the Model S and Model X should deliver similar benefits on a larger scale, helping keep these influential vehicles relevant and repairable for years to come

Continue Reading

News

Tesla flexes incredible Robotaxi metric that skeptics will hate

Published

on

Credit: Tesla

Tesla flexed one incredible Robotaxi metric during the Q2 Earnings Call that skeptics have to hate to hear. The company’s platform has already driven more than 380,000 miles of unsupervised ride-hailing across several states with no notable incidents.

During the company’s Q2 Earnings Call on Wednesday, Vice President of AI, Ashok Elluswamy, said:

“First of all, I’d like to state that the Robotaxi program has been operating extremely well. Especially in terms of safety, the program has had an impeccable safety record. We have driven more than 380,000 miles of unsupervised Robotaxi, now across six cities in two different states. We have had zero notable incidents. Any reports have been of other actors impacting us when we were stationary. I like to emphasize how safe the operation has been so far. Zero notable incidents over 380,000 miles.”

Elluswamy’s claim over Robotaxi miles is a significant milestone for Tesla in the grand scheme, especially considering this is a sizeable number of miles without any incident.

Tesla’s self-driving approach is much different than that of other companies. Tesla has maintained that vision is the only thing needed to have a solid and effective self-driving suite. Many self-driving companies utilize things like LiDAR, sensors, and other elements to improve performance, but Elluswamy sent a jab at those who believe it’s needed.

“Historically, the so-called experts have always claimed that you need LiDARs, radars, HD maps, and the entire kitchen sink to drive safely. Here we show that such is not true. You can have safe, comfortable, and affordable autonomy with just cameras. This record should be a huge validation of Tesla’s entire AI approach.”

The feat of accumulating this many miles without any driver behind the wheel is impressive. The thing is, Tesla is also doing this across several different locations, with varying traffic rules, pedestrian levels, weather patterns, and other important factors.

While Tesla is not ready to roll out an unsupervised platform completely, it is a slow but steady indication that the company is well on its way to figuring things out.

The company’s attitude toward expansion is slow, safe, and controlled, and despite this huge milestone, it will still be some time until we see Tesla truly unleash unsupervised rides more aggressively.

Continue Reading

Elon Musk

SpaceX Starship just nailed something it’s never done before

SpaceX’s Starship flew successfully Friday, landing both stages and deploying its first Starlink V3 satellites.

Published

on

By

Starship’s thirteenth test flight delivered exactly what SpaceX needed with a clean liftoff, two successful stage recoveries, and the first real payload the vehicle has ever carried to space. Booster 20 and Ship 40 lifted off at 5:51 p.m. CT from Starbase, and by the time the mission wrapped roughly an hour later, both halves of the rocket had done exactly what they were supposed to do.

Booster 20 separated from Ship 40 a few minutes into the flight and stuck a controlled splashdown in the Gulf of Mexico about six minutes after liftoff. That is a meaningful turnaround from Flight 12 in May, when the booster lost several engines during its boostback burn before a hard water landing attempt.


Starship 40’s performance was arguably the bigger win. The vehicle deployed the first 20 operational Starlink V3 satellites Starship has ever carried, then flew a suborbital arc to a landing in the Indian Ocean that SpaceX commentator Dan Huot called the company’s softest splashdown yet. “This is a dream scenario for this team that’s trying to get this heat shield data,” Huot said on the live broadcast, according to Space.com’s live coverage. “I’m a little over the moon right now. Wow. Lucky number 13.”

Unlike the mass simulators SpaceX flew on Flight 12, these were production Starlink V3 satellites, meant to extend solar arrays and antennas and attempt to link with the broader constellation before reentering minutes later. Getting real hardware through a full deploy sequence on only the second flight of the V3 generation keeps Starship on schedule for the payload work NASA is counting on for future Artemis lunar landings.

— TESLARATI (@Teslarati) July 25, 2026

The flight also arrives at a moment when SpaceX needed a win. SPCX has traded below its $135 IPO price since mid-July, as Teslarati reported when the mission slipped to Friday, and short interest has climbed to roughly a third of the tradable float. A clean flight will not fix a balance sheet, but it does answer the one question SpaceX absolutely needed answered this week: whether the fixes made after the July 16 abort would hold up under real flight conditions. They did, on both stages, on the first try after the redesign.

SpaceX has not set a target date for Flight 14, though the company has said it wants to push toward an orbital attempt on the next mission. After Friday, that goal looks a lot more within reach.

Continue Reading