05.04.2013 Views

The Nimrod Review - Official Documents

The Nimrod Review - Official Documents

The Nimrod Review - Official Documents

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

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

11.6 Second, the NSC became a documentary exercise and an end in itself. As explained in Chapter 9, the<br />

raison d’etre of a ‘Safety Case’ is to ‘identify, assess and mitigate’ all potential significant hazards to pieces<br />

of equipment, platforms or installations, including hidden, or previously unidentified, hazards. Lord Cullen<br />

regarded the drawing up of a ‘Safety Case’ as merely a means to achieving this end, i.e. it was intended to<br />

provide a structure for critical analysis and thinking, or a framework to facilitate a thorough assessment and<br />

addressing of serious risks. Unfortunately, in the case of the NSC, the production of a ‘Report’ became an end<br />

in itself. Critical analysis descended into a paperwork exercise. Compliance with regulations was the aim. This<br />

was partly because thinking on all sides was fatally undermined that by the assumption that the <strong>Nimrod</strong> was<br />

safe anyway.<br />

11.7 Third, the seeds of these problems were partly sown by BP1201 which espoused an “ implicit Safety Case”<br />

for legacy aircraft based on a “basic assumption that the aircraft is already operating to acceptable levels of<br />

safety.” 3 <strong>The</strong> notion of an “implicit” Safety Case is, however, something of an oxymoron. A Safety Case is<br />

intended to be an exercise in critical thinking and actual assessment of risk. An “implicit” Safety Case, based on<br />

the assumption there are no actual risks, is the antithesis of this. First, contrary to the philosophy expounded by<br />

Lord Cullen, 4 an “implicit” Safety Case sanctions reliance on past success as a guarantee of future safety in lieu<br />

of a proper risk analysis based on sound engineering practice. Second, it encourages ‘documenting’ the past<br />

rather than carrying out a fresh assessment of the potential risks in the future, and thus is an invitation to those<br />

inclined to paperwork exercises.<br />

11.8<br />

264<br />

5 Fourth, as Professor John McDermid pointed out to the <strong>Review</strong>, there is also a danger in merely contracting for<br />

a Safety Case ‘report’, as opposed to a proper ‘risk analysis’. If one contracts for the former, then this is precisely<br />

what one is likely to get. <strong>The</strong> <strong>Nimrod</strong> IPT contracted for a “Safety Case report” to comply with its obligations<br />

under BP1201. <strong>The</strong> <strong>Nimrod</strong> IPT’s own Safety Management Plan (SMP) highlighted that there was already a<br />

“high level of corporate confidence in the safety of the <strong>Nimrod</strong> aircraft”, but a lack of “structured evidence”<br />

to support that confidence. This was the context in which the <strong>Nimrod</strong> IPT instructed BAE Systems to develop a<br />

baseline safety case report. 6<br />

3 Chapter 9, paragraph 9.58.<br />

4 Subsequently recognised in the White Booklet in 2002, which stated that the non-occurrence of an accident was no guarantee of a safe system.<br />

5 Professor of Software Engineering and leader of the High Integrity Systems Engineering Group within the Department of Computer Science at the<br />

University of York.<br />

6 Cf. to similar effect the comments of the (then) IPTL at the Inaugural PSWG meeting on 18 March 2002, see paragraph 10.45 of Chapter 10A.

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

Saved successfully!

Ooh no, something went wrong!