2006 Royal Air Force Nimrod crash

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
2006 Royal Air Force Nimrod crash
Nimrod Waddington 2005 2.jpg
XV230 at the Waddington Airshow, July 2005
Accident summary
Date 2 September 2006 (2006-09-02)
Summary On board fire following aerial refuelling
Site Chalaghor in the Panjwaye District of Kandahar, Afghanistan
Crew 14
Fatalities 14 (all)
Survivors 0
Aircraft type Nimrod MR2
Operator Royal Air Force
Registration XV230

On 2 September 2006, a Royal Air Force Hawker Siddeley Nimrod suffered an in-flight fire and subsequently crashed in Kandahar, Afghanistan, killing all fourteen crew members on board. The crash, which occurred during a reconnaissance flight, was the biggest single loss of life suffered by the British military since the Falklands War.

Aircraft

The aircraft involved in the accident was XV230, the first of 38 Nimrod maritime reconnaissance/strike aircraft to enter operational service with the Royal Air Force on 2 October 1969.[1][2] At a ceremony held at Woodford airfield in Cheshire, the aircraft was handed over by the deputy managing director of Hawker Siddeley Aviation, Sir Harry Broadhurst. Receiving XV230 were the AOC-in Chief of Coastal Command, Air Marshal Sir John Lapsley. At Broadhurst's invitation, Lady Lapsley performed the naming ceremony. Later in the day an RAF crew flew XV230 to its base at RAF St Mawgan, Cornwall, where the Nimrod maritime operational training unit (MOTD) was to be formed.[3]

According to Jane's Information Group, XV230 was one of six Nimrods equipped with an L-3 Wescam MX-15 electro-optical turret in 2003. In June/July 2006 XV230 was given the capability to transmit real-time video imagery from the MX-15 to ground stations and commanders. This was implemented under Project Broadsword.[4]

Crash details

The aircraft is believed to have suffered a fuel leak during mid-air refuelling while it was monitoring a NATO offensive against Taliban insurgents west of Kandahar. The fuel appears to have leaked into the bomb bay where it caught fire, either as the result of an electrical fault or hot air leaking from a heating pipe.

The pilot reported a fire in his bomb-bay. He tried to reach Kandahar air base, taking the aircraft down from 23,000 to 3,000 feet (7,010 to 910 metres) in 90 seconds. An RAF Harrier aircraft followed the Nimrod down and the pilot saw a wing explode, followed a few seconds later by the rest of the aircraft.[5]

The crash site was about 25 miles (40 kilometres) west-north-west of Kandahar Airfield (which is located 10 miles (16 kilometres) south-east of the city of Kandahar) between two villages called Chil Khor and Fatehullah Qala in the Panjwaye District.[6] Witnesses included local men Abdul Manan, Afshan Hararoot and Haji Eisamuddin.[7]

Twelve RAF personnel, a Royal Marine and a British Army soldier aboard the Nimrod MR2, XV230 were killed. The 12 RAF crew were all from No. 120 Squadron RAF, based at RAF Kinloss in Scotland and the soldier and marine on board were serving with the Special Reconnaissance Regiment.[8]

A board of inquiry report was released in December 2007.[9]

On 23 May 2008 the assistant deputy coroner for Oxfordshire, Andrew Walker, handed down a narrative ruling that it had "never been airworthy from the first time it was released to the service nearly 40 years ago".

"It seems to me that this is a case where I would be failing in my duty if I didn't report action to the relevant authority that would prevent future fatalities,"

"I have given the matter considerable thought and I see no alternative but to report to the secretary of state that the Nimrod fleet should not fly until the ALARP [as low as reasonably practicable] standards are met."[10]

Controversy

There have been concerns in the British media about serviceability of the Nimrod fleet[11] and bereaved families are having to wait for years for the Oxfordshire coroner's office to hold inquests into military deaths.[12] Conservative MP, Mr Ian Liddell-Grainger called for its replacement - the BAE MRA4 - to be introduced more quickly.[13] The replacement aircraft suffered significant problems during development and construction which resulted in lengthy programme delays and the in-service date slipping nine years from 2003 to 2012.[14][15] The MR4 replacement aircraft was cancelled entirely following the 2010 Strategic Defence and Security Review.[16]

