Calendar An icon of a desk calendar. Cancel An icon of a circle with a diagonal line across. Caret An icon of a block arrow pointing to the right. Email An icon of a paper envelope. Facebook An icon of the Facebook "f" mark. Google An icon of the Google "G" mark. Linked In An icon of the Linked In "in" mark. Logout An icon representing logout. Profile An icon that resembles human head and shoulders. Telephone An icon of a traditional telephone receiver. Tick An icon of a tick mark. Is Public An icon of a human eye and eyelashes. Is Not Public An icon of a human eye and eyelashes with a diagonal line through it. Pause Icon A two-lined pause icon for stopping interactions. Quote Mark A opening quote mark. Quote Mark A closing quote mark. Arrow An icon of an arrow. Folder An icon of a paper folder. Breaking An icon of an exclamation mark on a circular background. Camera An icon of a digital camera. Caret An icon of a caret arrow. Clock An icon of a clock face. Close An icon of the an X shape. Close Icon An icon used to represent where to interact to collapse or dismiss a component Comment An icon of a speech bubble. Comments An icon of a speech bubble, denoting user comments. Comments An icon of a speech bubble, denoting user comments. Ellipsis An icon of 3 horizontal dots. Envelope An icon of a paper envelope. Facebook An icon of a facebook f logo. Camera An icon of a digital camera. Home An icon of a house. Instagram An icon of the Instagram logo. LinkedIn An icon of the LinkedIn logo. Magnifying Glass An icon of a magnifying glass. Search Icon A magnifying glass icon that is used to represent the function of searching. Menu An icon of 3 horizontal lines. Hamburger Menu Icon An icon used to represent a collapsed menu. Next An icon of an arrow pointing to the right. Notice An explanation mark centred inside a circle. Previous An icon of an arrow pointing to the left. Rating An icon of a star. Tag An icon of a tag. Twitter An icon of the Twitter logo. Video Camera An icon of a video camera shape. Speech Bubble Icon A icon displaying a speech bubble WhatsApp An icon of the WhatsApp logo. Information An icon of an information logo. Plus A mathematical 'plus' symbol. Duration An icon indicating Time. Success Tick An icon of a green tick. Success Tick Timeout An icon of a greyed out success tick. Loading Spinner An icon of a loading spinner. Facebook Messenger An icon of the facebook messenger app logo. Facebook An icon of a facebook f logo. Facebook Messenger An icon of the Twitter app logo. LinkedIn An icon of the LinkedIn logo. WhatsApp Messenger An icon of the Whatsapp messenger app logo. Email An icon of an mail envelope. Copy link A decentered black square over a white square.

MoD failures led to Moray Tornado crash

Post Thumbnail

A catalogue of failures have been blamed for causing the deaths of three RAF Lossiemouth pilots when their Tornado jets crashed over the Moray Firth in 2012.

The Military Aviation Authority (MAA) inquiry report into the tragedy – which was completed last year but only released this morning – raised a series of safety concerns.

The investigators identified 17 “contributory factors” – including the failure to fit a crash warning system to the jets and “ineffective” supervision of the pilots.

Further problems with the equipment and culture were also highlighted, as well as the decision-making of one of the pilots, and the weather conditions on July 3, 2012.

The inquiry’s findings and recommendations are expected to prompt heavy criticism of the Ministry of Defence, and lead to fresh calls for a fatal accident inquiry into the deaths.

The second anniversary of the collision will be marked at a ceremony at RAF Lossiemouth on Thursday.

The crash caused the deaths of Flight Lieutenant Adam Sanders, Squadron Leader Samuel Bailey and Flight Lieutenant Hywel Poole. A fourth man, who has not been named, survived

Responding to the panel’s findings, MAA director general Air Marshal Richard Garwood said: “The tragedy is that we have lost three highly professional, dedicated and capable aircrew and my sympathy goes to their families, friends and colleagues.

“As I am sure our lost crews would support, our job now is to use that we know of their final moments and the circumstances surrounding their flights to help prevent any further mid-air collisions.

“The service inquiry panel rightly identified the cause of the accident to be a ‘lack of recognition of converging flight paths which resulted in both aircraft being in the same airspace at the same time’.

“Although factually correct, I believe it somewhat simplifies the headline issue, and whilst not disagreeing with their statement, I would add that a lack of situational awareness of each others’ sortie, from the planning phase right through to the actual collision, was highly significant.”

He added: “As with many accidents, bad luck has to be part of the explanation, particularly in the closing stages when they wre belly up to each other, a few feet difference in altitude of one of the aircraft would have created a near miss rather than this tragic accident.

“Unfortunately, the final safety barrier which would have generated awareness of their close proximity did not exist as the Tornado GR4 is not fitted with a collision warning system.”

Military chiefs have previously confirmed that a collision warning system was first recommended for the Tornados in 1998 – but the equipment is not due to be fitted until December this year.

It has also emerged that the MoD temporarily cancelled the purchase of the £50million system in 2011 – despite the Military Aviation Authority warning in internal documents that delays to its installation were creating a “chronic risk”.

In a statement to parliament, Defence Minister Anna Soubry said: “A copy of the report has already been provided to relevant personnel and units in Defence to ensure the timely dissemination of these air safety lessons.

“The recommendations from the report have either been addressed or are in the process of being addressed.

“Our deepest sympathies remain with the families of those who lost their lives in this tragic accident.”

An MoD spokesman added: “The MAA service inquiry concluded that the cause of the accident in Moray Firth in 2012 was a lack of recognition of converging flight paths leading the two jets to collide in the same airspace.

“The service inquiry found that the lack of a collision warning system did not cause the accident but was one of 17 contributory factors which made it more likely to happen.

“While accidents like this are very rare, this demonstrates that military flying can never be without risk. The RAF is already implementing the lessons learnt from this tragic accident and now uses a flight planning aid to highlight potential aircraft conflicts prior to flight.

“The MoD is committed to reducing the risk of mid-air collisions and has developed a collision warning system for Tornado which is currently being trialled, and is expected to be introduced from the end of 2014.”