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.

RAF fighter jet had to swerve to avoid small aircraft over Loch Ness

An extra squadron of Typhoons is due to arrive at RAF Lossiemouth before 2020.
An extra squadron of Typhoons is due to arrive at RAF Lossiemouth before 2020.

A low flying RAF fighter pilot had to dodge a light aircraft over Loch Ness, an official probe has heard.

The Typhoon jet was flying at 360 feet above the ground and at 420 knots when the incident happened on July 19 over the Highlands.

The RAF pilot said that he entered a low-level system at 3pm and 20 miles south-west of Lossiemouth in Moray.

He called on the VHF common frequency and deconflicted his route with a Tucano turbo prop light aircraft that was entering low-level at a similar point.minutes later he again transmitted his position as ‘entering the Great Glen heading south-west.’

At the southern end of Loch Ness, he climbed briefly to maintain minimum separation distance against power lines and subsequently spotted a high-wing, light-aircraft approximately 3000 feet ahead, and 200-300 feet above.

He immediately took avoiding action by manoeuvring left and down to ensure separation – the closest point was estimated to be 1000 feet.

He assessed the risk of collision as ‘low’ but the light aircraft could not be traced.

A report by Air Command HQ to the UK Airprox Board – which investigates reported near misses – said the Typhoon pilot was conducting low-flying training in accordance with current regulations.

The Typhoon was not fitted with a collision warning system (CWS) however and since the light-aircraft could not be traced it is unknown whether or not it was equipped with a similar alert that could interact with the transponder on the Typhoon.

“Given the position and height of the Airprox, it is also unlikely that an air traffic service could have provided a barrier to this encounter,” said the report.

“The Typhoon pilot had transmitted his position and routing on the VHF common frequency approximately two minutes prior to the Airprox but had received no information from any other aircraft that his routing might have been in conflict with theirs.

“The final, effective, barrier in this case was ‘see and avoid’ – it cannot be determined if the light aircraft pilot saw the Typhoon but the Typhoon pilot saw the light aircraft at a range of approximately half-a-nautical mile and took action to increase separation, once again showing that disciplined lookout is essential…….”

In its conclusions the board said:”Unfortunately, this incident did not show on the National Air Traffic Services’ radar due to the height of the aircraft and so the light-aircraft pilot could not be traced.

“This meant that the board only had the Typhoon pilot’s report on which to base their assessment of the incident. Noting that the Typhoon pilot had called on the VHF common frequency, it was disappointing that the board could not determine whether the other pilot was also on this frequency or not, and whether terrain screening could account for him not hearing the Typhoon pilot’s call.

“Anecdotal evidence had shown that pilots operating in Scotland have welcomed the common frequency, but the RAF member noted that, in the main, there had been little feedback given to the RAF on whether the general aviation community found it useful or not, or to what extent it was used.

“The Typhoon was not fitted with a CWS, and so its pilot could not get any prior electronic warning of the other aircraft other than through the Typhoon’s on-board radar; given that the Typhoon was flying down the valley, the light-aircraft may have been obscured to the radar by the hills.

“Without a report from the light-aircraft pilot, the board could not determine whether the light aircraft might have been fitted with a CWS but it was considered unlikely.

“Ultimately, members agreed that see-and-avoid had worked in this incident in that the Typhoon pilot was able to see the light-aircraft with enough time to take avoiding action and ensure that there was safe separation between them.

“Both pilots were operating as they were entitled to, and so the board therefore concluded that the cause of the Airprox was simply a conflict in Class G (uncontrolled airspace), resolved by the Typhoon pilot. Members then debated the risk of the Airprox, with some members believing that safety had been degraded, whilst others argued that because of the early avoiding action by the Typhoon pilot normal safety standards had in fact pertained (Category E).

“In the end the Chairman put it to a vote and, by a large majority, the incident was assessed as Category E.”