SlideShare a Scribd company logo
1 of 24
COLUMBIA AND
CHALLENGER
DISASTERS
ROSS APTED
SPACE SHUTTLE
COLUMBIA DISASTER
On the 1st February 2003 A critical
systems failure occurred on the
space shuttle Columbia (STS - 107) on
its re – entry to the earth’s
atmosphere.
This caused the disintegration of the
shuttle leading to the death of all
seven crew members.




                                        STS-107 flight insignia
INVESTIGATION INTO THE ACCIDENT
Above image shows the Columbia disintegrating over Texas
NASA’S INITIAL
INVESTIGATION
The Columbia re-entry data showed that there was a loss of
temperature sensors and of hydraulic systems in the left
wing, indicating severe over heating.




            Image of shuttle taken during re-entry shows
              damage to the left wing’s leading edge
This initial data focused the investigation on the possibility
of a a foam strike.
               This is when foam from the shuttle’s largest
               component, the external tank, sheds and
               collides with other areas of the or shuttle
               during launch.



                       External Tank

The theory that is was a foam strike
was compounded by the fact that
foam sheading was a know problem
that had damaged previous orbiters




                                            Columbia launch
FOCUS OF
INVESTIGATION
The investigation focused entirely on the technical causes of
the accident.


       No formal model was used in the investigation.


       No attempted was made to investiigate the human
and    organizational cause of the accident.
RESULT OF
INVESTIGATION
It was conclude that the damage was
due to the foam sheading of the least
left bi-pod ramp causing a breach in the
reinforced carbon – carbon panels in
the left wing.

                         Left bi-pod ramp


The result of this was to retrain
employees at the assembly facility to
apply foam without defects.


      THIS WAS THE INCORRECT
              CAUSE
Technical causes




                                 Root cause

                                    Shuttle
                    Bi-pod
   Foam                            overheats
                  damages left
  applied                        dues to RCC
                    wing on
incorrectly                       damage on
                    launch
                                    re-entry
COLUMBIAN ACCIDENT
INVESTIGATION BOARD
This was an independent investigation board. The board
analyzed the accident in more robustly.


                Took into account technical cause, human cause and
                organizational cause.


      Investigation made use of effective modeling
approaches.


                Came to a different conclusion.

(Board, Columbia Accident Investigation, 2003)
FOCUS OF
INVESTIGATION
Technical
Carried out test to confirm that foam could have caused
damage to the RCC panels on the left wing. Used
compressed air gun to fire foam at wing leading edge.


Conducted further research into
the fitting of the foam concluded
that due to the technical and
organizational controls in place
the fault could not have occurred
there.

                                    Compressed air gun
                                    used to fire the foam.
Organizational
Several faults with NASA as an organization contributed to
the accident.


NASA’s reluctance to curb operational ambition in line their
shirking budget meant that greater efficiency had to be
achieved. This caused the schedule to be tightened; as a
result the workloads and the stress of the staff increased.




                                                     NASA budget
                                                     as percentage
                                                     of federal
                                                     budget
NASA was also found to have inadequate decision making
and risk-assessment processes.


NASA management knew about the foam sheading problem
for over 22 years before the accident occurred.


       The failure to correct the problem was due to conflict
       interests of managing positions. The managers not
       only had to ensure safety but they also had to make
       sure the launch was on schedule and in budget.
MODELING USED IN
THE INVESTIGATION
Investigation used fault trees to model the accident.
                                  A graphical representation of
                         all the events that could lead to a
                         system failure.


Each element in a fault tree represents a factor: technical,
human or organizing that could cause the element immediately
above it to fail.


This is ideal for modeling complex socio-technical systems, as
you can clearly see the chain of events that could lead to a
catastrophic system failure.
It is an effective tool for finding the correct chain of events
through a process of elimination.
EXAMPLE FAULT TREE




     Simple fault tree for a fire breakout
RESULT OF
    INVESTIGATION

     Organizational                        Technical causes
        causes


                    NASA        Left foam bi-
                Management      pod collides
  Nasa’s                                        Shuttle over       Shuttle
                failed to act    with RCC
budget is cut                                     heats        disintegration
                 on known        panels on
                  problem           wing
ACADEMIC
LITERATURE
Studying organisational cultures and their effects on safety
(Hopkins, 2006)


Beyond Normal Accidents and High Reliability Organizations: The Need for an
Alternative Approach to Safety in Complex Systems
( Marais, Dulac, & Leveson, 2004)

                  Both agree that a major factor contributing towards the accident was NASA
                  organizational culture.


