6.2 - Case Study 4 2/20/17, 9:55 AM 6.2 - Case Study 4 Due Feb 19 by 11:59pm Points 100 Submitting a text entry box or a file upload Case Study 4: The Space Shuttle Challenger Explosion Save the file as your lastname_case4 (e.g., pugh_case4.doc). The Space Shuttle Challenger Explosion First, view the following videos: Engineering Disasters - Challenger (2:21) Click the picture to link to History.com for video. (http://www.history.com/topics/challenger-disaster/videos/engineering-disasters---challenger) Challenger Accident Investigation (44:45) This NASA video is almost 45 minutes, but the analysis starts at 15:00 minutes if you want to fast forward to that point. Click the picture to link to YouTube for video. Challenger Accident Investigation (1986) (https://www.youtube.com/watch?v=MKG4bvZGWag) (https://www.youtube.com/watch?v=MKG4bvZGWag) Now, read Chapters 4 and 6 of the Presidential Commission Report, also known as the Rogers Report, on the Challenger accident. Chapter IV: The Cause of the Accident (http://www.history.nasa.gov/rogersrep/v1ch4.htm#4.1) Chapter VI: An Accident Rooted in History (http://www.history.nasa.gov/rogersrep/v1ch6.htm) Based upon the things you have read on the causes of the Challenger explosion and your own thoughts on what may have contributed, put yourself in the shoes of the engineering team developing the O-rings for the SRBs. Construct a fault tree analysis of the O-ring construction, keeping in mind the possibilities of temperature changes and other weather considerations. From this fault tree, draw conclusions in the form of a one to two-page summary about the risks you found, their criticality based upon the risk assessment matrix, and probable ways to mitigate the risks that your fault tree showed. Your summary should include an actual fault tree, showing correct transition gates, and a short narrative of the analysis. If you are unable to get a computer program that will draw the gates correctly, it is OK to hand draw the fault tree out legibly and scan it in for submission. Sometimes it is more important to get the information to the boss quickly as opposed to spending the time finding a computer to build it on. As always, if you need to do more research to accomplish this task, feel free. Just be sure to cite your sources accordingly. * This assignment has two requirements that must be completed. The first is a fault tree presenting the data you selected to analyze (an example https://erau.instructure.com/courses/55938/assignments/884242#submit Page 1 of 2 6.2 - Case Study 4 2/20/17, 9:55 AM is found in the Ericson text). The second is a short narrative to the boss telling them why the items you show in your chart are important and need to be addressed. Both of these must be turned in for this case study. Your Instructor will evaluate your analysis based on the Case Study Rubric below. File Upload Text Entry Google Doc Upload a file, or choose a file you've already uploaded. File: Choose File no file selected ! Add Another File Click here to find a file you've already uploaded Comments... Cancel Submit Assignment ASCI 611 6.2 Case Study Rubric V2 Criteria Analysis / Interpretation / Application view longer description Supporting References view longer description Style & Mechanics view longer description Ratings Pts Exceeds Standards 40.0 pts Meets Standards 36.0 pts Does Not Meet Standards 32.0 pts 40.0 pts Exceeds Standards 30.0 pts Meets Standards 27.0 pts Does Not Meet Standards 24.0 pts 30.0 pts Exceeds Standards 30.0 pts Meets Standards 27.0 pts Does Not Meet Standards 24.0 pts 30.0 pts Total Points: 100.0 https://erau.instructure.com/courses/55938/assignments/884242#submit Page 2 of 2