5:06 That pullout angle probably wasn’t any more comfortable than the G’s if I had to guess. Really cool seeing how this actually would have played out though! If I might ask, what are the red lines on the “CONT SIT 1” (5:06) supposed to be for?
It has been a while since I looked at the real life displays in the training documents, but I think it was just velocity/altitude upper limits for that situation. I may dig the documents out later.
The top-right plot is Angle of Attack (alpha) vs. Mach. I made it more detailed than the real displays. The red line is the alpha recovery profile in contingency GRTLS, I set it lower than the alpha used in normal GRTLS to make sure the DAP can keep stability during the pullout. Rememeber the Orbiter is much tail-heavier because the OMS dump is still in progress
What happens in the aftermath of this scenario? Navy/AF/Coast Guard/Nat Guard sent out helis and planes? Are they just visually scanning the ocean for the crew or do they have life rafts with GPS or something like that?
They had a SAR HC-130 on station 175nm downrange with rescue team and rafts, and others ready to go at Patrick AFB and the primary TAL sites. Th crew Launch and Entry suit had, in addition to a parachute, a life raft and a radio. GPS isn't mentioned anywhere. Source: Columbia accident report Volume 5 appendix G.2
@@kspencerian Do you know what it was called? I would love to see if I could find some material on it, as I am having trouble picturing how it worked/looked.
What if the orbiter happened across a black zone in the script? I know that in real life, the crew would document everything and try their hardest to save the orbiter and by extension themselves
@giuliodondi So, over the 333kn FCS rated limit but still hypothetically survivable. Interesting! Also, thank you so much for all the hard work on this and your OPS3 program, as well as the quick replies. You've inspired me to research the shuttle so much deeper than before, and boy, is it a beautiful machine (still a death trap, though).
afaik, ditching leads to LOCV (loss of crew and vehicle), so there isn't an abort scenario which results in a successful ditching, as the shuttle would effectively be destroyed/heavily damaged
Prior to the Challenger accident, ditching _was_ the only contingency abort option. Even at the time it was recognized that this wasn't very survivable (something like a 75% chance of survival -- if the shuttle had *no* payload. Adding even a small payload reduced the odds to zero). The general belief (pre-Challenger) was that a contingency abort would never be required, so the low survival chance was acceptable. Post Challenger parachutes were added for the crew and bailout became the only contingency aboey option.
It refers to pressing the Main engine Shutdown buttons on panel C3, on the central pedestal. This is because earlier on there was a failure of a flight-critical data bus (the Flight-forward #2) and so pressing those buttons made sure that the GPCs would be notified of the engine failures
@@willbradley1734 There’s another video on YT with this audio - it was a contingency abort training session before STS-26 that was broadcast on the NASA Select satellite feed way back in the day.
I would’ve guessed blue means “over water” as in the US Navy, “Blue Water Ops” indicates flying your fighter around in an area with no land based divert fields within the aircrafts combat radius, meaning you MUST land back on the carrier as there are no other landing sites available.
According to a NASA document, "blue" was the code for "SRBs still attached." Not good if you really, really need to start on any abort procedure. There's NO abort mode while the SRBs are lit and attached. And with Two Engine Out Blue, you have even less energy with one engine, no way to RTLS and you're about to drop like a stone (even worse than usual) and break up.
the immediate ace combat vibes took me off guard
that bailout escape pole would have been clutch, badass as hell
2:32 - I suspect that the first syllable was clipped. It sounds to me like “(Di-)scovery; I think we have a second engine down.”
I was in tension until the end. Damn.
nightmare stuff right here. good work.
Wake up babe, Gilulio Dondi dropped a new video !
Gotta love this videos
Love these videos, very well done
Great video fascinating, informative and exciting.
Lavoro Eccezionale Giulio!!
5:06 That pullout angle probably wasn’t any more comfortable than the G’s if I had to guess. Really cool seeing how this actually would have played out though! If I might ask, what are the red lines on the “CONT SIT 1” (5:06) supposed to be for?
It has been a while since I looked at the real life displays in the training documents, but I think it was just velocity/altitude upper limits for that situation. I may dig the documents out later.
The top-right plot is Angle of Attack (alpha) vs. Mach. I made it more detailed than the real displays.
The red line is the alpha recovery profile in contingency GRTLS, I set it lower than the alpha used in normal GRTLS to make sure the DAP can keep stability during the pullout. Rememeber the Orbiter is much tail-heavier because the OMS dump is still in progress
So cool and very interesting!
This was interesting good job
Cool, thanks for making this!
Very intense!
Hey I recognize that AC7 444 Briefing music!
What happens in the aftermath of this scenario? Navy/AF/Coast Guard/Nat Guard sent out helis and planes? Are they just visually scanning the ocean for the crew or do they have life rafts with GPS or something like that?
They had a SAR HC-130 on station 175nm downrange with rescue team and rafts, and others ready to go at Patrick AFB and the primary TAL sites.
Th crew Launch and Entry suit had, in addition to a parachute, a life raft and a radio. GPS isn't mentioned anywhere.
Source: Columbia accident report Volume 5 appendix G.2
epic
Man... looks like that jump would have been crazy to do.. i mean.. you dont want to hit the wing😬
That was a very real possibility. So the bailout option had a special pole that steered the bailing astronaut to avoid collision with the wing.
@@kspencerian Do you know what it was called? I would love to see if I could find some material on it, as I am having trouble picturing how it worked/looked.
This is crazy
Is the KoS script able to react to this dynamically? (Like if I use the test lite mod)
Yes it will detect failures and react to basically any situation
What if the orbiter happened across a black zone in the script?
I know that in real life, the crew would document everything and try their hardest to save the orbiter and by extension themselves
Imagine this happened irl
What was the peak EAS during pullout, if you remember? Was wondering how close she came to the 470kn black zone.
In a couple days I'll re-run a simulation and check the logs
OK, I redid the run and it peaked at 384kn in this case.
@giuliodondi So, over the 333kn FCS rated limit but still hypothetically survivable. Interesting!
Also, thank you so much for all the hard work on this and your OPS3 program, as well as the quick replies. You've inspired me to research the shuttle so much deeper than before, and boy, is it a beautiful machine (still a death trap, though).
Will there also be an updated TAL abort video? And other abort options like Abort Once Around
I'll eventually do Droop after single engine OPS3 and low-energy TAL
I know it glides terribly but was there any abort scenario that resulted in ditching rather than bailing out?
afaik, ditching leads to LOCV (loss of crew and vehicle), so there isn't an abort scenario which results in a successful ditching, as the shuttle would effectively be destroyed/heavily damaged
Prior to the Challenger accident, ditching _was_ the only contingency abort option. Even at the time it was recognized that this wasn't very survivable (something like a 75% chance of survival -- if the shuttle had *no* payload. Adding even a small payload reduced the odds to zero). The general belief (pre-Challenger) was that a contingency abort would never be required, so the low survival chance was acceptable.
Post Challenger parachutes were added for the crew and bailout became the only contingency aboey option.
can u send the craft files/ link for it?
coder was here
What do they mean by "we need to push buttons"?
It refers to pressing the Main engine Shutdown buttons on panel C3, on the central pedestal.
This is because earlier on there was a failure of a flight-critical data bus (the Flight-forward #2) and so pressing those buttons made sure that the GPCs would be notified of the engine failures
Where'd you get the audio from?
might be AI
@@willbradley1734 There’s another video on YT with this audio - it was a contingency abort training session before STS-26 that was broadcast on the NASA Select satellite feed way back in the day.
@@dsdy1205No, the audio is from a simulation of STS-26 doing an RTLS and contingency abort
how did you get the audio
What mod shows you the trajectory history in map view?
Principia
What does BLUE mean?
Just a label, doesn't codify anything
I would’ve guessed blue means “over water” as in the US Navy, “Blue Water Ops” indicates flying your fighter around in an area with no land based divert fields within the aircrafts combat radius, meaning you MUST land back on the carrier as there are no other landing sites available.
According to a NASA document, "blue" was the code for "SRBs still attached." Not good if you really, really need to start on any abort procedure. There's NO abort mode while the SRBs are lit and attached. And with Two Engine Out Blue, you have even less energy with one engine, no way to RTLS and you're about to drop like a stone (even worse than usual) and break up.
I always think blue stood for "you're boutta go for a swim in the frosty cold Atlantic Ocean"
Is this based on a real incident?
No, the audio is just a simulation of STS-26
How do you get the ascent interface to be the only thing onscreen?
it's only possible with a hack: hit f2 between the time you run the script and the gui gets rendered
alright, thank you!