Could someone refresh my memory; when was the last time a launch team extended an offical launch window set-up in advance with the Range? I vaguely remember we once extended a window to get a critical AF bird up but I don't remember any other. Yes the shuttle example is one where the short window was driven by mission constrainsts and they chose to change the constrainst. And a commerical bird usually have an orbital mechanics related sunlight contrainst for batteries/power issues. Maybe they had constrainst relieve from the customer already in their back pocket (in reserve), same with the Range support. I don't know the answer to that one.
What SpaceX has been repeatedly communicating is that they want to do things in a more iterative way and be much more efficient than "OldSpace" this way. Here, they have a customer who's clearly interested in making this better efficiency a reality so they are prepared to take quite a risk.
Quote from: cro-magnon gramps on 11/29/2013 04:23 pmcheck the times in the lower left hand corner... edit, sorry, #8 doesn't have the clock... but the Strong Back was retracting/retractedWhat is your point? The strongback is retracted minutes before launch.
check the times in the lower left hand corner... edit, sorry, #8 doesn't have the clock... but the Strong Back was retracting/retracted
Quote from: Lars_J on 11/29/2013 04:29 pmQuote from: cro-magnon gramps on 11/29/2013 04:23 pmcheck the times in the lower left hand corner... edit, sorry, #8 doesn't have the clock... but the Strong Back was retracting/retractedWhat is your point? The strongback is retracted minutes before launch.#8 was to show progression, but the firing pic #9 shows two times, T-000 and the actual time of 38:58... then they correct to T-002, so just shows that without watching the actual clock, which was what they were going by, it would be easy to assume that the count down went to 0.... btw, my clumsy attempt to visually confirm what Chuck said...
Quote from: Jim on 11/28/2013 11:17 pmCase of go fever. Shouldn't have started the terminal count if their data review wasn't complete. Who's watching the rocket? And who is reviewing data?They didn't succumb to it, but starting the countdown put some extra pressure on the review team. It is only human nature. I am glad they didn't go and took the conservative path. I am wondering if Spacex shouldn't revaluate the length of the terminal count and try to shorten it. More complex vehicles have done it, the shuttle was 9 minutes vs the 13 of a F9. It helps with launch window management. It might have an affect on recycle time, but that is a trade that can be done.
Case of go fever. Shouldn't have started the terminal count if their data review wasn't complete. Who's watching the rocket? And who is reviewing data?
Quote from: Jim on 11/29/2013 12:01 pmQuote from: Jim on 11/28/2013 11:17 pmCase of go fever. Shouldn't have started the terminal count if their data review wasn't complete. Who's watching the rocket? And who is reviewing data?They didn't succumb to it, but starting the countdown put some extra pressure on the review team. It is only human nature. I am glad they didn't go and took the conservative path. I am wondering if Spacex shouldn't revaluate the length of the terminal count and try to shorten it. More complex vehicles have done it, the shuttle was 9 minutes vs the 13 of a F9. It helps with launch window management. It might have an affect on recycle time, but that is a trade that can be done.During the countdown, the review team was asked "what their feeling was (on whether they could fix things in time for another attempt). They answered: "we don't have enough data to have a feeling one way or the other". So they may have started the countdown in case, the issues could be resolved in time. In SpaceX's defense, a lot of the other previous aborts were caused by non-issues. So it could have been another non-issue. But I am also glad that they took the safe and conservative approach. I wonder if Elon had a say in the final decision.
I know I am coming across as a broken record , but its Elons company.. so yes its his call..
Quote from: Avron on 11/30/2013 12:07 am I know I am coming across as a broken record , but its Elons company.. so yes its his call.. That does not follow, at all. Unless you have specific knowledge to the contrary, just because it's "his company" does not mean that every technical decision during the launch campaign flow is his to make.
Quote from: Herb Schaltegger on 11/30/2013 01:00 amQuote from: Avron on 11/30/2013 12:07 am I know I am coming across as a broken record , but its Elons company.. so yes its his call.. That does not follow, at all. Unless you have specific knowledge to the contrary, just because it's "his company" does not mean that every technical decision during the launch campaign flow is his to make.Exactly. That's why you hire experts. Elon may be the public face of SpaceX, and he may be the one setting the corporate goals, priorities, and culture, but it's the professionals who do the day to day work, and calling an abort is a decision for professionals.
We called manual abort. Better to be paranoid and wrong. Bringing rocket down to borescope engines ...
Quote from: llanitedave on 11/30/2013 01:21 amQuote from: Herb Schaltegger on 11/30/2013 01:00 amQuote from: Avron on 11/30/2013 12:07 am I know I am coming across as a broken record , but its Elons company.. so yes its his call.. That does not follow, at all. Unless you have specific knowledge to the contrary, just because it's "his company" does not mean that every technical decision during the launch campaign flow is his to make.Exactly. That's why you hire experts. Elon may be the public face of SpaceX, and he may be the one setting the corporate goals, priorities, and culture, but it's the professionals who do the day to day work, and calling an abort is a decision for professionals.Elon bills himself as the Chief Rocket Designer so he may well have had some say in this. His tweet indicated some ownership of the decision...Elon Musk @elonmusk 28 NovQuoteWe called manual abort. Better to be paranoid and wrong. Bringing rocket down to borescope engines ... .... yes that could be the royal we but I read it as having some say.
I had to agree with Jim’s “Go Fever” comment from yesterday. They really wanted to launch and were trying to “cowboy” it... It was a bit gut wrenching to watch and I wonder how much risk the S/C owner was willing to take apart from extending the window. The safe practices Jim is aware of has been developed over several decades and was paid for dearly.
Quote from: Rocket Science on 11/29/2013 01:10 pmI had to agree with Jim’s “Go Fever” comment from yesterday. They really wanted to launch and were trying to “cowboy” it... It was a bit gut wrenching to watch and I wonder how much risk the S/C owner was willing to take apart from extending the window. The safe practices Jim is aware of has been developed over several decades and was paid for dearly.The practices developed over several decades are one way to achieve a particular degree of safety. They are not necessarily the only way. If everyone just says that because the one way has been found to do it we'll never look for alternatives then we'll never make progress.I'm more interested in the reasons for the practices. If there is a good reason a long-standing practice is better than an alternative, then by all means we should stick with it. But it shouldn't be beyond questioning.In the case we're talking about here, SpaceX started a new countdown before they had finished their analysis of the data from the previous scrub, knowing that if the analysis didn't say it was safe to launch they could still call it off. From the outside, we have no way of knowing whether that was safe or not. It's possible it distracted people from their normal countdown duties. It's also possible the people involved in the analysis didn't have any active part in the countdown anyway. So claiming, just based on the information we have, that SpaceX was doing something unsafe is unsubstantiated.
In the case we're talking about here, SpaceX started a new countdown before they had finished their analysis of the data from the previous scrub, knowing that if the analysis didn't say it was safe to launch they could still call it off. From the outside, we have no way of knowing whether that was safe or not. It's possible it distracted people from their normal countdown duties. It's also possible the people involved in the analysis didn't have any active part in the countdown anyway. So claiming, just based on the information we have, that SpaceX was doing something unsafe is unsubstantiated.
It's also possible the people involved in the analysis didn't have any active part in the countdown anyway.