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

11.56<br />

11.57<br />

276<br />

‘generic’ MRA4 data to sentence MR2 and R1 hazards (see further below). By 16 August 2004, the situation<br />

had become critical with some 50 out of 104 hazards completed. By this stage, there was a serious backlog in<br />

the Mech Systems and Electrical Systems departments. Nevertheless, BAE Systems management continued to<br />

press for completion of the Task by the end of August 2004, because the project was perceived as prestigious<br />

and important for those involved and for future BAE Systems business. Chris Lowe demanded a “final push”<br />

for completion by the end of the week. It is no coincidence that Hazard H73 was part of this final push. In a<br />

matter of hours on 26 August 2004, Witness T [BAE Systems] sent no fewer than four completed Pro-Formas<br />

(Hazards H69, H76, H77 and H93) back to the Mechanical Systems Department. On 30 August 2004, the day<br />

before the Acceptance Conference, second issues of six hazards (Hazards H70, H72, H73, H74, H75 and H77)<br />

were formally signed-off and subsequently approved by Eric Prince.<br />

<strong>The</strong> dangers of putting undue time pressures on engineers was put by Counsel to the <strong>Review</strong> to Richard<br />

Oldfield:<br />

“MR PARSONS QC: <strong>The</strong> danger with ‘final pushes’ is that there are often casualties, aren’t there?<br />

MR OLDFIELD: I don’t think that would ever be the case, in terms of the professionalism of completing<br />

the task from the engineers.<br />

MR PARSONS QC: If you put engineers under pressure to complete a task in a short period of time,<br />

there is a risk that corners will be cut and mistakes will be made?<br />

MR OLDFIELD: I think we were just emphasising the fact that we wanted one last effort to actually<br />

complete it, as best we could. <strong>The</strong>re’s – I wouldn’t say there was any undue pressure that had been<br />

put on top of the engineers on that. <strong>The</strong>re was no additional, you know, excessive man hours that was<br />

worked for that last final push. It was just a case of emphasising the need to put extra effort in, in the<br />

last – last couple of weeks before the acceptance conference.”<br />

As I explain in further detail below, the quality of ‘assessment’ and ‘mitigation’ analysis done by BAE Systems in<br />

relation to the remaining hazards suffered as a result of these time, resource and management pressures.<br />

(12) BAE Systems used inappropriate data to sentence risks (including Hazard H73).<br />

11.58<br />

In my judgment, BAE Systems resorted to using inappropriate data to sentence hazards. This was due to time<br />

pressures, and a general lassitude about how hazards were closed off.<br />

Inappropriate use of MRA generic data<br />

11.59<br />

11.60<br />

<strong>The</strong> months of July and August 2004 were undoubtedly a time of growing pressure for those involved in the<br />

NSC within BAE Systems, as explained above. By 7 July 2004, Mech Systems’ task was only 20% done and only<br />

41 out of 104 hazards had been returned and 63 still remained to be done. Completion was subsequently put<br />

back to the end of August 2004. On 8 July 2004, following discussion within BAE Systems initiated by Witness<br />

R [BAE Systems] as to whether there were any “standard values” which could be used to sentence hazards,<br />

Witness S [BAE Systems] circulated an e-mail to the specialist engineers attaching MRA4 generic probability<br />

data which he said had been extracted from the <strong>Nimrod</strong> MRA4 System Safety Working Practices (Annex G). 32<br />

<strong>The</strong> generic failure types and probabilities were derived from the in-service data obtained from a number of<br />

other aircraft, such as the Tornado and the Hawk, and (apparently) gave a standard failure probability rating for<br />

a number of common failure types, including that for a failure of a “fuel pipe and associated coupling”, which<br />

was ascribed a failure probability of 1E-6. 33 Witness S [BAE Systems]’s email was copied to Chris Lowe, Richard<br />

Oldfield and Eric Prince.<br />

Chris Lowe’s evidence in interview on the use of MRA4 data was unsatisfactory. He said that he had been aware<br />

that the data existed and had been sent to Witness S [BAE Systems] and Witness K [BAE Systems], but professed<br />

not to have been aware at the time of the NSC as to “exactly” how they used that data, although he would<br />

32 AWN/NIM/897 Issue 7 (Revision 7, Version 2).<br />

33 This generic probability data had previously been agreed with the <strong>Nimrod</strong> MRA4 IPT for use for the <strong>Nimrod</strong> MRA4.

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

Saved successfully!

Ooh no, something went wrong!