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.

10B.67<br />

10B.68<br />

Chapter 10B – <strong>Nimrod</strong> Safety Case: <strong>The</strong> Facts (Third Phase)<br />

CASSANDRA Hazard Log following receipt of the baseline safety case from BAE Systems” and agreed with<br />

the status of the hazards set by BAE Systems and enclosed the evidence to set the rest in the form of Annex A<br />

attached to Frank Walsh’s letter of 1 February 2005, save for three hazards (Hazards H86, H87 and A6) which<br />

required further work (see below). <strong>The</strong>re seems little doubt that a copy of Annex A (expressly referenced in<br />

the letter) was in fact attached to the letter. <strong>The</strong> letter concluded:“BAE Systems are to accept this letter as the<br />

approval to set the CASSANDRA hazards in accordance with Reference A and the status of all hazards and<br />

accidents with the exception of H86, H87 and A6 to managed”.<br />

It is, on the face of it, puzzling that this letter came to be written and signed at all at this stage. <strong>The</strong> letter<br />

was, on any view, inappropriate and premature because the risks listed could not properly be considered<br />

as “Managed” at this stage. All 33 hazards listed in Annex A were potentially “Catastrophic” risks. <strong>The</strong> 21<br />

“Interacting systems hazards”, together with three others listed in Annex A, were given a PCS of “Remote”.<br />

<strong>The</strong>se 24 hazards were, therefore, to be classified as category ‘B’ or “Undesirable” risks in the HRI, i.e. they<br />

required management action to introduce control measures and “shall only be acceptable once reduced<br />

to ALARP”. <strong>The</strong>re were seven hazards in Annex A which had been given a PCS of “Improbable” and were,<br />

therefore, properly to be classified as category ‘C’ or “Tolerable” risks, i.e. tolerable only if further risk reduction<br />

was “impracticable or……grossly disproportionate”. Furthermore, there were two hazards in Annex A (H86<br />

and H87) which had been given a PCS of “Occasional” and were, therefore, properly classified as category<br />

‘A’ or “Unacceptable” risks on the HRI, i.e. requiring “Urgent management action since such risk cannot be<br />

justified save in extraordinary circumstances”. <strong>The</strong> <strong>Nimrod</strong> SMP provided that, in relation to category ‘A’ or<br />

‘B’ hazards, it was (only) when control and mitigation actions had been approved by the PE/IPTL and where<br />

the PE/IPTL “…is satisfied that the actions are progressing to plan”, that he/she could change a hazard from<br />

“Approved” to “Managed”. <strong>The</strong> two category ‘A’ risks (Hazards H86 and H87) were expressly left at the<br />

“Approved” stage. However, the 24 category ‘B’ risks were described in the letter as “Managed”. <strong>The</strong>re is no<br />

evidence, however, of any approved management ‘actions’ being in progress to introduce further mitigating<br />

control measures for any of these 24 hazards. Accordingly, these 24 hazards should not properly have been<br />

referred to as “Managed” in any relevant sense. (<strong>The</strong> same is true for the 16 other hazards which BAE Systems<br />

had also classified as “Remote” in Annex B to the BLSC Phase 2, properly classified as ‘B’ or “Undesirable”).<br />

<strong>The</strong>re is, however, an air of finality about the letter of 22 February 2005 which suggests that Frank Walsh and<br />

George Baber considered the management of all but two of the hazards in Annex A as finished. <strong>The</strong>y were<br />

wrong about this.<br />

In these circumstances, two questions arise. First, why did Frank Walsh draft the letter in this way and attach<br />

Annex A? <strong>The</strong> most likely explanation is that he did not know what he was doing. He was simply out of his<br />

depth. He had never done this sort of exercise before, having never come across a Safety Case or Hazard Log<br />

of this type. He had had little or no training or guidance as to how to go about it or the level of rigour that<br />

was required. Second, why did George Baber sign the letter? <strong>The</strong> answer is almost certainly simply because<br />

it was put in front of him by a junior officer whom he assumed did know what he was doing, and he did not<br />

check that it was correct. I discuss these issues of responsibility in more detail in Chapter 11.<br />

16 March 2005: Frank Walsh ‘manages’ remaining hazards down to ‘Improbable’<br />

10B.69<br />

10B.70<br />

At some stage, Frank Walsh realised that, notwithstanding the letter of 22 February 2005 purporting to give<br />

BAE Systems approval to set the status of the vast majority of the hazards listed in Annex A as “Managed” in<br />

CASSANDRA, it remained necessary to manage a large proportion of hazards in Annex A to acceptable levels,<br />

i.e. an HRI of ‘C’. <strong>The</strong>re were a total of 24 Class A and B hazards in Annex A: 22 hazards (including Hazard<br />

H73) had been ascribed a PCS of “Remote”, and 2 hazards had been ascribed a PCS of “Occasional”. <strong>The</strong><br />

eight hazards which had been ascribed a PCS of “Improbable” fell into Class C category and were, therefore,<br />

the only ones which could properly be set as “Managed”. Frank Walsh clearly recognised that the remainder<br />

could not remain as class ‘A’ or ‘B’ risks.<br />

Precisely how and when Frank Walsh came to this realisation again is not clear. It may be that he picked this<br />

up during a conversation with someone at BAE Systems. In any event, at some stage on or before 16 March<br />

2005, he drew up a revised version of Annex A. He admitted in interview that he prepared this document<br />

255

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

Saved successfully!

Ooh no, something went wrong!