Connect with us

News

SpaceX gears up for Crew Dragon’s first recovery with a giant inflatable cushion

Published

on

Paired with observations and comments from sources familiar with the company, all signs seem to indicate that SpaceX is planning to recover their first Crew Dragon spacecraft with a giant inflatable cushion, to be towed a hundred or so miles off the coast of California by one of the company’s Port of LA-stationed recovery vessels.

Despite a minor mishap during some sort of inaugural sea-trial of a custom Crew Dragon mass simulator, SpaceX technicians are pushing ahead with a test campaign intended properly characterize exactly how to best recover a Dragon while side-stepping around the problems caused by seawater immersion.

Why recover your Dragon?

First off, why would SpaceX choose to develop a new method of Dragon recovery – different than the company’s current experience with simply landing the capsules in the ocean – with the expectation that it will debut during the recovery of Crew Dragon after its very first demonstration mission (DM-1)? A huge number of unknowns and major questions remain, but the decision to attempt to avoid seawater immersion during the DM-1 Dragon recovery is very likely no coincidence.

Over the last several years, SpaceX engineers and technicians have learned a huge amount from recovering, refurbishing, and even reusing Cargo Dragons to resupply the International Space Station for NASA. Of all the lessons learned, the most unequivocal has to be a newfound appreciation for just how difficult it is to safely and reliably reuse spacecraft and rocket components after landing and being immersed in seawater. Despite SpaceX’s growing experience with reusing both Falcon 9 and Cargo Dragon, Dragons still typically require a bare minimum of 6-12 months of refurbishment before they are ready for another launch.

For Crew Dragon’s DM-1 debut, it thus makes sense that SpaceX wants to recover the spacecraft in such a way that it is exceptionally easy to rapidly refurbish. Perhaps just several months after that capsule returns to Earth, currently expected no earlier than December 2018, SpaceX’s first crewed Crew Dragon demonstration’s tentative April 2019 launch debut will depend entirely on the completion and review of an In-Flight Abort (IFA) test planned just one month prior, March 2019.

Advertisement
-
-

The planned IFA test of Crew Dragon hinges entirely on DM-1 and Dragon refurbishment because the present plan (and launch schedule) absolutely depends on reflying DM-1’s Crew Dragon capsule, potentially recovered from orbit as few as three months prior.

Crew Dragon completed a successful pad-abort test in 2015. (SpaceX)

With a successful 2015 Pad Abort already under Crew Dragon’s belt, SpaceX voluntarily chose to conduct an additional complimentary in-flight abort not explicitly required by NASA, designed to demonstrate that Dragon will be able to safely extract astronauts from a failing rocket at the point of peak aerodynamic pressure (Max-Q). Essentially, a combination of successful aborts both on the launch pad and during Max-Q would theoretically demonstrate beyond any reasonable doubt that Crew Dragon really is capable of safely aborting a launch and protecting its astronauts at any point during launch.

Cargo Dragon has demonstrated that – apparently – no amount of heroics can refurbish the recovered spacecraft in just a small handful of months after seawater immersion, not without major changes to its design. As such, preventing that with some sort of inflatable cushion (or even Mr Steven’s net) would likely save many months of drying, cleaning, and requalification testing of all externally impacted components.

How to recover your Dragon

While the “why” is fairly obvious at this point, the “how” of actually making such a cushioned recovery happen is far less clear. Still, we at least know from several recent comments from SpaceX CEO Elon Musk and statements made in environmental impact analyses that the company has been considering such recoveries for some time.

Despite the fact that Crew Dragon’s original propulsive landing capability was nixed due to the unlikelihood of NASA ever certifying it for crewed landings and the expense required to attempt that certification, there is still clearly some latent interest (and value) in precisely landing Crew Dragon, even if only to speed up capsule and crew recovery after splashdown. A March 2018 preliminary environmental impact analysis of Gulf of Mexico Dragon recoveries – as a backup to bad weather in the Pacific and Atlantic – made the interest in precision exceptionally clear.

“The splashdown zone is a circle with a radius of approximately 5.4 nautical miles. … Dragon has been designed to perform precision landings in order to minimize the size of the splashdown zone and recovery time.”

Admittedly, a circle with a diameter of 10.8 nautical miles (20 km) does not exactly scream “precision” and ~20 km is likely around a thousand times less precise than what’s needed to land on the 30m-diameter inflatable structure present at Berth 240, but it’s probable that the splashdown zone as discussed is a worst-case scenario meant to give SpaceX’s recovery team plenty of wiggle room.

 

Advertisement
-
-

Musk also took a few seconds of a Falcon Heavy post-launch press conference to briefly describe Mr Steven, and he just so happened to touch on fairing and Dragon recovery:

“And we’ve got a special boat to catch the fairing. … It’s like a giant catcher’s mitt in boat form. I think we might be able to do the same thing with Dragon. So…if NASA wants us to, we can try to catch Dragon. Literally, it’s meant for the fairing, but it would work for Dragon, too.” – Elon Musk

Mr Steven takes one for the team

