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.

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

10A.28 <strong>The</strong> Feasibility Study explained that the methodology to be employed was the “top level down” approach<br />

considered acceptable for legacy aircraft by BP1201 and the <strong>Nimrod</strong> SMP. 29 Fault Tree Analysis (FTA) was<br />

recommended. Goal Structured Notation (GSN) (an illustrative technique which provides a useful structured<br />

way of presenting a complex safety argument) 30 would be used to demonstrate the achievement of the<br />

relevant goals supported by strategies and evidence. <strong>The</strong> key goals were:<br />

10A.29<br />

Top level goal: “<strong>The</strong> aircraft is deemed acceptably safe to operate and maintain within specified<br />

contexts” (Goal 1);<br />

First sub-goal: “All identified potential safety hazards risks be demonstrated as having been<br />

mitigated to a level that is [ALARP] or eliminated where appropriate” (Goal 2); and<br />

Second sub-goal: “All relevant safety and certification requirements and standards are demonstrated<br />

as having been met” (Goal 3).<br />

<strong>The</strong> Feasibility Study promised a Baseline Safety Case Report (BLSC Report) which would be a ‘snapshot in<br />

time’ in which “all potential safety hazards will have been identified and appropriately addressed”. 31 <strong>The</strong> substrategy<br />

to achieve the first sub-goal included “Each potential safety hazard mitigated to a level of ALARP<br />

or eliminated where possible.” 32 A three-stage ‘iterative’ process33 was envisaged, which Witness A [BAE<br />

Systems] explained in interview with the <strong>Review</strong> was to be based on “best engineering judgment”, namely:<br />

(a) identify hazard; (b) quantify and assess hazard risk; and (c) mitigate hazard as necessary.<br />

Warning regarding <strong>Nimrod</strong> in-service statistical data<br />

10A.30<br />

<strong>The</strong> Feasibility Study sounded a strong note of caution in relation to the use of statistical data in isolation. It<br />

warned that the small <strong>Nimrod</strong> fleet size and low statistical population “... lead to relatively low confidence<br />

levels in any statistical data based on in-service failure rates of a unit or system”. 34 Regrettably, this warning<br />

was eventually ignored by BAE Systems itself and the <strong>Nimrod</strong> IPT, as explained below.<br />

Joint Working Group<br />

10A.31<br />

10A.32<br />

<strong>The</strong> Feasibility Study recommended the setting up of a Safety Case Working Group jointly composed of BAE<br />

Systems and <strong>Nimrod</strong> IPT “Specialist Engineers close to both projects”. It was envisaged that the joint Working<br />

Group would meet regularly to ensure joint input into all stages of the Safety Case process, i.e. the identification<br />

of hazards, determining their cause and effect, the mitigation of all hazards and the consequent population<br />

of the hazard log. 35 <strong>The</strong> setting up of a joint Safety Case Working Group consisting of approximately eight<br />

people “split between BAE Systems and MoD chosen for their genuine specialist knowledge” to carry out the<br />

“identification and addressing of all hazards”, was subsequently highlighted by Chris Lowe at the Inaugural<br />

<strong>Nimrod</strong> PSWG Meeting on 18 March 2002. 36 Unfortunately, the NSC process turned out to be far from<br />

joint: save for the preparation of the Fault Tree Analysis, BAE Systems did all three stages leading to the NSC<br />

without significantly involving the <strong>Nimrod</strong> IPT or <strong>Nimrod</strong> operators. This was a fundamental mistake.<br />

<strong>The</strong> upbeat tone of BAE Systems’ Feasibility Study would have given the IPT further confidence that BAE<br />

Systems was indeed ready, willing and able to carry out the NSC task as required. It was understandable<br />

that the IPT should have confidence in BAE Systems. It was, after all, the DA for the <strong>Nimrod</strong> and the Original<br />

Equipment Manufacturer (OEM) for both <strong>Nimrod</strong> types. It retained ownership of the original certification<br />

for the civil certification for the Comet, and much of the design data and sub-data that was part of the<br />

civil certification. BAE Systems was also carrying out an increasing amount of <strong>Nimrod</strong> Line 4 (i.e. deep)<br />

29 Ibid, paragraph 2, page 7.<br />

30 www.yellowbook-rail.org.uk/site/events/ybug2007/yellow%20book%20gsn%20presentation%20-%20kelly.ppt<br />

31 Ibid, paragraph 3, page 7.<br />

32 Ibid, paragraph. 6.6<br />

33 Ibid, page 9.<br />

34 Ibid, paragraph 8.1.3.<br />

35 BAE Systems Proposal to <strong>Nimrod</strong> (ES) IPT – <strong>Nimrod</strong> Baseline SC (Phase 1) (August 2002) (and see paragraph 10.2 of the Feasibility Study).<br />

36 Chris Lowe’s presentation to the Inaugural <strong>Nimrod</strong> PSWG Meeting 18 March 2002.<br />

197

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

Saved successfully!

Ooh no, something went wrong!