Connect with us

News

SpaceX Starship prototype in limbo after engine test lights rocket on fire

Published

on

The fate of SpaceX’s fourth full-scale Starship prototype appears to be in limbo after a third (seemingly successful) engine ignition test unintentionally caught the rocket on fire.

Now more than 12 hours after Starship SN4 fired up its new Raptor engine, the ~30m (~100 ft) tall, 9m (~30 ft) wide prototype is apparently trapped with one or both of its propellant tanks still partially filled with liquid (or gaseous) methane and/or oxygen. An initial road closure scheduled from noon to 6pm local quickly came and went and SpaceX and Cameron County Texas have since modified the paperwork, extending the closure a full 24 hours. In other words, SpaceX has reason to believe that Starship SN4 may continue to be unsafe (i.e. pressurized) as many as ~30 hours after it technically completed its third static fire test – extremely unusual, to say the least.

There’s only one obvious conclusion to draw. Whether it was something invisible to the public eye or damage related to the off-nominal fire that burned for some 15 minutes after Raptor shut down, SpaceX appears – to some extent – to have lost control of Starship SN4.

At the moment, it’s unclear what is wrong and what SpaceX is attempting to do to resolve the problem. Based on photos of Starship SN4 taken before the fire, there is good news and bad news from what can be publicly ascertained. Controlled from the ground by unprotected wires strung up and down the rocket and connected at its base, the uncontrolled fire that burned in at least two locations around Starship’s aft may have severed some or all of those critical connections.

Advertisement
Starship SN4’s third successful Raptor test caused a secondary fire that has put the vehicle in a state of limbo. (LabPadre)

That would render Starship – potentially perfectly healthy and operational – almost entirely uncontrollable, while also potentially removing SpaceX’s access to telemetry. In other words, the company may currently have no idea how pressurized all or part of Starship SN4 is and may also have little to no control of some or all of the rocket. For that to be true, Starship SN4 would, however, have to have less than fully redundant control hardware. To perform hops, for example, the ship would need both wired and radio links capable of sending telemetry and receiving commands to remain both on the ground and after liftoff.

It’s possible that Starship SN4 has the necessary hardware installed but that it wasn’t activated for the static fire test (think “Starship will never leave the ground, why would we need to enable wireless controls?”). It’s also possible that the blown pipe and methane leak that appeared to cause the secondary fire damaged crucial propellant management hardware (valves, pumps, etc.) or was just a symptom of an even worse overpressure event that damaged or destroyed multiple such systems.

Given that safety is almost certainly the priority, chances are that some combination of fairly mild hardware failure and telemetry/control loss has left SpaceX with just enough uncertainty that it can’t risk sending technicians to the launch site to inspect the damage and reestablish control. As a result, the only option left is to quite literally sit and wait until it’s once again safe to approach the rocket. Thankfully, at this point, the risk of the mystery problem actually destroying Starship SN4 is very low. If, as it appears, only its methane tank is affected, leaving some unknown quantity of latent liquid methane trapped inside, it’s possible that waiting will actually solve the problem and safe the rocket.

Starship SN4 is pictured a few hours before its ill-fated third static fire test. (NASASpaceflight – bocachicagal)
On a positive note, it appears that the concerning amount of dark smoke created in the first minute or two of the post-test fire was caused by a huge amount of tape/insulation/???? wrapped around part of Starship’s test stand in the hours before its May 19th test attempt.(NASASpaceflight – bocachicagal)

The fact that Starship hasn’t exploded yet strongly implies either that the amount of propellant trapped is minuscule or that the vast majority of SN4’s propellant management systems (including vents) remain functional. Assuming that’s the case, any remaining cryogenic propellant will eventually boil into gas, increasing the pressure inside Starship’s tanks, while those tanks will continue to vent to prevent an explosion or rupture. Eventually, Starship SN4 will be empty once again and SpaceX will be able to approach the rocket to regain control and begin inspections and repairs.

Regardless, after such an unintentionally eventful static fire test, it’s extremely unlikely that SN4 will be ready for its inaugural flight test within the next few days. Stay tuned for updates as SpaceX works to regain control over the fourth full-scale Starship prototype.

Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.

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

Investor's Corner

Lucid denies rumors of bankruptcy after over 40% stock drop

Published

on

Credit: Lucid

Electric vehicle maker Lucid Group has denied rumors of an imminent bankruptcy after a report from this morning sent the stock on a dramatic drop on Wall Street, seeing losses of more than 40 percent during trading hours.

Lucid’s Director of Communications, Nick Twork, responded to the report from Eletric-Vehicles.com, which stated the company’s restructuring advisor, AlixPartners, was asked to review two decisions: taking Lucid shares private or filing for Chapter 11 bankruptcy protection.

The report also claims AlixPartners told the Lucid board to “concentrate on Gravity production while improving its quality, and to temporarily hold back the Lucid Air, the sedan that has defined the company since its launch.”

Twork said:

Shares rebounded after the response to the report, halving its losses as the trading day neared 3 p.m. Eastern.