Even more experimental than fairing recovery, SpaceX happened to experience a minor incident while attempting to test aspects of its prototype Dragon catcher apparatus in early August. Partially captured by Teslarati photographer Pauline Acalin, SpaceX technicians were lifting a Crew Dragon heatshield mass simulator with a healthy topping of buoys onto Mr Steven. Moments after it was lowered onto the deck, the whole setup disappeared below the vessel’s side rails in a massive boom.

 

According to sources familiar with SpaceX’s recovery fleet, the mishap was much less severe than the deafening noise it produced seemed to indicate from the sidelines. They described the aftermath as “an annoying accident” that was unlikely to take any significant amount of time to repair. More likely than not, Mr Steven’s wooden deck suffered some level of structural degradation after several years of active use, something that SpaceX technicians only discovered after loading (or maybe dropping) a heavy Dragon mass simulator aboard.

Regardless, one could certainly say that the test in question was more or less a success, as it most certainly demonstrated whether Mr Steven’s deck was actually capable of supporting the heavy test article (it was not). A few repairs and structural reinforcements later, the vessel is likely already back in working order, with photos taken on August 19th showing that the focus has returned to the vessel’s arms (two of which must have been removed earlier this week).

Mr Steven sans two arms, August 19th. (Pauline Acalin)

For prompt updates, on-the-ground perspectives, and unique glimpses of SpaceX’s rocket recovery fleet check out our brand new LaunchPad and LandingZone newsletters!

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 Full Self-Driving v14.3.7 early review: FSD saved me from an accident

Published

on

Credit: Teslarati

Tesla released Full Self-Driving version 14.3.7 yesterday, and after about 90 miles of testing today, it is evident there are some definite fixes from version 14.3.6, which I wrote about last week and called a regression.

Within the first 40 minutes of my drive on v14.3.7, it saved me from getting into an accident with an unaware Dodge Charger driver, and some of the things Tesla seemed to miss in v14.3.6 were definitely improved. All in all, the release so far has some really great performance, and I’m looking forward to testing it further.

For now, here’s everything I noticed with v14.3.7:

Overall Improvement

Just generally speaking from a ride perspective, this was a really great experience. A lot of the hesitancy I experienced on v14.3.6 was gone. There were no instances of brake-stabbing, wheel-jerking, or any uncertain or unconfident movements. It was void of anything that I felt made it timid with v14.3.6.

The one thing I do hope to see down the road is a smaller need to adjust Speed Profiles so often. Because Tesla calls FSD “Supervised,” I’m okay with needing to hit the scroll wheel a few times a drive.

However, I hope that things can be incrementally improved upon with speed. Sometimes it’s too fast; other times it’s too slow. It’s a difficult thing to hone in and refine, but I hope it eventually gets there.

I didn’t notice any significant left lane camping or any behaviors that were completely out of line. I am hopeful that this opinion does not change, but after driving a few days with this version and putting it in a variety of different situations, you are exposed to more behaviors, some of which are not necessarily what I’d prefer.

Advertisement
-
-

The big things to notice, at least in my experience thus far, are that the major issues with previous versions — meaning the braking stabbing and wheel jerking — simply weren’t there. That’s enough to already consider this progress compared to .6.

Manual Signal Override is More Responsive

On .6, I had quite a few issues with FSD ignoring my manually input turn signals. If Tesla wants to call it “Supervised,” then the car should not ignore any input the driver gives. If I touch the accelerator on FSD, the car speeds up.

The car did a great job of obeying my turn signals when I wanted it to change lanes, which is welcome.

Parking Lot Performance

Before .6, I traditionally took over in nearly every parking lot my car entered, because I knew it would not park somewhere that I wanted, and usually, it was just a tad too timid in this setting.

The one bright spot of .6 was how well it handled parking lots. This continued with v14.3.7:

Advertisement
-
-

 

I’m always really happy to see progress at all, but once parking preferences come to FSD, as long as this performance is still around, that could potentially be the biggest improvement I’ve seen in FSD in the year I’ve been using it personally on a daily basis.

Full Self-Driving Averts Disaster

A Dodge Charger changed into my lane without checking if I was there, running me off the road. FSD made the initial avoidance maneuver; I grabbed the wheel out of instinct, looked in my side mirror to ensure I had nobody following closely behind, hit the brake, and straightened the car back up to avoid a curb:

Advertisement
-
-

There have been quite a few responses to this video stating that I should never have grabbed the wheel. To be honest, I really wish I had not done so, because I do believe FSD would have avoided any sort of collision with anything, including the car or the curb.

However, this was the first time I had ever been this close to being hit while using FSD. My natural reaction was to take over. I think if I had had something like this happen before, my reaction might have been different.

Hitting the brake avoided hitting the curb, while FSD swerved to avoid the car. My concern after the car was clear of my front end was the curb. All in all, I’m really happy with how things turned out, and I think anyone could be a critic of how I handled it. I only had a split second to really make a decision, and thankfully, any damage was avoided.

It is clear FSD managed to avoid the car coming down before I was able to. I truly credit FSD for avoiding the collision.

What Needs to Improve

