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 />

9.57<br />

178<br />

BP1201 recognised that such an ‘implicit’ Safety Case was less desirable than an ‘explicit’ one and set out in<br />

Annex C a strategy for the safety assessment of legacy systems. <strong>The</strong> ‘strategy’ laid down in BP1201 comprised<br />

four phases:<br />

9.57.1 Phase 1 – Form a strategy for constructing the Safety Case: This phase was to culminate in the completion<br />

of an ESMP for the Safety Case which had been reviewed and endorsed by the PSWG.<br />

9.57.2 Phase 2 – Form a strategy for managing the acceptability of safety throughout the aircraft’s operational<br />

life: This would rely upon the implicit Safety Case and subsequent changes being acceptably demonstrated<br />

within an explicit Safety Case.<br />

9.57.3 Phase 3 – Construct the Safety Case: <strong>The</strong> explicit Safety Case structure was to contain the following<br />

components: (i) Safety Management Plan; (ii) (Limited) Safety Assessment; (iii) Hazard log; and (iv) Safety<br />

Case Report. It was to contain a safety assessment which provided an assurance that all the top level<br />

hazards presented by the aircraft had been satisfactorily managed during its operational life.<br />

9.57.4 Phase 4 – Manage the acceptability of safety throughout the aircraft’s operational life: Current<br />

airworthiness related management systems, i.e. change control and reporting procedures, would have<br />

to be adapted to support the explicit Safety Case.<br />

9.58 In my view, there are a number of fundamental problems with, or objections to, the notion of an ‘ implicit’ Safety<br />

Case. First, it is something of an oxymoron: one either prepares a proper ‘Safety Case’ or one does not. Second,<br />

the concept of an “implicit Safety Case” does not comply with Lord Cullen’s concept of a “thorough assessment”<br />

of the risks posed by a platform. This is because, in effect, the notion assumes that a legacy aircraft is safe merely<br />

because it was built to design and has been operating without mishap for a number of years. Third, the very<br />

fact that BP1201 expressly permitted such an assumption is, perhaps, undesirable in itself, because it may tend<br />

to undermine the resolve of those carrying out the Safety Case. 84 It is also troubling that the ‘Phase 1 strategy’<br />

in Annex C of the original BP1201 referred to above included the statement: “make the basic assumption that<br />

the aircraft is already operating to acceptable levels of safety and determine that level of safety.” Any genuine<br />

assessment should, however, be a matter of engineering judgment, not assumption. Otherwise, the process is<br />

self-defeating.<br />

9.59<br />

It should be noted that Issue 2 of BP1201, published in September 2002, did not include the guidance contained<br />

in the former Annex C, although it continued to endorse the notion of an implicit Safety Case for legacy<br />

systems. Otherwise, it largely followed the original BP1201, with the addition of the further comment that the<br />

purpose of a hazard Log was “to provide a ‘corporate memory’ for IPT managers, and potentially, operators, of<br />

the hazards, associated safety risks and mitigating action”. 85<br />

84 C.f. the reference to the NSC being “underpinned” by the in-service history in BAES Equipment Safety Case Baseline Report No. MBU-DEF-C-NIM-<br />

SC0713 dated September 2004, page 4.<br />

85 BP1201, Issue 2, paragraph 14.

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

Saved successfully!

Ooh no, something went wrong!