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

No cross-reference to functional hazard Pro-Forma Hazard H34<br />

11.73<br />

280<br />

No regard or cross-reference seem to have been made to the warning in the functional hazard Pro-Forma<br />

completed for the whole fuel system by Mech Systems on 30 July 2004 (Functional Hazard H34) which listed a<br />

number of fuel leak incidents and stated:<br />

“5. Conclusion…<br />

<strong>The</strong> design of the fuel system is such that the LRU failures can be tolerated, with the system<br />

being managed by the flight engineer. <strong>The</strong> trend of incidents with respect to leakage from<br />

fuel couplings and from the Jettison pipe flap areas poses more of a zonal hazard than a<br />

functional one.” (emphasis added)<br />

Leak paths notoriously unpredictable<br />

11.74 BAE Systems further sought to justify the classification of “Improbable” (1 x 10-6 to 10-7 ) to the <strong>Review</strong> on the<br />

additional basis that “any leak would still have to migrate to a source of ignition, which is clearly always less<br />

than a certainty”. 37 In my view, this sort of ex post facto rationalisation was grasping at straws and unhelpful.<br />

<strong>The</strong>re was no indication that this was a part of the thought process at the time. Nor should it have been, given<br />

the notorious unpredictability of leak paths.<br />

Causation – use of MRA4 generic data<br />

11.75<br />

It is clear, in my view, that the inappropriate use by BAE Systems of MRA4 generic data to sentence MR2 and<br />

R1 hazards was the key factor which led to an incorrect and overly optimistic probability being ascribed to<br />

Hazard H73. It is equally clear that, but for the inappropriate use of MRA4 generic data, the outcome would<br />

have been different. As Witness R [BAE Systems] admitted in interview, without the MRA4 generic data, Mech<br />

Systems would not have been able to progress the sentencing exercise and would have had to go back to<br />

the Airworthiness Department and ask for further information. It is likely that, in these circumstances, the<br />

Airworthiness and Mech Systems Departments would have been forced to look hard at the fault data in the RAF<br />

MDS. Moreover, when BAE Systems came to conduct its review of the Safety Case in 2008 (Safety Case 2), the<br />

maintenance personnel from the <strong>Nimrod</strong> Servicing Group estimated that the probability of fuel coupling leaks<br />

was far more frequent than the MRA4 generic data suggested.<br />

(13) When presenting the results of its work at the ‘Customer Acceptance Conference’,<br />

BAE Systems misrepresented that it had completed the task and deliberately<br />

did not disclose to the <strong>Nimrod</strong> IPT or QinetiQ the actual percentage figures for<br />

the large proportion of hazards which it had left “Open” and “Unclassified” or<br />

otherwise draw attention to the large gap remaining in its analysis.<br />

11.76<br />

In my judgment, BAE Systems is open to severe censure for giving the misleading impression at the Customer<br />

Acceptance Conference that it had completed the NSC task satisfactorily and for failing to disclose to the <strong>Nimrod</strong><br />

IPT or QinetiQ the known percentage figures for the large proportion of hazards which it had left “Open” and<br />

“Unclassified” (many with only vague recommendations of ‘further work’ being required) and otherwise failing<br />

to draw its customer’s attention to the large gap remaining in its analysis. I am satisfied, for the reasons given<br />

below, that this was a conscious and deliberate decision on the part of the senior BAE Systems personnel<br />

present because the figures were embarrassing and they wanted to avoid any argument with the <strong>Nimrod</strong> IPT at<br />

the meeting as to whether the NSC task should be signed off or not.<br />

37 BAE Systems’ Written Submissions to the <strong>Review</strong>.

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

Saved successfully!

Ooh no, something went wrong!