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.6 review: a rare regression, but some bright spots

Published

on

Credit: Tesla

Tesla released Full Self-Driving version 14.3.6 last week, and after what was potentially one of the best FSD releases in v14.3.5, there has been a bit of a regression. While there are some bright spots, the changes made to v14.3.6 seem to have backtracked some behaviors.

Overall, it is hard to really complain about FSD in any sense; it has revolutionized how I travel literally anywhere. According to my self-driving app, the last time I went a day without using it was 59 days ago.

However, I think it’s also important to recognize when things are just plain bad with FSD. There are times it does truly mind-boggling things, and I’ll dive into those here. Additionally, I only had these issues on local roads, not on highways. Highway operation, generally, is always incredible other than the occasional complaint about speed or left lane camping.

With those things being said, my personal experience may not represent others’ experiences. A handful of people have said they have had a similar experience on v14.3.6, while others have said it is more than normal.

Turning Hesitancy, Inaccuracy

I’ve noticed more inaccuracy turning into multi-lane stretches of road than in any version I can remember. I’ve had at least three instances of FSD turning into a stretch of roadway that has two or more lanes, and not selecting a lane confidently as it has in past versions.

Instead, the car will drive over one of the dashed road lines, and the steering wheel will jerk back and forth before picking the lane. It should be said that it has always picked the correct lane when choosing based on the navigation, but it is still very indecisive. The steering wheel jerking is reminiscent of some of the later versions of v13.

I admit I really hate to see the steering wheel jerking come back. However, I think when Tesla releases v14.3.7, it won’t be present. When there are occurrences of it in FSD versions, it is usually resolved by the following release.

FSD Disregards Manual Turn Signals

This is my biggest bone to pick with FSD other than Navigation issues, but this one seems like it would be such an easy fix.

If Tesla is going to put the word “Supervised” on the end of “Full Self-Driving,” then when I tell the car to do something, it should do it. If I input an increase in speed by pressing the accelerator, the car will immediately respond. It does not disregard my input because it feels it is traveling at the right speed.

FSD should never disobey and turn off turn signals that the driver inputs. Trying to direct the car into the correct lane, I had initiated the left turn signal not once, not twice, but three times, with the car turning it off all three times and continuing in a lane that would end in just one block. The only solution at this point would be to zipper merge.

This goes back to the fact that self-driving’s biggest bottleneck might be rider preference. A zipper merge might have been more than reasonable, might have saved me time that I spent sitting through an additional light cycle, and might be something many drivers would do. I was in no hurry, I traditionally do not try to zipper merge because it feels inconsiderate, and lastly, the car should have just followed my input.

Advertisement
-
-

This caused me to disengage and drive manually the rest of the way home. Sometimes I just do not need FSD to try to pass every car it can at intersections.

Bird Braking is a Thing of the Past

The big complaint with recent versions of Full Self-Driving has been what we’ve coined as “bird braking,” which is when the car will brake suddenly as a bird flies past.

There have been zero issues with this so far in v14.3.6, which is an excellent improvement.

FSD Might Already Be Taking Note of Driver Preferences

Another thing I have noticed over the past few days is that v14.3.6 seems to already be taking my preferences with navigation into account.

This is something that is supposed to be rolling out with the Summer Update, but I have a hunch it’s already present and might have been included in this v14.3.6 build. On Friday, FSD pulled into an entrance to a local convenience store that it had never attempted to go into before.

Typically, I manually pull into this entrance because it avoids heavy cross traffic at the main entrance. FSD has always chosen that congested main entrance.

Additionally, FSD has pulled into my assigned parking spot at my townhouse community on multiple occasions with this release. This is something that used to happen ocassionally, but not consistently.

It also navigated back to the same convenience store last night, drove through crazy cars scrambling to gas pumps, navigated out of the parking lot correctly, drove me home, and, once again, parked in my assigned spot.

As previously stated, this release just seems to have a few things that need to be brought to Tesla’s attention, and also to make others who use FSD aware of some things that I’ve experienced. I look forward to the next release that will remedy these issues, just as Tesla has always done in the past.

