Connect with us

News

SpaceX schedules second Starship static fire after first test ends prematurely

On January 6th, SpaceX fired up Starship SN9's three Raptor engines for the first time. (NASASpaceflight - bocachicagal)

Published

on

Update: SpaceX appears to have plans for a second triple-Raptor static fire for Starship SN9 after the rocket’s first test was cut short for unknown reasons.

Identical to previous road closure windows, SpaceX will have an opportunity to test Starship SN9 from 8 am to 5 pm CST (UTC-6) on Friday, January 8th, potentially paving the way for a high-altitude launch attempt early next week if the second static fire goes as planned. Stay tuned for updates!

In what is likely one of the last steps before SpaceX’s next high-altitude Starship launch attempt, the company appeared to successfully put Starship serial number 9 (SN9) through its first triple-Raptor static fire test.

Relatively late into a test window that opened at 8 am CST (UTC-6) but was later pushed to noon, SpaceX’s first Starship SN9 static fire attempt began in earnest around 3:15 pm CST. Signified by venting activity at the propellant farm tasked with preparing and loading liquid oxygen and methane on Starships, slight tweaks in the test flow were observed but the static fire occurred more or less when expected at 4:07 pm.

SN9 ignited all three of its Raptors in quick succession and shut the engines down over the course of 1.5-2 seconds – extremely short relative to all previous nominal Starhopper or Starship-mounted Raptor static fires. Long-time followers immediately noted that small discrepancy, speculating that it could either have been a post-ignition abort or intentionally shortened to avoid damaging the pad’s concrete surface (an incident that’s occurred several times during recent tests).

Not long before the short static fire, SpaceX extended the end of its January 6th test window (in the form of road closure notices) from 5 pm to 8 pm. Oddly, rather than the expected response of detanking Starship and reopening the road after a successful test, SpaceX essentially recycled SN9 and began a separate test around 6 pm. The road was never reopened and a SpaceX team never headed back to the pad between the tests, implying that the company may have run into a minor hardware or software bug earlier in the day.

Advertisement
-

It’s unclear what the actual goal of the second attempt was and it’s more or less impossible to know for sure with confirmation from CEO Elon Musk. It’s possible – if unlikely – that the first static fire went exactly as planned and the follow-up test was meant to be a simple data-gathering wet dress rehearsal (WDR). Either way, after a surprise downpour briefly engulfed Starship SN9 minutes prior, the second test appeared to abort about 30 minutes into propellant conditioning and loading, precluding both a complete WDR and/or static fire.

Starship SN9 is pictured preparing for its first static fire attempt on January 3rd. (NASASpaceflight – bocachicagal)

According to a test notice received on January 6th by NASASpaceflight contributer and photographer Mary (bocachicagal), SpaceX has another test window available on January 7th in the event that Wednesday’s testing was partially unsuccessful. In a rare case, SpaceX’s hand-distributed warning for residents preceded any additional planned road closures, the last of which lifted on January 6th.

On January 5th, SpaceX received a trio of Temporary Flight Restrictions (TFRs) from the FAA that will allow the company to restrict access to nearby airspace for high-altitude Starship launch attempts on January 8th, 9th, and 10th. Lacking an unequivocally successful static fire, it’s highly unlikely – but not impossible – that Starship will be ready for a launch attempt during any of those three windows. Still, it’s safe to say that SN9 is probably less than a week away from its first flight – expected to be a carbon copy of SN8’s 12.5 km (7.8 mi) launch and landing attempt – if SpaceX can complete a full-duration static fire in the next day or two.

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 Semi catches fire in California: what we know

Published

on

Credit: KTVU

A Tesla Semi caught fire in Hayward, California, which caused both directions of traffic to shut down for hours before being completely reopened early on Wednesday, the California Highway Patrol said.

The fire occurred just after 5:30 local time in Hayward on Tuesday, as the Semi caught fire in the southbound lanes of I-880 before CHP officials made the decision to shut down both lanes of traffic due to potential risks from hazardous chemical smoke.

There were no injuries reported.

The cause of the fire is currently unknown, as neither Tesla nor the CHP have not determined a cause.

However, some images taken before the Semi was completely destroyed by the fire seem to indicate this might have been an older unit, as it appears to be one of the designs that Tesla shipped as part of its pilot program, before revising it and starting mass production just a month ago.

At the time of publication, CHP had not returned our request for a comment for additional details, including the Semi involved and any potential collaboration on an investigation between the CHP and Tesla. We will update this story when we hear back from them.

