OK, all flight controllers, I'm going around the horn
Retro? Go
FIDO? Go
Guidance? Go
Control? Go
TELCOM? Go
GNC? Go
EECOM? Go
Surgeon? Go
Are there any recorded instances of a No-Go?
$\begingroup$
$\endgroup$
2
-
6$\begingroup$ Does it have to be Kranz? $\endgroup$– Organic MarbleCommented Aug 22, 2019 at 11:34
-
1$\begingroup$ @OrganicMarble Ha, good point! Have updated my question. $\endgroup$– John TopleyCommented Aug 22, 2019 at 12:20
Add a comment
|
3 Answers
$\begingroup$
$\endgroup$
14
One thing to note is that these polls of the room are largely for-the-record - in other words, if a flight controller was sitting on a problem that would prevent the accomplishment of a major milestone, and didn't tell Flight about it until the poll, that flight controller would not be in MCC for their next shift.
That said, and apologies because it's anecdotal, I've heard it at least once on the loops myself.
During the first attempt to launch STS-088, when Ascent/Entry Flight Director John Shannon polled for a go for launch, Weather (the controller position) was "no-go, forecast no-go" (meaning that current conditions were outside of flight rules, and were not forecast to improve by the launch time)1. Despite this, Flight reported to the Launch Director at KSC that Houston was go for launch. The Weather guy couldn't believe what he was hearing and requested clarification from Flight on the loops, and was shot down.
That was a weird launch attempt for several reasons and I'm kinda glad it got scrubbed. The next day everyone was on their A game and it went off fine.
1This wasn't news to Flight, it had been reported to him previously.
I don't think Weather being no-go for launch is particularly novel; this just happens to be one that I was there for.
answered Aug 22, 2019 at 13:02
-
13$\begingroup$ I agree, in my experience listening to these polls if there is ever an issue they will say something along the lines of "Hold Hold Hold" and then the issue. For me, majority of the time it's weather. Even tho we call it a Go/No-Go, "No Go" is almost never said. $\endgroup$ Commented Aug 22, 2019 at 20:06
-
7$\begingroup$ Hearing Weather did not concur makes me wonder... What the hell happened with Challenger given Thiokol and NASA knew they were launching outside the vehicle's operating specs. Was someone missing from the room? Or were they present and made the wrong call? $\endgroup$– jwwCommented Aug 23, 2019 at 5:27
-
26$\begingroup$ @jww: Overriden from above. Its a pretty sad story. Challenger didn't have to explode. They should have listened to the engineers, 'cause the engineers told them the cold was a problem. The whole story is too long for a comment. $\endgroup$– JRECommented Aug 23, 2019 at 7:45
-
5$\begingroup$ I honestly want more on that story, why was the weather man ignored on his no-go? $\endgroup$ Commented Aug 23, 2019 at 17:25
-
3$\begingroup$ @MagicOctopusUrn I was actually looking for some confirming info, and there was a thread on nasaspaceflight.com about this launch attempt which linked to a video! I was excited, but the link was dead. I posted a question about if there was any way to get the video back, and they deleted the whole thread!! Google "all-eventful STS-88 countdown" and you'll get a hit, but if you click on the link, it's gone. I also dug out my console log, but it doesn't have a lot of supporting detail, I just wrote "weather marginal". $\endgroup$ Commented Aug 23, 2019 at 17:33
$\begingroup$
$\endgroup$
The No GO happens all the time. Many recent ULA and Spacex Launches get a NO GO - Most of the time its the Weather and the Range Telemetry guys. High Altitude winds , Range tracking failures , data drops etc. If you watch Spaceflightnow or any of the launch scheduling websites you see launch halts in the last 4 or 30 minute hold all the time, then the launch usually goes fine after a day or two delay
$\begingroup$
$\endgroup$
3
Apollo 11 had a conditional "Go" from flight during the "1202 alarm" discussions.
Armstrong: Give us a reading on the twelve-oh-two program alarm, Mission Control.
Flight: We’re go on that flight
Kranz: We’re go on that alarm?
Flight: If it doesn’t reoccur, we will be go
CAPCOM: Roger. We got – we’re go on that alarm
Aldrin: We got good data
As Mr Marble points out in the other answer, these round-the-horns are the final confirmation checks before major mission events and are the culmination of extended periods of discussions checks, and re-checks. Any No-Go decision would and should have been discussed and resolved before this final round of confirmation.
-
1$\begingroup$ This answer also highlights the point of a Go, No-Go poll: Getting clear statements from all teams as to whether or not anything they've been working on needs to put the launch on hold. A critical safety step to make sure everyone is perfectly clear as to what each team's status actually is. [Something may have just happened, or a previously 'known' issue may actually be far more serious than people outside of a given team understood it to be.] $\endgroup$ Commented Aug 23, 2019 at 19:20
-
$\begingroup$ I can’t help but do not find the we will be go very clear, especially since it did reoccurred. It just was a situation with not enough time budget and thanks god they had a robust system. $\endgroup$– eckesCommented Aug 24, 2019 at 22:50
-
$\begingroup$ @eckes Sometimes you have to roll the hard six $\endgroup$ Commented Aug 25, 2019 at 12:11