{"id":16831,"date":"2022-01-20T08:25:02","date_gmt":"2022-01-20T13:25:02","guid":{"rendered":"https:\/\/ops.group\/blog\/?p=16831"},"modified":"2023-01-25T08:09:00","modified_gmt":"2023-01-25T13:09:00","slug":"nat-doc-007-changes-2022","status":"publish","type":"post","link":"https:\/\/ops.group\/blog\/nat-doc-007-changes-2022\/","title":{"rendered":"NAT Doc 007 Changes 2022"},"content":{"rendered":"

It has happened again. They have made amendments to NAT Doc 007.<\/strong> We took a look and the first thing we noticed is a lot of red text!<\/span><\/strong><\/p>\n

Thankfully, on reading it, we have determined there are not really any actual changes<\/i>\u00a0(i.e. nothing that you probably don\u2019t already know about). It is more a great rewording to incorporate things you already know about in a tidier and more coherent way.<\/p>\n

So here is a summary of the changes, and here is a link<\/a> in case you do want to take a look for yourself. Version 2022-1 is applicable from Jan 2022.\u00a0<\/strong><\/p>\n

The Very Simple Summary<\/h3>\n

MNPS is out<\/h4>\n

They have removed all historical references to it.<\/p>\n

OWAFS is in<\/h4>\n

Well, it was already but now we have some definitions and a few additional paragraphs on it.<\/p>\n

OWAFS (in case you don’t know) means \u2018Operations Without an Assigned Fixed Speed\u2019<\/strong> and it means that the requirement to issue a fixed Mach in the NAT has been removed. If you are told to \u2018Resume Normal Speed\u2019 this means you can fly at your chosen cost index speed. Just let ATC know if it is a big change (M.02 or more)<\/strong>.<\/p>\n

The Chapter by Chapter Review<\/h3>\n

Chapter 1<\/h4>\n

MNPS references have been removed, as have the old MNPS performance specs. Now it is all PBN. They have also taken out the old bits about trials and implementation because MNPS evolution to NAT HLA and PBN has happened.<\/p>\n

Chapter 2<\/h4>\n

They have amended the examples of NAT Track Messages. No great difference.<\/p>\n

Chapter 3<\/h4>\n

5.1.12<\/strong> is the new paragraph on OWAFS and it says this:<\/p>\n

\u201cWith the implementation of OWAFS, flight crews can expect ATC to issue the clearance RESUME NORMAL SPEED when traffic permits after oceanic entry. This clearance allows the flight crew to select a cost index (ECON) speed instead of a fixed Mach number with the condition that ATC must be advised if the speed changes by plus or minus Mach .02 or more from the last assigned Mach number.\u201d<\/i><\/p>\n

Chapter 6<\/h4>\n

There are some subtle word changes here. The one to know is under 6.1.22<\/strong> (and throughout the chapter). When using HF, SATVOICE or CPDLC flight crew SHALL <\/b>maintain a continuous air-ground communication.<\/b><\/p>\n

‘Shall’ not ‘should’.\u00a0It also used to just say \u2018listening\u2019 instead of that continuous air-ground bit.<\/p>\n

Chapter 7\u00a0<\/span><\/h4>\n

This whole chapter is about ‘Application of Mach Number Technique’. So more OWAFS info.\u00a0<\/span><\/p>\n

In summary<\/strong> – You should receive a \u2018RESUME NORMAL SPEED\u2019 clearance after oceanic entry. If it doesn\u2019t come through automatically then request normal speed.<\/p>\n

ATC will still occasionally use mach number technique to maintain longitudinal spacing so if they give you an assigned mach number, stick to it. But if you get that \u201cresume normal speed\u201d clearance then you can fly at your cost index (ECON) speed and just let ATC know if it is more than a M0.02 difference.<\/p>\n

Chapter 10<\/h4>\n

Another \u2018should\u2019 to \u2018shall\u2019 change.<\/p>\n

If you are on T9 route<\/strong> then you shall <\/b>change your squawk to 2000 10 minutes after passing BEGAS or LASNO. If you are on T290<\/strong> then you shall <\/b>change it 10 minutes after ADVAT or GELPO<\/p>\n

A permanent military area also looks like it has been removed.<\/p>\n

That’s all we saw.<\/h4>\n

If you spot any changes we have missed please share them with us at news@ops.group<\/a><\/p>\n

Further reading<\/h4>\n

To see a full version of this new NAT Doc 007, with all the changes incorporated, go here<\/a>.<\/p>\n

The last time they updated it was back in July 2020, which you can read about here<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

It has happened again. They have made amendments to NAT Doc 007. We took a…<\/p>\n","protected":false},"author":51,"featured_media":16835,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[801,192,20,1368],"class_list":{"0":"post-16831","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-briefings","8":"tag-nat-doc-007","9":"tag-nat-hla","10":"tag-north-atlantic","11":"tag-owafs"},"_links":{"self":[{"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/posts\/16831","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=16831"}],"version-history":[{"count":11,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/posts\/16831\/revisions"}],"predecessor-version":[{"id":21178,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/posts\/16831\/revisions\/21178"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/media\/16835"}],"wp:attachment":[{"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/media?parent=16831"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/categories?post=16831"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/tags?post=16831"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}