The southbound lanes were reopened at 3:30 a.m. on Wednesday, with the northbound lanes opening last night a few hours after the fire began. The CHP did state that the lithium batteries were “incredibly difficult to extinguish,” according to NBC Bay Area.

The truck’s driver said that the Semi caught fire, but he did not have an explanation.

An estimated 5,000 to 7,000 semi-truck and large commercial vehicle fires occur on U.S. roadways every year.

Continue Reading

News

Tesla’s ‘Emergency Drive Away’ function gets its first use in the real world

Published

on

Credit: Tesla

Tesla’s launch of the “Emergency Drive Away” function a few months back offered owners a safe option to evacuate an area if they were in reasonable danger. The function finally got its first use in the real world, but it appears it was by mistake.

A video shared by u/Joshalander in the r/TeslaLounge subreddit recorded the instance from his vehicle and said the incident took place in Austin this past weekend during the city’s F1 Race.

“Was charging around 6 AM this past Sunday in Austin before heading to the F1 race and heard a pop. Looked over and saw the new emergency drive-away feature in action. Genuinely felt bad for the dude when he got out and realized what happened, since he looked exhausted and only seemed to half-read the prompts.”

Emergency Drive Away unlatches the Supercharger connector from the vehicle, but still causes damage to both the car and the Supercharger. Tesla has said that it will cost up to $25,000 in repairs to have everything fixed back to normal.

Additionally, the company said that if it were not used in an emergency situation, the driver of the vehicle who activated the Emergency Drive Away feature would be responsible for all repair costs.

Tesla constitutes the following situations as reasonable justifications for activating the feature:

  • You face an immediate threat to your life or personal safety.
  • You must leave the area immediately.
  • Exiting the vehicle is unsafe.
  • Unplugging the charge connector would unreasonably delay your departure or expose you to a risk to your personal safety.

After using the feature, Tesla requires the driver to schedule Service so the car can be inspected.

Continue Reading

News

Tesla’s Cybercab battery design could make robotaxis even cheaper

Tesla built the Cybercab’s battery pack with spare room for a future switch to LFP.

Published

on

By

Tesla built the Cybercab’s battery pack with empty space inside it on purpose, and the reason points to a cheaper robotaxi down the road.

Robert Sumpf, Tesla’s director of mechanical design engineering for battery modules and packs, said the extra room beside and beneath the Cybercab’s modules was left there so the company can move to lithium iron phosphate cells later. “So, we protected this pack to go to an even lower energy dense chemistry as we scale and need to bring LFP into the platform,” Sumpf said in a Cybercab deep dive with Munro Live.

The Cybercab runs on Tesla’s own 4680 cells with a nickel chemistry today. LFP cells store less energy for their size, so a straight swap would cut range. The reserved space lets Tesla add more LFP cells to make up the difference. In return, Tesla would get cells that cost less, run cooler and survive more charge cycles. LFP became the most used EV battery chemistry in the world last year.

Not all of that room was planned for a chemistry change. Lars Moravy, Tesla’s Vice President of Vehicle Engineering, said part of it exists because “we didn’t need as many batteries as we thought we did.” Tesla told Sandy Munro in early 2025 that it was targeting a Cybercab pack under 50 kWh with close to 300 miles of range.

The pack also breaks from the structural design Tesla used in some Model Y and Cybertruck builds. Instead of potting hundreds of cells into one block, the Cybercab uses four separate, individually sealed modules, so a bad module can be replaced without scrapping the whole pack. Sumpf was blunt about the older approach, giving the Model Y structural battery “a grade D” because it was hard to build and nearly impossible to repair. He estimated a fully structural pack gains about 10% more cell volume, but said “the issue is the service cost.”

Advertisement
-

That cost matters more for a car that rarely sits parked. Cybercab chief engineer Eric Earley said replacing an entire pack “before half a million miles is a killer on cost,” which is why remanufacturing and serviceability were built into the design from the start.

The same Munro Live tour produced Moravy’s admission that the Cybercab line at Giga Texas is now outpacing Robotaxi deployments, along with a look at the robotaxi’s unorthodox paint process. Tesla is aiming to deliver the first Cybercabs to outside customers by the end of 2026, though Elon Musk has said the vast majority will stay owned by Tesla and run as a transport service.

Sumpf did not give a date for an LFP version, name a cell supplier or say how a chemistry change would affect range. For now, the 4680 cars keep piling up: Texas DMV records from Tuesday list 544 Cybercabs authorized for Tesla’s Robotaxi fleet, more than the 507 Model Ys on the same roster for the first time.

Continue Reading