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

290<br />

<strong>The</strong> engines would only be on full power in the air. This passage would appear, therefore, to conflict with the<br />

earlier (erroneous) suggestion that the Cross-Feed/SCP duct was only pressurised during “during engine start”<br />

(on the ground).<br />

Blow-off valve – not taken into account as potential source of fuel<br />

11.117 <strong>The</strong>re was some suggestion on behalf of BAE Systems that the Pro-Forma for Hazard H73 did not cover the<br />

risk presented by fuel from the blow-off valve because the outside of the fuselage was not considered to be a<br />

‘zone’ and, accordingly, no specific zonal analysis was done on this area on the starboard side forward of the<br />

No. 7 Tank Dry Bay starboard. This is surprising for a number of reasons. First, No. 1 blow-off valve is located<br />

in Zone 127 and, therefore, should have been the subject of inspection and analysis as to what hazard it might<br />

represent to other proximate zones. Second, the ZHA Checklist specifically highlighted the risk which migrating<br />

fluids might represent to other zones. Appendix C3/4 contains a table of ‘generic’ hazards. <strong>The</strong> table includes<br />

a ‘hot surfaces’ section which refers to “Pipes” and specifically contemplates “Potential for fluid migration from<br />

other bays vertically and laterally”. Accordingly, if any such hazards were identified, the potential for migration<br />

of fluids from other bays “vertically and laterally” should have been carefully checked. Third, some of the risks<br />

associated with Air-to-Air Refuelling (AAR) were contemplated and touched upon in the Mech Systems Pro-<br />

Forma relating to the fuel system and in the Fire & Explosion Report, 46 albeit not the specific risk associated with<br />

fuel venting from No. 1 blow-off valve. Fourth, the risk of fuel entering apertures in the fuselage during venting<br />

from No. 1 blow-off valve during AAR had been highlighted during BAE Systems’ work on the AEW3 project<br />

in 1983 and further investigation by way of dye tests recommended. <strong>The</strong> failure of BAE Systems to recall this<br />

during the ZHA was a lack of corporate memory by the DA.<br />

Causation<br />

11.118 It was further argued by BAE Systems in their submissions to the <strong>Review</strong> that the errors which it made in relation<br />

to the use of the Cross-Feed duct and the insulation (and which it admitted) were not, however, causative of<br />

the accident to XV230. This was because the overall probability assessment in the Hazard H73 Pro-Forma was,<br />

in any event, driven by the probability of a fuel leak, which was assessed as “Improbable”. 47 I do not accept this.<br />

First, as explained above, the assumption that a fuel leak was ‘improbable’ was erroneous and derived from<br />

inappropriate data. Second, and in any event, even if a fuel leak was ‘improbable’, it was in my view nonsensical<br />

to assume a risk of ‘1’ for the ignition source and then focus solely on the (im)probability of a fuel leak (as BAE<br />

Systems suggested in evidence they did), since any fuel leak would, by definition, cause a catastrophic fire.<br />

Having identified Zone 614 as a ‘fire zone’, rather than simply assigning a probability to the fuel source, BAE<br />

Systems ought to have focused its attention on addressing the risk of a catastrophic fire itself.<br />

Personal responsibility of Witness R [BAE Systems]<br />

11.119 It is quite clear that, when drawing up the Pro-Forma for Hazard H73, Witness R [BAE Systems] totally failed<br />

to grasp the true nature of the risk presented by the juxtaposition of the Cross-Feed/SCP duct with the fuel<br />

couplings in the starboard No. 7 Tank Dry Bay. <strong>The</strong> proximity of heat and fuel in this zone represented a serious<br />

catastrophic threat to the aircraft. Witness R [BAE Systems], however, assessed the probability of Hazard H73 as<br />

only ‘improbable’ (1 x 10-6-10-7 ), which equated to a classification of a Category ‘C’ risk, i.e. ‘tolerable’.<br />

11.120 Why did Witness R [BAE Systems] get it so wrong? And why did the Pro-Forma he drew up for Hazard H73<br />

contain such significant errors? In my view, the answer lies in four overlapping reasons:<br />

11.118.1 First, he was someone relatively inexperienced, who had been brought in at a late stage from another<br />

department to a project with which he was previously unfamiliar; he did not have a great knowledge<br />

of the <strong>Nimrod</strong> and its systems, and had never actually inspected an MR2 or R1; he was under time<br />

pressure; and he was given inadequate guidance as to how to go about the task.<br />

46 e.g. <strong>The</strong> Mech Systems Pro-Forma for Hazard H34 referred to five incidents during AAR and stated “<strong>The</strong>se incidents have been the result of damage<br />

caused during the refuelling process or ‘dirty basket’. As a functional failure the ability to refuel in flight is not considered flight critical.”<br />

47 BAE Systems stated in writing to the <strong>Review</strong>: “Given that the risk of a fire/explosion arising from a fuel leak can, as a matter of logic, never be higher<br />

than the risk of a fuel leak itself, it follows that the errors made on the Mechanical Systems pro-forma (i.e. the suggestions that all of the bleed air<br />

ducting was insulated and that the ducting was only pressurised during engine start) had no impact on the overall zonal hazard (H73) probability<br />

assessed by the Mechanical Systems Department, which was one of improbable.”

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

Saved successfully!

Ooh no, something went wrong!