You’re halfway across the Atlantic when ATC declares that they are suspending all services. TIBA procedures are now in effect. Would you know what to do next? As Covid infections impact ATC facilities, short notice closures are currently a constant risk. With the possibility of an entire oceanic ATC area being shut down due to Covid, there are some big questions to consider, and to factor in to your planning: Are you tankering enough fuel if you suddenly have to fly around large sections of oceanic airspace? Where are your ETPs? Do you have a wet footprint?

Back in 2011, there was an incident where transatlantic flights were not allowed to enter CYQX/Gander oceanic airspace due to a smoke situation in ATC control centre which meant that controllers had to be evacuated. They issued a Notam, but that wasn’t much use to the traffic en-route at the time, which all had to be re-routed around the CYQX/Gander Oceanic FIR – a vast portion of oceanic airspace.

Fast forward to March of this year, where New York Air Route Traffic Control Center was forced to temporarily close due to a controller testing positive for Covid-19. The affected airspace restricted flights into New York area airports, with aircraft having to take longer routes in order to avoid closed sectors, as well as Oceanic airspace which stretches from New York past Bermuda and services flights heading to the Caribbean, Europe, South America, and Africa.

The New York ARTCC is not the only ATC center that has been affected over the past few months due to controllers coming down sick with coronavirus. Eleven sites across the US, including at major airports in New York, Chicago, and Las Vegas, have been temporarily closed for cleaning, affected flight operations. Some facilities have been closed for several days leaving inbound and departing aircraft left to their own devices for taxi, take-off, and landing.

NAT Doc 006 is the official go-to manual to check what happens during these “ATC Zero” events on the North Atlantic, but the spate of recent ATC shutdowns in the US led the FAA to re-examine the increased potential for these situations occurring during the Covid crisis, and in early July they published a SAFO as a result.

The NAT Doc 006 and the US SAFO are great resources, but here are two more which you might not know about!

Code7700.com has published an excellent 2-page crib sheet with clear guidance for pilots on what to do in these situations. You can download it here:

And 30WestIP.com have recorded a video webinar discussing this topic in more detail, which you can view here:

July 2020: There’s a bunch of new things to tell you about the North Atlantic this month! Here’s a summary:
– Two new ICAO NAT Ops Bulletins
– An updated NAT Doc 007 from ICAO (aka the North Atlantic “Ops Bible”)
– A guide for pilots from the FAA about what to do if ATC suddenly has to suspend services
– Some juicy Notams from all the NAT FIRs extending the relaxation of the North Atlantic datalink mandate rules until the end of September.

ICAO NAT Ops Bulletins

Two new ICAO NAT Ops Bulletins have been published this week, but it looks like there’s no need to panic.

First up, there’s 2019_003 Rev 2: Data Link Performance Improvement Options, which is just an updated list of common datalink errors and what to do about them.

Second, there’s a new Bulletin called 2020_002: Surveillance Service in the NAT Region / Flight Crew Operating Procedures. This is a strange one. The message seems to be this: back in the old days, you used to get a call from ATC saying “radar service is terminated” or “surveillance service is terminated” when heading out into the NAT, or when crossing from one oceanic control centre to the next. But nowadays, with improved SSR equipment and ADS-B more widely implemented, you might not get this message anymore.

ICAO NAT Doc 007 (2020, Version 2)

ICAO has published an updated version of the NAT Doc 007, applicable from July 2020. There are only some minor changes from the previous version, concerning the Tango Routes:

• There’s now a specific note saying that state approval is required to operate on these.
• There’s also a change to the transponder procedures when using T9 or T290: normally you change transponder code to 2000 30mins after NAT entry, but because of the limited time spent in the NAT HLA when flying on T9 and T290 you should instead make this change 10mins after joining either of those routes.

T9 is southbound only, even levels between FL300-400. T290 is northbound only, odd levels from FL290-410. For more info on the Tango Routes, check out our article here.

What to do during “ATC Zero” events

