{"id":29746,"date":"2026-02-25T16:44:11","date_gmt":"2026-02-25T21:44:11","guid":{"rendered":"https:\/\/ops.group\/blog\/?p=29746"},"modified":"2026-02-25T17:01:22","modified_gmt":"2026-02-25T22:01:22","slug":"nat-cpdlc-route-uplinks-crew-confusion-and-errors","status":"publish","type":"post","link":"https:\/\/ops.group\/blog\/nat-cpdlc-route-uplinks-crew-confusion-and-errors\/","title":{"rendered":"NAT CPDLC Route Uplinks: Crew Confusion and Errors"},"content":{"rendered":"<p>On Jan 27, the FAA published an <a href=\"https:\/\/www.faa.gov\/other_visit\/aviation_industry\/airline_operators\/airline_safety\/info\/all_infos\/InFO26005.pdf\" target=\"_blank\" rel=\"noopener\">Information Note for Operators (InFO)<\/a> warning that <strong>crews have been responding to CPDLC route uplinks late or incorrectly<\/strong> when entering or while inside Gander\u2019s oceanic airspace.<\/p>\n<p>Aside from confusion, this has led to<strong> increased frequency congestion, controller workload, and interventions to prevent route deviations.<\/strong><\/p>\n<p>The InFO isn\u2019t regulatory, but it highlights a persistent NAT issue that the FAA wants operators and training departments to address.<\/p>\n<p>Here\u2019s what\u2019s going on.<\/p>\n<h4 class=\"p1\">The Backstory<\/h4>\n<p>It\u2019s no surprise there\u2019s confusion. Over the past few years, NAT oceanic procedures have changed significantly.<\/p>\n<p>In 2023, the NAT began transitioning toward <strong>Oceanic Clearance Removal (OCR).<\/strong> Gander implemented this change, meaning crews submit a Request for Clearance (RCL) prior to the Oceanic Entry Point. If no change is required, they are considered cleared as filed. If a change is required, ATC issues a specific amended route or level.<\/p>\n<p>In December 2024, Gander began <strong>issuing amended oceanic routes and levels via CPDLC<\/strong> following the RCL process. The goal was to standardise amendments via datalink rather than voice, and reduce readback\/hearback error opportunities.<\/p>\n<p>It didn\u2019t go smoothly. Reports of confusion followed &#8211; especially around how amended routes were being issued and how they were being integrated into the FMS.<\/p>\n<p>In May 2025, NAV CANADA <a href=\"https:\/\/ops.group\/blog\/back-to-the-radio-gander-goes-voice-only-pre-oceanic\/\">temporarily reverted<\/a> to <strong>issuing pre-oceanic entry amendments by VHF instead.<\/strong> However, Gander has indicated it intends to resume CPDLC route uplinks, potentially before summer 2026.<\/p>\n<p>So this issue isn\u2019t historical. It\u2019s current \u2013 and likely to become more relevant again soon.<\/p>\n<h4 class=\"p1\">Crew Error<\/h4>\n<p data-start=\"1958\" data-end=\"2054\">Gander has reported a significant number of uplinks that are not promptly or correctly actioned.<\/p>\n<p data-start=\"2056\" data-end=\"2093\"><strong>The typical sequence looks like this:<\/strong><\/p>\n<p data-start=\"2095\" data-end=\"2301\"><em>CPDLC route uplink sent \u2192 crew responds \u201cWILCO\u201d \u2192 about 5 minutes later ATC sends \u201cCONFIRM ASSIGNED ROUTE\u201d \u2192 crew replies with the route string (e.g. N47A RESNO 47N050W 48N040W 49N030W 49N020W MALOT GISTI).<\/em><\/p>\n<p data-start=\"2303\" data-end=\"2333\"><strong>ATC is verifying three things:<\/strong><\/p>\n<ul>\n<li data-start=\"2337\" data-end=\"2374\">You received the correct clearance.<\/li>\n<li data-start=\"2337\" data-end=\"2374\">You loaded the correct route.<\/li>\n<li data-start=\"2337\" data-end=\"2374\">Your FMS matches what they issued.<\/li>\n<\/ul>\n<p data-start=\"2449\" data-end=\"2585\"><strong>The problem arises when crews respond to \u201cCONFIRM ASSIGNED ROUTE\u201d before the new route has actually been loaded and verified in the FMS.<\/strong><\/p>\n<p data-start=\"2587\" data-end=\"2678\">In that case, the system transmits the currently active route &#8211; not the newly assigned one. That mismatch generates an alert on the controller\u2019s side.<\/p>\n<p data-start=\"2740\" data-end=\"2810\">There\u2019s a second issue as well: misinterpreting certain CPDLC uplinks.<\/p>\n<p data-start=\"2812\" data-end=\"2920\"><strong>UM79 \u201cCLEARED TO [point] VIA ROUTE CLEARANCE\u201d is not a direct-to clearance.<\/strong> It is a new route to that point.<\/p>\n<p data-start=\"2922\" data-end=\"3031\"><strong>UM80 \u201cCLEARED ROUTE CLEARANCE\u201d is not \u201ccleared as filed.\u201d<\/strong> It is a new route that must be loaded and executed.<\/p>\n<p data-start=\"3033\" data-end=\"3088\">In either case, these errors trigger something called an &#8216;out-of-conformance alert&#8217; to controllers. This is when small CPDLC errors turn into big ATC workload.<\/p>\n<p data-start=\"3090\" data-end=\"3303\">The scale of the issue is not trivial. The North Atlantic Central Monitoring Agency reported 475 lateral errors in 2025 &#8211; a 71% increase over the previous year. Total errors across all categories rose 29%, to 600.<\/p>\n<h4><strong>Out-Of-Conformance Alerts<\/strong><\/h4>\n<p>Behind the scenes, Gander\u2019s system compares what you are expected to fly with what you are actually flying.<\/p>\n<p>When ATC issues an amended oceanic route or level, this info is entered into their system as a &#8216;reference trajectory&#8217;. Your aircraft reports its actual position and intent via ADS-C, and the system continuously compares the two.<\/p>\n<p><strong>If there is a mismatch &#8211; whether because the wrong route was loaded or the wrong route was confirmed &#8211; an out-of-conformance alert is generated.<\/strong><\/p>\n<p>These take time for controllers to clear, cause distraction and add to frequency congestion. These aren&#8217;t necessarily a loss of sep, but they are a big deal in busy NAT airspace to prevent potential for traffic situations.<\/p>\n<p><strong>In other words, if you reply to &#8220;CONFIRM ASSIGNED ROUTE&#8221; before loading it, you&#8217;re sending ATC your old one.<\/strong><\/p>\n<h4 class=\"p1\"><b>So, what does the FAA suggest?<\/b><\/h4>\n<p>The key takeaway is simple: <strong>load the new route, verify it matches the clearance, then confirm it.<\/strong><\/p>\n<p class=\"p1\">The info note lists a bunch of useful resources to help with this, that we have re-produced below:<\/p>\n<ul>\n<li>NAT Oceanic Clearance Removal Bulletin, <a href=\"https:\/\/www.icao.int\/EURNAT\/EUR-NAT-DOCS?fid=3493\" target=\"_blank\" rel=\"noopener\">2023_001. <\/a><\/li>\n<li>NAT Oceanic Errors Safety Bulletin (OESB), <a href=\"https:\/\/www.icao.int\/EURNAT\/EUR-NAT-DOCS?fid=3493\">2017_002,<\/a> CPDLC section.<\/li>\n<li>Advisory Circular (AC) <a href=\"https:\/\/www.faa.gov\/regulations_policies\/advisory_circulars\/index.cfm\/go\/document.list\/?q=%2291-70%22&amp;statusID=2\" target=\"_blank\" rel=\"noopener\">91-70D<\/a>, Oceanic and Remote Continental Airspace Operations, paragraph 4.4.3 and Figure 4-1.<\/li>\n<li>AIP <a href=\"https:\/\/www.navcanada.ca\/en\/aeronautical-information\/aip-canada.aspx\" target=\"_blank\" rel=\"noopener\">Canada, ENR 7<\/a>\u00a0North Atlantic (NAT) Operations.<\/li>\n<li>ICAO Global Operational Data Link Document (GOLD) <a href=\"https:\/\/ops.group\/blog\/wp-content\/uploads\/2026\/02\/GOLD-reroute-procedures.pdf\" target=\"_blank\" rel=\"noopener\">Reroute Procedures.<\/a><\/li>\n<\/ul>\n<h4><strong>More Questions?<\/strong><\/h4>\n<p>We&#8217;ll try and answer them. If we can&#8217;t, we&#8217;ll put you in touch with who can. You can reach us on <a href=\"mailto:blog@ops.group\">blog@ops.group<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>On Jan 27, the FAA published an Information Note for Operators (InFO) warning that crews&#8230;<\/p>\n","protected":false},"author":49,"featured_media":29822,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[48,102,21],"class_list":{"0":"post-29746","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-briefings","8":"tag-cpdlc","9":"tag-gander","10":"tag-nat"},"_links":{"self":[{"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/posts\/29746","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=29746"}],"version-history":[{"count":26,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/posts\/29746\/revisions"}],"predecessor-version":[{"id":29821,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/posts\/29746\/revisions\/29821"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/media\/29822"}],"wp:attachment":[{"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/media?parent=29746"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/categories?post=29746"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/tags?post=29746"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}