A Framework for Dynamic Safety and Risk Management Modeling in Complex
Engineering Systems
  (Dulac, 2007)

                  Takes it a step further and analyzes NASA using STAMP modeling
                  the paper finds that STAMP is ideally sited with its control framework to
                  model every aspect of NASA: social, organizational, technical and how they
                  interact.
CHALLENGER
DISASTER
On January 28, 1986
the space shuttle
Challenger (STS-51-L)
broke apart in flight,
minutes after take off,
killing all of its 7 crew
members.




                            STS-51-L flight insignia
INVESTIGATION INTO THE ACCIDENT
Above image shows the Challenger disintegrating 73 seconds after launch
ROGERS COMMISSION
(PRESIDENTIAL COMMISSION on the Space Shuttle Challenger Accident,
1986)




Presidential Commission on the
Space Shuttle Challenger Accident
was an independent investigation
into the accident.
                    Solid Rocket booster


The investigation found that the
right solid rocket booster become
separated, causing damage to the
external tank. This led to the
destruction of the shuttle by
aerodynamic forces.
The investigation found that the O-ring joint failure was the
cause of the accident.




                      The O-ring sealed a joint connecting
the                   solid rocket booster to the main part
of                    the shuttle




 Both the primary and secondary O-rings failed, allowing
heated gases and flames to escape and make contact with
the external tank, causing a structural failure.
FOCUS OF
INVESTIGATION
Technical
The O-ring joint was know to be inadequate and was in the
process of being redesigned. It was found that in pervious
flights O-ring erosion had occurred which rendered the
secondary O-ring useless.


Organizational
On the day of launch engineers were concerned that the
temperature was too low to launch(-2.2C lowest launch
temperature recorded) and that there was to much ice on the
shuttle. O-rings would not perform correctly at this
temperature.
NASA management was told of this issue but it was deemed an
acceptable risk and the launch went ahead.
RESULT OF
INVESTIGATION
Technical concerns-             the sold rocket boosters were
                         redesigned.
Organizational concerns-      A new safety office was
                        created to allow better communication
                              and risk assessment.
Cause


                                                Ice conditions not
            Root                                    assessed
                                                     correctly     Organizational
                              O-ring failure
            Shuttle
                             caused rocket
         disintegrated
                            booster to detach
                                                Design flaw in O-
                                                     rings        Technical
ACADEMIC
LITERATURE
Understanding the Challenger Disaster: Organizational
Structure and the Design of Reliable Systems
(Heimann, 1993)


A critical analysis of factors related to decisional processes
involved in the challenger disaster
(Gouran , Hirokawa,, & Martz, 1986)




                  These papers both focus on the decision making
                  process at NASA and why it how this process can be
                  made more robust.
REFERENCES
Marais, K., Dulac, N., & Leveson, N. (2004). Beyond Normal Accidents and High Reliability
Organizations: The Need for an Alternative Approach to Safety in Complex Systems.
Cambridge.
Board, Columbia Accident Investigation. (2003). Columbia Accident Investigation Board Vol 1.
Washington, D.C: Columbia Accident Investigation Board.
Dulac, N. (2007). A Framework for Dynamic Safety and Risk Management Modeling in Complex
Engineering Systems. Cambridge: MIT.
Gouran , D. S., Hirokawa,, R. Y., & Martz, A. E. (1986). A critical analysis of factors related to
decisional processes involved in the challenger disaster. Central States Speech Journal , 37.
Heimann, C. F. (1993). Understanding the Challenger Disaster: Organizational Structure and
the Design of Reliable Systems. The American Political Science Review , 87, 421-435.
Hopkins, A. (2006, December). Studying organisational cultures and their effects on safety.
Safety Science , 44, pp. 875-889.
Keong, T. H. (1997, July 9). Risk Analysis Methodologies. Retrieved June 8, 2012, from
pacific.net.sg: http://home1.pacific.net.sg/~thk/risk.html
PRESIDENTIAL COMMISSION on the Space Shuttle Challenger Accident. (1986). Report of the
PRESIDENTIAL COMMISSION on the Space Shuttle Challenger Accident. Washington, D.C.:
PRESIDENTIAL COMMISSION on the Space Shuttle Challenger Accident.

More Related Content

What's hot

The communication challenges at nasa
The communication challenges at nasaThe communication challenges at nasa
The communication challenges at nasa
Aneth Sanchez
 
