{"id":24344,"date":"2024-01-22T09:34:01","date_gmt":"2024-01-22T14:34:01","guid":{"rendered":"https:\/\/ops.group\/blog\/?p=24344"},"modified":"2024-01-23T08:12:18","modified_gmt":"2024-01-23T13:12:18","slug":"nat-conundrums-volume-iv","status":"publish","type":"post","link":"https:\/\/ops.group\/blog\/nat-conundrums-volume-iv\/","title":{"rendered":"NAT Conundrums Volume IV: Contingency Procedures"},"content":{"rendered":"
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n

Welcome to our 4th Volume of North Atlantic Conundrums!<\/p>\n

Volume I<\/a>\u00a0covered the following three conundrums:<\/b><\/p>\n

1. To SLOP, or not to SLOP?
\n2. What\u2019s the difference between the NAT Region and the NAT HLA?
\n3. Can I fly across the North Atlantic without Datalink?<\/p>\n

Volume II<\/a>\u00a0covered these additional three:<\/b><\/p>\n

4. Do you need to plot on Blue Spruce Routes?
\n5. Do we still fly Weather Contingency Procedures on Blue Spruce routes?
\n6. When can we disregard an ATC clearance and follow the contingency procedure instead?<\/p>\n

Volume III<\/a> looked at: <\/b><\/p>\n

7. GOTA airspace.<\/p>\n

And this post, Volume IV, looks at NAT Contingency Procedures –\u00a0<\/b>not those related to weather issues (which are well-known and described in the regs without the risk of misinterpretation), but those related to times when you need to deviate from your ATC clearance<\/span> (due to comms issues, turbulence, depressurization, engine failure, immediate diversion, and other emergency situations).<\/p>\n<\/div>\n<\/div>\n

\n
\n

\"\"<\/p>\n

What are in-flight contingency procedures on the NAT, and which regulation governs them?<\/h4>\n

These are established to address situations where aircraft may encounter difficulties or emergencies while operating in the NAT airspace. They are primarily governed by the ICAO Document 4444, which outlines regulations for air traffic management practices and procedures. In this article, we will focus specifically on non-weather related contingency procedures.<\/b><\/p>\n

I\u2019ve heard of the NAT Doc 007. Is it the main reference for NAT contingency procedures?<\/h4>\n

Yes and no. While the NAT Doc 007 is a valuable resource for operators in the North Atlantic region, it\u2019s important to note that it explicitly states, \u201cthis document is for guidance only.<\/i>\u201d The primary regulatory framework for contingency procedures in the NAT remains ICAO DOC 4444.<\/strong><\/p>\n

Do I need a clearance to continue my flight?<\/h4>\n

Yes, you typically need a clearance to continue your flight. If an aircraft is unable to continue the flight in accordance with its ATC clearance, a revised clearance shall be obtained, whenever possible, prior to initiating any action.<\/p>\n

Are there situations where I may not have a clearance?<\/h4>\n

There may be exceptional circumstances (such as emergencies or comms difficulties) where obtaining a clearance becomes challenging. In such cases, pilots should prioritize safety and follow established contingency procedures to ensure safe flight operations while seeking to obtain a revised clearance as soon as possible.<\/p>\n

If I have already reported a contingency situation and subsequently receive a clearance, should I always follow the new clearance?<\/h4>\n

Yes, if you have been issued a clearance, you should adhere to it as long as it is safe to do so. If the new clearance is not safe, request an alternative clearance from ATC. Safety should always be the top priority.<\/p>\n

If I have not yet been able to obtain a clearance, what should I do?<\/h4>\n

The procedure changed on the NAT in 2019, and then became the global standard in 2020 – so there is now one standard set of Contingency Procedures for all oceanic airspace worldwide<\/strong> (well, almost all airspace – there are still a few places which have slight differences, although these will eventually get aligned):<\/p>\n<\/div>\n

Leave your cleared track or ATS route by initiating a turn of at least 30 degrees to the right or left, in order to establish and maintain a parallel, same-direction track or ATS route offset of 5 NM. <\/span><\/p>\n

Once established on a parallel, same-direction track or ATS route offset by 5.0 NM, you have two options: <\/span><\/p>\n

    \n
  1. Establish a 500 ft vertical offset (or 1000 ft if above FL 410) from the usual flight levels, and proceed as required by the operational situation, or if an ATC clearance has been obtained, in accordance with the clearance.<\/span><\/li>\n
  2. Descend below FL 290, and establish a 500 ft vertical offset from those flight levels normally used, and proceed as required by the operational situation or if an ATC clearance has been obtained, in accordance with the clearance.<\/span><\/li>\n<\/ol>\n
    \n

    The first rule is straightforward, involving manoeuvring to navigate between significant traffic operating in the North Atlantic High-Level Airspace (NAT HLA) by adjusting altitude with a 500 or 1000 feet offset before making a turn. However, the second rule, when maintaining altitude is not feasible, can sometimes be misinterpreted.<\/strong><\/p>\n

    Why is the rule of descending below FL290 sometimes misunderstood?<\/h4>\n

    The current wording of ICAO Doc 4444<\/strong> can sometimes lead to confusion, as it may imply that aircraft must first descend to establish a 500 ft vertical offset before making any lateral deviation. This is not the intended interpretation.<\/strong><\/p>\n

    This misinterpretation was perpetuated by the 2023 version of the NAT Doc 007<\/strong> (version 2023-1), which said: \u201cdescend below FL 290, and establish a 150 m (500 ft) vertical offset from those flight levels normally used, then proceed<\/strong><\/span>\u2026”.<\/em> This wording inadvertently supported the misconception by introducing the word \u201cthen\u201d implying a strict sequence in the procedure.<\/p>\n

    The new 2024 version of the NAT Doc 007<\/strong> (version 2024-1), which becomes applicable in March 2024<\/a>, has been corrected, replacing the word \u201cthen\u201d with \u201cand\u201d, in line with ICAO Doc 4444.<\/p>\n

    How should it be understood?<\/h4>\n

    The purpose of updating the contingency procedures in Doc 4444 was notably to provide a clear and effective way for aircraft to safely navigate and disengage from OTS (Organized Track System) with adjacent and nearby PBCS tracks without the risk of collisions. This is achieved by offering two primary options:<\/p>\n

      \n
    1. Using vertical offsets; or<\/li>\n
    2. In cases where maintaining altitude becomes impractical and to mitigate the risk of conflicts with the majority of traffic, which is located within the NAT HLA, descending below FL 290 before diverging.<\/li>\n<\/ol>\n

      As a result, depending on the situation, lateral divergence can be initiated as soon as FL 290 is crossed during descent<\/strong>, without the prior obligation to establish first at a potentially low FL offset before proceeding with the divergence.<\/p>\n

      In cases of depressurization<\/strong> requiring a descent to lower levels, or an engine failure<\/strong> necessitating a descent to lower levels depending on ETOPS speed, it may be preferable to initiate the turn as soon as the aircraft passes FL 290 when the alternate airport is located behind. This helps save valuable time<\/strong>, approximately 10 minutes, in returning to the same point as when crossing FL 290, especially in emergency situations.<\/p>\n

      In other circumstances (like when the alternate airport is located ahead), a pilot may elect to establish the vertical offset first.<\/strong><\/p>\n

      The Doc 4444 regulations allow for both of these courses of action.<\/strong> Moreover, it\u2019s worth noting that the fuel planning for critical ETOPS scenarios typically does not account for continuing for a long time in the wrong direction before initiating divergence.<\/p>\n

      How do I know that this is the correct interpretation?<\/h4>\n

      Because we asked ICAO.<\/p>\n

      They told us that after reviewing all the working papers, it’s clear that the intent is focused on getting below FL290 before doing anything (if possible).<\/strong><\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n

      We also received confirmation that the SASP secretary, the ATM ops panel secretary, and the Flight Ops panel secretary had all discussed the issue and had agreed that the interpretation provided was correct. This does not reflect a specific panel viewpoint but rather a consolidated ICAO Secretariat view of the interpretation.<\/p>\n

      While it is preferable, given favorable conditions, to be at the offset level before initiating a turn (as this minimizes the potential for conflicts with other aircraft operating on adjacent tracks, providing some vertical \u2018separation\u2019 before turning across parallel tracks), the primary emphasis remains on descending below FL290.<\/strong> This priority is clarified in Doc 4444 Note 2 to 15.2.3.2(a) :<\/p>\n

      \u201cNote 2.\u2014 Descent below FL 290 is considered particularly applicable to operations where there is a predominant traffic flow (e.g. east-west) or parallel track system where the aircraft\u2019s diversion path will likely cross adjacent tracks or ATS routes. A descent below FL 290 can decrease the likelihood of conflict with other aircraft, ACAS RA events and delays in obtaining a revised ATC clearance.\u201d<\/span><\/em><\/p>\n

      Ultimately, in emergency situations where it becomes absolutely necessary to deviate from the rules, it’s down to the pilot-in-command to assess the validity of an immediate diversion in consideration of the risk of conflict with nearby aircraft in the high-level oceanic airspace. As ICAO Annex 2 says:<\/p>\n

      \u201cThe pilot-in-command of an aircraft shall have final authority as to the disposition of the aircraft while in command… the pilot-in-command may depart from these rules in circumstances that render such departure absolutely necessary in the interests of safety.”<\/span><\/em><\/p>\n

      \n
      \n
      \n
      \n

      Key takeaways<\/h4>\n

      In non-weather contingency scenarios, once you’re established on a parallel, same direction track or ATS route, offset by 5 NM, there are two cases to consider:<\/p>\n

        \n
      • If you can maintain altitude, adjust your altitude by 500 or 1000 feet and then make a lateral turn to insert yourself between the traffic in the NAT-HLA.<\/li>\n
      • If maintaining altitude is not possible, descend below FL290 while continuing your descent toward a 500 feet offset, allowing you to diverge beneath the traffic in the NAT HLA.<\/li>\n<\/ul>\n

        In cases where maintaining altitude is not feasible, there is no obligation to first establish an offset level before initiating divergence once FL 290 has been crossed during descent.<\/strong><\/p>\n

        With any luck, future versions of Doc 4444 will make all of this more explicit, in order to avoid various misinterpretations!<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

        Welcome to our 4th Volume of North Atlantic Conundrums! Volume I\u00a0covered the following three conundrums:…<\/p>\n","protected":false},"author":32,"featured_media":24433,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[2086,21,20],"class_list":{"0":"post-24344","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-briefings","8":"tag-conundrums","9":"tag-nat","10":"tag-north-atlantic"},"_links":{"self":[{"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/posts\/24344","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\/32"}],"replies":[{"embeddable":true,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/comments?post=24344"}],"version-history":[{"count":11,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/posts\/24344\/revisions"}],"predecessor-version":[{"id":24446,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/posts\/24344\/revisions\/24446"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/media\/24433"}],"wp:attachment":[{"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/media?parent=24344"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/categories?post=24344"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ops.group\/blog\/wp-json\/wp\/v2\/tags?post=24344"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}