{"id":28822,"date":"2025-10-21T10:35:21","date_gmt":"2025-10-21T14:35:21","guid":{"rendered":"https:\/\/ops.group\/blog\/?p=28822"},"modified":"2025-10-22T05:35:08","modified_gmt":"2025-10-22T09:35:08","slug":"spoofed-before-the-nat-heres-what-to-do","status":"publish","type":"post","link":"https:\/\/ops.group\/blog\/spoofed-before-the-nat-heres-what-to-do\/","title":{"rendered":"Spoofed Before the NAT? Here\u2019s What to Do"},"content":{"rendered":"

An OPSGROUP member on a recent westbound NAT flight from the Middle East received the following message via CPDLC:<\/p>\n

\"\"<\/p>\n

The crew contacted Shanwick via HF, who requested their RNP capability<\/strong> and operational status.<\/p>\n

The controller explained that due to their point of departure (OMAA\/Abu Dhabi) they wanted to be certain the aircraft had not been contaminated by GPS jamming or spoofing<\/strong> before it entered oceanic airspace.<\/p>\n

It’s been a while since we wrote about this procedure<\/a>, and since then we’ve had this NAT Ops Bulletin<\/a> published by ICAO telling operators what to do on the NAT if they’ve experienced jamming\/spoofing, so we reached out to NATS directly for an update. Here\u2019s what they had to say…<\/strong><\/p>\n

Defensive Measures<\/h4>\n

NATS reported they continue to receive a large number of flights every day that have been impacted by GPS interference prior to oceanic boundaries.<\/p>\n

The issue is that once an aircraft\u2019s navigation system has been \u2018contaminated\u2019 by bad GPS data, it may not be possible to recover full RNP capability in flight, even if the normal GPS signal is restored.<\/p>\n

These aircraft may no longer meet RNP 4\/10 accuracy required in the NAT HLA, even long after the trigger event occurred.<\/strong><\/p>\n

The NAT Ops Bulletin<\/a> which was published back in Jan 2025 requires crew of NAT-bound aircraft that have encountered GPS interference to notify their first NAT ANSP via RCL. Even if your aircraft shows no lingering effects, ATC still want to know.<\/strong><\/p>\n

NATS advise that late notification by pilots of a RNP degradation (such as approaching an oceanic entry point) greatly increases controller workload.<\/strong> They often need to move other aircraft out of the way to provide increased separation (in some cases from 14nm to 10 minutes), it\u2019s a big deal.<\/p>\n

As a result, they are employing defensive controlling measures.<\/strong> Based on previously spoofed\/jammed flights and regions of known risks, they may proactively contact flights assessed as higher risk to confirm status before entry – although the exact selection criteria isn’t public.\u00a0Increased separation will be applied until normal navigation performance is confirmed by the pilots.<\/p>\n

In a nutshell, this is why the OPSGROUP member received the message above.<\/p>\n

A special thank you to NATS for their help in answering this question.<\/p>\n

Jammed or spoofed? You need to let your NAT ANSP know<\/h4>\n

The NAT Ops Bulletin<\/a> we keep mentioning – this provides the guidance for NAT traffic on how to manage GNSS interference. Here it is again, so you can’t miss it! \u2b07\ufe0f<\/p>\n

\"\"<\/a><\/p>\n

Key takeaway from this:<\/span> If you suspect or know that your aircraft has encountered any kind of GPS interference (both jamming or spoofing), NAT-bound traffic must let their first NAT ANSP know in the RCL – <\/strong>even if the aircraft appears to have recovered.<\/strong><\/b><\/span><\/p>\n

This is prefixed by ‘ATC REMARKS\/GNSS INTERFERENCE’ and must include details of any system degradations.<\/p>\n

A few messages to keep handy are:<\/p>\n

\u2018ATC REMARKS\/GNSS INTERFERENCE NO IMPACT.\u2019<\/strong><\/p>\n

\u2018ATC REMARKS\/GNSS INTERFERENCE NO CPDLC\/ADS\u2019<\/strong><\/p>\n

\u2018ATC REMARKS\/GNSS INTERFERENCE RNP 10 ONLY\u2019<\/strong><\/p>\n

\u2018ATC REMARKS\/GNSS INTERFERENCE NON-RNP10<\/strong><\/p>\n

By including your status in the RCL, you are giving ATC a head\u2019s up\u00a0before\u00a0you arrive.<\/strong><\/p>\n

In most cases, you will still be allowed in the NAT HLA.<\/strong> A loss of RNP 4 isn\u2019t a deal breaker, as you can still enter under RNP 10. But your clearance may be less optimal (likely level changes) due to the increased separation from other traffic.<\/p>\n

The big one to look for is a loss of RNP 10.<\/strong> You will not be cleared into the NAT HLA, and instead will need to remain below FL290 or above FL410. With an obvious fuel impact, this may lead to an unplanned diversion.<\/p>\n

The Bulletin includes a handy flow chart that\u2019s worth printing and keeping in your flight bag.<\/p>\n

\"\"<\/a>

Click for PDF.<\/p><\/div>\n

Latest ICAO Feedback<\/h4>\n

The latest three-yearly ICAO Assembly was held in Montreal from Sep 23 – Oct 3.<\/p>\n

During the event, ICAO issued its strongest condemnation yet<\/a> of both Russia and North Korea<\/strong>, directly blaming them for deliberate GNSS interference<\/strong> in violation of the Chicago Convention. Russia, in particular, has been blamed by ICAO for destabilising navigation<\/strong> across European airspace.<\/strong><\/p>\n

We continue to receive regular reports from OPSGROUP members of both jamming and spoofing. Interference is now a regular occurrence in the Baltic region, particularly around Kaliningrad, Eastern Finland, the Baltic Sea, and nearby airspace.<\/strong> Other reports have been received from Germany, Poland and Norway.<\/strong><\/p>\n

Recent airspace incursions, airstrikes and drone activity associated with the ongoing conflict in Ukraine<\/strong> have almost certainly escalated the use of GPS interference as a defensive measure. Civil aviation will continue to operationally grapple with this hazard. With no obvious solution in site, our best defence remains procedures like the one detailed above.<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"

An OPSGROUP member on a recent westbound NAT flight from the Middle East received the…<\/p>\n","protected":false},"author":49,"featured_media":12760,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[405,404,21,2258],"class_list":{"0":"post-28822","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-briefings","8":"tag-gnss","9":"tag-gps","10":"tag-nat","11":"tag-rcl"},"_links":{"self":[{"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/posts\/28822","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/users\/49"}],"replies":[{"embeddable":true,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/comments?post=28822"}],"version-history":[{"count":31,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/posts\/28822\/revisions"}],"predecessor-version":[{"id":28890,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/posts\/28822\/revisions\/28890"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/media\/12760"}],"wp:attachment":[{"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/media?parent=28822"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/categories?post=28822"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/tags?post=28822"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}