ptfrd

joined 6 months ago
[–] ptfrd@sh.itjust.works 1 points 2 days ago

as far as I’m aware, they’ve done 1 EVA to look at the thing

Don't think so.

They do have access to camera imagery, but as you say, most problems like this probably need much more intrusive investigation.

[–] ptfrd@sh.itjust.works 2 points 3 days ago (1 children)

How could I forget!

TBH, I mean that in the sense that you can't forget something you never knew about in the first place ;)

I had never heard of this concept before. Is it something to do with this?

[–] ptfrd@sh.itjust.works 13 points 3 days ago

Departure will be televised.

(I looked it up because I was vaguely wondering whether broadcasting this would be too embarrassing!)

[–] ptfrd@sh.itjust.works 2 points 3 days ago

If the Boe-CFT mission had gone to plan, Crew-9 would have been scheduled to launch in mid August with Zena Cardman commanding. The article reports that she has just announced that her father died in August, perhaps about a week before what would have been the launch date.

Got me wondering how situations like that are handled. And what if a close family member dies just a day or two before launch? Or even less time than that?

On a related matter, I've also been wondering at what point the backup crews are 'stood down'. I don't think it's the very last minute. I think there's a window of time during which any serious issues to do with a member of a primary crew would just result in a scheduled launch not going ahead (as opposed to going ahead on schedule but with a crew member swapped out).

[–] ptfrd@sh.itjust.works 2 points 5 days ago

Damn, they should've collab'ed with the Marshall Mathers Space Flight Center, like I been sayin

