On 30/05/2024 11:17 Snidely <[email protected]> wrote:

Starliner is again at SLC-41 ahead of crewed launch, L0 currently June
1st 12:25 pm EDT.

/dps

--
Killing a mouse was hardly a Nobel Prize-worthy exercise, and Lawrence
went apopleptic when he learned a lousy rodent had peed away all his
precious heavy water.
_The Disappearing Spoon_, Sam Kean

AFAIK the Crew Dragon docked at the ISS isn't suitable for a rescue mission since it's not modified to perform an EVA. Only the Crew Dragon capsule being used for the Polaris Dawn mission is fitted (or being fitted) for EVA.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 30/05/2024 18:35 Snidely <[email protected]> wrote:

The Running Man scribbled something on Thursday the 5/30/2024:

On 30/05/2024 11:17 Snidely <[email protected]> wrote:

Starliner is again at SLC-41 ahead of crewed launch, L0 currently June
1st 12:25 pm EDT.

/dps

--
Killing a mouse was hardly a Nobel Prize-worthy exercise, and Lawrence
went apopleptic when he learned a lousy rodent had peed away all his
precious heavy water.
_The Disappearing Spoon_, Sam Kean

AFAIK the Crew Dragon docked at the ISS isn't suitable for a rescue mission >> since it's not modified to perform an EVA. Only the Crew Dragon capsule being
used for the Polaris Dawn mission is fitted (or being fitted) for EVA.

Why are you talking about rescue missions? Starliner's heat shield is intact.

/dps

--
potstickers, Japanese gyoza, Chinese dumplings, let's do it

Because they said there's about a 0.75% chance that the helium leak could result in a failure to initiate the retro-burn.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2024-06-01 10:57 a.m., Snidely wrote:

Thursday, Snidely quipped:

Starliner is again at SLC-41 ahead of crewed launch, L0 currently June
1st 12:25 pm EDT.

Working around GSE issues with LOX topping.  L-01:29:01, and still
within the built-in hold.

Scrubbed. Darn.


Alain Fournier

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 01/06/2024 13:26 Alain Fournier <[email protected]> wrote:

On 2024-06-01 10:57 a.m., Snidely wrote:

Thursday, Snidely quipped:

Starliner is again at SLC-41 ahead of crewed launch, L0 currently June
1st 12:25 pm EDT.

Working around GSE issues with LOX topping.? L-01:29:01, and still
within the built-in hold.

Scrubbed. Darn.

Alain Fournier

One of the three redundant computers failed to start up properly (took too long to start up). They want to investigate before giving the go.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 02/06/2024 14:20 Snidely <[email protected]> wrote:

After serious thinking Alain Fournier wrote :

On 2024-06-01 10:57 a.m., Snidely wrote:

Thursday, Snidely quipped:

Starliner is again at SLC-41 ahead of crewed launch, L0 currently June 1st >>>> 12:25 pm EDT.

Working around GSE issues with LOX topping. L-01:29:01, and still within >>> the built-in hold.

Scrubbed. Darn.


Alain Fournier

Ground-based sequencer computer didn't sequence?

/dps

--
Rule #0: Don't be on fire.
In case of fire, exit the building before tweeting about it.
(Sighting reported by Adam F)

<https://www.theregister.com/2024/06/03/boeing_starliner_launch_scrubbed/>

Turned out to be a redundant power supply of the ground sequencer computer that needs to be replaced. Not anything major. They should be back on the pad within a few days.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 02/06/2024 14:22 Snidely <[email protected]> wrote:

On Friday or thereabouts, The Running Man declared ...

On 30/05/2024 18:35 Snidely <[email protected]> wrote:

The Running Man scribbled something on Thursday the 5/30/2024:

On 30/05/2024 11:17 Snidely <[email protected]> wrote:

Starliner is again at SLC-41 ahead of crewed launch, L0 currently June >>>>> 1st 12:25 pm EDT.

/dps

--
Killing a mouse was hardly a Nobel Prize-worthy exercise, and Lawrence >>>>> went apopleptic when he learned a lousy rodent had peed away all his >>>>> precious heavy water.
_The Disappearing Spoon_, Sam Kean

AFAIK the Crew Dragon docked at the ISS isn't suitable for a rescue mission
since it's not modified to perform an EVA. Only the Crew Dragon capsule >>>> being used for the Polaris Dawn mission is fitted (or being fitted) for >>>> EVA.

Why are you talking about rescue missions? Starliner's heat shield is
intact.

/dps

--
potstickers, Japanese gyoza, Chinese dumplings, let's do it

Because they said there's about a 0.75% chance that the helium leak could
result in a failure to initiate the retro-burn.

Was that 0.75% before or after the new backup backup procedure was implemented (using 4 RCS thrusters twice)?

/dps

--
Who, me? And what lacuna?

Here's your answer:

"As it turned out, there was something to be concerned about. The review turned up what he called a ?design vulnerability? with Starliner?s propulsion system that had not been recognized. Starliner?s service module has four areas called ?doghouses?
spaced 90 degrees apart that host both larger Orbital Maneuvering and Attitude Control (OMAC) thrusters and smaller reaction control system (RCS) thrusters. If two adjacent doghouses failed for some reason, though, it would prevent the spacecraft from
doing a deorbit burn even though the spacecraft is designed with multiple ways to carry out the deorbit burn using combinations of OMAC and RCS thrusters."

<https://www.thespacereview.com/article/4805/1>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)