Callaway golf company (cgc)
Callaway golf company (cgc)Callaway golf company (cgc)
Callaway golf company (cgc)
Bent Qtr
 
Afa Comparision between breadtalk & Old Chang Kee
Afa Comparision between breadtalk & Old Chang KeeAfa Comparision between breadtalk & Old Chang Kee
Afa Comparision between breadtalk & Old Chang Kee
bottletree
 
GE’s two Decades Transformation
GE’s two Decades TransformationGE’s two Decades Transformation
GE’s two Decades Transformation
Karan Jaidka
 
Firestone Tire & Rubber
Firestone Tire & RubberFirestone Tire & Rubber
Firestone Tire & Rubber
Andrew Chin
 
Groupthink_lecutre_final
Groupthink_lecutre_finalGroupthink_lecutre_final
Groupthink_lecutre_final
Steve Shore
 

What's hot (20)

Ethical problem(challenger disaster)
Ethical problem(challenger disaster)Ethical problem(challenger disaster)
Ethical problem(challenger disaster)
 
Challenger space-shuttle-incident
Challenger space-shuttle-incidentChallenger space-shuttle-incident
Challenger space-shuttle-incident
 
The communication challenges at nasa
The communication challenges at nasaThe communication challenges at nasa
The communication challenges at nasa
 
Jack Welch: GE's Two Decade Of Transformation
Jack Welch: GE's Two Decade Of TransformationJack Welch: GE's Two Decade Of Transformation
Jack Welch: GE's Two Decade Of Transformation
 
Hubble Error : Case Study by Vedang R. Vatsa
Hubble Error : Case Study by Vedang R. VatsaHubble Error : Case Study by Vedang R. Vatsa
Hubble Error : Case Study by Vedang R. Vatsa
 
Ge’s two decade transformation-Case PPT
Ge’s two decade transformation-Case PPTGe’s two decade transformation-Case PPT
Ge’s two decade transformation-Case PPT
 
GE's Two-Decade Transformation: Jack Welch's Leadership
GE's Two-Decade Transformation: Jack Welch's LeadershipGE's Two-Decade Transformation: Jack Welch's Leadership
GE's Two-Decade Transformation: Jack Welch's Leadership
 
Acme and omega
Acme and omegaAcme and omega
Acme and omega
 
Challenger disaster
Challenger disasterChallenger disaster
Challenger disaster
 
Callaway golf company (cgc)
Callaway golf company (cgc)Callaway golf company (cgc)
Callaway golf company (cgc)
 
NFL: Digital media strategy case review
NFL: Digital media strategy case reviewNFL: Digital media strategy case review
NFL: Digital media strategy case review
 
Afa Comparision between breadtalk & Old Chang Kee
Afa Comparision between breadtalk & Old Chang KeeAfa Comparision between breadtalk & Old Chang Kee
Afa Comparision between breadtalk & Old Chang Kee
 
GE’s two Decades Transformation
GE’s two Decades TransformationGE’s two Decades Transformation
GE’s two Decades Transformation
 
Firestone Tire & Rubber
Firestone Tire & RubberFirestone Tire & Rubber
Firestone Tire & Rubber
 
Renault-Nissan Strategic Alliance, Case Analysis
Renault-Nissan Strategic Alliance, Case AnalysisRenault-Nissan Strategic Alliance, Case Analysis
Renault-Nissan Strategic Alliance, Case Analysis
 
Project oxygen yakhin_roman
Project oxygen yakhin_romanProject oxygen yakhin_roman
Project oxygen yakhin_roman
 
Bayonne packaging inc case analysis
Bayonne packaging inc case analysisBayonne packaging inc case analysis
Bayonne packaging inc case analysis
 
HIGH FREQUENCY ACTIVE AURORAL RESEARCH PROGRAM (H.A.A.R.P)
HIGH FREQUENCY ACTIVE AURORAL RESEARCH PROGRAM (H.A.A.R.P)HIGH FREQUENCY ACTIVE AURORAL RESEARCH PROGRAM (H.A.A.R.P)
HIGH FREQUENCY ACTIVE AURORAL RESEARCH PROGRAM (H.A.A.R.P)
 
Groupthink_lecutre_final
Groupthink_lecutre_finalGroupthink_lecutre_final
Groupthink_lecutre_final
 
The Walt Disney: The Entertainment King
The Walt Disney: The Entertainment KingThe Walt Disney: The Entertainment King
The Walt Disney: The Entertainment King
 

Similar to Columbia and Challenger