Concerns were again raised when on 5 November 2007, Nimrod XV235 was reported to have suffered a similar fuel leak. The aircraft landed safely. The Ministry of Defence (MoD) then suspended all in-flight refuelling of the Nimrod fleet.

The Scottish National Party's Westminster leader, Angus Robertson criticised delays in inquiries. He said the wait for the MoD inquiry and a coroner's inquest was a "disgrace" that dates have still to be set for the publication of the board of inquiry's findings and a coroner's inquest into the deaths. He was also quoted as saying "Everybody's thoughts are with the families and friends of those who lost their lives. They are having to wait far too long to receive answers to many questions. A 12-month wait is a disgrace - Publication dates have been put back and put back and the Ministry of Defence should get on with it."[17]

In March 2009, following continued questions about the safety of the Nimrod fleet and despite constantly stating that the aircraft were airworthy, the MoD grounded the Nimrod fleet for "vital safety modification[s]". Engine bay hot air ducts and fuel seals were to be replaced.[18]

There are those who opine that the loss was a foreseeable consequence of design and production failures.[19]

Concerns about the safety of the Nimrod fleet have continued to surface since the loss of XV230. In April 2009 it was reported that the Defence Minister had "glossed over Nimrod safety fears".[20] The Independent newspaper claimed that a report into the safety of Britain's ageing fleet of Nimrods, which a defence minister claimed did not reveal "any significant airworthiness issues", exposed almost 1,500 faults – 26 of which threatened the aircraft's safety.

Board of Inquiry findings

On 4 December 2007 the report of the findings of the official Board of Inquiry into the loss of XV230 was published. The Board believed that the No 7 tank dry bay was the most likely location for the seat of the fire, with the most probable cause being escaped fuel having come into contact with a Supplementary Conditioning Pack (SCP) airpipe at 400 degrees Celsius "...after entering a gap between two types of insulation". Four separate factors were listed as contributing to the accident:[21] Age of the aircraft; Maintenance policy; Failure of hazard analysis and lack of a fire detection and suppression system; Not identifying the full implications of successive changes to the fuel system and associated procedures.[22]

Links into the full report on the XV230 accident can be found here [23]

On 23 May 2008, the coroner who led the inquest into these deaths stated that the entire Nimrod fleet had "never been airworthy from the first time it was released to service" and urged that it should be grounded.[10] Assistant deputy coroner for Oxfordshire Andrew Walker added: "This cavalier approach to safety must come to an end. There were failures...[in monitoring the aircraft's safety]...that should, if the information had been correctly recorded and acted upon, have led to the discovery of this design flaw within the Nimrod fleet."[24]

Nimrod review

External image
Nimrod MR1 XV230 cutaway and weapon loadout
image icon An old 1970's cutaway of Nimrod MR1 XV230 retouched by Flight Global in 2006.

The Terms of Reference for the Nimrod Review were set out by the Secretary of State for Defence, Des Browne, on 13 December 2007.[25][dead link]

It emerged in May 2009 that an RAF commander destroyed a number of official documents after the loss of Nimrod XV230. The Times newspaper,[26] 31 May 2009, reported that all documents relating to the aircraft were immediately impounded but Sqn Ldr Guy Bazalgette, commander of the Nimrod detachment in the Gulf, managed to retrieve one file. Bazalgette subsequently destroyed the document but later told the coroners inquest that none of the shredded documents were relevant to the loss of XV230. However, Bazalgette admitted: "They should not have been shredded and it was my fault that they were."

Also in May 2009, Charles Haddon-Cave, QC, leading the Nimrod Review issued a number of Salmon letters to organisations and senior RAF officers warning them they were likely to be criticised in its formal report. The so-called Salmon letters give those who are likely to be criticised by the inquiry the opportunity to respond to the criticism before the report’s publication. The MoD and the Nimrod inquiry team declined to say which senior RAF officers received letters.[26]

On 28 October, Haddon-Cave presented his report, summarised by the statement:

<templatestyles src="Template:Blockquote/styles.css" />

Its production is a story of incompetence, complacency and cynicism. The best opportunity to prevent the accident to XV230 was tragically lost

