Who Fits Where in the NAT · 2016-02-01 · Who Fits Where in the NAT PRESENTED BY: Bill Smith,...

Who Fits Where in the NAT

PRESENTED BY:

Bill Smith, Scott International Procedures

Monday, March 23 | 9:30 a.m. – 10:00 a.m.

International Operators Conference | San Antonio, TX | March 23 – 27, 2015

Who Fits Where in the North Atlantic

• Why be aware?

• A brief historical review of NAT separation standards

• Current route structures / CNS requirements / separation standards

• Future plans / changes to watch for

2

Why be aware?

Isn’t this Safety Day?

• It is Safety Day!

• Knowledge regarding route structures, CNS requirements and separation

standards is important from a Safety perspective

– Allows Operations to be flown as planned

– Allows knowledgeable application of Contingency guidance material in PANS-ATM

(DOC 4444) and Regional Supps (ICAO Doc 7030)

– Error Management becomes more and more important .. Review SOPs for currency

• NAT Airspace/equipment requirements/separation standards continually

becoming more complex

– Requires time and effort to stay abreast of the changes

3

Why be aware? Fuel Plan vs actual burn with reroute

4

FUEL TIME CORR TOGWT LDGWT AVG W/C

DEST EINN 008859 03.41 ------ 041958 033099 P086

RESV 001766 00.45 ------

ALTN 000500 00.12 ------ ALTN EICK DIST 0057 W/C P026

HOLD 000000 00.00 ------

ADDL 000498 00.13

REQD 011623 04.51 ------ BOW 027200 PAYLOAD 000800

EXTRA 002335 00.59

TAXI 000042

TTL AT BO 013958 05.50 ------ RTE MAN DIST 1914

FUEL TIME CORR TOGWT LDGWT AVG W/C

DEST EINN 007225 03.20 ------ 039958 032733 P097

RESV 001554 00.45 ------

ALTN 000500 00.12 ------ ALTN EICK DIST 0057 W/C P026

HOLD 000000 00.00 ------

ADDL 001285 00.36

REQD 010564 04.53 ------ BOW 027200 PAYLOAD 000800

EXTRA 001394 00.39

TAXI 000042

TTL AT BO 011958 05.32 ------ RTE MAN DIST 1748

Core track FL 370 Track edge FL 330

22.5% increase in trip burn!

Why be aware? General application of contingency guidance

From ICAO DOC 4444 PANS-ATM

Chapter 15.2 SPECIAL PROCEDURES FOR INFLIGHT CONTINGENCIES

IN OCEANIC AIRSPACE

15.2.2.3 ……In general terms, the aircraft should be flown at a flight level and

an offset track where other aircraft are least likely to be encountered.

“YOU HAVE TO KNOW WHERE THEY ARE, TO KNOW WHERE THEY AREN’T”

5

Why be aware?

Are your SOP’s current/ adequate?

• Misunderstanding of ARINC 424 Waypoint naming convention last Spring.

– Confirm LAT/LONG as part of Navigation crosschecks?

6

A Brief History of the NAT

Sometimes knowing where you’ve been, helps identify where you’re going

7

8

In 1939

46 Flying boats crossed the NAT from Jun-Oct

https://www.iaa.ie/nac-history

• 18 hours from Ireland to Newfoundland

• Communications via Morse Code

• Traffic density not a significant problem!

9

Post-War Years 1946-1958

https://www.icao.int/EURNAT/Pages/main_history.aspx

• Establishment of ICAO

• Establishment of EUR/NAT Regional Office in Paris

• Land Planes rapidly replace Flying Boats, steady increase in NAT traffic

• 1956, First NAT Regional Air Navigation Meeting with emphasis on:

• Improving communication: Air - Ground and Ground – Ground

• More precise application of separation criteria

• Higher speed operations

• Need for more timely information flow and weather info for higher

atmospheric levels

• Evolution into cyclic traffic scheme, with accompanying congestion within

minimum time (most economical) E/B and W/B flows

• Traffic congestion causes significant economic penalties for operators pushed

