0% found this document useful (0 votes)
26 views14 pages

Nat Hla Guide

Uploaded by

Luis Laria
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
26 views14 pages

Nat Hla Guide

Uploaded by

Luis Laria
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 14

NAT-HLA

A How to Guide

This document is for guidance only while preparing for a North Atlantic Crossing.

Forms part of the NAT-HLA E-Learning course.

Company documentation MUST be used at all times


NAT High Level Airspace (HLA):

๏ FL285 - FL420 inclusive, within Gander, Iceland, Bodo, Shanwick, Santa Maria, and New York ‘East’ OCA’s. This
used to be called MNPS Airspace.

๏ The airplane must be RNP10 or RNP4. It must also be RVSM approved and have two LRNS’s (Long Range Nav
systems) – INS or GPS.
๏ Datalink is required between FL350-390, with a couple of exceptions – N of 80N, NY OCA, Blue Spruce and
Tango routes. You’ll need HF to be able to enter the Shanwick OCA. (Datalink will be mandated from FL280-
FL410 inclusive from January 30th 2020)

Flight Planning:

๏ Most importantly, you have to tell ATC what you are capable of – so put the right letters in, or you’ll be routing via
Iceland at 280.

๏ This means: In Item 10 – equipment,


✓ R for RNP, X for HLA Approval,
✓ W for RVSM; in Item 18 –
✓ PBN/A1 for RNP10 or L1 for RNP4, and
✓ SUR/180 for RSP180.
✓ Then in 10a J5 for FANS 1/A,
✓ P2 for RCP240, and in
✓ 10b D1 for Datalink.

๏ You don’t have to file on a NAT Track but when the tracks are active, it’s better for everyone if you’re on one.
Don’t file to cross them unless you’re above or below them.

๏ A ‘random route’ must have a waypoint every 10 degrees of longitude. You can mirror a track, and also join an
outer track half way along.

๏ You can plan at any Flight Level in the HLA, no need to follow ICAO standard Cruising Levels.

๏ If you’re running against the main flow (ie. departing New York at 8am), get up to FL430 if you can, or expect to be
held down at FL290 for a long time.

NAT Crossing paperwork:

๏ You must have a copy of the NAT Track message if you’re crossing when they are active (Eastbound
0100-0800 UTC, and Westbound 1130-1900 UTC, at 30 West), even if you're not flying on them.

๏ The Track Message has a TMI (Track Message Identification) number that’s basically todays day of the year (like
TMI031 on January 31st). It lists all the tracks.

๏ You should have an Oceanic Checklist.


Special Requirements:

๏ If you want to fly a PBCS (core) NAT Track between FL350- FL390, you must have ADS-C with RSP180, and
CPDLC with RCP240. Also, you need RNP4.

๏ Elsewhere in the NAT HLA 290-410, you need ADS-C + CPDLC (with a few little exceptions).

Pre-Flight, Taxi, Airborne

๏ Get the FMS loaded. ARINC424 is the standard naming convention for whole degree waypoints, so 53N030W will
be 5330N in your FMS. For half-degree waypoints, ICAO says to use the full coordinates. Crosscheck entries.

๏ Check the LRNS position

๏ Once Airborne, about an hour before oceanic entry, check position again.

Oceanic Clearance

๏ You need a specific clearance to enter Oceanic Airspace.

๏ Request it about 60 mins before entering, on CPDLC, VHF, or HF. (check regional requirements in LIDO)

๏ When you get your clearance, do not climb to your ocean level without a clearance from Domestic ATC. This
happens pretty often. Your Oceanic Clearance is valid from the Oceanic Entry Point (OEP) only.

๏ Revise your estimate for the OEP when it changes by more than 3 minutes.
๏ When clearance is received: Do a careful crosscheck with the OFP to avoid GNE (Set FMS for SLOP, MACH
selection)

Equipment Failure before the boundary

๏ HF fail: Oceanic Clearance received – fly the clearance. Tell Domestic ATC. Use Satcom Voice, CPDLC, or VHF
relay with other aircraft. Don’t revert to the filed flight plan.

๏ HF fail: No Oceanic Clearance received, and no contact with Domestic ATC: enter the OCA at the FPL requested
Oceanic level and speed but do not execute any subsequent step climbs in the Flight Plan. If you're flying
westbound, and have not yet entered Shanwick FIR, divert back to EINN

๏ Datalink – affecting CPDLC or ADS-C. Tell ATC. They will try to accommodate you within the Datalink
mandated area (FL350-390), but you may be rerouted.