You’re halfway across the Atlantic when ATC declares that they are suspending all services. TIBA procedures are now in effect. Would you know what to do next? As Covid infections impact ATC facilities, short notice closures are currently a constant risk.

The FAA has published a safety alert for international flight crew with contingency procedures in the event of loss of ATC services in Oceanic airspace. It’s a good one to have in your flight bag. Dispatchers and flight crew are reminded to be thoroughly familiar with AIP specific procedures and traffic management contingency plans for the regions they are operating in. You can read the FAA’s alert here.

They have also published another one for ATC Zero events in Terminal airspace, which you can read here. There have been multiple ‘ATC Zero’ events at major air traffic control centres due to Covid prevention and the subsequent cleaning required. The alert contains important information regarding instrument approach selection, TCAS use, alternate minima, aerodrome lighting and other CTAF procedures at unattended airports. There are also important considerations applicable to Part 121 operations discussed.

NAT Datalink Mandate

EGGX/Shanwick, BIRD/Reykjavik, CZQX/Gander, KZWY/New York Oceanic West and LPPO/Santa Maria have all published Notams extending the relaxation of the North Atlantic datalink mandate rules until the end of September. This is due to the fact that there’s still significantly less traffic because of all the Covid restrictions. Non-datalink mandate compliant aircraft may therefore continue to flight plan and operate across the North Atlantic between FL290-410 until Sept 30. For more info on the NAT Datalink Mandate, check out our article here.

In addition, ICAO are saying that due to the decrease in traffic, there is a significantly higher chance of flights being cleared as requested, and are encouraging operators to file and request their optimal profiles at all stages of the flight. Read ICAO’s guidance here.

For a brief history of the most significant North Atlantic-related ops changes, check out our dedicated article here.

NAT Doc 007 is the Bible of the North Atlantic. It’s full of NAT goodness – all the specifics about how to operate your aircraft safely through the complex airspace of the region is here.

And there’s another new edition!

The NAT changes over the last few years have been coming thicker and faster than the sandwiches at Katz’s Deli on the Lower East Side. And now, there’s more. Effective August 7th, 2019, NAT Doc 007, Version 3, is the latest tome to digest. As aviation documents go, it’s written in pretty digestible language. There’s just a lot in it. But this is the first time we’ve had 3 editions of this in one year.

So, we’re going to start naming them after 007 Movies to keep track of them all. This is the “Two is Not Enough” edition.

NAT Doc 007, Version 3, 2019:
Download the full NAT Doc 007.

So, here are the three things that have changed this time:

1. We got new SLOP rules! This is a biggie. Instead of the three previous choices (0, 1, or 2nm), we now have Twenty One choices! More on this below.

2. 99 problems and Datalink is one. The short version: check that you’ve got the latest software update for your datalink.

3. The next datalink mandate (2C) is capped at FL410. This comes in January 30th next year. And so, the Checklist for Dispatchers is updated.

The new SLOP rules

Now, let’s take a closer look at the big change – SLOP (Strategic Lateral Offset Procedure). To get up to speed, check out our full article on SLOP – the how, and why (and where).

The change here is that instead of just being able to SLOP 1 or 2 nm right of track, (or fly the centreline), you go from these three choices to twenty one – you can use any one of 21 Micro-SLOP offsets. Specifically: 0.0 nm, 0.1 nm, 0.2 nm …. OK, you get it. All the way up to 2.0 nm Right of track.

Simple, right?

Not quite. It’s not yet fully clear which of the OCA’s have given the green light for this, even though NAT Doc 007 now says you should Micro-SLOP if you can.

But, phoning around the Oceanic Houses, we’ve got this to tell you:

