normally butters Ars Praefectus
18y
5,285
ahsgdbeyb3 said:
I am curious about what role exactly he had here in the control room. Operators freezing up sounds like an understandable response, but also sounds like there was a lack of sims to prepare then for such events. The flight director would be the one who should keep them on focus, not a manager. I would actually keep such 'VIP' people out of the control room, they tend not to be able to offer much of use during an actual flight, so I'm wondering how SpaceX managed their presence here and what kind of access to the loops they were/are given?
SpaceX has a "responsible engineer" culture. The engineers who know the most about a system assume responsibility for that system and may eventually have a management role and/or represent that system on console in mission control. This philosophy extends to higher levels. The manager of the Dragon program is a responsible engineer wearing a manager hat, not an MBA. David Giger was responsible for Dragon as a whole, and that was the role he was playing when he reminded the team that Dragon is still alive and might still be saved.

This isn't how NASA works. This isn't how legacy NASA contractors work. For example, Boeing outsources Starliner mission control to NASA. Boeing trains NASA controllers and managers on how to operate Starliner, and they provide "back room" engineering support for the NASA controllers on console. I'll never forget the video from Mission Control Houston during the Starliner OFT-1 MET clock anomaly when the thrusters were firing like crazy immediately after separating from the launch vehicle. The NASA Flight Dynamics Officer was gesticulating wildly in an animated conversation facing the Flight Director, obviously unprepared for this scenario and probably not giving the Flight Director the answers he wanted to hear. I felt sorry for him.