A C C I D E N T I N V E S T I G A T I O N B O A R DCOLUM.docx
A C C I D E N T  I N V E S T I G A T I O N  B O A R DCOLUM.docxA C C I D E N T  I N V E S T I G A T I O N  B O A R DCOLUM.docx
A C C I D E N T I N V E S T I G A T I O N B O A R DCOLUM.docx
ransayo
 
The Challenger and Columbia Shuttle DisastersTo be considered co.docx
The Challenger and Columbia Shuttle DisastersTo be considered co.docxThe Challenger and Columbia Shuttle DisastersTo be considered co.docx
The Challenger and Columbia Shuttle DisastersTo be considered co.docx
mamanda2
 
Rodney rocha
Rodney rochaRodney rocha
Rodney rocha
NASAPMC
 
Rodney rocha
Rodney rochaRodney rocha
Rodney rocha
NASAPMC
 
The Challenger Disaster A Case-study in Engineering Ethics.docx
The Challenger Disaster A Case-study in Engineering Ethics.docxThe Challenger Disaster A Case-study in Engineering Ethics.docx
The Challenger Disaster A Case-study in Engineering Ethics.docx
mamanda2
 
Nasa tragedies and lessons
Nasa tragedies and lessonsNasa tragedies and lessons
Nasa tragedies and lessons
pkmarvel
 
2011.11.01 - VV&A 3.2
2011.11.01 - VV&A 3.22011.11.01 - VV&A 3.2
2011.11.01 - VV&A 3.2
SMART-Lab
 
Nieberding.joe
Nieberding.joeNieberding.joe
Nieberding.joe
NASAPMC
 
Societal Issues in Engineering Design
Societal Issues in Engineering DesignSocietal Issues in Engineering Design
Societal Issues in Engineering Design
Gupta Pandiri
 
Case Study 1The Challenger Space Shuttle disasterand the.docx
Case Study 1The Challenger Space Shuttle disasterand the.docxCase Study 1The Challenger Space Shuttle disasterand the.docx
Case Study 1The Challenger Space Shuttle disasterand the.docx
wendolynhalbert
 
Ag avt-140-01
Ag avt-140-01Ag avt-140-01
Ag avt-140-01
ceginc
 
52352main contour
52352main contour52352main contour
52352main contour
Pedro León
 
Zlozenie wraku
Zlozenie wrakuZlozenie wraku
Zlozenie wraku
wikb
 

Similar to Columbia and Challenger (20)

A C C I D E N T I N V E S T I G A T I O N B O A R DCOLUM.docx
A C C I D E N T  I N V E S T I G A T I O N  B O A R DCOLUM.docxA C C I D E N T  I N V E S T I G A T I O N  B O A R DCOLUM.docx
A C C I D E N T I N V E S T I G A T I O N B O A R DCOLUM.docx
 
The Challenger and Columbia Shuttle DisastersTo be considered co.docx
The Challenger and Columbia Shuttle DisastersTo be considered co.docxThe Challenger and Columbia Shuttle DisastersTo be considered co.docx
The Challenger and Columbia Shuttle DisastersTo be considered co.docx
 
Rodney rocha
Rodney rochaRodney rocha
Rodney rocha
 
Rodney rocha
Rodney rochaRodney rocha
Rodney rocha
 
The Challenger Disaster A Case-study in Engineering Ethics.docx
The Challenger Disaster A Case-study in Engineering Ethics.docxThe Challenger Disaster A Case-study in Engineering Ethics.docx
The Challenger Disaster A Case-study in Engineering Ethics.docx
 
KXEX2165_Moral & Ethics_Assignment 2
KXEX2165_Moral & Ethics_Assignment 2KXEX2165_Moral & Ethics_Assignment 2
KXEX2165_Moral & Ethics_Assignment 2
 
Nasa tragedies and lessons
Nasa tragedies and lessonsNasa tragedies and lessons
Nasa tragedies and lessons
 
2011.11.01 - VV&A 3.2
2011.11.01 - VV&A 3.22011.11.01 - VV&A 3.2
2011.11.01 - VV&A 3.2
 
LSP
LSPLSP
LSP
 
Nieberding.joe
Nieberding.joeNieberding.joe
Nieberding.joe
 
Societal Issues in Engineering Design
Societal Issues in Engineering DesignSocietal Issues in Engineering Design
Societal Issues in Engineering Design
 