Lucid has struggled to get its sales off the ground and into more respectable numbers, but the company is in its early years, when things are hard to begin with. It is also backed by several notable investors, including the Saudi Public Investment Fund (PIF), which has nearly limitless money and likely would not ditch an investment of this size so soon.

Lucid shares were down just 14 percent at the time of publication, a far cry from the 55 percent its losses topped out at during the day.

Continue Reading

News

Tesla owner attempts resale of Model S Signature Edition for over $260k

Published

on

Credit: Tesla

A Tesla owner who purchased a Model S Signature Edition, one of the final 250 units of the all-electric flagship vehicle that the company discontinued earlier this year, is attempting to sell the car despite a no-resale clause that prohibits reselling for the first year.

The car is being sold by J&S Autohaus in Ewing, New Jersey, and is priced at $260,490, well above the $159,420 that Tesla sold it for earlier this year.

To those who do not know, the Model S Signature was a highly exclusive, limited-run farewell variant of the Model S Plaid that was produced this year to mark the end of production of both the Model S and Model X, Tesla’s two flagship vehicles.

Limited to just 250 units with invite-only sales, it serves as a collector’s item celebrating the legacy of the Model S, which helped pioneer Tesla’s electric vehicle success since its 2012 launch.

It bundles top-tier performance with bespoke cosmetic and luxury upgrades, plus Tesla’s Luxe Package. Here’s what the Model S Signature has over the typical Model S Plaid:

  • Exclusive Exterior – Unique Garnet Red Paint, matching door handles, gold Tesla “T” badges upfront, gold Plaid and Signature badging at the rear.
  • Premium Interior – White Alcantara upholstery with gold piping/accents, gold Plaid seat badges, Signature-marked door sills, individually numbered dashboard plaque, gold puddle lights, special interior lighting sequence, and a custom Signature key fob.
  • Performance Upgrades – Carbon-ceramic brakes with gold calipers
  • Bundled Luxe Package – Full Self-Driving (Supervised), four years of Premium Connectivity, free lifetime Supercharging
  • Performance Metrics – ~1,020 horsepower, sub-2-second 0-60 MPH, ~390-mile range

Tesla quickly introduced a No Resale Agreement for the Signature Editions of the Model S and Model X, which would penalize the seller for “the amount of $50,000 or the value received as consideration for the sale or transfer, whichever is greater.”

The company continues:

“If you sell or otherwise transfer the ownership of your Model S or Model X, the remainder of the Recommended Maintenance, Wheel and Tire Protection Plan, and Windshield Protection Plan will transfer automatically to the buyer. The Full Self-Driving (Supervised), Free Supercharging and Premium Connectivity will not transfer with the vehicle and will terminate once the ownership of the Model S or Model X is transferred.”

Tesla will likely come after the seller, especially as it has been about two months since Tesla launched deliveries.

Continue Reading

News

Tesla Full Self-Driving v14.3.5 Early Impressions: new features and early performance

Published

on

Credit: TESLARATI

Tesla rolled out Full Self-Driving (Supervised) v14.3.5 yesterday, and about fifty miles of driving on the new version has given me enough time to highlight what seems to be strong about the release and what is not.

Additionally, Tesla has added a few new features with this specific update, which we’ll highlight as well.

Tesla Full Self-Driving v14.3.5 Performance

The new update is business as usual. Things seem to be running completely normal and necessary, but there are a few things that we’ve seemed to pick up on based on our own experience with v14.3.5, as well as what other users are seeing.

Initially, it seems to be more aware of its surroundings, making moves that are incredibly courteous to other drives and operating just a tad more reserved than what the suite might have done previously.

We had two instances where it showed this, the first being FSD needing to pass a Flagger Force vehicle that was placing down signage for the day. Their work truck was right at the front corner of a right-hand turn; typically where most cars travel when they take that turn.

FSD v14.3.5 recognized this, slowed down, and took the turn wide with no issues:

Additionally, v14.3.5 backed up for a semi truck that was making a wide turn onto a road my car was on. This is not new, but it seemed to be backing up for courtesy; it didn’t seem completely necessary, but it might have put some peace of mind in the truck driver’s head:

X user Mike P, also a Pennsylvania native like myself, shared three clips of his Tesla running v14.3.5 performing similar maneuvers. He said:

“FSD turns right into a small alley that only fits one car at a time, sees oncoming car, reverses out of alley to make space, realizes oncoming car is actually parking, re-enters alley.”
Check it out here:

It seems like Speed Profiles are still in need of some tweaking; I am adjusting what Speed Profile I’m in frequently, constantly changing it to get it to travel at the correct speed. This was an issue for me on v14.3.4. It seems like they’re just a little inconsistent.

Terrible Parking

Parking attempts on v14.3.5 were not good. There are quite a few people who have said this:

David Moss, the Tesla owner who has taken multiple coast-to-coast drives without any interventions, also has had some issues with parking early on with v14.3.5:

New Features

Tesla has added the ability to open Camera Preview at any time. Previously, it was only available in Park. Here’s what that feature looks like in action:

Check back later this week for a longer review of what we’ve noticed on Full Self-Driving v14.3.5.

Continue Reading