July 2020 North Atlantic Ops Update

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.


Iceland ATC strike bigger than ever

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.


Oceanic Errors

Unfortunately, we don’t fly with three in the cockpit anymore – or even four. The navigators job falls squarely onto the front two seats. Over one weekend in April there was one Gross Navigation Error, and two close calls reported on the North Atlantic.

April 22nd (Friday)
Democratic Republic of the Congo Boeing 727 100 (9QCDC/DRC001) from Santa Maria Island, Azores (LPAZ) to St. John’s NL (CYYT)
At 1235Z, Observed on radar to be over position 4720N 4745W, which was approximately 60 miles north of the cleared route 45N 45W – 47N 50W. The crew reported correctly while in oceanic airspace. The flight was cleared direct to YYT and landed without incident at CYYT. There was no traffic, and no other impact to operations.

April 24th (Sunday)
Neos Airline Boeing 767-300 (INDDL/NOS730) from Ferno, Italy (LIMC) to Havana, Cuba (MUHA)
Cleared via 49N030W 48N040W 45N050W. At 30W, the flight reported 48N040W 44N050W. The aircraft recleared to 45N050W prior to proceeding off course.

Apr 25th (Monday)
Transportes Aereos Portugueses Airbus A330-202 (CSTOO/TAP203) from Lisbon, Portugal (LPPT) to Newark, NJ (KEWR)
Cleared 46N030W 46N040W 45N050W. The aircraft reported proceeding via 46N030W 46N040W 44N050W, as per the original flight plan. The aircraft was recleared via 45N050W prior to proceeding off course.

Did you notice how hard it was to find the error in the above two examples?

 

Gross Navigation Errors are a really interesting topic, and relevant not just on the North Atlantic but in any Oceanic or Remote airspace where ATC cannot monitor the aircraft tracking.

What defines a GNE? Normally, 25nm: That is, when on “own navigation” the aircraft departs the cleared route by more than 25nm. The NAT Central Monitoring Agency (CMA) now defines a Gross Navigation Error as 10nm instead of 25nm.

Annually, the biggest offenders in order of “market share” are: 1. Corporate/Private, 2. Military/State 3. Civil airlines.

How to Avoid a GNE?
(aka How to avoid a Nastygram from the Authorities):

In general, when operating outside of ATC Radar coverage in any airspace:

  • Crews: Don’t have more than one paper copy of the Flight Plan in the cockpit. Mark the active one “Master Document”. Hide any other copies where you won’t find them.
  • Ops: If you send a new Flight Plan to the crew, tell them what the changes are – especially if you’ve filed a different route in Oceanic or Remote Airspace.
  • Fly the Clearance, not the Filed Plan. This is the biggest gotcha. As soon as you reach the Oceanic Entry Point, or leave radar airspace – refer only to the most recent Clearance from ATC. The filed plan is a request only – sounds obvious, but most GNE’s occur because the crew fly the filed plan although there was a reroute.
  • Be aware of the ‘ARINC424 problem’: In the aircraft FMS, and map display, the current common waypoint format is 5230N for position 52N030W (as prescribed by ARINC 424). To show position 5230N030W – ARINC 424 offers a format N5230. The potential for confusion is clear. ICAO, in NAT Ops Bulletin 3/15, have recommended that operators use the format H5230, if a five-letter FMS format waypoint is required. In addition pilots are recommended to cross check any waypoints that don’t have a ‘name’.
  • Use a plotting chart – it’s mandatory. You don’t have to use ours, but use one.
  • Use an Oceanic/Remote Area Checklist (sample link below).

And specifically on the Atlantic:

  • Read the advice on the Daily Track Message – waypoint cross check, Fly the Clearance (and be sure it is the clearance!)
  • Know the weather deviation procedures: Even with the new “Half Tracks”, there are no changes to the in flight contingency procedures and weather deviation procedures as detailed in PANS ATM Doc444 Para15.2 & 15.2.3.

Here’s some links and resources that we think are really useful:

 

For regular notices and content like the above, consider joining OPSGROUP.

 


Did you know MNPS is over? Meet HLA, the new North Atlantic Airspace.

From Feb 4th, 2016, MNPS (Minimum Navigation Performance Specifications) Airspace is being dumped as a term (no loss, really), and replaced by the much more user friendly NAT High Level Airspace or NAT HLA. MNPS first came into being in 1977, and this change is significant in that the requirements for approval to enter the new NAT HLA are updated – you must now have RNP4, or RNP10. Also, the rest of the Atlantic welcomes Bodø Oceanic to the fray – it joins Shanwick, Gander, Reykjavik, New York, and Santa Maria to make up the new NAT HLA, which keep the original vertical profile of FL285-FL420.

In short, that’s all you need to know. You should read our International Ops Notice 01/16 for the full story.