away (laterally and vertically) from most economical routes due to large

separation standards:

• 2000’ vertical above FL290

• 30 minutes longitudinal

• 120 nm lateral

10

Early Jet Age 1958-1965


11

Early Jet Age 1958-1965


• 1961 4th NAT Regional Air Navigation Meeting

• Reviewed NAT Regional Plan to meet demand for foreseeable future

• 1965 Special meeting

• Meeting endorsed 90nm LAT Separation

• Significant resistance to Reduced Lateral Separation Minimum (RLatSM)

• Status quo maintained (120nm LAT, 30 Min Long, 2000’ Vert above FL290)

• Formed NAT Systems Planning Group

• NAT SPG expected to recommend process to gain acceptance of reduced

separations

12

1965-1971


• Collection of Coastal and Ship based RADAR Data regarding Actual Nav

Performance

• Development of statistical, computer based methods of analyzing the data

• 1970 5th NAT Regional Meeting approved adoption of composite separation, (60

nm lateral AND 1000’ vertical) after a short trial period

• Some congestion relief/ economic benefit

• NAT SPG continued work with the target of 60nm lateral separation and gradual

reduction in longitudinal separation

13

1971-Present


• 1977- Defined/ adopted NAT MNPS Requirements

• Requirement for operational approval

• Operators unable to upgrade/ obtain approval must avoid MNPS Airspace

• Vertically (Above FL420, Below FL285)

• Restricted to Special Radio Routes (Blue Spruce)

• Continue application of composite separation with data collection/analysis to

achieve consensus on further reduction of LAT and Long Separations

• No change in Separation Minima…… no economic gain….yet

14

1971-Present


• 1980 After 3 years of additional data collection/analysis, consensus achieved on

• Lat Separation Reduction to 60 nm

• Long Separation Reduction to 15 Min

• Later reduction of Long Sep Min to 10 min

• Economic benefits of 1977 MNPS ‘mandate’ achieved

15

1977-Present


• Continued planning and collection/analysis of traffic data, including planning for

DATALINK capabilities

• 1997 Adoption of RVSM within NAT MNPS Airspace FL290-FL410

• Non-RVSM approved operators must avoid above or below

• May 2010 trial RLongSM to 5 min suspended in June

• 2011 re-start of trial RLongS to 5 Min using CPDLC/ADS-C

• 2013 DATALINK (CPDLC & ADS-C) Mandate for two core NAT tracks

FL360-FL390

• Non-equipped aircraft must avoid

• Above/Below/Laterally

16

1977-Present

https://www.icao.int/EURNAT/Pages

• Continued planning and collection/analysis of traffic data

• Including Communication, Navigation and Surveillance System performance

• Feb 2015 DATALINK (CPDLC & ADS-C) Mandate expanded to all NAT

tracks FL350-FL390

• Non-equipped aircraft must avoid increased volume of airspace

• Above/Below/Laterally

• Accompanying economic penalty

17

1960s-Present

• Graphic review of Separation Standards

18

Prior to 1970


120NM 120NM

FL 280

FL 290

FL 350

FL 330

FL 310

Longitudinal separation 30 minutes

19

1970-1980


FL 280

FL 290

FL 350

FL 330

FL 310


FL 300

FL 340

FL 320

60NM 60NM 60NM 60NM

20 https://www.icao.int/EURNAT/Pages/main_history.aspx

60NM 60NM

FL 280

FL 290

FL 350

FL 330

FL 310

Longitudinal separation 15 to 10 minutes

FL 300

FL 340

FL 320

FL 410

60NM 60NM

1980- 1997

21 https://www.icao.int/EURNAT/Pages/main_history.aspx

FL 280

FL 290

FL 350

FL 330

FL 310


FL 300

FL 340

FL 320

FL 410

60NM 60NM 60NM 60NM

1997- Present

22

Prior to 1980


30 Min Longitudinal Separation

23

After 1980



24

After 1980



25

After 2011


5 Min Longitudinal Separation trial

DATALINK Required

26

ADS-B

