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.

Military jets narrowly avoid mid-air collision near Inverness Airport

Montage of RAF Tornados and Inverness Airport
Montage of RAF Tornados and Inverness Airport

The crews of two military jets narrowly avoided a head-on mid-air collision near Inverness Airport, flying within 400ft of each other after the crews failed to hear an instruction.

The drama, On February 5, involved an RAF Tornado jet and a Tucano turboprop training aircraft flying out of RAF Lossiemouth, two miles south of Inverness Airport.

Investigators gave the incident a “B rating” which is their second highest category and listed when “the safety of the aircraft may have been compromised.”

They said the crews and an RAF controller all played a part.

The UK Airprox Board investigated the incident which involved one of two Tornados on a training sortie and one of two Tucanos that were flying to RAF Lossiemouth.

In its report, the board said the Tornado crews “climbed into conflict” with the Tucano.

HQ Air Command states in the report that the jet crews did not hear an instruction from an RAF controller to stop climbing, and the controller did not ask the crews for confirmation that they had heard his instruction.

The board said the controller had “gone the extra mile” to get the aircraft to pass safely but had used some phraseology that may have confused the Tornado crews.

The investigation found that the Tornado formation did not hear a “stop climb” instruction.

According to the report, the controller did not challenge the Tornados to confirm the instruction and the Tornado crew “did not take adequate action to ensure sufficient separation, leading to a late sighting.”

At the time, the crews were discussing an issue but “did not feel that this had distracted them.”

HQ Air Command said the controller interpreted the transmission of the (Tornado) formation callsign as acknowledgement of the instruction even though a full read-back should have been transmitted by the Tornados.

It said that “highlighted the importance of adherence to standard phraseology – it is usually borne out of bitter experience – and the importance of insisting that clearances be read back in full.”

The board concluded that all those involved had allowed “an assumption or inaction to prevail to some degree,” resulting in “substantially reduced separation where safety margins had been much reduced below normal.”

It said no-one involved “had taken charge of the situation suifficiently.”

It also noted that standard phraseology “was there for a reason, to avoid confusion to the greatest extent possible, and that non-standard phraseology often served to generate confusion or not resolve the issue at hand.”

Ends.