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.

Chronology – three phases<br />

10A.8<br />

Chapter 10A – <strong>Nimrod</strong> Safety Case: <strong>The</strong> Facts (Phases 1 and 2)<br />

<strong>The</strong> chronology of what took place during the drawing up of the NSC conveniently falls to be considered in<br />

three phases:<br />

(1) Phase 1 conducted by BAE Systems (April 2001 to April 2003): following the initial scoping of the NSC<br />

task, the carrying out of the hazard identification task by BAE Systems (Phase 1).<br />

(2) Phase 2 conducted by BAE Systems (August 2003 to September 2004): the carrying out of the hazard<br />

analysis and hazard mitigation tasks by BAE Systems, and the handing over of the six NSC Reports by<br />

BAE Systems to the <strong>Nimrod</strong> IPT (Phase 2).<br />

(3) Third Phase conducted by the <strong>Nimrod</strong> IPT (November 2004 to March 2005): Following handing over<br />

of the NSC Reports by BAE Systems to the <strong>Nimrod</strong> IPT and the ‘signing-off’ of the task (supported<br />

by QinetiQ), the <strong>Nimrod</strong> IPT then proceeded to sentence the remaining hazards left “Open” by BAE<br />

Systems, and the NSC for both <strong>Nimrod</strong> MR2 and R1 was declared completed in March 2005. 8<br />

Phase 1 conducted by BAE Systems (April 2001 to April 2003)<br />

10A.9<br />

10A.10<br />

10A.11<br />

10A.12<br />

10A.13<br />

10A.14<br />

<strong>The</strong> <strong>Nimrod</strong> IPT determined early in 2001 to develop an ‘explicit’ Safety Case for the <strong>Nimrod</strong> fleet, and to task<br />

BAE Systems to draw it up. Whilst, technically under BP1201, the <strong>Nimrod</strong> IPT could have relied on the Military<br />

Airworthiness (MA) Release as an ‘implicit’ Safety Case, 9 it was clearly desirable for a ‘legacy’ platform of<br />

the age of the <strong>Nimrod</strong> to have an ‘explicit’ Safety Case. BP1201 provided that a Safety Case must provide a<br />

“credible” justification of safety and must be “consistent, complete and comprehensible”. 10<br />

<strong>The</strong> scope of the NSC task to be carried out by BAE Systems was initially laid down by the <strong>Nimrod</strong> IPT in<br />

a Post Design Services (PDS) Task Request Form sent to BAE Systems on 11 April 2001. 11 This outlined the<br />

respective responsibilities within the IPT and RAF for the NSC, the strategy to be employed, and the scope of<br />

BAE Systems’ involvement:<br />

As to responsibilities, the following were to said to have key roles in developing the NSC: (1) all IPTs were<br />

required to establish a Platform Safety Working Group (PSWG) “to develop and maintain” a platform Safety<br />

Case; (2) the <strong>Nimrod</strong> IPTL would chair the PSWG and was responsible for the NSC; (3) the <strong>Nimrod</strong> Head of<br />

Air Vehicle (NIM(ES)AV) was responsible for managing the development of the NSC on behalf of the IPTL; and<br />

(4) the Fixed Wing Airworthiness Management Group (FWAMG) would “monitor” the implementation of the<br />

NSC on behalf of the Defence Aviation Safety Board (DASB). I discuss later the extent to which, if any, of the<br />

above, in fact, had any real involvement in the development of the NSC.<br />

As to strategy, it was envisaged there would be four phases for Safety Cases for ‘legacy’ platforms: (1)<br />

Phase 1: develop a strategy to construct the Safety Case; (2) Phase 2: develop a strategy for the ongoing risk<br />

management of the <strong>Nimrod</strong>; (3) Phase 3: construct the Safety Case; and (4) Phase 4: manage the safety of<br />

the <strong>Nimrod</strong> throughout its operational life.<br />

As to BAE Systems’ involvement, it was envisaged that much of the work would be based on BAE Systems’<br />

information as the aircraft DA. It was expected that BAE Systems Chadderton would “assess the level of<br />

information currently available to it” and provide: (a) an initial “hazard assessment” carried out at system<br />

level; (b) a detailed “Fault Tree” analysis at system level; and (c) a “safety assessment” detailing the findings<br />

of the studies and assessing the risk of functional failures.<br />

BAE Systems was given two initial tasks. First, to provide an initial assessment of the current availability of<br />

appropriate Hazard Data and Fault Tree Analysis data, i.e. “how much data is readily available within the ADA<br />

for the <strong>Nimrod</strong> Platform”. Second, to provide a business strategy to develop a Safety Case by 31 December<br />

2002 and costings within 60 days, the overall scope of the work being envisaged as “considerable”. <strong>The</strong><br />

second task was carried out. <strong>The</strong> first was not.<br />

8 E-mail from Frank Walsh to BAE Systems, dated 16 March 2005.<br />

9 BP1201, paragraph 12.<br />

10 Ibid, paragraph 9.<br />

11 PDS Task Request Form number AV(PDS)814 drafted by the <strong>Nimrod</strong> IPT (NIM(ES)AV(PDS), SPTO).<br />

193

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

Saved successfully!

Ooh no, something went wrong!