NAT DOC 005 2nd Ed.

• Increasing number of aircraft equipped

• Addition of ADS-B service areas based on ground antenna locations and ATS

provider capability

• Permits increased areas where surveillance separation (5-10nm) rather than

procedural separation between A/C pairs when DCPC can be established

27 NAVCANADA AIC 29/13

28 http://www.isavia.is/english/air-navigation/ads-b/

29

Future plans-Nov 2015


• Trial RLatSM to ½ degree Latitude (25nm based on ‘gentle slope rule’) on three

core tracks within Data Link Mandate FLs

• Will require RNP4

• Non-RNP 4 equipped aircraft will have to avoid these tracks/FLs vertically

or horizontally

30

NOV 2015

FL 340

FL 350

FL 410

FL 390

FL 370

FL 360

FL 400

FL 380

25NM

60NM 60NM 60NM

25NM

31

RLatSM tracks

NAT DOC 008 Application of Separation Minima Nov 2014

30nm

32

Future Plans-Dates TBD

• Expand DLM to entire NAT Region….FLs yet TBD

• Non-equipped aircraft must avoid vertically or laterally (ADS-B service area)

• Expand Airspace where RLatSM is used…… FLs determined by DLM FLs

• Non- RNP 4 equipped aircraft will have to avoid these tracks/FLs vertically

or horizontally

• ‘Mixed Mode’ (RNP4 and RNP10) operations expected outside OTS

• ADS-B surveillance airspace should be available for non CPDLC/ADS-C

equipped flights………. exact definitions TBD

NAT DOC 009 Service Development Roadmap June 1, 2014

33

Future Plans-2015

• MNPS Airspace to be re-defined as PBN Airspace

• New MNPS approvals will be based on RNP10 or RNP4 specification

• Former MNPS approved aircraft still able to operate within airspace

• Target date 2020 all aircraft in NAT PBN airspace will have RNP10 or RNP4

specification approval. Former MNPS Authorization no longer valid


34

Future Plans-Dates TBD

• Expand ADS-B based surveillance service/ separation standards to entire NAT

Region

• Based on

• ADS-B Receivers installed on LEO Satellites (Iridium Next)

• ATS Provider capabilities

• DCPC

• May reduce/eliminate need for NAT OTS


35

How to Stay Aware

• Near Term

• AIPs and AICs from NAT ATS Provider States

• http://www.eurocontrol.int/articles/ais-online

• NAT OPS Bulletins

• http://www.icao.int/EURNAT/Pages/EUR-and-NAT-

Document.aspx?RootFolder=%2FEURNAT%2FEUR%20and%20NAT%20Documents%2FNAT%20D

ocuments%2FNAT%20OPS%20Bulletins&FolderCTID=0x012000DAF95319EADD9946B510C5D7B5

95637D00AA5EB47B299B9A4BAD1968B24E18655C&View={2666E7DD-5F4E-4E64-B16A-

CF142A1E5BC9}

36

How to Stay Aware

• Longer Term

• NAT DOC 005 Future ATM Concept of Operations for the NAT Region

• http://www.icao.int/EURNAT/EUR%20and%20NAT%20Documents/NAT%20Documents/NAT%20Doc

%20005/NAT%20Doc005%202nd%20Ed-Nov%202012.pdf

• NAT DOC 009 (as revised) NAT Service Development Roadmap

• http://www.icao.int/EURNAT/EUR%20and%20NAT%20Documents/NAT%20Documents/NAT%20Doc

%20009%20-%20NAT%20SDR/NAT%20Doc%20009,%20Ed1%20-

%20NAT%20SDR%20(Aug2014).pdf


37

How to Stay Aware

• Longer Term

• Reports of NAT SPG Meetings

• http://www.icao.int/EURNAT/Pages/EURNAT-Meetings-NATSPG.aspx

38 NAT DOC 009 Service Development Roadmap June 1, 2014

39

THANK YOU!

Date post:	13-Apr-2020
Category:	Documents
Upload:	others
View:	0 times
Download:	0 times