๏ One LRNS failure (of two) – request a re-clearance below or above NAT HLA, fly the Blue Spruce routes, or land
and get it fixed.
๏ Don’t forget that you need two FMCs too.
Entering the Ocean

๏ No more radar controller, you’re on your own now.

๏ Select a SLOP offset – always right of track, 1 or 2nm, or 0.7nm etc. if you can. If you can't, maintain the
centerline. Don't go left.

๏ Logon to EGGX, and call Shanwick on HF for a radio check.

๏ Expect a “Confirm Assigned Route” message on CPDLC.

๏ Check next waypoint is correct, and that you’re going there.

๏ Set #1 VHF to 121.5, and #2 to123.45 for turbulence complaints

๏ Squawk 2000, 30 minutes after passing the Oceanic Entry Point.

๏ Get SELCAL check

๏ Advise next FIR

If you do have to make a voice position report, then do it like this:


Position, SULTAN 05, RESNO at 1235, Flight Level 330, Estimating 56 North 020 West at 1310, 56 North 030 West
Next.

Going around Weather

๏ If you spot a CB ahead, request a deviation from ATC. If ATC says no, or is too slow to respond, follow the
weather deviation procedure (new 2019):

๏ Turn away from the tracks, turn on your lights

๏ Call on 121.5 and 123.45 to tell others

๏ If deviating >5nm, if north of track descend 300 feet; if south of track climb 300 feet, but only once you are
5nm off track.

๏ Once clear, and back within 5nm of track, return to level.

Going Off Track

๏ Engine Failure: Take action according to the Oceanic In-Flight Contingency Procedure (new 2019):

๏ Turn away from the track at an angle of at least 30 degrees, and offset by 5nm.

๏ Offset by 500ft from normal (eg. FL305), but ideally descend below FL290 to get away from the core traffic.

๏ Call on 121.5, 123.45, squawk 7700, watch TCAS.

๏ When finished aviating and navigating, talk to ATC on HF, get a new clearance to your diversion airport.
Non-Normal
&
Equipment Failures
If you don’t have RNP4, then:

RNP 4
๏You can’t use the NAT PBCS Tracks between FL350 and FL390.
๏If you also don’t have RNP10, then you can’t enter the NAT HLA Airspace,

HF If you don’t have HF, then

๏ You can’t enter the Shanwick OCA. Other OCA’s may approve Satcom for primary comms.

๏ If you’re making a full NAT crossing, then you’re basically going via Iceland on the Blue Spruce
routes. One example route is RATSU-ALDAN-KFV–EPENI–63N30W–61N40W-OZN-58N50W-HOIST-LOACH-YYR.

๏ Canada publishes two routes that can be flown VHF, without prior approval:

below FL 195, routing Iqaluit (Frobay) – Sondre Stromfjord – Keflavík

FL 250 or above, routing Goose VOR – Prins Christian Sund (or Narsarsuaq) –Keflavik. You still need HLA
approval to go above FL285.

๏ Canada will approve other routes without HF, but you’ll have to ask ATC nicely first. In general, crossing from
Greenland-Canada south of 60N, at FL200 or above, should be fine.

PBCS If you don’t have PBCS, then

๏ You can’t use the PBCS Tracks between FL350-390.

๏ PBCS means having both RCP240 and RSP180 – 4 minute comms loop, and 3 minute position reporting.
2LRNS

If you only have one Long Range Nav System:

๏ For a full crossing, use the Blue Spruce routes. You only need a single LRNS - and HLA approval if using them
between FL285-FL420.

๏ You need HF for the ones that enter Shanwick OCA

๏ You can use Tango 9 with a single LRNS, but T13, T213 and T16 need two.

Blue Spruce Routes:

๏ Alpha GOMUP 60N15W 61N1630W BREKI KFV HF required


๏ Bravo 1 ATSIX 61N12°34'W ALDAN KFV HF required
๏ Bravo 2 RATSU ALDAN KFV No HF needed

๏ Charlie 1 KFV SOPEN DA SF YFB No HF needed


๏ Charlie 2 SF DARUB YXP No HF needed
๏ Delta KFV EPENI 63N30W 61N40W OZN No HF needed
๏ Echo OZN 59N50W AVUTI PRAWN YDP No HF needed
๏ Fox OZN 59N50W CUDDY PORGY HO No HF needed
๏ Golf OZN 58N50W HOIST YYR No HF needed
DATA If your Datalink isn’t working:
LINK

๏ Then either, or both, ADS-C and CPDLC isn’t working.

๏ You can’t operate in the NAT HLA between FL350-FL390

