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

422<br />

between the engine bays and including the fuselage under-floor compartments) would be the starting point for<br />

the further analysis to satisfy the BOI recommendation.<br />

<strong>The</strong> problems identified<br />

15.27<br />

15.28<br />

Having examined the existing Pro-Formas for the 11 priority zones, the front line operators from Kinloss<br />

reported that they found the Pro-Formas difficult to follow and raised a number of observations, including the<br />

following:<br />

15.27.1 <strong>The</strong>re was a lack of standard terminology in the Pro-Formas.<br />

15.27.2 BAE Systems’ recommendations in respect of the “further work” that was required needed to be<br />

clearly identified.<br />

15.27.3 <strong>The</strong>re was a lack of standard format for the zonal Pro-Formas.<br />

15.27.4 Some of the Pro-Formas contained erroneous mitigation.<br />

15.27.5 Some of the Pro-Formas showed a confusion between the MR2 and R1.<br />

Following discussions at the SC2 meetings, it was decided between the <strong>Nimrod</strong> IPT and BAE Systems that the<br />

structure of the Pro-Forma would be modified. <strong>The</strong> original Pro-Forma for each hazard included all possible<br />

causes of the hazard and all mitigations; this led to difficulty in identifying which mitigation applied to which<br />

cause. In order to improve the clarity of the Pro-Formas, it was decided that individual causes and their specific<br />

mitigations should be separated out and placed in their own individual Pro-Forma.<br />

QinetiQ input<br />

15.29<br />

15.30<br />

15.31<br />

During the course of the early SC2 meetings, the QinetiQ Capability Leader – Safety raised a number of issues<br />

and concerns about the underlying structure of the Safety Case with the <strong>Nimrod</strong> IPT. 37 <strong>The</strong>se included the<br />

following:<br />

15.29.1 It was difficult to see the linkage between accidents and hazard controls.<br />

15.29.2 <strong>The</strong> subsuming of individual hazards into one hazard made the linkage of hazards to accidents<br />

incorrect.<br />

15.29.3 It was difficult to identify what the specific controls were, and the status of their implementation.<br />

15.29.4 Accident controls had been incorrectly applied to hazards, resulting in an incorrect definition of hazard<br />

probabilities, e.g. fire extinguishers may mitigate the severity of the accident but do not mitigate the<br />

probability of a hazard occurring.<br />

At the meeting on 5 February 2008, QinetiQ also suggested that the method by which the accident probability<br />

was defined was incorrect. QinetiQ had additionally highlighted in a Platform Safety <strong>Review</strong>, 38 that the existing<br />

Hazard Log used the worst-case hazard probability as the overall accident probability. <strong>The</strong> overall accident<br />

probability for a zone is, however, a combination of the probability of all the potential hazards and their causes,<br />

not just the probability of the worst-case scenario occurring.<br />

It is, therefore, apparent that, contrary to what BAE Systems sought to suggest, the early meetings identified<br />

problems with the NSC which went far beyond the mere correction of a few factual errors and re-categorisation<br />

of associated hazards. Rather, it was discovered and determined that there were significant underlying structural<br />

issues to be addressed, coupled with flaws in the logical analysis.<br />

37 QINETIQ/EMAE/lx/SES/<strong>Nimrod</strong>/597732/009/Platform Safety <strong>Review</strong>.<br />

38 Ibid.

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

Saved successfully!

Ooh no, something went wrong!