05.04.2013 Views

The Nimrod Review - Official Documents

The Nimrod Review - Official Documents

The Nimrod Review - Official Documents

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>The</strong> <strong>Nimrod</strong> <strong>Review</strong><br />

NASA Space Shuttle “Columbia” (2003)<br />

17.1<br />

448<br />

“<strong>The</strong> dwindling post Cold War Shuttle budget that launched NASA leadership on a<br />

crusade for efficiency in the decade before Columbia’s final flight powerfully shaped the<br />

environment in which Shuttle managers worked. <strong>The</strong> increased organisational complexity,<br />

transitioning authority structures and ambiguous working relationships that defined the<br />

restructured Space shuttle program in the 1990s created the turbulence that repeatedly<br />

influenced decisions made before and during STS-107”.<br />

(Columbia Accident Investigation Board Report, 2003)<br />

<strong>The</strong>re are uncanny, and worrying, parallels between the organisational causes of the loss of <strong>Nimrod</strong> XV230 and<br />

the organisational causes of the loss of the NASA4 Space Shuttle “Columbia” in 2003.<br />

17.2 Columbia was lost on 1 February 2003 as a result of a breach in the thermal protection system on the leading<br />

edge of the left wing. This was caused by a piece of insulating foam which, after launch, separated from the left<br />

bipod ramp section of the external tank, and struck the leading edge of the port wing in the vicinity of the lower<br />

half of the reinforced carbon-carbon panel number 8. During re-entry to the Earth’s atmosphere this breach in<br />

the thermal protection system proved fatal: it allowed super-heated air to penetrate through the leading edge<br />

and progressively melt the aluminium structure of the port wing, resulting in a weakening of the structure until<br />

increasing aerodynamic forces caused loss of control, failure of the wing, and the breakup of the orbiter.<br />

Columbia Accident Investigation Board Report (2003)<br />

17.3<br />

5 <strong>The</strong> Columbia Accident Investigation Board (CAIB) emphasised the importance of identifying the fundamental<br />

‘organisational causes’ of accidents rather than focusing merely on errors and omissions by individuals:<br />

“Many accident investigations make the same mistakes in defining causes. <strong>The</strong>y identify<br />

the widget that broke or malfunctioned, then locate the person most closely connected<br />

with the technical failure: the engineer who miscalculated an analysis, the operator who<br />

missed signals or pulled the wrong switches, the supervisor who failed to listen, or the<br />

manager who made bad decisions. When causal chains are limited to technical flaws<br />

and individual failure, the ensuing responses aimed at preventing a similar event in the<br />

future are equally limited: they aim to fix the technical problem and replace or retrain the<br />

individual responsible. Such corrections lead to a misguided and potentially disastrous<br />

belief that the underlying problem has been solved. <strong>The</strong> Board did not want to make these<br />

errors. A central piece of our expanded cause model involves NASA as an organisational<br />

whole.” 6<br />

17.4 <strong>The</strong> CAIB found that the organisational causes of the loss of Columbia were rooted in the Space Shuttle’s history<br />

and culture:<br />

“<strong>The</strong> organisational causes of this accident are rooted in the Space Shuttle’s history and<br />

culture, including the original compromises that were required to gain approval for the<br />

Shuttle program, subsequent years of resource constraints, fluctuating priorities, schedule<br />

pressures, mischaracterisations of the Shuttle as operational rather than developmental,<br />

and lack of an agreed national vision. Cultural traits and organisational practices detrimental<br />

to safety and reliability were allowed to develop, including: reliance on past success as a<br />

substitute for sound engineering practices (such as testing to understand why systems<br />

were not performing in accordance with requirements/specifications); organisational<br />

barriers which prevented effective communication of critical safety information and stifled<br />

professional differences of opinion; lack of integrated management across program<br />

4 U.S. National Aeronautics and Space Administration.<br />

5 CAIB was set up by President George W. Bush and reported in August 2003.<br />

6 CAIB Report, Chapter 7, page 177.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!