The key changes include a reduction in separation to ‘half-track’<\/strong> compared to the existing structure, introduction of 24 new Oceanic Entry Points (OEPs)<\/strong>, and some procedural changes. These changes affect all operators on the North Atlantic. The Shanwick and Gander OCAs and adjoining domestic airspace will be affected.<\/p>\n 1956 Selcal introduced on HF<\/p>\n 1961 First occasional use of NAT Tracks<\/p>\n 1965 First publication of daily NAT Tracks<\/p>\n 1966 Consolidation of Shannon and Prestwick centers to create ‘Shanwick’<\/p>\n 1977 MNPS Introduced<\/p>\n 1981 Longitudinal separation reduced to 10 minutes<\/p>\n 1996 GPS approved for navigation on NAT; OMEGA withdrawn<\/p>\n 1997 RVSM introduced on the NAT<\/p>\n 2006 CPDLC overtakes HF as primary communications method<\/p>\n 2011 Longitudinal separation reduced to 5 minutes<\/p>\n 2015 RLAT introduced<\/p>\n Gander OCA\/Gander Domestic Boundary:<\/p>\n LIBOR, NIFTY, RADUN, TOXIT, VESMI, BOKTO, ENNSO, IRLOK, KODIK, MELDI, PELTU, SAXAN, UMESI, BUDAR, IBERG, MUSAK, OMSAT, RELIC.<\/strong><\/p>\n <\/p>\n Additional new waypoints for NAR Design:<\/p>\n MUSLO, SINGA, UDMAR, ALSOP, DUBVI<\/strong><\/p>\n <\/p>\n Scottish\/Shanwick Boundary<\/p>\n <\/p>\n OEPs in bold, landfall fix in brackets:<\/p>\n 60.5N LUSEN<\/strong> (ELCOG)<\/p>\n 59.5N ORTAV<\/strong> (ODPEX)<\/p>\n 57.5N ETILO<\/strong> (EVNAL)<\/p>\n <\/p>\n Best Oceanic Transition Area:<\/p>\n 47.5N UMLER<\/strong> (UMOXA)<\/p>\n 46.5N BUNAV<\/strong> (TIVLU)<\/p>\n <\/p>\n You can download a plotting chart that shows these new waypoints from the Flight Service Bureau.<\/p>\n <\/p>\n As the RLatSM Tracks will always be within MNPS airspace, operators must meet the existing basic MNPS requirements and the additional RLatSM requirements.<\/p>\n Any flight that meets the following requirements as filed in their ICAO flight plan can be routed or re-routed by ATC on an RLatSM track:<\/p>\n This means that simply including the appropriate codes in the ICAO flight plan makes a flight eligible for the routing. The documentation as currently worded could imply that, to be eligible, you must meet the requirements, and if you did not flight plan a RLatSM track, then you would NOT be routed onto a RLatSM track. This is not the case.<\/strong> If the codes appear in your ICAO flight plan, then they CAN<\/strong> route you onto an RLatSM track whether you filed the route or not.<\/p>\n Logon to OCA Datalink 20 minutes prior OCA boundary unless already logged on to adjacent ACC. The logon is required so that ATC can send a check message for the next waypoints. Failure to log on means RLatSM clearance will be cancelled.<\/p>\n There are no changes to the inflight contingency procedures<\/strong> and weather deviation procedures as detailed in PANS ATM Doc444 Para15.2 and 15.2.3.<\/p>\n SLOP procedures are also unchanged.<\/p>\n As noted in the last briefing on RLatSM, as of 12 Nov 2015, the format of the NAT Track message will change slightly. Item 3 in the notes will list the letters of the RLatSM Tracks. An example of this format is below:<\/p>\n ARINC 424 coding format in the North Atlantic uses the position of the alpha character “N” to denote full-degree or half-degree of latitude. For half-degree of Latitude waypoints, an “N” prefix is used:<\/p>\n N5040 \u2013 leading character \u2013 half degree of latitude, i.e. 50 30 00N 040 00 00W<\/strong><\/p>\n 5040N \u2013 trailing character \u2013 full degree of latitude, i.e. 50 00 00N 040 00 00W<\/p>\n Incorrect placement of the \u201cN\u201d character (prefix vs. suffix) can, and has, led to gross navigation errors and reduced separation of aircraft.<\/p>\n Pilot Preflight and Inflight SOP must call for each pilot to independently display and verify the expanded DEGREES and MINUTES loaded into the Flight Management Computer (FMC) for each waypoint defining the cleared route of flight.<\/strong><\/p>\n Due to operational difficulties in using the “N” prefix format that resulted in GNEs, effective September 17, 2015, Jeppesen began supplying third-party providers with a navigation database with the “H” prefix enabled (H5520 = N55\u00b030′ W020\u00b0 00′).<\/p>\nHistory<\/h3>\n
12 November 2015 Changes<\/h3>\n
\n
RLat Tracks<\/h3>\n
\n
New Oceanic Entry Points<\/h3>\n
Aircraft Requirements<\/h3>\n
\n
ICAO Flight Plan<\/h3>\n
\n
Pilot Requirements<\/h3>\n
Contingency Actions<\/h3>\n
Track Message<\/h3>\n
![\"\"](\"\/media\/rokgallery\/4\/43f09194-1149-4ff5-8fac-85f5b6effa05\/900ee57c-bf79-4cdf-b5ce-e933fa273e1c.png\" "\\"\\"")
<\/p>\nEMPHASIS \u2013 Error Checking<\/h3>\n
![\"\"](\"http:\/\/aircrewacademy.com\/blog\/wp-content\/uploads\/2015\/11\/_media_rokgallery_0_0f912b5c-d3a4-448b-fd7a-78091124ae7c_b9f0cdaa-c20a-4761-b33f-e5d382e74049.jpg\")
Thank you to FSB for information provided for use in this briefing.<\/p>\n","protected":false},"excerpt":{"rendered":"