CAIB: Scott Hubbard NASA Ames Center Director
Columbia Accident Investigation Board Video Interview with Scott Hubbard NASA Ames Center Director
Segments:
00m00s Call to Duty
02m26s CAIB Chairman and Early Formulation
06m02s Importance of Board Member Expertise
07m33s Start-up Transients
09m55s Early Planning For The Report
12m03s The Need For Independence
13m20s Formulation of Teams
15m40s Time Allocation – Investigation Phases
18m13s Impact Testing – Planning & Controversy
25m36s Impact Testing Proceeds
36m40s Psychological & Sociological Issues
37m42s Independent Analysis & Investigation
39m15s Maintaining Independence
44m12s Returning to NASA
46m54s Writing The Report
51m18s Key Takeaways
Related Resources
-
Apollo 1-Challenger-ColumbiaEvery year as we get back in the saddle, our Remembrance Day signals us to think back to the tragic events of Apollo 1, Challenger and Columbia as well as the context surrounding them. We’re accountable for learning from not just what went wrong, but how we recovered. As an example, read these rules recorded by Wayne Hale, former NASA Flight Director and Space Shuttle Program Manager. By actually applying such lessons from the past to your current work, our actions can honor our lost crews beyond silent reflection.
-
Shuttle Software AnomalyCase Study–A few minutes after the Shuttle Endeavour reached orbit for STS-126 on Nov. 14, 2008, mission control noticed that the shuttle did not automatically transfer two communications processes from launch to orbit configuration. Primary communications continued to use S-band frequencies after they should have transferred to the more powerful Ku-band. The link between the shuttle and its payload — the Payload Signal Processor (PSP)–remained configured for a radio link rather than switching.
-
Overview on Organizational Silence (SMA-OV-WBT-131)The course is for all NASA personnel and defines the basic knowledge, types, factors and consequences behind organizational silence; identifies organizational silence conditions; and describes tactics and steps to combat organizational silence.