(I sent two letters back in autumn, JAXA must not've got 'em. There prob'ly was a problem at the post office or somethin)

[–] ptfrd@sh.itjust.works 2 points 5 days ago (3 children)

Plus the occasional ULA sniper wielding the SpaceXpelliarmus spell.

[–] ptfrd@sh.itjust.works 3 points 5 days ago (1 children)

A landing leg failure, for example, likely could be quickly cleared because it is not used in other phases of flight

I assume SpaceX wouldn't make any big assumptions along these lines though?

I imagine, for example, that a worn component that could fail catastrophically on landing might also be at risk of some kind of failure during max Q, in a way that affects the primary mission.

Of course, there could come a point where you judge that so unlikely as to be not worth wasting any (further) time on.

But as an armchair observer I'm fairly glad to see a pause at this point before Polaris Dawn, even just a couple of days ...

“We’re just focused on recovery weather at this point,” he said after the announcement of the FAA investigation into the booster landing anomaly. “I think that is still gate to our launch.”

Surprising. Does this mean they have good reason to think they'll get a Public Safety Determination in a matter of days? Does the FAA work weekends?

P.S. If a landing leg realistically could, say, pop open at max Q, I guess that further strengthens the argument in favour of rocket 'catchings' rather than rocket landings!

[–] ptfrd@sh.itjust.works 3 points 1 week ago

the company will likely need to redesign some elements in the spacecraft's propulsion system to remedy the problems

I expect they'll make a change to whatever is responsible for the helium leaks. But as for keeping the thrusters healthy, Steve Stich keeps talking about software/operational changes as a way to accomplish that, so we might not see much of a redesign (at least in the short/medium term).

Had the Starliner test flight ended as expected, with its crew inside, NASA targeted no earlier than August 2025 for Boeing to launch the first of its six operational crew rotation missions to the space station. In light of Saturday's decision, there's a high probability Starliner won't fly with astronauts again until at least 2026.

Wasn't it actually February 2025? With the delay to August 2025 only announced very recently, as a result of all these CFT problems?

And that might be all the extra time Boeing needs. Especially considering my previous point.

originally planned for an eight-day stay at the station

Well, yes, as a bare minimum.

the owners of a private space station will almost certainly go with the less expensive, flight-proven vehicle to transport people to and from orbit.

Will it be their decision, when the people being transported are NASA astronauts? I could easily see NASA wanting to continue their 'dissimilar redundancy' policy indefinitely.

[–] ptfrd@sh.itjust.works 5 points 1 week ago

Me too. I had thought we were talking about a 1% chance or something like that.

But at the press conference, one of the journalists seemed to be asking about the probability of disaster, and gave 10% as an example. None of the NASA people took the opportunity to say "no that's far too high", or "I'm very confident the uncrewed return of Starliner will be successful", or anything like that.

[–] ptfrd@sh.itjust.works 2 points 1 week ago* (last edited 1 week ago) (2 children)

I've been wondering why there's such a big gap between Starliner's expected departure ("early September") and the launch of Crew-9 (no earlier than 2024-09-24).

My least bad guess is that NASA doesn't see much difference in the risk of having Butch & Suni return as (little more than) cargo inside Crew-8's Dragon capsule, and the risk of them returning in the actual standard/proper crew configuration in this Starliner capsule. In which case they might as well get Starliner back ASAP, while making no attempt to bring the Crew-9 date forward (which could have been doable given that the plan as of last month was to be ready by 2024-08-18).

Has anyone got a better guess?

I do know that a standard Starliner departure involves waiting for a suitable opportunity / time window. But there must be suitable opportunities much closer to the 24th, right? Why aren't they waiting for the last possible (or maybe penultimate) opportunity? In the unlikely event of Starliner failing to undock or whatever, it'd be no big deal to delay Crew-9 again, so I don't think that would be the reason.

I had been imagining a much greater level of dependency or 'coupling' between the two events. Perhaps with NASA looking at the Crew-9 launch weather forecasts before deciding whether to undock Starliner about 3 days earlier, or something. Or even (less seriously), the Crew-9 crew strapped into their Dragon, on the launchpad, and hearing on their comms system something like "Starliner has successfully exited the ISS's Keep Out Sphere, so NASA is 'go' for propellant load on Falcon 9".

I was hoping somebody would ask this question during the press conference, but they didn't.

[–] ptfrd@sh.itjust.works 1 points 1 week ago

the host says they’re going to higher altitudes than the Apollo program

Ah, yes, well normally that would be my opportunity to remind people of Gell-Mann amnesia.

But this time it’s unfair to the host. Isaacman has made that mistake himself on (I think) multiple occasions. She might have got it from him. (Perhaps indirectly.) Here’s one: https://youtu.be/aASZ2rKdS6I?t=1m2s (He meant “since”, not “than”.)

One source of confusion might be if this crew is planning to be in the highest 'free' orbit of Earth ever occupied by humans. Where I'm using 'free' as a vague way of trying to exclude, for example, the astronauts who were actually on the moon (which is of course orbiting the Earth).

Is that a scientifically/technically legitimate & meaningful distinction? If so, is there a better term for it?

 

A Youtuber called Ellie in Space claims that a NASA source sent her the following message. It was in response to a question about when NASA knew that the Boe-CFT mission's Starliner vehicle would not be able to undock and return to Earth autonomously without being reconfigured.

So if you want to know when??? Well always, but it wasn't a reasonable consideration to retain the unmanned Starliner capsule software to work in the manned version of the capsule as a contingency. Would you call that a mistake?? Maybe, but let's think about the need to really ever plan to send folks up to space and leave them there with no way to fly home... they would always chose to risk the ride vs having no way home.

No one really considered this very unique and dynamic situation would happen.

Background

I believe this issue was first brought to light by Eric Berger.

Regardless, sources described the process to update the software on Starliner as "non-trivial" and "significant," and that it could take up to four weeks. This is what is driving the delay to launch Crew 9 later next month.

A couple of days later, NASA held a press teleconference in which they emphasized that what was needed was merely a "data load", not a software change. But they indicated timelines that do seem consistent with the "up to four weeks" claim by Berger's source.

My questions

Aren't there several realistic scenarios where you'd want to undock a crew vehicle, without its crew (or at least without them being in a fit state to operate the vehicle), in less than 4 weeeks?

Can Crew Dragon do it? Soyuz?

 

Relevant portion of the video is 18:06 - 22:22.

Key quote: "We'll move a Dragon recovery vessel to the Pacific some time next year, and we'll use SpaceX facilities in the Port of Long Beach for initial post-flight processing".

Although this was revealed in a Crew-9 briefing, it doesn't actually apply to Crew-9.

The announcement has just now been posted to the SpaceX website.

Key excerpts:

During Dragon’s first 21 missions, the trunk remained attached to the vehicle’s pressurized section until after the deorbit burn was completed. Shortly before the spacecraft began reentering the atmosphere, the trunk was jettisoned to ensure it safely splashed down in unpopulated areas in the Pacific Ocean.

After seven years of successful recovery operations on the U.S. West Coast, Dragon recovery operations moved to the East Coast in 2019, enabling teams to unpack and deliver critical cargo to NASA teams in Florida more efficiently and transport crews more quickly to Kennedy Space Center. Additionally, the proximity of the new splashdown locations to SpaceX’s Dragon processing facility at Cape Canaveral Space Force Base in Florida allowed SpaceX teams to recover and refurbish Dragon spacecraft at a faster rate [...]

This shift required SpaceX to develop what has become our current Dragon recovery operations, first implemented during the Demo-1 and CRS-21 missions. Today, Dragon’s trunk is jettisoned prior to the vehicle’s deorbit burn while still in orbit, passively reentering and breaking up in the Earth’s atmosphere in the days to months that follow. [...]

When developing Dragon’s current reentry operations, SpaceX and NASA engineering teams used industry-standard models to understand the trunk’s breakup characteristics. These models predicted that the trunk would fully burn up due to the high temperatures created by air resistance during high-speed reentries into Earth’s atmosphere, leaving no debris. The results of these models was a determining factor in our decision to passively deorbit the trunk and enable Dragon splashdowns off the coast of Florida.

In 2022, however, trunk debris from NASA’s Crew-1 mission to the International Space Station was discovered in Australia, indicating the industry models were not fully accurate with regards to large, composite structures such as Dragon’s trunk. [...]

After careful review and consideration of all potential solutions – coupled with the new knowledge about the standard industry models and that Dragon trunks do not fully burn-up during reentry – SpaceX teams concluded the most effective path forward is to return to West Coast recovery operations.

To accomplish this, SpaceX will implement a software change that will have Dragon execute its deorbit burn before jettisoning the trunk, similar to our first 21 Dragon recoveries. Moving trunk separation after the deorbit burn places the trunk on a known reentry trajectory, with the trunk safely splashing down uprange of the Dragon spacecraft off the coast of California.

 

That's 27 hours from now.

SpaceX is targeting Saturday, July 27 for a Falcon 9 launch of 23 Starlink satellites to low-Earth orbit from Launch Complex 39A (LC-39A) at NASA’s Kennedy Space Center in Florida. Liftoff is targeted for 12:21 a.m. ET, with backup opportunities available until 4:21 a.m. ET.

And here is their blogpost, dated 2024-07-25, announcing that the mishap report has been submitted to the FAA, and discussing some of the details.

During the first burn of Falcon 9’s second stage engine, a liquid oxygen leak developed within the insulation around the upper stage engine. The cause of the leak was identified as a crack in a sense line for a pressure sensor attached to the vehicle’s oxygen system. This line cracked due to fatigue caused by high loading from engine vibration and looseness in the clamp that normally constrains the line.

38
submitted 1 month ago* (last edited 1 month ago) by ptfrd@sh.itjust.works to c/spacex@sh.itjust.works
 

During tonight’s Falcon 9 launch of Starlink from Space Launch Complex 4 East at Vandenberg Space Force Base in California, the second stage engine did not complete its second burn. As a result, the Starlink satellites were deployed into a lower than intended orbit. SpaceX has made contact with five of the satellites so far and is attempting to have them raise orbit using their ion thrusters.

There's also a tweet saying the same thing in fewer words.

This is the affected mission: Starlink 9-3 launch bulletin

Let's hope it was due to SpaceX pushing the envelope on their in-house Starlink missions in some way, though I have no specific guesses along those lines. Perhaps a manufacturing defect or an operational mistake are more likely to be the leading candidates for the cause.

 

Quote from Bill Nelson:

... SpaceX, by having the return of the first stage, has brought the cost down significantly. That has affected the entire launch industry. We'll be seeing attempts at bringing the second stage down on some missions.

The key sentence is (currently) 52 minutes and 48 seconds into the video. Approximately 49 minutes after the event started.

No other mention is made of this. Should we assume he's specifically referring to the 2nd Stage of the Falcon 9? What is the likelihood that he is mistaken? Could he just be thinking of the existing deorbit procedure? Or could SpaceX be putting parachutes on some of their 2nd Stages in the near future?

view more: next ›