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.

Fire & Explosion Report completed<br />

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

10A.163 <strong>The</strong> Fire/Explosion Hazard Assessment (Fire & Explosion Report) was completed by Chris Lowe in August<br />

2004. 72 It had originally been envisaged that Mech Systems would produce the Fire & Explosion Report and<br />

that this would be based on a ZHA. <strong>The</strong>re was a logic to this because Mech Systems were best placed to<br />

carry out such a task. As at 7 April 2004, it was envisaged that Chris Lowe would provide Eric Prince with<br />

a skeleton for the Fire & Explosion Report and Eric Prince would allocate resources from Mech Systems. <strong>The</strong><br />

value of a Fire & Explosion Report had been questioned but defended by Chris Lowe. By 10 May 2004, it was<br />

decided that the Fire & Explosion Report should be done by Witness U [BAE Systems] of Mech Systems using<br />

Chris Lowe’s framework and MSC thesis. 73 However, the task was eventually passed to the Airworthiness<br />

Department because Witness U [BAE Systems] did not have sufficient time and Chris Lowe ultimately drew it<br />

up himself. He said that he completed it over a period of six weeks by working on it at home. It is unfortunate<br />

that he had not been present at either visit to RAF Kinloss or RAF Waddington and therefore had not<br />

examined the aircraft.<br />

10A.164<br />

<strong>The</strong> Fire & Explosion Report purported to highlight the catastrophic risk of a serious on-board fire. In particular,<br />

it stated pertinently:<br />

“In the case of a deep-seated on-board fire remaining undetected and unsuppressed<br />

during flight, irrespective of the location of the fire on the aircraft, it can very quickly<br />

contribute to any combination of major structural failure, loss of fundamental control or<br />

total loss of thrust; thus resulting in catastrophic loss of aircraft and occupants.<br />

In the case of an on-board fire-related explosion (such as a fuel tank explosion), such an<br />

event invariably leads to all three consequences simultaneously. …” 74<br />

10A.165 Unfortunately, the Fire & Explosion Report was of very poor quality. It contained numerous errors and omissions<br />

and failed to identify and highlight the catastrophic risk of an ‘uncontrollable’ fire risk in the starboard No. 7<br />

Tank Dry Bay. <strong>The</strong>re was also little, or no, attempt to reconcile the apparently contradictory conclusions of the<br />

Fire & Explosion Report and the BLSC Reports. <strong>The</strong>se matters are particularised and analysed in more detail<br />

in Chapter 11.<br />

16 August 2004: task only 68% complete<br />

10A.166 By 16 August 2004, the position had clearly become critical. Only 50 out of 104 hazard Pro-Formas had been<br />

done. <strong>The</strong>re remained 33 to be completed by Mech Systems, 29 by Electrical Systems, seven by Avionics and<br />

one by Structures. <strong>The</strong>re were, however, only two weeks to go until the Customer Acceptance Conference<br />

(see below). At a review meeting that morning, Chris Lowe said there was to be a “final push” and the aim<br />

was for “end of the week completion”. A further week was going to be required to carry out the necessary<br />

input into CASSANDRA and finalise the reports (on the basis of inputting at a rate of half an hour per hazard).<br />

Mech Systems was told “to come up with a plan” to complete the remaining hazards “by the end of the<br />

week”. This was not realistic. It was also likely to put undue pressure on the engineering staff involved to<br />

cut corners simply to finish the job. Witness K [BAE Systems]’s note of the meeting states that Eric Prince<br />

“played along with this deadline”. He did not come up with a plan. Eric Prince suggested in interview with<br />

the <strong>Review</strong> that Chris Lowe had not meant that all the hazards should be completed by the end of the week,<br />

but merely that he (Eric Prince) was required to come up with a plan by the end of the week; and further, that<br />

this was “the usual sort of pressure” which was encountered with projects. In my view, neither explanation<br />

was convincing.<br />

72 BAE Systems Report MBU-DEF-C-NIM-SC0710: “PDS Task 06-3409 <strong>Nimrod</strong> MR Mk2 & R Mk 1 Safety Case Baseline Report Phase 2 Fire/Explosion<br />

Hazard Assessment”, dated August 2004.<br />

73 Lancaster University Engineering Department, September 2003.<br />

74 BAE Systems Report MBU-DEF-C-NIM-SC0710: “PDS Task 06-3409 <strong>Nimrod</strong> MR Mk2 & R Mk 1 Safety Case Baseline Report Phase 2 Fire/Explosion<br />

Hazard Assessment”, dated August 2004, Page 12.<br />

225

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

Saved successfully!

Ooh no, something went wrong!