{"id":14290,"date":"2021-10-20T09:42:22","date_gmt":"2021-10-20T13:42:22","guid":{"rendered":"https:\/\/ops.group\/blog\/?p=14290"},"modified":"2024-05-14T05:03:00","modified_gmt":"2024-05-14T09:03:00","slug":"communication-breakdown-on-the-nat","status":"publish","type":"post","link":"https:\/\/ops.group\/blog\/communication-breakdown-on-the-nat\/","title":{"rendered":"Communication Breakdown on the NAT"},"content":{"rendered":"

Lost comm procedures in the NAT HLA (or when you\u2019re trying to get into the NAT HLA) are a complex and confusing thing, so here is our “Natter on the NAT” – a recap on what to do when nobody wants to talk to you.<\/strong><\/p>\n

You aircraft has lost everything it uses to communicate.<\/h4>\n

The likelihood of every communication system you have breaking all at once is fairly minimal, and given the equipment requirements to enter the NAT HLA, you are going to have more than just VHF onboard. You will also have HF, datalink, probably SATCOM\u2026<\/p>\n

But if it does happen (maybe a freak bolt of mega lightning or something) then the first thing to do is still try each system, including back up boxes, <\/strong>and your headset for that matter.<\/p>\n

Still no luck? Don\u2019t panic. While you can\u2019t hear anyone, or talk to anyone, they can all still hear and talk to each other. So you are the only uncoordinated thing out there<\/strong> right now. First up, let ATC know by squawking 7600.<\/strong><\/p>\n

\"\"

This shows the minimum equipment you need for the NAT HLA.<\/p><\/div>\n

The next thing to do depends on where in the NAT you are.<\/p>\n

Already in it?<\/b><\/span> Great, simple. You already have a clearance and you already know where you are going, so carry on as you are, transmit blind, and once you exit follow the lost comm procedures for the place you are entering.<\/p>\n

Not in it, but have a clearance?<\/b><\/span> <\/b>This is up to you really. You have your clearance (and have confirmed it) so ATC know that you know that they know that you know what you are cleared to do. So if you want to stick to in and head on in you can, but you are going to have to maintain your speed, level etc all the way through. And if you have a weather issue or an emergency you are also going to be on your own.<\/strong><\/p>\n

No clearance yet?<\/b><\/span> <\/b>This one is a bit tougher. It probably isn\u2019t the best plan to head in (following your flight planned route), especially if you are heading into Shanwick. Shanwick have diversion procedures in place<\/strong> to take you to Shannon and the best idea might be to head there and get yourself fixed.<\/p>\n

The exact wording is “it is strongly recommended that a pilot experiencing communications failure whilst still in SHANNON FIR\/UIR\/SOTA\/NOTA does not enter SHANWICK Oceanic Control Area”<\/em>.<\/p>\n

The Irish AIP have the procedures for comms failure if planning on entering\u00a0and they are worth a read.<\/a>\u00a0They have a pretty handy summary of what to do for Shanwick in there.<\/p>\n

\"\"

It is unlikely you will ever lose every system. Check backup boxes and attempt contact via other methods.<\/p><\/div>\n

You have lost HF<\/h4>\n

If you\u2019re already in, there isn\u2019t much you can do. Stick to your clearance and keep in contact on CPDLC. Remember, HF frequencies are pretty rubbish at the best of times so if you discovered the failure while trying to make an HF call, then try a different frequency.<\/p>\n

Lower ones work better at night, higher ones by day<\/strong>, and always try the middle ones for good measure. Have a quick glance at space weather too because if there are geomagnetic storms forecast it could be there is a general HF blackout going on that is affecting everyone.<\/p>\n

Collins Aerospace publish a daily list of HF frequency assignments<\/strong> for their side (the US side) of the North Atlantic and you can find them here. <\/a>\u00a0Worth a look before you fly, if you’re going to be in the US North Atlantic area.<\/p>\n

The Comms requirements changed a bit in February 2021<\/a>, and basically, what they say, is that you need two long-range comms systems<\/strong> if routing anywhere outride VHF coverage. One of these has to be HF.<\/strong><\/p>\n

Here is a particularly horrible picture of where VHF has got you covered.<\/p>\n

\"\"

If you’re flying at FL300, this is your VHF coverage.<\/p><\/div>\n

You can route through if your HF was already broken and you told ATC in advance<\/strong> (Item 18 on the flight plan) and they gave you the thumbs up, but if you are heading there and it goes suddenly before entry then you are going to need to talk to ATC.<\/p>\n

Shanwick OCA needs HF, no exceptions<\/strong> (not even the Blue Spruce routes that fall within the Shackwick OCA) so don\u2019t go diverting immediately but do get talking (on whatever else you have available) to sort it out before you enter.<\/p>\n

We might as well cover HF blackouts while we\u2019re here.<\/h4>\n

These happen when space weather happens. They aren\u2019t super common and they are usually minor (lasting 10 minutes or less)<\/strong>. But when they do happen, everyone can lose HF, including ATC.<\/p>\n

You probably should make position reports on 123.45<\/strong> to be on the safe side because there might be no coordination between traffic and ATC for the period of the blackout.<\/strong> Keep trying different methods to get hold of ATC as well (but don\u2019t get all crazy at them though – they will be busy and will contact you when able).<\/p>\n

Now, because coordination between ATC and everyone else is an issue, they actually don\u2019t want everyone diverting all over the place, so stick with your clearances. The big point here is – if you don\u2019t have a NAT clearance yet, you need to stick to your DOMESTIC clearance. <\/b>That means you have to stick with what you were most recently told to do, not what you filed for on your flight plan.<\/p>\n

\"\"

The NOAA scales – anything above R1 or R2 is rare.<\/p><\/div>\n

Datalink problems.<\/h4>\n

So your texting system is on the blink? Unfortunately, the Datalink Mandate is in force<\/strong><\/a> now so you need this to enter. If you ask ATC nicely (and have everything else working) they might still let you in. \u00a0<\/span><\/p>\n

You don\u2019t need it if you are north of 80N, in NYC Oceanic, on Tango 9 or 290 route, or in the \u2018surveillance airspace\u2019 over Iceland\/Greenland<\/strong>. So if you can re-route via any of this, that might be a good plan. Otherwise you do also have the option of flying above or below the NAT HLA (so below FL290 or above FL410) if your aircraft (and your fuel) can do that.<\/p>\n

Remember, datalink uses CPDLC and ADS-C<\/strong> so if either of them is broken, your datalink probably is as well.<\/p>\n

SATCOM<\/h4>\n

Most datalink systems also require SATCOM – so while you don\u2019t need it to use it, if your aircraft needs it for the Datalink to work, then what we said above applies.<\/p>\n

Let\u2019s talk ATC – Strikes.<\/h4>\n

An ATC strike is *usually notified in advance. The chances of them walking out without warning is fairly remote. So if you know about it beforehand, plan accordingly. If it happens while you\u2019re there, treat it as an ATC Zero event.<\/strong><\/p>\n

ATC Zero.<\/h4>\n

There is no-one out there. Maybe they had to evacuate? There was some sort of emergency or major technical issue that\u2019s has taken down an entire ATC provider? Occasionally it is Notam-ed, but in that case you won\u2019t have been given clearance to head through, so we are talking those unforeseen sudden zero events.<\/strong><\/p>\n

Each region has its own contingency procedures<\/strong> which you can find in their AIP, or better still in NAT Doc 006, which was also updated in Feb 2021.<\/a><\/p>\n

These routes are really for when big stuff happens – the entire ATC for a sector is evacuated for example. In most cases, other units will try and manage control as best they are able, but it will be fairly limited.<\/p>\n

So, if you\u2019re already inside, continue<\/strong> and start trying to make contact with the next sector (as they will hopefully be managing control as much as they can). If it is a big ATC zero event you are probably going to have to follow the contingency routes to exit the NAT HLA (rather than your clearance) but this will be \u2018activated\u2019 by whichever ATC is taking over control.<\/p>\n

If you already have your clearance<\/strong> to enter you can, and you can transmit position reports on 123.45, but it is not really advisable. The best plan is to organise a re-routing.<\/p>\n

If you don\u2019t already have a clearance<\/strong> then you aren\u2019t going to be able to enter the ATC zero bit and you will need to plan a re-route around the affected sector.<\/p>\n

Feeling the need to read more?<\/h4>\n

Here are some handy links to things on the subject.<\/p>\n

Changes to NAT Doc 006<\/a>\u00a0– our blog post summarising what these were.<\/p>\n

The Irish AIP (again)<\/a> in case you missed the link earlier.<\/p>\n

The GOLD Manual (2017 edition)<\/a>\u00a0– for all your Datalink info.<\/p>\n

Opsgroup Member?<\/h4>\n

Then click here<\/a> to download our handy little Comms Issues on the NAT “Opsicle” <\/strong>– a refreshing bit of ops info, just for members.<\/p>\n

\"\"<\/a>

OPSGROUP members: click to download PDF.<\/p><\/div>\n

If you\u2019re not an OPSGROUP member<\/strong>, but you\u2019d like to be, you can join here<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

Lost comm procedures in the NAT HLA (or when you\u2019re trying to get into the…<\/p>\n","protected":false},"author":51,"featured_media":17622,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[1567,1937,1709,192],"class_list":{"0":"post-14290","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-briefings","8":"tag-atc-zero","9":"tag-hf-blackout","10":"tag-lost-comms","11":"tag-nat-hla"},"_links":{"self":[{"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/posts\/14290","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\/51"}],"replies":[{"embeddable":true,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/comments?post=14290"}],"version-history":[{"count":18,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/posts\/14290\/revisions"}],"predecessor-version":[{"id":25284,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/posts\/14290\/revisions\/25284"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/media\/17622"}],"wp:attachment":[{"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/media?parent=14290"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/categories?post=14290"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/tags?post=14290"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}