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.

Chapter 11 – <strong>Nimrod</strong> Safety Case: Analysis and Criticisms<br />

by the <strong>Nimrod</strong> IPT to allow QinetiQ to become too involved. As regards the latter point, there are indications of<br />

a disturbing, suspicious attitude towards QinetiQ displayed by George Baber at the Fourth PSWG Meeting on<br />

Friday 21 November 2003 at RAF Wyton, QinetiQ when he accused QinetiQ of just “touting for business” and<br />

also by Frank Walsh, who rejected QinetiQ’s re-write of the <strong>Nimrod</strong> IPT’s Local Business Instructions (LBI) for the<br />

Safety Cases for modifications to the <strong>Nimrod</strong> fleet as “gold-plated” and “out of proportion”.<br />

11.245 If QinetiQ had been formally tasked to carry out a full audit of the NSC, the outcome might have been<br />

different.<br />

(10) <strong>The</strong> <strong>Nimrod</strong> IPT failed properly to manage the NSC post its production and failed in<br />

any meaningful sense to treat it as a “living” document.<br />

11.246 In my judgment, the <strong>Nimrod</strong> IPT failed properly to manage the NSC post its production and failed in any<br />

meaningful sense to treat it as a “living” document. Whilst highly regrettable, against the background of<br />

‘assumed’ safety and the paperwork nature of the exercise (see above), it is perhaps not altogether surprising<br />

that there was a less than thorough or pro-active management of the risks identified by the NSC following its<br />

completion.<br />

XV227 duct failure - ‘wake up call’<br />

11.247 In my view, the above criticism is borne out by the manner in which the <strong>Nimrod</strong> IPT dealt with the two duct<br />

failures on XV227 and XV229 vis-à-vis the NSC. As explained in Chapter 7, on 22 November 2004, <strong>Nimrod</strong> MR2<br />

XV227 suffered a major hot air duct failure in a section of the Cross-Feed/SCP duct just aft of the ‘elbow’ at the<br />

bottom of No. 7 Tank Dry Bay due to corrosion. 130 <strong>The</strong> hot air leak of gases up to 420ºC caused serious damage<br />

inter alia to control cables and pulleys, hydraulic pipeline fairleads, numerous fuel seals, and structural members<br />

in the vicinity in No. 7 Tank Dry Bay. It was, in fact, exactly the sort of serious zonal incident envisaged by Hazard<br />

H73: “in an area closely packed with flight control cables and pulleys, hydraulic services, unprotected electrical<br />

cables and hot air ducting there exists potential for hot air ... leaks and possible fire”. 131 As the BOI observed,<br />

“... the incident illustrates the extensive effects of heat damage concomitant on the spread of hot gases within<br />

this area.” 132 XV227 was fortunate not to have been lost entirely.<br />

11.248 In these circumstances, there is no doubt in my mind that the XV227 incident should have been a “wake<br />

up call” (as one <strong>Nimrod</strong> line maintenance engineer called it) to those responsible for maintaining the NSC.<br />

Unfortunately, it was not.<br />

11.249 <strong>The</strong> XV227 investigation and the compiling of the NSC were not completely concurrent exercises. As explained<br />

in Chapter 10B, the NSC was effectively ‘signed-off’ by the end of 2004, although a significant number of<br />

hazards remained to be ‘managed’ by the <strong>Nimrod</strong> IPT in early 2005, and the NSC itself was supposed to be a<br />

‘living’ database. On 26 November 2004, the <strong>Nimrod</strong> IPT issued an Urgent Technical Instruction133 that the SCP<br />

should be electrically isolated for “Nil use” across the fleet pending further advice from the IPT. Subsequently,<br />

between December 2005 and April 2006, BAE Systems was tasked to conduct a detailed investigation of the<br />

incident. Unfortunately, it would appear that neither the <strong>Nimrod</strong> IPT (nor BAE Systems), thought to revisit and<br />

fundamentally reconsider the risk categorisation of Hazard H73 in the light of this near-catastrophic incident,<br />

notwithstanding that the Fault Investigation report (MOD Form 761) into the incident noted (‘for reference<br />

only’) that “a bleed air duct failure of this nature, in this aircraft zone, is recognised in the <strong>Nimrod</strong> Baseline<br />

Safety Case hazard ref. NM/H73”. Whilst Frank Walsh sent a copy of the “Initial Report of Serious Occurrence<br />

or Fault” (Annex A to BP 1301) in respect of the XV227 incident to Witness C [BAE Systems] on 14 December<br />

2004, together with photographs of the damage, he requested merely that these be ‘added’ to CASSANDRA<br />

against Hazard H73.<br />

130 At point in the duct between the Pressure Regulating and Shut off Valve (PRSOV) and the Flow Limiting Venturi.<br />

131 See section 1 of Mech Systems Pro-Forma for Hazard H73.<br />

132 BOI Report, Exhibit E [E-2].<br />

133 UTI/NIM/026, dated 26 November 2004.<br />

319

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

Saved successfully!

Ooh no, something went wrong!