STS 93 Ascent Issues "We don't need any more of these" - MCC Loop
ฝัง
- เผยแพร่เมื่อ 20 เม.ย. 2019
- Amazing professionalism as Columbia suffered from issues during her STS-93 launch. This video was exclusively provided to NASASpaceFlight.com
Story behind this here:
waynehale.wordpress.com/2014/... - วิทยาศาสตร์และเทคโนโลยี
"Yikes"
"You bet"
"Concur"
"We don't need any more of these!"
One of my favorite quotes of space flight history.
What about "IT'S THE KABOOM CASE, FLIGHT!"
We don't need any more of these *how 'bout that*
Just read the book by Eileen Collins - she mentioned the
"Yikes"
"You bet"
"Concur"
"We don't need any more of these"
line, and I remembered it from the NSF intro!
10:20 Is my Favorite Moment of the Shuttle Programs Post MECO Sequence.
Absolutely awesome exchange!
When Flight says "YIKES!" then you know you dodged a bullet
Or “lodged” a bullet😬😂😂💣
😂😂😂😂
A gold bullet!
Actually they DIDN'T dodge the bullet--but fortunately, it was only a minor flesh wound!
Wow, it’s amazing how much vital, rapid communication goes on between the flight controllers in the MMC. This could have gone way worse.
Wow! That was intense. Thank you for providing this unique piece of history for us to experience. Best thing I’ve watched in a long time. 👍🏼
they managed these in-flight failures incredibly well and got them into orbit with just a very small (15ft per second) underspeed. LOX ran out at the end causing engine shutdown. Scary stuff all the issues they had that flight.
This was wonderful, Who ever tracked the speaking parties for this, thank you ehem Chris..
It was a fantastic way to follow the flight.
Wasn't this the "Gold Pin" incident, where a cooling line was plugged with a gold shunt, but blew out and into the inside of the booster nozzle creating a leak in coolant/fuel, and almost killed them all....?
Yes it was
Gold shunt in an oxygen injector yes
See 4:31 they do determine the issue where "Main Engines" say a prethrust nozzle leak, so a fuel discharge pressure low, and HPOT "half way" to turbine temps! Of course they didn't know WHY there was a leak of cooling hydrogen in the nozzle at that time which turned out to be the gold pin rupturing 3 nozzle pipes (and remember the engineers who built it determined that if 5 were broken it would cause lack of cooling and a burn through of the engine, and loss of the shuttle).
Yes, plus a whole bunch of other shit too.
I was looked up "yikes, you bet, we don't need any more of these"
Because of the intro and outro of your current streams, but the audio is set to the failure of SN1
How far you've come
Absolutely legendary
Sn10
@@ryanhamstra49 whatever
I was tired I think idk
@@Arae_1 😝 not trying to be that guy….
@@ryanhamstra49 oh I know, I don't mind
An amazing piece of Shuttle/Human Space Flight history. Chandra and the 2 stage IUS weighed in at 50,162 pounds, the heaviest Shuttle payload. Columbia and Chandra/IUS weighed in at 270,142 pounds.
Pretty damn incredible when you have a tank holding over half a million gallons of fuel/oxidizer, are burning it at 1,200 gallons per SECOND, have an unexpected low-level cut-off, and are only 15 ft/sec off target velocity while going 17,000 MPH.
The calculations just completely blow my mind, and even then, this obviously wasn’t a nominal launch. 😳
BUT it wasn't just that potentially catastrophic leak which everyone focuses on (which ME determine is that problem at 4:31 - of course they didn't know what had caused the leak), but also the glitch had caused AC1 shutdown (causing loss of telemetry), Fuel Cell PH warning (which if were true, a fuel cell could potentially explode), two DCs offline (albeit just 1 of the 2 in each of two of the three engines - and not being able to control engine direction would be a disaster), and running out of main propulsion fuel 0.15s before orbit, yes - see at 9:21 how MPS say "LOX low level cut" in the middle of all the MECO statements! Which is explained at 10:10 and the cause of the "Yikes!" statement.
I think we overlook why at 9:56 Collins said "it's good to back in 0g again" - I don't think it was just because she likes to be in space, she certainly could see the fuel cell PH warning light and would know the consequences if that were true, but I think she'd have been able to see warnings on the DCs going out, AC1 offline, as well as the LOX level dropping to zero as they were approaching orbit.
Consider how you worry about your gas gauge getting to zero as you're trying to get to the gas station...
I wonder if she needed to change her diaper after all that!
These tanks were always just about empty at MECO. Usually less than 3000 pounds out of the total of 1.6 million pounds of propellant that the External Tank launched with was remaining at MECO. The tank is dropped before reaching orbit so that it falls towards the Indian/Pacific Oceans.
The pilot probably needed the diaper change, since the engine gages are on his side of the cockpit!
@@EditGuy6610 Shuttles could be flown by both the Commander and the Pilot.
From the POV of the Commander it's more about having a safe place to plan a return from orbit with the delta-v you can use to do it to allow for kinder suborbital mechanics, issues of fuel and engine operation before that make it much scarier. You don't need a lot to do a retro burn, its about attitude, timing and delta-v, it's the getting into the stable orbit in the first place that's important.
0:57 at this point in the launch a tiny gold plug blocking off an injector that wasn't in use shot out and punctured something like 3-4 of the nozzle cooling tubes. (damaged or malfunctioning, standard practice with the shuttle) A couple other minor faults occurred at the same time but the first call out you will here is a woman's voice saying she has an issue with one of the fuel cells. The fuel cells work by burning a small amount of the rockets fuel and oxidizer to generate electricity, the fuel leak and subsequent fuel pressure drop caused a warning for that fuel cell as its own fuel supply pressure also dropped a bit. I believe the safety cutout for those nozzle cooling tubes is 5 tubes punctured would leads to an engine failure/shutdown which at that altitude almost certainly means they will be using one of their "works on paper but never tried" abort scenarios.
The fuel cell issue caused some electrical issues that caused some incorrect readings.
I wonder what they found when that orbiter arrived at the OPF post landing? That most have been some interesting post-flight debriefing.
What they found was that the right engine nearly blew up because three of the cooling lines were breached. The breach happened because an injector post plug came out during main engine start.
@@ethanfairweather8736 The leak was actually noticed during the standard post-launch footage review as it was indicated by a bright white spot on the inside of the right engine nozzle in the footage. And they did get eyes on the three ruptured coolant tubes of the nozzle during the standard post-landing runway inspection of the orbiter, so they knew of the leak long before the OPF roll-in. What they did find in the OPF after the mission was the extensive wire damage that caused the entire fleet to be grounded for repairs for 6 months (July-December 1999), with two missions fighting it out to be the "Return To Flight" mission, those two where STS-103(Discovery to HST) and STS-99(Endeavour on a extensive terrain mapping mission). Eventually it was decided to have STS-103 to be the RTF missions.
Columbia only got a cursory inspection the OPF as she was going to Palmdale for her next Orbiter Major Down Period (OMDP) where it would be easier to do the inspections and repairs without her tieing up an OPF (only 3 available, for 4 orbiters). She would swap places with Atlantis which had just completed her latest OMDP and had returned to KSC to await an open OPF to undergo start of mission processing for STS-101, a space station logistics and outfitting mission ahead of the launch of the Russian Service Module.
@@ethanfairweather8736 It didn't nearly blow up. Didn't come close to that.
That was me driving to work in my old car every day! scary stuff, glad they retired the remaining ones b4 anything else bad happened. (and, yes I have a new car)
Are there any similar recordings/full mission control loops for any other flights?
Small Correction - at 08:25, the "handing over to TDRS" call was made by GC, not INCO. Reason I know is because I work with the guy and would recognize that voice anywhere.
It's never good when the flight director says yikes.
Correct me if I'm wrong but this was the mission post-flight they discovered pinhole leaks around the bottom of the bell, caused by corrosive aspects of the masking tape used to "seal" the bell pligs/covers during processing?
yes
@@hamzahkhan8952 thanks. It's been a while, so details are a bit fuzzy, but I had a feeling...
@@jeffnoe5004 np. kinda suprised you saw my reply considering you poste this over a year ago.
@hamzahkhan8952 I haven't changed my email, so I still get notifications from YT. It's kinda cool because I enjoy getting or giving follow-ups on comments on the more scientific or interesting vids I come across in my travels.
@@jeffnoe5004 thats nice. 👍
10:21 You’re welcome
About as close to a "throw everything at them" Sim that you'll get in a real flight.
1. Short circuit casued by a screw head with a slight burr on it that had been quietly sawing it's way into brittle Kapton wiring on every launch. The jolted of SRB ignition on those dlight finally sealed in deal.
2. Much more serious , a oxidizer injector "post pin" (a brass pin they used to plug worn LOX injectors) came loose at SSME start and hit the insde of the nozzle, rupturing 3-4 H2 coolant pipes in the nozzle. This caused a hydrogen leak which paradoxically caused an over use LOX and caused the early engineering shutdown. The big risk was that the LOX injector was plugged for a reason, had it failed and dumped LOX into the engine, it would have been an instant lose of vehicle and crew situation.
3. An ( erroneous) alert of a failed hydraulic power unit on the RH SRB. This would be very serious (no steering) but was just to loose cable.
If Columbia lost two SSME’s could it perform a TAL abort using the remaining engine and the OMS engines?
It depends when it would lose two engines. If immediately after liftoff, not even RTLS would be possible. It would be single engine blue scenario, which is similar to RTLS in that shuttle is turned around back towards Florida, but it couldn't reach any runway and crew would have to bail out and be recovered by booster recovery ships, vehicle would be lost.
Unless I missed something, the first call after which single engine TAL was possible was "single engine OPS 3", which means shuttle is high enough that in case of a TAL at that point (which would be required if two engines failed), it can use standard reentry software (OPS 3), instead of TAL reentry software (OPS 6).
Failure of a second engine just after the single engine TAL window closed would have resulted in loss of vehicle and crew. This is why in the flight where one engine did fail there was discussion of setting main engine limits (checking) to inhibit (off) and after Flight checked with FIDO and FIDO confirmed outside TAL region the crew were told to set limits to inhibit. A little later the Shuttle became capable of abort AOA (abort once around the planet and land) and the fatal single engine window closes. Aborts TAL, AOA and ATO were the three settings on the cockpit abort mode selector. The specific TAL site to use was loaded and perhaps changed during the ascent, if I remember correctly there was a primary and at least two alternates that NASA sent people to on each flight, selected from around fifty depending on the planned flight trajectory.
James Day, the abort selector has RTLS, ATO, and TAL.
I believe an AOA was performed via OPS 104 for OMS-1 and then OPS302 for a OMS-2 deorbit.
Wonder who the capcom was. Sounds like Charlie Hobaugh during the earlier
The CAPCOM was Columbia's next Commander (STS-109), Scott Altman. FLIGHT was John Shannon.
We don't need any more of these!
Yikes!
You Bet
Concur
We don’t need any more of these
I like how low resolution it is, despite the fact I have it on 720p