Better Recognition of Potholes, Uneven Roads, Sharp Changes in Roadway/Bumps

On Friday, my Fianceè and I were in the car, and FSD was driving us. We crossed over a roadway that has a traffic light, and FSD was traveling at 40 MPH on Standard, 5 MPH over the speed limit. Everything was more than reasonable.

However, the road we were crossing at the light has a major bump both as you start and finish crossing it. Without a speed reduction, your car can go airborne. The Tesla did just this on Friday on v14.3.6; it was an uncomfortable bounce that pretty much confirmed I would not ever let FSD go over again unless we were sitting at that intersection when there is a red light.

I even tried scrolling down into Sloth quickly, but I ended up just taking over:

Advertisement
-
-

A few people have said it remains related to the vision-based approach and its difficulty comprehending 3D. This is a huge issue because this can cause serious damage at certain speeds.

Navigation

Nothing new here. I still turn off “Online Routing” quite frequently to get the car to take logical routes from time to time.

Auto Wipers

Auto Wipers are just plain bad. I really hope Tesla just uses a rain sensor. I thought they had improved at one point, but I still get dry wipes, Speed 4 on a drizzle, and Speed 2 on a steady rain. In reality, these should be switched.

You can watch our full review of Tesla Full Self-Driving v14.3.7 below:

Advertisement
-
-

Continue Reading

Elon Musk

SpaceX’s biggest test yet arrives this week and it’s not a rocket launch

Published

on

By

SpaceX will report second quarter results after the market closes on Tuesday, August 4, marking the first time the company has opened its books to the public since its record IPO in June. Management will host a live audio only webcast at 4:30 p.m. ET, streamed on X, with no dial in option.

The debut carries more weight than a typical first quarter as a public company. Two trading days after the release, on August 6, the first tranche of SpaceX’s lockup expires, freeing roughly 911.5 million insider and employee shares, worth well over $100 billion at current prices and the largest such release in Wall Street history. A second, larger tranche tied to the stock trading 30 percent above its $135 IPO price never triggered, since shares have spent most of July trading below that price.

Wall Street’s models point to revenue near $6.9 billion for the quarter, up sharply from the $4.69 billion SpaceX reported in the first quarter, with a narrower per share loss than the $1.27 posted three months earlier, according to estimates compiled by Motley Fool. Those numbers will be the first look at how SpaceX’s three segments, Starlink, launch and AI, are performing independently.

SpaceX scores another massive Pentagon deal to support military satellites

Investors heading into the call have a specific list of questions. How many net new Starlink subscribers did SpaceX add after ending March with 10.3 million, and is average revenue per user holding up as the service expands into lower income markets. How much of the AI segment’s revenue reflects contract signings with Anthropic, Google and Reflection AI this year, deals that combined could annualize to nearly $28 billion if fully ramped. Whether capital expenditures, which nearly doubled in the AI segment alone between 2024 and 2025, are still accelerating or starting to plateau. And whether management offers any forward guidance at all, something SpaceX has never done publicly.

The report will also land days after Elon Musk publicly denied a Wall Street Journal report describing internal planning to separate Tesla’s China business ahead of a potential Tesla-SpaceX merger. Whether Musk or SpaceX executives address that speculation on the call, even indirectly, maybe something investors will be listening for on Tuesday.

As Teslarati reported after Musk’s own warning to short sellers last week, the CEO has made clear he expects skeptics to be proven wrong over time. Tuesday will be the first chance for the numbers themselves to make that case.

Advertisement
-
-
Continue Reading

Elon Musk

SpaceX’s Starship just got filmed by its own cargo

SpaceX released new footage of Starship in space captured by the Starlink satellites it deployed.

Published

on

By

SpaceX released a new video Friday evening showing Starship from an angle showcased by its own Starlink satellites, watching the rocket drift away in orbit.

The 65 second clip, posted on X, stitches together footage from four cameras mounted on a single Starlink V3 satellite. It opens with a close view of Starship’s 171 foot upper stage, still catching sunlight, then pulls back as the two spacecraft separate.

The footage comes from Starship’s 13th flight test, which launched July 24 from Starbase after a scrubbed attempt and an abort caused by an engine issue the week before. When Flight 13 finally flew, it carried the first batch of functional Starlink V3 satellites Starship has ever deployed, twenty of them, with six equipped with cameras meant to scan the ship’s heat shield during reentry.

Flight 13 checked most of its boxes. Starship deployed all 20 satellites, relit a Raptor engine in space, and splashed down softly in the Indian Ocean off Western Australia. Musk’s longer term plan calls for a Starlink V3 constellation of 100,000 satellites, according to a recent FCC filing, with Starship as the only vehicle capable of launching them at the volume that requires. Each Starship flight is designed to carry up to 60 V3 satellites once the vehicle reaches routine service, well beyond what Falcon 9 can carry in a single mission.

Advertisement
-
-

Starship is next expected to fly with an attempt at catching the ship itself with the launch tower’s mechanical arms, a maneuver SpaceX has so far reserved for the Super Heavy booster.

Continue Reading