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 19 – Shortcomings of Current System<br />

the MOD tends to focus and spend its money in making individual pieces of equipment (e.g. aero-engines)<br />

extremely safe, which means that it does not have the resources to spend on other measures which might<br />

significantly reduce the overall net Risk to Life (e.g. collision avoidance systems such as TCAS 8 or additional<br />

spares). This imbalance is caused by myopia and a poor appreciation of the total risk picture. <strong>The</strong> result is<br />

that resources are not targeted as effectively as they might be. Further, the difficulty in comparing like-withlike<br />

and making relative assessments of risk across domains and platforms, means that the higher level<br />

governance boards which manage Airworthiness across Defence (e.g. MARSB) lack appropriate information<br />

to manage aviation risks or direct resources appropriately. <strong>The</strong> US Air Force Safety Center told me of a striking<br />

example of the advantages of being able to address Risk to Life across all platforms and operations: the US<br />

Navy, which assesses Risk to Life across all lines of development, came to realise that most aircrew deaths<br />

and injuries at various aircraft bases were attributable to motorbike accidents and, as a result, it instigated<br />

a successful advanced motorbike training programme, which substantially reduced road accident deaths for<br />

aircrew, thereby preserving one of its most precious assets.<br />

(10) <strong>The</strong>re are too many different Hazard Risk Matrices.<br />

19.14<br />

<strong>The</strong>re are a myriad of different Hazard Risk Matrices used to determine risk categorisations. This is confusing,<br />

potentially dangerous, and makes it more difficult to compare risks across platforms.<br />

(11) <strong>The</strong>re is a lack of independence and transparency.<br />

19.15<br />

<strong>The</strong> Assistant Service Chiefs have each had bestowed on them the conflicting roles of Duty Holder and Release<br />

to Service Authority. This runs entirely counter to the principle of independent regulation and assessment<br />

which is a key tenet of proper Airworthiness regulation as practiced by e.g. the UK Civil Aviation Authority.<br />

<strong>The</strong>se are pivotal regulatory functions that the Assistant Chiefs are expected to undertake in addition to their<br />

(very demanding) primary duties.<br />

(12) <strong>The</strong>re is a lack of consistency across all three Services.<br />

19.16<br />

Each of the three Services executes the Release to Service Authority function differently. <strong>The</strong> Navy and Army<br />

carry out this regulatory function from within their operating authorities. <strong>The</strong> RAF relies on the expertise of<br />

experienced air operators; the Navy relies on aircraft engineers; and the Army relies on a mixture. In effect,<br />

there are three quite different arrangements for what is the same regulatory function, whilst none, in my<br />

view, provides an example of best practice.<br />

(13) <strong>The</strong> interface between the MOD and Industry is not working as it should.<br />

19.17<br />

<strong>The</strong> Regulator has initiated a move towards a more ‘civil’ Airworthiness regulatory model in order to seek to<br />

improve the interface between Industry (who manufacture and support the MOD’s aircraft) and the Front Line<br />

military. <strong>The</strong> transition to a ‘hybrid’ model has, however, proved difficult. This is due in part to the fundamental<br />

differences between civil and military operations and to the difficulties of meshing different regulatory<br />

systems. <strong>The</strong> Military Approved Organisation Scheme (MAOS) was devised to align with the approval system<br />

used by the civil sector and to make it easier and less expensive for the MOD to contract with Industry. Those<br />

Industry support organisations that have been approved under the MAOS system have been permitted to<br />

devise their own systems for maintenance management. Unfortunately, these do not necessarily correlate<br />

with those used by the Forward environment who operate and support the aircraft, which has e.g. made the<br />

tracking of life critical components difficult. Most importantly, Industry MAOS support organisations will not<br />

recognise engineering decisions made by the Front Line engineering officers taken e.g. to defer corrective<br />

maintenance or accept capability limitations, even though these decisions are a fundamental requirement<br />

for military air operations. Rather, Industry MAOS support organisations typically demand corrective action<br />

before aircraft are handed over to Industry for routine maintenance. At RAF Marham, for instance, where<br />

MAOS is in place, Industry has on occasion even been unwilling to recognise component life data issued<br />

8 Traffic Collision Avoidance System.<br />

475

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

Saved successfully!

Ooh no, something went wrong!