Case Study 1The Challenger Space Shuttle disasterand the.docx
Case Study 1The Challenger Space Shuttle disasterand the.docxCase Study 1The Challenger Space Shuttle disasterand the.docx
Case Study 1The Challenger Space Shuttle disasterand the.docx
 
Ag avt-140-01
Ag avt-140-01Ag avt-140-01
Ag avt-140-01
 
Fatigue stresses
Fatigue stressesFatigue stresses
Fatigue stresses
 
PellegrinoHonorsThesis
PellegrinoHonorsThesisPellegrinoHonorsThesis
PellegrinoHonorsThesis
 
Proc,Air,Water_July 2016
Proc,Air,Water_July 2016Proc,Air,Water_July 2016
Proc,Air,Water_July 2016
 
52352main contour
52352main contour52352main contour
52352main contour
 
Zlozenie wraku
Zlozenie wrakuZlozenie wraku
Zlozenie wraku
 
Altair ProductDesign Case Study - Orion Crew Module Water Landing Simulation ...
Altair ProductDesign Case Study - Orion Crew Module Water Landing Simulation ...Altair ProductDesign Case Study - Orion Crew Module Water Landing Simulation ...
Altair ProductDesign Case Study - Orion Crew Module Water Landing Simulation ...
 
PAUT Inspection Simulation of Welds at NASA
PAUT Inspection Simulation of Welds at NASAPAUT Inspection Simulation of Welds at NASA
PAUT Inspection Simulation of Welds at NASA
 

More from stargate1280

Fault Tree - Kegworth
Fault Tree - KegworthFault Tree - Kegworth
Fault Tree - Kegworth
stargate1280
 
FRAM Analysis - Kegworth
FRAM Analysis - KegworthFRAM Analysis - Kegworth
FRAM Analysis - Kegworth
stargate1280
 
Cream analysis of the Kegworth Air Disaster
Cream analysis of the Kegworth Air DisasterCream analysis of the Kegworth Air Disaster
Cream analysis of the Kegworth Air Disaster
stargate1280
 
Overview of Systemic Modeling Approaches
Overview of Systemic Modeling ApproachesOverview of Systemic Modeling Approaches
Overview of Systemic Modeling Approaches
stargate1280
 
Overview of Systemic Modeling Approaches
Overview of Systemic Modeling ApproachesOverview of Systemic Modeling Approaches
Overview of Systemic Modeling Approaches
stargate1280
 
Summary of Selected Accident Modeling Papers
Summary of Selected Accident Modeling Papers Summary of Selected Accident Modeling Papers
Summary of Selected Accident Modeling Papers
stargate1280
 
Summary of Selected Accident Modeling Papers
Summary of Selected Accident Modeling Papers Summary of Selected Accident Modeling Papers
Summary of Selected Accident Modeling Papers
stargate1280
 
Overview modeling approches part 1
Overview modeling approches part 1Overview modeling approches part 1
Overview modeling approches part 1
stargate1280
 
Aviation accidents and incidents
Aviation accidents and incidentsAviation accidents and incidents
Aviation accidents and incidents
stargate1280
 

More from stargate1280 (11)

Final
FinalFinal
Final
 
Fault Tree - Kegworth
Fault Tree - KegworthFault Tree - Kegworth
Fault Tree - Kegworth
 
FRAM Analysis - Kegworth
FRAM Analysis - KegworthFRAM Analysis - Kegworth
FRAM Analysis - Kegworth
 
Cream analysis of the Kegworth Air Disaster
Cream analysis of the Kegworth Air DisasterCream analysis of the Kegworth Air Disaster
Cream analysis of the Kegworth Air Disaster
 
Overview of Systemic Modeling Approaches
Overview of Systemic Modeling ApproachesOverview of Systemic Modeling Approaches
Overview of Systemic Modeling Approaches
 
Overview of Systemic Modeling Approaches
Overview of Systemic Modeling ApproachesOverview of Systemic Modeling Approaches
Overview of Systemic Modeling Approaches
 
Summary of Selected Accident Modeling Papers
Summary of Selected Accident Modeling Papers Summary of Selected Accident Modeling Papers
Summary of Selected Accident Modeling Papers
 
Summary of Selected Accident Modeling Papers
Summary of Selected Accident Modeling Papers Summary of Selected Accident Modeling Papers
Summary of Selected Accident Modeling Papers
 
Overview modeling approches part 1
Overview modeling approches part 1Overview modeling approches part 1
Overview modeling approches part 1
 
Aviation accidents and incidents
Aviation accidents and incidentsAviation accidents and incidents
Aviation accidents and incidents
 
