Connect with us

News

SpaceX breaks Starship test record, rolls next booster to launch pad

Published

on

SpaceX has completed a record-breaking test of a Starship booster and rolled a newer Super Heavy prototype to the launch pad just hours apart.

Almost six weeks after SpaceX began Super Heavy Booster 7’s static fire test campaign, the company has broken new ground by simultaneously igniting seven Raptor engines at once. A matter of hours later, confirming SpaceX CEO Elon Musk’s plans in real time, the company transported a second Super Heavy prototype (Booster 8) from the factory to the launch pad, where it joined Booster 7.

According to Musk, those rockets will soon switch places, ensuring that no time is wasted while SpaceX continues to gradually work towards Starship’s first orbital launch attempts.

Booster 7 kicked off the most important stage of its flight qualification process on August 9th and 11th with two back-to-back static fires, each igniting just one of 20 installed Raptor engines. Both appeared to be successful and SpaceX returned B7 to its Boca Chica, Texas factory, reinstalled a full set of 33 engines, and sent the Super Heavy back to the launch pad two weeks later.

On August 31st, SpaceX attempted to ignite three of Booster 7’s 33 Raptors. One engine failed to ignite but the others did not, resulting in a mostly successful two-engine test. Over the next two weeks, SpaceX performed several ignition-free ‘spin-prime’ tests, two of which appeared to spin up all 33 engines without causing an explosion. Finally, SpaceX telegraphed its next major goal with a seven-engine spin-prime test on September 16th and another (albeit with a slightly different set of engines) on September 19th.

Shortly after the second seven-engine spin-prime, SpaceX refilled Booster 7 with propellant, went back through the same procedures, and ignited the same seven engines for about five seconds. No obvious issues arose and Musk later implied that the test went well. It set a new record for the largest number of Raptors simultaneously ignited on a single prototype and likely also broke the record for most thrust produced by a vehicle tested at Starbase.

Advertisement
-

If all seven upgraded Raptor V2 engines were operating at full throttle, they could have briefly produced more than 1600 tons (~3.6M lbf) of thrust – roughly equivalent to two Falcon 9 boosters. Measuring about 69 meters (~225 ft) tall and 9 meters (~30 ft) wide, Super Heavy will be the most powerful liquid rocket booster ever tested once it ignites as few as 20 of its 33 engines at full thrust.

In an increasingly rare update, Musk revealed that SpaceX will once again return Booster 7 to Starbase’s factory for mysterious “robustness upgrades” after the latest round of testing. Musk doesn’t seem to think that those upgrades will take very long, and anticipates that Starbase’s “next big test” will be the first complete wet dress rehearsal of a fully-assembled two-stage Starship, followed by Super Heavy’s first 33-engine static fire test, “in a few weeks.”

More likely than not, each step of that process will take multiple attempts and uncover issues that will then need to be corrected and verified over the course of several months. But with Starship 24 having already completed a full six-engine static fire, there’s a small chance SpaceX will find itself with a fully-stacked Starship that is more or less ready for its first orbital launch attempt by the end of October.

In the meantime, after Booster 7 returns to the factory, Booster 8 – finally complete after a relatively slow six-month assembly – will kick off basic proof testing at SpaceX’s South Texas orbital launch site. SpaceX wasted no time preparing for that swap and transported Booster 8 to the pad just seven hours after Booster 7’s seven-engine static fire. If things move more smoothly than they did with B7, it’s possible that B8 will complete proof testing and be ready to head back to the factory for Raptor installation by the time B7’s upgrades are finished – a very efficient transition if it works out that way.

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

Verizon, AT&T and T-Mobile are trying to shut Starlink out before FCC vote

AT&T, Verizon and T-Mobile want 290 MHz cut from an FCC satellite plan before Thursday.

Published

on

By

Starlink D2D direct to device vs Verizon, AT&T (Concept render by Grok)

AT&T, Verizon and T-Mobile are asking the Federal Communications Commission to pull nearly 300 MHz of spectrum out of a proposal that would let satellite companies like SpaceX offer cell service directly to ordinary phones. The request lands one day before the agency votes on it.

The FCC will vote Thursday, October 29, on a notice of proposed rulemaking that would make an additional 482 MHz available for direct to device service, expanding the number of eligible bands from five to 13, according to the FCC fact sheet. It would also scrap the rule requiring a satellite operator to lease spectrum from carriers, replacing it with a certification that the operator has coexistence agreements in place or holds the terrestrial license itself.

That second path matters for SpaceX. As Teslarati reported earlier this month, SpaceX agreed to buy Grain Management’s nationwide 800 MHz portfolio to turn Starlink Mobile into a full US carrier, adding to the spectrum it already bought from EchoStar.

The carriers want two bands removed, 2.5 GHz and 3.45 GHz, which make up 290 MHz of the 482 MHz on the table. Through industry group CTIA, they argued that about 300 million users depend on those bands and that satellite operations in them are not technically feasible. T-Mobile, which calls 2.5 GHz the foundation of its Ultra Capacity 5G network, said in its own filing that satellite interference could wipe out up to 96% of a cell site’s uplink coverage area and cut uplink speeds by 88% to 99%.

Executives from all three carriers met with FCC staff on October 20, and T-Mobile CEO Srini Gopalan met separately with FCC Chairman Brendan Carr. T-Mobile’s role stands out because it is still SpaceX’s US launch partner for Starlink Mobile. The three carriers have also teamed up on their own satellite joint venture to pool spectrum, a move widely seen as a response to Starlink.

Advertisement
-

SpaceX is asking for the opposite. In an October 23 filing after meetings with FCC staff and commissioners’ offices, the company asked regulators to add the 902 to 928 MHz band to the proposal. “Doing so now saves time later,” SpaceX wrote. The company also asked the FCC to modernize interference rules and align satellite deployment requirements with those for terrestrial cell networks, saying the goal is to let satellite and ground networks work together so Americans stay connected wherever they are.

The carriers have not been shy about how they view SpaceX as a competitor. On Verizon’s third quarter earnings call Monday, its chief executive said Starlink Mobile “just can’t compete with a terrestrial network” and estimated SpaceX would need four to six years and $300 billion to $500 billion to build a full US carrier network.

Thursday’s vote will not settle which bands survive. Adopting the notice opens a public comment period, with final rules to come later in the proceeding. The FCC already considered and rejected 2.5 GHz for satellite coverage once, in 2024. SpaceX also is not the only satellite player watching: the FCC approved Amazon’s $11.6 billion acquisition of Globalstar on October 27, giving its planned direct to device fleet its own mobile satellite spectrum.

Continue Reading

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