1. Gander – you can micro-SLOP right now! An AIP amendment will follow soon.
2. Shanwick – you can micro-SLOP right now! A Notam will be published soon, and the AIP will be updated in Dec 2019.
3. New York – they will allow micro-SLOP from 12th Sept 2019, and will update the AIP in Jan 2020.
4. Santa Maria – you can micro-SLOP right now! Nothing published officially yet, but that’s what the good people from the oceanic control centre have told us.
5. Iceland – just like New York, they will allow micro-SLOP here from 12th Sept 2019 as well. When that happens, you will still not be allowed to SLOP below FL285 within the Reykjavik CTA (that’s the domestic part over Iceland, and the airspace over Greenland above FL195). We asked them to publish a Notam about this – and they actually did!! Check it out!
6. Bodo – Nothing official yet, but ATC say they “have no objections” to operators micro-SLOPing right now. (Currently, SLOP is only allowed here above FL285 within the OCA.)

That’s the current picture as of 1100z on Monday 19th Aug.

We will update this as soon as we get more info. Got something for us? Email us!

Of all the hundreds of questions we see in OPSGROUP, one region stands out as the most asked about – the NAT/North Atlantic. So, we made one of our legendary guides, to get everything into one PDF.  It’s called “My first North Atlantic Flight is tomorrow” – and now we’ve updated it for 2018!

Contents:

• 1. What’s different about the NAT?
• 2. Changes in 2018, 2017, 2016, 2015
• 3. NAT Quick Map – Gander boundary, Shanwick boundary
• 4. Routine Flight Example #1 – Brussels to JFK (up at 5.45am)

• 5. Non Routine-Flights: No RVSM, No RNP4, No HF, 1 LRNS, No HLA, No ETOPS, No TCAS, No Datalink – what you can do and where you can go
• 6. Diversion Airports guide: Narsarsuaq, Sondy, Kef, Glasgow, Dublin, Shannon, Lajes, Fro Bay, Goose Bay, Gander, St. Johns
• 7. Airport data
• 8. Overflight permits – routine and special

• 9. Special NAT procedures: Mach number technique, SLOP, Comms, Oceanic Transition Areas, A successful exit, Screwing it up, Departing from Close Airports
• 10. North Atlantic ATC contacts for Shanwick, Gander, Iceland, Bodo, Santa Maria, New York – ATC Phone, Radio Station Phone, AFTN, Satcom, CPDLC Logon codes; and adjoining Domestic ATC units – US, Canada, Europe.
• 11. NAT FPL Codes
• 12. NAT Flight Levels
• 13. Flight Plan Filing Addresses by FIR
• 14. Links, Questions, Guidance

Excerpt from the Routine Flight #1:

To get your copy – there are three options:

1. OPSGROUP Members, login to the Dashboard and find it under “Publications > Guides”. All FSB content like this is included in your membership, or
2. Join OPSGROUP with an individual, team, or department/airline plan, and get it free on joining (along with a whole bunch of other stuff), or
3. Purchase a copy in the Flight Service Store!

Last week we reported on an equipment issue with Iridium satcom that prompted a ban by a number of Oceanic ATC agencies. Some aircraft were receiving massively delayed clearances sent by ATC via CPDLC – and one took the instruction and climbed 1000 feet, even though the message was meant for the flight the aircraft operated previously.

Here were the areas which had previously published Notams restricting the use of Iridium: Brazil Atlantico (SBAO), Auckland (NZZO), Chile (SCIZ), Japan (RJJJ), Anchorage (PAZA), Oakland (KZAK), New York (KZNY and KZWY).

However, all FIR’s have now removed their notams which banned the use of Iridium for CPDLC and ADS-C. This has happened after tests were performed last week using Iridium SATCOM which confirmed that Iridium no longer queues CPDLC uplinks for more than five minutes.

Article header photo by @Zelgomat

Last week we reported on an equipment issue with Iridium satcom that prompted a ban by a number of Oceanic ATC agencies. Some aircraft were receiving massively delayed clearances sent by ATC via CPDLC – and one took the instruction and climbed 1000 feet, even though the message was meant for the flight the aircraft operated previously.

Today, we checked-in again with all the oceanic ATC centres, to see what their current policy is on the issue.

