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.

5.67<br />

5.68<br />

Chapter 5 – Leak from Fuel Coupling<br />

monitor the frequency or extent of fuel leaks generally: they were seen as essentially a routine maintenance<br />

issue preventing aircraft flying, but not necessarily as a threat to the aircraft. Each incident appears to have<br />

been treated in isolation, with no attempt to gather evidence of patterns or trends. As fuel represents the most<br />

unpredictable ‘third’ of the fire equation, 64 there should always be careful and unremitting focus on managing,<br />

tracking, monitoring and reducing fuel coupling leaks to ALARP.<br />

In my view, the maintenance regime operated for many elements of the <strong>Nimrod</strong> fuel system prior to the loss of<br />

XV230 in September 2006, was unsatisfactory because:<br />

5.67.1 Although the ‘Corrective Maintenance’ regime reflected common practice in the aviation field, it failed<br />

to detect an increase in fuel leaks, despite the conduct of the data reviews mandated to ensure the<br />

efficacy of the system. Perhaps the policy’s greatest failing, though, is that it appears to have imbued<br />

a sense that fuel leaks were not an occurrence that required careful monitoring. Fuel coupling leakage<br />

was not perceived as a significant risk in itself, as the majority of leaks were considered to be extremely<br />

small and no one had realised the ignition threat posed by the Cross-Feed/SCP ducting.<br />

5.67.2 Fuel leak mapping and zonal surveys of the fuel system, conducted prior to and during periodic<br />

maintenance, were of limited value in detecting fuel leaks as they were undertaken either with the fuel<br />

system empty, or full but not under pressure. <strong>The</strong> fuel system was not tested or inspected under pressure,<br />

unless a component was replaced under the Corrective Maintenance policy, or following scheduled<br />

maintenance to confirm correct reassembly of the fuel system. (<strong>The</strong> AAIB 65 report, produced as part of<br />

the investigation into the loss of XV230, highlighted that the maintenance regimes for some civilian<br />

aircraft included checking the fuel system for leaks while under pressure.) 66 Further, visual inspections<br />

were confined to external signs of damage, deterioration, corrosion, or leaks. Couplings were not<br />

dismantled to check the condition of their rubber seals; however, such a process would have involved<br />

the wholesale replacement of the seals as once disturbed they are automatically replaced. It is difficult<br />

to see, therefore, how incipient fuel leaks might be detected with any level of confidence.<br />

5.67.3 <strong>The</strong>re was no system of formal random ‘sampling’ of components such as seals to check their in-service<br />

condition, or any pro-active method to anticipate leaks.<br />

5.67.4 <strong>The</strong>re was a lack of guidance in the Aircraft Maintenance Manual (AMM) regarding the fitting of<br />

fuel couplings which meant that ground crew had no immediately available reference to ensure that<br />

the couplings were fitted correctly. Couplings have been found incorrectly assembled allowing some<br />

rotation of the coupling body. <strong>The</strong> Illustrated Spares Catalogue did not identify the part numbers of the<br />

couplings illustrated, such that maintainers had to rely on using the part number of the removed part<br />

to identify the necessary replacement – something which could perpetuate previous misidentifications.<br />

<strong>The</strong> MOD was at fault in particular because:<br />

5.68.1 Although Reliability Centred Maintenance was supposed to be used to determine fault trends, the MOD<br />

failed to detect the increase in fuel leaks, as it was not focused on individual fuel system components,<br />

nor was it directed to investigate fuel leak rates. <strong>The</strong> Maintenance Data System (MDS) managed through<br />

the Logistics Analysis and Research Organisation (LARO) captured maintenance work orders (MWO)<br />

but was not used to extract trend analysis for fuel leaks. <strong>The</strong> platform ‘fault trend analysis’ produced<br />

annually did not go down to component level. <strong>The</strong>re was thus no means of investigating easily fuel leak<br />

rates, or indeed noticing increases over time; a fact illustrated by the BOI’s need to interrogate several<br />

thousand records to produce their own analysis.<br />

5.68.2 <strong>The</strong> system was reliant solely on IRs or SFRs, raised by air or ground crew, to reveal problems. However,<br />

unless a fuel leak was determined to have posed a threat to an aircraft, it would generally simply be<br />

recorded as a fault and rectified in the normal manner (although all leaks discovered whilst airborne<br />

64 A fire requires fuel, heat and oxygen to ignite.<br />

65 Air Accident Investigation Branch.<br />

66 BOI Report, Exhibit 12, page 48.<br />

87

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

Saved successfully!

Ooh no, something went wrong!