The report:

  • Accused the MoD of "deep organisational trauma" resulting from the strategic defence review of 1998
  • Sacrificing safety to cut costs, resulting in a "systemic breach" of the military covenant
  • A safety review of the Nimrod MR2 carried out by the MoD, BAE Systems and QinetiQ branded a "lamentable job"

Mr Haddon-Cave condemned the change of organisational culture within the MoD between 1998 and 2006, when financial targets came to distract from safety, quoting a former senior RAF officer who told the inquiry:

<templatestyles src="Template:Blockquote/styles.css" />

There was no doubt that the culture of the time had switched. In the days of the RAF chief engineer in the 1990s, you had to be on top of airworthiness. By 2004 you had to be on top of your budget if you wanted to get ahead.

Mr Haddon-Cave directly criticised 10 individuals in the report - five at the MoD, three at BAE Systems and two at QinetiQ - while throughout the review BAE Systems had been a company "in denial." Mr Haddon-Cave's report directly criticised two RAF officers:

  • Air Commodore George Baber - a group captain at the time, led the MoD integrated project team responsible for a safety review of the RAF's Nimrods, which took place between 2001 and 2005. Mr Haddon-Cave accused Baber of a "fundamental failure of leadership" in drawing up the "safety case" into potential dangers in the fleet: "He failed to give the NSC (Nimrod safety case) the priority it deserved. In doing so, he failed, in truth, to make safety his first priority."
  • Wing Commander Michael Eagles - then head of air vehicle for the Nimrod, Wing Cdr Eagles was supposed to be in charge of managing production of the safety review. The report found that he delegated the project "wholesale" to an MoD civilian worker who was too inexperienced and not competent to manage it: "Michael Eagles failed to give adequate priority, care and personal attention to the NSC task. He failed properly to utilise the resources available to him within the Nimrod IPT to ensure the airworthiness of the Nimrod fleet."

Defence Secretary Bob Ainsworth said the "rigorous" report would make distressing reading for the relatives of those who died.

<templatestyles src="Template:Blockquote/styles.css" />

On behalf of the MoD and the Royal Air Force, I would like again to say sorry to all the families who lost loved ones. I am sorry for the mistakes that have been made and the lives that have been lost as a result of our failure. Nothing I can say or do will bring these men back.

Mr Ainsworth told the Commons the two RAF officers had been moved to staff posts which held no responsibility for safety and the RAF would now consider if any "further action" would be taken against them.

Legal proceedings

In December 2008 the Defence Secretary John Hutton was served with a writ by relatives of two of 14 men who died.[27]

In March 2009 in response to the writ, the Ministry of Defence admitted responsibility for the deaths of the 14 servicemen aboard Nimrod aircraft XV230, after two families brought a landmark legal action using human rights law. High Court papers submitted by the MoD in response to the claim accept for the first time that the reconnaissance aircraft, which exploded mid-air in Afghanistan, was "not airworthy". The papers add: "The defendant owed to the deceased a duty of care and the accident was caused by this breach of that duty of care."[28]

References

  1. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  2. ↑ RAF Kinloss - Nimrod - Through The Years
  3. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  4. ↑ Crashed RAF Nimrod identified Jane's Defence Business News
  5. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  6. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  7. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  8. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  9. ↑ PR Newswire : Release of Nimrod XY230 board of inquiry (BOI)
  10. ↑ 10.0 10.1 "Nimrod inquest coroner declares whole fleet 'never airworthy' " The Guardian. 2008-05-23. Retrieved on 2008-05-24
  11. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  12. ↑ Adams, Stephen (2007-08-23) Attacks on 'appalling' wait for inquests Telegraph, Accessed 2015-05-13
  13. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  14. ↑ BAe Nimrod MRA4
  15. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  16. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  17. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  18. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  19. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  20. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  21. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  22. ↑ Burns, John F., "Cost Cuts Led to British Jet Crash, Study Says", New York Times, 28 October 2009.
  23. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  24. ↑ Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  25. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  26. ↑ 26.0 26.1 Lua error in package.lua at line 80: module 'strict' not found.
  27. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  28. ↑ Lua error in package.lua at line 80: module 'strict' not found.

External links

Retrieved from "https://infogalactic.com/w/index.php?title=2006_Royal_Air_Force_Nimrod_crash&oldid=1710422"