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

228<br />

10A.174.3 Section 6 of the Pro-Forma incorrectly stated that the Cross-Feed duct “is only pressurised when<br />

the cross-feed pipe is open, i.e. during engine start”, and failed to take into account the lengthy<br />

periods the cross-feed duct can be pressurised (at a working temperature of up to 420°C) when<br />

feeding the SCP.<br />

10A.174.4 Section 6 of the Pro-Forma stated that “From in-service data the potential for fuel pipe leakage<br />

is given as Improbable”, i.e. 10 -6 . Any line engineer would have known this was unrealistic.<br />

10A.174.5 <strong>The</strong> Pro-Forma failed to pick up on the zonal risk presented by the location and proximity of the<br />

No. 1 fuel tank blow-off valve immediately forward of the starboard No. 7 Tank Dry Bay, such that<br />

fuel expelled from the blow-off valve could track back onto the SCP pipe elbow and ignite.<br />

10A.175 I deal with these errors in more detail in Chapter 11. I conclude that the Pro-Forma for Hazard H73 was a sloppy<br />

and muddled piece of work, carried out under time pressure without sufficient guidance or management<br />

oversight. It should be emphasised that some of the mistakes in the Pro-Forma were very basic indeed.<br />

For instance, the mistake in relation to the Cross-Feed duct being pressurised “only…during engine start”<br />

displayed a startling lack of knowledge by BAE Systems about its own aircraft. Anybody who knew anything<br />

about <strong>Nimrod</strong>s would know the cross-feed duct was bound to be used in flight (a) to re-start engines which<br />

had been routinely shut down and (b) to run the SCP.<br />

Last minute rush: task not completed by 31 August<br />

10A.176 <strong>The</strong> process of completing Pro-Formas continued right up to the Customer Acceptance Conference on 31<br />

August 2004. On 28 August 2004, Witness K [BAE Systems] reported to Eric Prince that Mech Systems had<br />

completed 49 out of 58 Pro-Formas, Electrical Systems had completed 18 out of 35 Pro-Formas and Avionics<br />

had completed 10 out of 12. On the afternoon of 30 August 2004, the day before the Customer Acceptance<br />

Conference, Witness K [BAE Systems] reported to Eric Prince that Mech Systems had completed 52 of the<br />

Pro-Formas with 6 “on-going”, and Electrical Systems had completed 27 of the Pro-Formas with several<br />

for signature and 4 “on-going”. In fact, several Pro-Formas were not completed by Electrics until after the<br />

Customer Acceptance Conference: Hazards H67, H78, and H79 were completed by Witness T [BAE Systems]<br />

on or after 2 September 2004; and Hazard H63 was not completed until 24 September, i.e. somewhat<br />

curiously after the final hard copy of the report had already been circulated to Frank Walsh.<br />

FSD and Serous Fault Signals: word search<br />

10A.177 A further troubling feature is that, as late as 24 August 2004, the results of a word search on the VC10 &<br />

<strong>Nimrod</strong> Flight Safety Database in relation to ‘fire’, ‘smoke’, ‘fumes’, ‘burning’ and ‘smell’ was circulated. It is<br />

not clear, however, as to what use, if any, this research was put.<br />

16 August: BAE Systems’ internal “Independent <strong>Review</strong>”<br />

10A.178 At the 16 August 2004 meeting, it had been decided that Chris Lowe should request Witness V [BAE Systems]<br />

or Witness A [BAE Systems] to carry out an ‘independent’ review of the NSC work prior to the Customer<br />

Acceptance Conference. Witness A [BAE Systems] was ultimately contacted on 24 August 2004 by Chris<br />

Lowe, who e-mailed him with copies of what were referred to as “the major reports in support of the<br />

safety case you may wish to peruse”. But only copies of three out of the six ‘deliverable’ reports were in fact<br />

attached, namely, the Fire & Explosion Report, <strong>Review</strong> of Accident History, and Certification Statement, the<br />

latter two of which comprised essentially factual summaries as opposed to analytical analysis. Witness A<br />

[BAE Systems] was not shown the BLSC Reports for the MR2 and R1. Nor was he asked to conduct a proper<br />

“independent review” of the <strong>Nimrod</strong> BLSC. Rather, he explained in evidence that he was only asked to “cast<br />

an eye” over the three reports. It appears that an internal BAE Systems meeting may have taken place on<br />

Wednesday 26 August 2004, attended by Witness A [BAE Systems] and Chris Lowe, at which only these three<br />

reports were reviewed.

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

Saved successfully!

Ooh no, something went wrong!