2010 Flash Crash
2010 Flash Crash2010 Flash Crash
2010 Flash Crash
 

Recently uploaded

Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME
Cloud Frontiers:  A Deep Dive into Serverless Spatial Data and FMECloud Frontiers:  A Deep Dive into Serverless Spatial Data and FME
Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME
Safe Software
 

Recently uploaded (20)

AWS Community Day CPH - Three problems of Terraform
AWS Community Day CPH - Three problems of TerraformAWS Community Day CPH - Three problems of Terraform
AWS Community Day CPH - Three problems of Terraform
 
Exploring the Future Potential of AI-Enabled Smartphone Processors
Exploring the Future Potential of AI-Enabled Smartphone ProcessorsExploring the Future Potential of AI-Enabled Smartphone Processors
Exploring the Future Potential of AI-Enabled Smartphone Processors
 
Workshop - Best of Both Worlds_ Combine KG and Vector search for enhanced R...
Workshop - Best of Both Worlds_ Combine  KG and Vector search for  enhanced R...Workshop - Best of Both Worlds_ Combine  KG and Vector search for  enhanced R...
Workshop - Best of Both Worlds_ Combine KG and Vector search for enhanced R...
 
Connector Corner: Accelerate revenue generation using UiPath API-centric busi...
Connector Corner: Accelerate revenue generation using UiPath API-centric busi...Connector Corner: Accelerate revenue generation using UiPath API-centric busi...
Connector Corner: Accelerate revenue generation using UiPath API-centric busi...
 
A Year of the Servo Reboot: Where Are We Now?
A Year of the Servo Reboot: Where Are We Now?A Year of the Servo Reboot: Where Are We Now?
A Year of the Servo Reboot: Where Are We Now?
 
Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...
Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...
Mastering MySQL Database Architecture: Deep Dive into MySQL Shell and MySQL R...
 
Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME
Cloud Frontiers:  A Deep Dive into Serverless Spatial Data and FMECloud Frontiers:  A Deep Dive into Serverless Spatial Data and FME
Cloud Frontiers: A Deep Dive into Serverless Spatial Data and FME
 
TrustArc Webinar - Unlock the Power of AI-Driven Data Discovery
TrustArc Webinar - Unlock the Power of AI-Driven Data DiscoveryTrustArc Webinar - Unlock the Power of AI-Driven Data Discovery
TrustArc Webinar - Unlock the Power of AI-Driven Data Discovery
 
Automating Google Workspace (GWS) & more with Apps Script
Automating Google Workspace (GWS) & more with Apps ScriptAutomating Google Workspace (GWS) & more with Apps Script
Automating Google Workspace (GWS) & more with Apps Script
 
Top 5 Benefits OF Using Muvi Live Paywall For Live Streams
Top 5 Benefits OF Using Muvi Live Paywall For Live StreamsTop 5 Benefits OF Using Muvi Live Paywall For Live Streams
Top 5 Benefits OF Using Muvi Live Paywall For Live Streams
 
Strategies for Unlocking Knowledge Management in Microsoft 365 in the Copilot...
Strategies for Unlocking Knowledge Management in Microsoft 365 in the Copilot...Strategies for Unlocking Knowledge Management in Microsoft 365 in the Copilot...
Strategies for Unlocking Knowledge Management in Microsoft 365 in the Copilot...
 
Real Time Object Detection Using Open CV
Real Time Object Detection Using Open CVReal Time Object Detection Using Open CV
Real Time Object Detection Using Open CV
 
A Domino Admins Adventures (Engage 2024)
A Domino Admins Adventures (Engage 2024)A Domino Admins Adventures (Engage 2024)
A Domino Admins Adventures (Engage 2024)
 
Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff
Strategize a Smooth Tenant-to-tenant Migration and Copilot TakeoffStrategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff
Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff
 
🐬 The future of MySQL is Postgres 🐘
🐬  The future of MySQL is Postgres   🐘🐬  The future of MySQL is Postgres   🐘
🐬 The future of MySQL is Postgres 🐘
 
Tata AIG General Insurance Company - Insurer Innovation Award 2024
Tata AIG General Insurance Company - Insurer Innovation Award 2024Tata AIG General Insurance Company - Insurer Innovation Award 2024
Tata AIG General Insurance Company - Insurer Innovation Award 2024
 