EGGX/Shanwick told FSB that they are aware of the issue, reviewed it, but have decided not to ban the use of Iridium for either CPDLC or ADS-C just yet. LPPO/Santa Maria have the same position. So, in this airspace, you can use Iridium, for now.

CZQX/Gander said they did a safety analysis of it, and decided not to ban it. They have all kinds of conformance alerts in place to prevent any problems from happening – so if aircraft deviate they get notified immediately.

BIRD/Reykjavik aren’t that concerned about the issue – they use HF most of the time anyway.

Chile (SCIZ)
Japan (RJJJ)
Anchorage (PAZA)
Oakland (KZAK)
New York (KZNY and KZWY)
All these centres have published Notams instructing crews not to use Iridium for CPDLC or ADS-C. Until the fault is fixed, in those regions you’ll have to either use HF for ATC comms, or use another SAT provider.

Auckland (NZZO) and Brazil (Atlantico SBAO) have applied the ban to CPDLC alone. Use ADS-C if you like.

From Iridium themselves, they told FSB: “We’ve updated their queue management system. Every minute, there is a queue check. If there is any message that is older than 4 minutes, it marks as timed out, and will not be delivered. This update was done at ground level, so it does not require any software updates by the user. We’re still waiting on feedback from FAA workgroup on the fix and if it’s sufficient to allow use of Iridium for CPDLC and ADS-C.”

That’s it for now! We’ll keep you posted, or, even better – tell us below in the comment section if you hear news.

The 2017 version of NAT Doc 007, North Atlantic Airspace and Operations Manual, was published in January 2017 by ICAO/NAT SPG.

Download the original document here (PDF, 5mB), and see also:

• A summary of the changes in the 2017 edition
• The OPSGROUP NAT Ops Guide – “My First North Atlantic Flight is tomorrow”

Feb 15th, 2017 In the first six weeks of 2017 there have been some important changes on the NAT/North Atlantic. These are published in the latest edition of NAT Doc 007, January 2017.

• TCAS 7.1: From January 1st, 2017, TCAS 7.1 is required throughout the entire NAT region.
• Cruising Level: Effective 2017, you no longer need to file an ICAO standard cruising level in NAT airspace.
• Gross Nav Error:  is now defined as greater than 10nm (used to be 25nm)
• Contingency Procedure: Published January 2017, a new turn-back (180) procedure is introduced – turn back to parallel previous track by 15nm.
• Datalink Mandate Exemptions: Announced January 2017, new exemptions for Phase 2B of the Datalink mandate, which will start on December 7, 2017 (FL350-390). Exempt: Tango Routes, airspace north of 80N, and New York OCA.

Feb 15th, 2017: FSB published the full NAT Crossing Guide “My first North Atlantic Flight is tomorrow“.

– What’s different about the NAT, changes in 2017, 2016, 2015, NAT Quick Map
– Routine Flight Example #1 – Brussels to JFK (up at 5.45am)
– Non Routine-Flights: No RVSM, No RNP4, No HF, 1 LRNS, No HLA, No ETOPS, No TCAS, No Datalink – what you can do and where you can go
Take a look.

We say the words with trepidation, because it’s been promised a few times over the last few months but then closures continued – but what we can tell you is that:

• There was an agreement on July 18,  that appears to be holding
• There have been no closures of BIKF, BIRK, or BIRD in the last week or so.

With that in mind we think it’s safe to say that the strike is over, and it should be Ops normal through Iceland from now on.

We had some really positive hints at a resolution of the Iceland ATC strike last week, but it’s not over yet – by any measure. Today sees another long list of airspace and airport closures. Oceanic Eastbound, Westbound and landing traffic all affected.

BIKF/KEFLAVIK A0454/16 06JUL 1007Z