Advertisement
-
-
Continue Reading

Elon Musk

Musk’s massive Terafab project will get final location soon

Published

on

Credit: SpaceX

Elon Musk’s massive Terafab project, which will be the first true conglomeration between each of his major entities, is set to get its final location soon, the CEO said on Tesla’s recent earnings call.

“The Terafab, we expect to announce a location soon, and provide more details about our plans in that regard. We’ll leave that to the product, the launch announcement rather than try to squeeze it into an earnings call,” Musk said last Wednesday.

Tesla Terafab set for launch: Inside the $20B AI chip factory that will reshape the auto industry

Terafab was announced by Musk back in March and was essentially a massive, vertically integrated semiconductor manufacturing project that would provide all the chips the three companies needed for their AI initiatives without needing third-party companies.

The plant will produce over 1 terawatt of AI compute each year, and will help back up projects like Optimus, Full Self-Driving, and other AI-based projects that Musk’s companies are working on.

In April, less than a month after the project was launched, Intel announced it would join the project, contributing manufacturing expertise and consulting to Terafab as a whole. Intel is one of three chip manufacturers that produce sub-5 nanometer chips at scale. TSMC and Samsung are the other two.

However, there was no true indication of where Terafab would end up, but most believe it will likely be somewhere in Texas. Business Insider has reported that SpaceX plans to build out Terafab in Grimes County, Texas, but this is unconfirmed.

Advertisement
-
-

Musk confirmed recently that it would not be on Giga Texas property, as it is simply too large.

Terafab holds much of Musk’s grand ambitions for the future within its construct. It holds so much responsibility for the future and the biggest projects that Musk’s companies can imagine.

Advertisement
-
-

“I think this is a very big announcement and it deserves to have its own day in the spotlight and not be squeezed into an earnings call,” he said. “I do think Terafab is going to be an amazing initiative and a necessary one, and one without which we will be constrained in our ability to scale Optimus production, because we simply won’t have enough AI chips.”

He continued by stating that Terafab is necessary for scaling Optimus, which Musk said could be the biggest product of any kind of all time. “It’s crucial to solve that, and we’ll have to solve memory, logic, and packaging in order to scale Optimus.”

Continue Reading

News

Elon Musk reveals SpaceX performed secret Starship test on Flight 13

Published

on

Credit: SpaceX

SpaceX performed a secret test on a specific portion of Starship with its recent 13th test flight last week, CEO Elon Musk revealed.

Starship’s 13th test flight took place last Friday, and in many aspects, it was one of the most overwhelmingly successful launches in the project’s history.

All of the mission objectives were met without incident, both the Super Heavy Booster and Ship managed to perform safe splashdowns in the Gulf of America and the Indian Ocean, respectively, and the deployment of Starlink satellites came and went without any complications.

However, there was more on the agenda for SpaceX with Flight 13. Musk revealed an internal test of the ship’s heat shield tiles, as the space exploration company wanted to push them to the limits after previous issues.

Many noticed that Starship’s initial launch seemed to be more accelerated than normal, and that was not a mistake. Musk revealed that SpaceX decided to give Flight 13 an intentionally aggressive acceleration rate in an effort to test how well the tiles would remain attached to the ship:

Advertisement
-
-

SpaceX had issues with some of the heat shield tiles remaining attached early on in the Starship program. The first six test flights presented some kind of anomaly with them, so the company’s big focus with them was to figure out a way to keep them intact through the duration of the flight.

Things truly improved as Flight 10 showed that ceramic tiles generally stayed attached to the ship far better due to refined attachment, as SpaceX utilized pins instead of adhesives. Flights 10 through 13 truly showed some clear progress with the heat shield tiles, and this latest test seems to be where some real progress was noticed, especially by Musk.

The 13th Starship launch last Friday was the second with Starship V3, SpaceX’s latest and greatest iteration of the spacecraft. Goals and ambitions are getting even grander as the project continues to progress. Musk has already hinted that SpaceX will likely try to catch Starship with Flight 14.

Advertisement
-
-
Continue Reading