๏ You will have to make HF voice reports

๏ There are exempted areas, where you’re all good: North of 80N, Surveillance airspace (where ATC can see you on
radar or ADS-B), the Tango Routes, Blue Spruce routes, and New York Oceanic East. If you have ADS-B and VHF,
Gander will accept you on a line RATSU 61N20W 63N30W 62N40W 61N50W SAVRY or north of.

CPDLC is mandated FL290-FL410 inclusive from January 30th 2020

HF Radio is the primary comms method on the Ocean,It is not the more pleasant form of communications.

To save you having to listen to it all the time, you use SELCAL so that ATC can reach you if needed, but you’ll need
a quick SELCAL check first.

If you lose contact for any reason, 5616, 5598, 8864, and 8891 (frequencies) are good starting points for all OAC’s.

You can use CPDLC (and need to for most of the HLA between FL350-390), but because HF remains the
‘primary’, you still need a Selcal check when you cross an FIR boundary. Check LIDO for Logon codes.

You can also use SATCOM – but it’s kind of an exception.

If you really can’t raise ATC on HF, and you don’t have CPDLC, then call the Radio Station for the FIR you’re in (rather
than the controller), and make a position report. Check LIDO for Satcom numbers.

If your TCAS isn’t working:


TCAS

It is a must! You cannot cross no matter what!

It is a must for the whole World too.


NAT Flight Plan Codes
== Equipment==
C LORAN C D DME
E1 FMC WPR ACARS
E2 D-FICS ACARS
E3 PDC ACARS
F ADF G GNSS H HF I INS
J1 CPDLC ATN VDL Mode 2
J2 CPDLC HFDL
J3 CPDLC VDL Mode A/0
J4 CPDLC VDL Mode 2
J5 CPDLC SATCOM (INMARSAT)
J6 CPDLC SATCOM (MTSAT)
J7 CPDLC SATCOM (Iridium)
M1 ATC RTF SATCOM (INMARSAT)
M2 ATC RTF (MTSAT)
M3 ATC RTF (Iridium)
O VOR P2 CPDLC RCP 240
R PBN (Item 18 PBN/D1 etc)
S Standard Equipment VHF VOR ILS
V VHF W RVSM
X MNPS Y 8.33
Z Other Equipment (Comment in 18)
==Transponder==
C Mode C only
S Mode S basic
E/H/I/L/P/S/X Mode S extended
B1/B2/U1/U2/V1/A2 ADS-B
D1/G1 ADS-C
==PBN codes==
A1 RNP10/10nm Oceanic
B2 RNP5 GPS B3 DME B4 VOR
C2 RNP2 GPS C3 DME
L1 RNP4 Oceanic
==PBCS codes==
Item 18 SUR/RSP180 RSP180
North Atlantic Contacts / Always check LIDO

Shanwick
Iceland
ATC: Prestwick Supervisor +44 1294 655 141 ATC: Reykjavik Supervisor + 354 424 4141
Radio: Ballygirreen Supervisor +353 61 471 199 Radio: Supervisor +354 563 6502
CPDLC Logon: EGGX CPDLC Logon: BIRD
SatCom: Shanwick Radio 425002 SatCom: Iceland Radio 425105

Gander Santa Maria


ATC: Watch Manager +351 296 820 400
ATC: Oceanic Supervisor +1-709 651-5207
Radio: Supervisor +351 296 820 401
Radio: Shift Manager 1-709-651-5222
CPDLC Logon: LPPO
CPDLC Logon: CZQX
SatCom: Santa Maria Radio 426305
SatCom: Gander Radio 431613

New York Bodo


ATC: Oceanic Watch Desk +1 631 468 5959 ATC: Supervisor +47 755 42900
Radio: Shift Manager +1 631 468 1413 Radio: +47 755 42940
CPDLC Logon: KZWY CPDLC Logon: ENOB
SatCom: New York Radio 436623 SatCom: Bodo Radio 425702
Diversions

NAT Flight Levels

Note: Since January 2017, you don’t have to pick an ICAO standard cruising level for your direction of flight. However, it’s good
to know how Gander and Shanwick normally use levels. Also, bear in mind that if you’re going eastbound against the NAT flow,
you’re pretty much going to get FL290 or FL410, and westbound FL300 or FL430. Plan fuel accordingly.
Region you want to fly and what you need.

Remember: CPDLC is mandated in NAT-HLA from FL280-FL410 inclusive from January 30th 2020.

NAT-HLA & THE NAT TRACKS Region will require CPDLC.

You might also like