(NOTAMR A0453/16) – DUE TO STAFF SHORTAGE BIKF TWR SERVICE LIMITED
TO SCHEDULED COMMERCIAL AND INTERNATIONAL
FLIGHTS, AMBULANCE AND EMERGENCY  FLIGHTS.
NO TOUCH AND GOES OR LOW APPROACHES FOR VFR
TRAINING FLIGHTS, ONLY DEPARTURE AND ARRIVAL.
TWR BIKF SERVICE LIMITED TO AMBULANCE AND
EMERGENCY FLIGHTS ONLY DURING THE FOLLOWING
HOURS: 09:00-09:30, 11:30-12:00 AND 14:00-14:30. 06 JUL 10:05 2016 UNTIL 06JUL 21:00 2016.

BIRD/REYKJAVIK OACC A0452/16 05JUL 2146Z

(NOTAMR A0451/16) – DUE TO STAFF SHORTAGE IN REYKJAVIK OACC WESTBOUND
TFC PLANNING TO ENTER BIRD FROM ENSV VIA GUNPA,
VALDI, IPTON, INGAL, ISVIG AND EGPX VIA LIRKI, GONUT,
OLKER, MATIK AND RATSU AND THEN PROCEEDING INTO EGGX
OR CZQX SHALL REMAIN SOUTH OF BIRD CTA. 06 JUL 11:00 2016 UNTIL 06 JUL 20:00 2016.

BIRD/REYKJAVIK A0450/16 05JUL 1518Z

– DUE TO STAFF SHORTAGE IN REYKJAVIK CENTRE,
OPERATORS SHALL FILE TO COMPLY WITH THE FOLLOWING:
1. EASTBOUND TFC WILL NOT BE ACCEPTED FROM CZQX AND
EGGX EXCEPT  TRAFFIC WITH DESTINATION IN ICELAND,
SCANDINAVIA, BALTIC STATES AND RUSSIA.
2. EASTBOUND TRAFFIC FROM AERODROMES EAST OF 105W
WITH  DESTINATIONS IN THE MIDDLE EAST SHALL REMAIN CLEAR OF
BIRD CTA.
OPERATORS ARE URGED TO KEEP REQUESTS FOR LEVEL AND
SPEED AMENDMENTS WITHIN BIRD CTA TO A MINIMUM.
FOR FURTHER INFORMATION CALL REYKJAVIK SHIFT
MANAGER +354 424 4141. 06 JUL 02:00 2016 UNTIL 06 JUL 08:00 2016.

BIRD/REYKJAVIK A0452/16 05JUL 2146Z

(NOTAMR A0451/16) – DUE TO STAFF SHORTAGE IN REYKJAVIK OACC WESTBOUND
TFC PLANNING TO ENTER BIRD FROM ENSV VIA GUNPA,
VALDI, IPTON, INGAL, ISVIG AND EGPX VIA LIRKI, GONUT,
OLKER, MATIK AND RATSU AND THEN PROCEEDING INTO EGGX
OR CZQX SHALL REMAIN SOUTH OF BIRD CTA. 06 JUL 11:00 2016 UNTIL 06 JUL 20:00 2016.

The strike goes on … but there may be a solution by Friday this week. Icelandic MPs passed a bill forcing a resolution to the ongoing pay dispute with air traffic controllers. The new law states that the air traffic controllers’ union and the airport operator Isavia have until Friday to reach an agreement – failing this, the matter be sent to a court of arbitration for a final resolution.

In the interim, sporadic airport closures at BIKF/Keflavik and BIRK/Reykjavik continue, as do general airspace restrictions in the BIRD FIR. If you can avoid a stop in Iceland, it would seem sensible to do so until the conflict is resolved.

BIRD/Reykjavik Oceanic Operators planning eastbound flights across the NAT should be aware of a NOTAM issued earlier by Reykjavik Oceanic/Iceland ATC, that essentially asks traffic to avoid the airspace wherever possible, due to further ATC Industrial Action. Eastbound flights in particular will not be accepted into the airspace unless:

– Destination is in Iceland, Scandinavia, Baltic States or Russia
– Departure point is west of Denver (105W)

Refer to NOTAM A0248/16

We recommend to monitor BIRD/Iceland NOTAMs carefully as similar restrictions can apply in the next few days.