Repurposing LNG terminals for Hydrogen Ammonia: Feasibility and Cost Saving
Repurposing LNG terminals for Hydrogen Ammonia: Feasibility and Cost SavingRepurposing LNG terminals for Hydrogen Ammonia: Feasibility and Cost Saving
Repurposing LNG terminals for Hydrogen Ammonia: Feasibility and Cost Saving
 
Top 10 Most Downloaded Games on Play Store in 2024
Top 10 Most Downloaded Games on Play Store in 2024Top 10 Most Downloaded Games on Play Store in 2024
Top 10 Most Downloaded Games on Play Store in 2024
 
HTML Injection Attacks: Impact and Mitigation Strategies
HTML Injection Attacks: Impact and Mitigation StrategiesHTML Injection Attacks: Impact and Mitigation Strategies
HTML Injection Attacks: Impact and Mitigation Strategies
 
Artificial Intelligence Chap.5 : Uncertainty
Artificial Intelligence Chap.5 : UncertaintyArtificial Intelligence Chap.5 : Uncertainty
Artificial Intelligence Chap.5 : Uncertainty
 

Columbia and Challenger

  • 2. SPACE SHUTTLE COLUMBIA DISASTER On the 1st February 2003 A critical systems failure occurred on the space shuttle Columbia (STS - 107) on its re – entry to the earth’s atmosphere. This caused the disintegration of the shuttle leading to the death of all seven crew members. STS-107 flight insignia
  • 3. INVESTIGATION INTO THE ACCIDENT Above image shows the Columbia disintegrating over Texas
  • 4. NASA’S INITIAL INVESTIGATION The Columbia re-entry data showed that there was a loss of temperature sensors and of hydraulic systems in the left wing, indicating severe over heating. Image of shuttle taken during re-entry shows damage to the left wing’s leading edge
  • 5. This initial data focused the investigation on the possibility of a a foam strike. This is when foam from the shuttle’s largest component, the external tank, sheds and collides with other areas of the or shuttle during launch. External Tank The theory that is was a foam strike was compounded by the fact that foam sheading was a know problem that had damaged previous orbiters Columbia launch
  • 6. FOCUS OF INVESTIGATION The investigation focused entirely on the technical causes of the accident. No formal model was used in the investigation. No attempted was made to investiigate the human and organizational cause of the accident.
  • 7. RESULT OF INVESTIGATION It was conclude that the damage was due to the foam sheading of the least left bi-pod ramp causing a breach in the reinforced carbon – carbon panels in the left wing. Left bi-pod ramp The result of this was to retrain employees at the assembly facility to apply foam without defects. THIS WAS THE INCORRECT CAUSE
  • 8. Technical causes Root cause Shuttle Bi-pod Foam overheats damages left applied dues to RCC wing on incorrectly damage on launch re-entry
  • 9. COLUMBIAN ACCIDENT INVESTIGATION BOARD This was an independent investigation board. The board analyzed the accident in more robustly. Took into account technical cause, human cause and organizational cause. Investigation made use of effective modeling approaches. Came to a different conclusion. (Board, Columbia Accident Investigation, 2003)
  • 10. FOCUS OF INVESTIGATION Technical Carried out test to confirm that foam could have caused damage to the RCC panels on the left wing. Used compressed air gun to fire foam at wing leading edge. Conducted further research into the fitting of the foam concluded that due to the technical and organizational controls in place the fault could not have occurred there. Compressed air gun used to fire the foam.
  • 11. Organizational Several faults with NASA as an organization contributed to the accident. NASA’s reluctance to curb operational ambition in line their shirking budget meant that greater efficiency had to be achieved. This caused the schedule to be tightened; as a result the workloads and the stress of the staff increased. NASA budget as percentage of federal budget
  • 12. NASA was also found to have inadequate decision making and risk-assessment processes. NASA management knew about the foam sheading problem for over 22 years before the accident occurred. The failure to correct the problem was due to conflict interests of managing positions. The managers not only had to ensure safety but they also had to make sure the launch was on schedule and in budget.
  • 13. MODELING USED IN THE INVESTIGATION Investigation used fault trees to model the accident. A graphical representation of all the events that could lead to a system failure. Each element in a fault tree represents a factor: technical, human or organizing that could cause the element immediately above it to fail. This is ideal for modeling complex socio-technical systems, as you can clearly see the chain of events that could lead to a catastrophic system failure. It is an effective tool for finding the correct chain of events through a process of elimination.
  • 14. EXAMPLE FAULT TREE Simple fault tree for a fire breakout
  • 15. RESULT OF INVESTIGATION Organizational Technical causes causes NASA Left foam bi- Management pod collides Nasa’s Shuttle over Shuttle failed to act with RCC budget is cut heats disintegration on known panels on problem wing
  • 16. ACADEMIC LITERATURE Studying organisational cultures and their effects on safety (Hopkins, 2006) Beyond Normal Accidents and High Reliability Organizations: The Need for an Alternative Approach to Safety in Complex Systems ( Marais, Dulac, & Leveson, 2004) Both agree that a major factor contributing towards the accident was NASA organizational culture. A Framework for Dynamic Safety and Risk Management Modeling in Complex Engineering Systems (Dulac, 2007) Takes it a step further and analyzes NASA using STAMP modeling the paper finds that STAMP is ideally sited with its control framework to model every aspect of NASA: social, organizational, technical and how they interact.
  • 17. CHALLENGER DISASTER On January 28, 1986 the space shuttle Challenger (STS-51-L) broke apart in flight, minutes after take off, killing all of its 7 crew members. STS-51-L flight insignia
  • 18. INVESTIGATION INTO THE ACCIDENT Above image shows the Challenger disintegrating 73 seconds after launch
  • 19. ROGERS COMMISSION (PRESIDENTIAL COMMISSION on the Space Shuttle Challenger Accident, 1986) Presidential Commission on the Space Shuttle Challenger Accident was an independent investigation into the accident. Solid Rocket booster The investigation found that the right solid rocket booster become separated, causing damage to the external tank. This led to the destruction of the shuttle by aerodynamic forces.
  • 20. The investigation found that the O-ring joint failure was the cause of the accident. The O-ring sealed a joint connecting the solid rocket booster to the main part of the shuttle Both the primary and secondary O-rings failed, allowing heated gases and flames to escape and make contact with the external tank, causing a structural failure.
  • 21. FOCUS OF INVESTIGATION Technical The O-ring joint was know to be inadequate and was in the process of being redesigned. It was found that in pervious flights O-ring erosion had occurred which rendered the secondary O-ring useless. Organizational On the day of launch engineers were concerned that the temperature was too low to launch(-2.2C lowest launch temperature recorded) and that there was to much ice on the shuttle. O-rings would not perform correctly at this temperature. NASA management was told of this issue but it was deemed an acceptable risk and the launch went ahead.
  • 22. RESULT OF INVESTIGATION Technical concerns- the sold rocket boosters were redesigned. Organizational concerns- A new safety office was created to allow better communication and risk assessment. Cause Ice conditions not Root assessed correctly Organizational O-ring failure Shuttle caused rocket disintegrated booster to detach Design flaw in O- rings Technical
  • 23. ACADEMIC LITERATURE Understanding the Challenger Disaster: Organizational Structure and the Design of Reliable Systems (Heimann, 1993) A critical analysis of factors related to decisional processes involved in the challenger disaster (Gouran , Hirokawa,, & Martz, 1986) These papers both focus on the decision making process at NASA and why it how this process can be made more robust.
  • 24. REFERENCES Marais, K., Dulac, N., & Leveson, N. (2004). Beyond Normal Accidents and High Reliability Organizations: The Need for an Alternative Approach to Safety in Complex Systems. Cambridge. Board, Columbia Accident Investigation. (2003). Columbia Accident Investigation Board Vol 1. Washington, D.C: Columbia Accident Investigation Board. Dulac, N. (2007). A Framework for Dynamic Safety and Risk Management Modeling in Complex Engineering Systems. Cambridge: MIT. Gouran , D. S., Hirokawa,, R. Y., & Martz, A. E. (1986). A critical analysis of factors related to decisional processes involved in the challenger disaster. Central States Speech Journal , 37. Heimann, C. F. (1993). Understanding the Challenger Disaster: Organizational Structure and the Design of Reliable Systems. The American Political Science Review , 87, 421-435. Hopkins, A. (2006, December). Studying organisational cultures and their effects on safety. Safety Science , 44, pp. 875-889. Keong, T. H. (1997, July 9). Risk Analysis Methodologies. Retrieved June 8, 2012, from pacific.net.sg: http://home1.pacific.net.sg/~thk/risk.html PRESIDENTIAL COMMISSION on the Space Shuttle Challenger Accident. (1986). Report of the PRESIDENTIAL COMMISSION on the Space Shuttle Challenger Accident. Washington, D.C.: PRESIDENTIAL COMMISSION on the Space Shuttle Challenger Accident.