Connect with us

News

SpaceX Starship nails ‘flip’ maneuver in explosive landing video

SpaceX has published footage of Starship's first spectacular 'flip' maneuver, showing the rocket's final moments - both good and less so. (SpaceX)

Published

on

Update: SpaceX has published a video taken near the launch pad of Starship nailing an exotic ‘flip’ maneuver shortly before a hard landing destroyed the rocket.

Both the company, test directors, and CEO Elon Musk have all made it abundantly clear that despite the explosive end, Starship SN8’s maiden flight was a spectacular success, proving that the rocket is capable of performing several previously-unproven maneuvers and surviving the associated stresses. Notably, according to tweets posted by Musk not long after, Starship SN8 performed almost perfectly, failing a soft landing (already proven by SN5 and SN6) solely because of low pressure in the rocket’s secondary ‘header’ fuel tank.

Two of SN8’s three Raptors burn to slow the Starship down. (SpaceX)

For unknown reasons, that tank or its associated plumbing were unable to maintain the pressure needed to feed Raptor with enough propellant, resulting in fuel starvation mid-burn. A lack of fuel and surplus of oxygen effectively turned the landing engine into a giant oxygen torch, melting the copper walls of its combustion chamber (hence the green plume). Had the header tank maintained the correct pressure, SN8 would have very likely landed intact (or at least had a much softer landing).

In simpler terms, it seems that Raptor isn’t to blame for Starship SN8’s failed landing and fixing a pressurization problem will be dramatically faster and easier than rectifying a rocket engine design flaw.

SN8’s Raptor plume turns an ominous green as fuel starvation turns the engine into a copper-melting oxygen torch. (SpaceX)

In perhaps the most spectacular aerospace demonstration since Falcon Heavy’s 2018 debut, SpaceX’s first full-size Starship prototype came within a hair’s breadth of sticking the landing after an otherwise successful ~12.5 km (7.8 mi) launch debut.

To quote SpaceX’s test director, heard live on the company’s official webcast moments after Starship serial number 8 (SN8) exploded on impact, “Incredible work, team!” For most, praise shortly after a rocket explosion could easily feel nonsensical, but in the context of SpaceX’s iterative approach to development, a Starship prototype failing just moments before the end of a multi-minute test can be considered a spectacular success.

Chock full of surprises, Starship SN8 ignited its three Raptor engines for the third time and lifted off at 4:45 pm CST (UTC-6) on the program’s high-altitude launch debut.

Starship’s first multi-engine liftoff. (Richard Angle)

About 100 seconds after liftoff, already representing the longest-known ignition of one – let alone three – Raptor engines, one of those three engines appeared to shut down, causing the two remaining engines to gimbal wildly in an effort to retain control. Another two minutes after that, one of those Raptors also shut down, leaving one engine active. That one engine continued to burn for another minute and a half, producing just enough thrust to more or less maintain Starship SN8’s altitude at apogee while performing a bizarre horizontal slide maneuver.

Liftoff. (Richard Angle)
Two engines burning. (Richard Angle)
One engine burning. (Richard Angle)

Finally, at a bit less than five minutes after liftoff, Starship cut off all Raptor engines and began falling back to earth. Looking spectacularly similar to fan-made renders and CGI videos of the highly-anticipated ‘skydiver’ or ‘belly-flop’ maneuver, Starship – belly down – spent around two minutes in a rock-solid freefall, using four large flaps to maintain stability.

Freefall, near apogee. (Richard Angle)
Moments before an aggressive flip maneuver. (Richard Angle)
Fully sideways, SN8 ignites one Raptor to kick into a 90-degree flip maneuver. (Richard Angle)

Around 4:52 pm, Starship SN8 performed exactly as expected, igniting one – and then two – Raptor engines while fully parallel to the ground to complete an aggressive 90-degree flip, transitioning into vertical flight for an attempted landing. Unfortunately, although it’s difficult to judge what was intentional and what was not, things began to go wrong after that point -visible in the form of one of the two reignited Raptors flashing green before shutting down.

At the same time, the plume of the lone remaining engine flashed an electric green, quite literally consuming its copper-rich internals in an unsuccessful attempt to slow Starship down. According to SpaceX CEO Elon Musk, Raptor performed “great” throughout the launch and landing attempt, with the bright-green plume likely explained by extremely oxygen-rich combustion caused by low “fuel header tank pressure.”

Advertisement
-
The green flash of death. (Richard Angle)
?
RIP SN8. (Richard Angle)
The wreckage of Starship SN8. As SpaceX succinctly notes, SN9 is up next!

Regardless of the specific cause, Starship SN8 smashed into the ground around 10-20 seconds early, traveling about 30 m/s (~70 mph) too fast. To be clear, in SpaceX’s eyes, the test – primarily focused on demonstrating multi-engine ascent, freefall stability, header tank handover, engine reignition, and a flip-over maneuver – was a spectacular success, completing almost every single objective and seemingly doing so without any major issues.

Clocking in at an incredible (and unexpected) ~400 seconds (~6.5 minutes) from liftoff to explosion, it’s difficult to exaggerate the sheer quantity of invaluable data SpaceX has likely gathered from SN8’s sacrifice. Thanks to SN8’s primarily successful debut, SpaceX’s Starship test and launch facilities (minus the rocket’s remains on the landing zone) appear to be almost completely unharmed, likely requiring only minor repairs and refurbishment. Further, Starship SN9 is effectively complete and patiently waiting a few miles down the road, ready to roll to the launch pad almost as soon as SpaceX has understood the cause of SN8’s hard landing.

Stay tuned for more analysis, photos, and videos as the dust settles.

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