4 ms·
> On the webcast, the host went silent for over a minute when fairing separation should have occurred, before coming back with Or the host was not cleared to v
by jnsaff2 9y ago
> On the webcast, the host went silent for over a minute when fairing separation should have occurred, before coming back with
Or the host was not cleared to view the fairing separation/payload themselves and had to get their information from others.
- Robotbeat 9y agoBingo. Everything even close to the payload would need to be approved before being mentioned by the host. And the penalty for screwing that up is pretty stiff (for the company and employee), so you sure as heck are going to error on the side of caution.
- peeters 9y agoOh no doubt he was waiting for info to be relayed to him, I just felt the combination of his sigh, his language (we'll address the situation), and the fact that there was such a long silence indicated that he didn't anticipate it taking so long to have confirmation of fairing deploy. In typical launches the confirmation comes a few seconds after deployment, not a couple minutes. And if you anticipate 1-2 minutes of nothing to report, usually you'd plan to be saying something in the meantime to avoid dead air. I could obviously be misinterpreting it, but this was my impression when watching it live, before we even knew there was an issue with the payload. When I watched it I thought they had lost it until he came back and said fairing deploy was successful.