fpl 2012 worksheet - icao.int meetings seminars and workshops/fpl... · in amendment 1 to doc 4444,...

INTERNATIONAL CIVIL AVIATION ORGANIZATION

European and North Atlantic Office

ORGANISATION DE L'AVIATION CIVILE INTERNATIONALE

Bureau Europe et Atlantique Nord

ORGANIZACIÓN DE AVIACIÓN CIVIL INTERNACIONAL

Oficina Europa y Atlántico Norte

МЕЖДУНАРОДНАЯ ОРГАНИЗАЦИЯ ГРАЖДАНСКОЙ АВИАЦИИ

Европейское/Североатлантическое бюро

Tel.: National 01 46 41 85 85

Fax: National 01 46 41 85 00 E-mail: [email protected]

International +33 1 46 41 85 85 International +33 1 46 41 85 00 Web: http://www.paris.icao.int

When replying please quote

Reference : EUR/NAT 10-0465.TEC (STC/CUP)2010-06-21 21 June 2010

Subject : FPL 2012 Worksheet

Action

required : Please refer to paragraph 3 and Appendix A

Madam, Sir,

1. I have the honour to refer to the implementation of the new contents of the ICAO Flight Plan

(FPL) in 2012 following the approval of Amendment 1 to Procedures for Air Navigation Services – Air

Traffic Management (PANS-ATM) (Doc 4444), Fifteenth Edition.

2. In order to respond to requests from States in the Eastern part of the ICAO EUR Region for

more information on the activities involved in enabling this change in their States, the EUR/NAT Office of

ICAO will be organizing a five-day FPL2012 workshop, at the kind invitation of Ukraine, in Kyiv, from 29

June to 1 July 2010.

3. Additionally, please find attached a worksheet, in Adobe Acrobat and Excel formats

(Appendix A), that had been reviewed at the ATMGE/11 and COG/47 meetings, which serves to lead users

through a detailed analysis process that identifies the impact of each change for flight plan filers, flight

planning services, flight data processing systems and flight data users arising from the implementation of the

new contents of FPL 2012.

4. The eleventh meeting of the Air Traffic Management Group – Eastern part of the ICAO

EUR Region (ATMGE/11) had recognised the worksheet as a potentially valuable tool and recommended

that it be circulated to ATMGE States prior to the workshop in order to assist them in their planning and

implementation activities. This recommendation was supported by the forty-seventh meeting of the EANPG

Programme Coordinating Group (COG/47), Rostov-on-Don, Russian Federation, from 15 to 18 June 2010,

(COG Decision 47/4 - Distribute FPL 2012 Worksheet refers).

5. I wish to invite you to make use of the attached FPL2012 Worksheet to identify the impact

of each change arising from the implementation of the new contents of FPL 2012 for all your State’s

stakeholders concerned.

Please accept the assurances of my highest consideration.

Karsten Theil

ICAO Regional Director

Europe and North Atlantic

Enclosure: FPL 2012 Worksheet (Adobe Acrobat & Excel formats)

Distribution: Armenia, Azerbaijan, Belarus, Bulgaria, Estonia, Georgia, Kazakhstan, Kyrgyzstan, Latvia,

Lithuania, Poland, Republic of Moldova, Romania, Russian Federation, Tajikistan, Turkey,

Turkmenistan, Ukraine, Uzbekistan, Eurocontrol, IAC, IACA, IATA and IFATCA









3 bis villa Emile Bergerat, 92522 Neuilly-sur-Seine Cedex, France









3 bis villa Emile Bergerat, 92522 Neuilly-sur-Seine Cedex, France

Part I - Overview Appendix A to

SL EUR/NAT 10-0465.TEC (STC/CUP)

Description

of the

Tabs

Guidance: The Guidance Tab contains

a description of each of the 27

substantive (i.e., non-editorial) changes

in Amendment 1 to DOC 4444, along

with descriptions of the probable

impacts to each of the system

categories described below.

Checklist: The checklist tab contains a

spreadsheet which details the 27

substantive changes, their descriptions

and a series of impact questions to

answer.

Detailed Changes: The Detailed

Changes tab lists all of the

approximately 150 changes in

Amendment 1, including editorial

changes. Each is mapped to one of the

identified 27 substantive changes or to

"Editorial/Clarification".

A/C Perf Cat: The A/C Perf Cat tab

provides a description of ICAO aircraft

performance categories referrenced in

Attachment 1 (informational only).

Instructions

How to use the

checklist to evaluate

changes imposed by

Amendment 1

Step 1. Evaluate each change. In the

"Guidance" tab, each new requirement

is summarized and guidance is provided

for each of the four types of systems

(described below).

Step 2. In evaluating a change, you can

go to the "Detailed Changes" tab and

filter on the change being evaluated.

Each line-by-line amendments relating

to that change is shown.

Step 3. The results of the evaluation

should be tabulated on the "checklist"

spreadsheet.

Description

of the

System

Categories

Filer: An individual or organization that

files an FPL or related ATS message.

Flight Planning Service: A system that

electronically sends an FPL or related

ATS message over AFTN to an FDP

(e.g., flight services organizations,

commercial services, etc.).

FDP (Flight Data Processing)

Systems: A system that accepts and

processes an FPL or related ATS

message for ATC purposes.

Flight Data User: A system that

receives data from FDP systems which

has been derived from an FPL or related

ATS message, but does not directly

receive FPLs or related ATS messages.

How to Use This Spreadsheet

1 of 1

Part II - Guidance Appendix A to


New Requirement Description Filers Flight Planning Services FDP Systems Flight Data Users

1

Date of Flight

Requirements

A new field 18 item, DOF/, will be optionally allowed in an FPL. Furthermore, filing up to 120 hours (5

days) in advance of the flight will be permitted.

1. Include the date of flight when the

proposed time is more than 24 hours

in advance.

1. If your interface already allows for

date of flight entry, use that to

populate DOF/ when flight is more

than 24 hours in advance.

1. Accept DOF/ in messages

2. If present, use DOF/ to determine

the date instead of only using the

EOBT.

3. Account for use of DOF/ in EO BT

amendments.

4. For flight plans without an EOBT,

process as currently done.

Changes for flight data users will be

highly ANSP-specific. Need to assess

whether any data currently used by

other systems (e.g. Traffic Flow

Management Systems) is affected, or

whether any existing systems require

any of the new information.

2

ACID format (Field 07) The existing requirement is clarified to indicate that only letters and numbers are permitted. No

hyphens or other special characters are allowed. Since registration numbers in some countries are

expressed with hyphens, it appears they wanted to clarify this. There is no change to the existing

requirement.

1. No change- file per current rules.

Make sure to omit any hyphens or

spaces in registration numbers

1. No change expected. 1. No change expected. Changes for flight data users will be







3

Field 10 format The permitted field 10 format used to be a series of 1 to 25 letters followed by an oblique stroke

followed by 1 to 2 letters. Now, not only are the maximum lengths of the subfields before and after the

stroke increased but the format will include letter-digit combinations in addition to single letters. Note

that for any letter, it either always occurs alone or always occurs with a following digit.

1. Follow the new format 1. Modify accept and send the new

format.

1. Modify to accept and send the new

format.

2. Need to change all affected ICDs,

e.g. NAT, PAC, NAM and CAR/SAM

ICDs..








4

GPS Augmentation for

Landing Capability

There are two new capabilities expressed in ICAO Field 10a:

A: GBAS Landing System

B: LPV (APV with SBAS)

GBAS is Ground-Based Augmentation System.

The purpose of LPV (Localizer Performance with Vertical guidance) is to fly ILS look-alike procedures

published as RNAV GNSS with LPV minima, by using SBAS (Space Based Augmentation System) or

ABAS (Aircraft Based Augmentation System).

1. File the new data codes as

appropriate and necessary for desired

services.

2. Note: Each ANSP needs to

evaluate whether it will have

procedures or automation that require

filing of this information.

1. Modify user interface as necessary

to provide reasonable interface to

pilots/dispatchers for filing the new

capabilities.


data.

1. Accept, store, and forward these

items in flight data messages.

2. Provide Air Traffic Controller

interface to view and modify this data

3. Assess whether automation is

necessary to automatically notify of

equppage/non-equippage, or

automatically validate qualification for

the route filed








5

ACARS capability Aircraft Communications Addressing and Reporting System (ACARS) is a digital datalink system for

transmission of short, relatively simple messages between aircraft and ground stations via radio or

satellite.

Three new Field 10a designators have been added to describe ACARS capability of an aircraft:

E1: FMC WPR ACARS- This is the capability to send FMC Waypoint Reports via ACARS. Some NAT

FIRs presently accept ACARS FMC Waypoint Reports (FMC WPR) as an alternative to ADS for

aircraft that do not support ADS.

E2: D-FIS ACARS- The ability to receive airfield and weather information via the automatic terminal

information service (ATIS), and regular meteorological information (VOLMET) through ACARS.

E3: PDC ACARS- The ability to receive Pre-Departure Clearance messages through ACARS.



services.








capabilities.


data.









the route filed








1 of 6




6

CPDLC capability Controller Pilot Data Link Communications (CPDLC) used to be designated by a “J” in ICAO Field 10a,

with details of the capability described in Field 18. Now, most of those details are designated within

Field 10a through the following designators:

J1 CPDLC ATN VDL Mode 2

J2 CPDLC ATN FANS 1/A HFDL

J3 CPDLC ATN FANS 1/A VDL Mode A

J4 CPDLC FANS 1/A VDL Mode 2

J5 CPDLC FANS 1/A SATCOM(INMARSAT)

J6 CPDLC FANS 1/A SATCOM(MTSAT)

J7 CPDLC FANS 1/A SATCOM(Iridium)



services.








capabilities.


data.









the route filed








7

Satellite RTF The FPL will now allow a filer to specify one of several satellite communication capabilities:

M1 ATC RTF SATCOM(INMARSAT)—ATC radiotelephone capability via INMARSAT

M2 ATC RTF (MTSAT)—ATC radiotelephone capability via MTSAT

M3 ATC RTF (Iridium)—ATC radiotelephone capability via Iridium



services.








capabilities.


data.









the route filed








8

VHF/8.33 kHz VHF channel spacing in some airspace (e.g. within Europe) has been reduced from 25 kHz to 8.33

kHz to allow for more capacity. The United States has not made this change and therefore the

capability is not relevant to U.S. operations.

The amendment designates the letter “Y” for this capability. Note that Y was previously used “as

prescribed by ATS” and was sometimes used to denote Canadian MNPS capability.



services.








capabilities.


data.









the route filed








9

ADS-B capability The existing FPL format only allows for a non-descriptive “D” for “ADS capability” in Field 10b. The

new FPL format expands Field 10b to provide a detailed accounting of ADS-B capability.

E Transponder Mode S including aircraft identification, pressure-altitude and extended squitter(ADS-

B)capability

B1 ADS-B with dedicated 1090 MHz ADS-B "out" capability

B2 ADS-B with dedicated 1090 MHz ADS-B "out" and "in" capability

U1 ADS-B "out" capability using UAT

U2 ADS-B out and in capability using UAT

V1 ADS-B "out" capability using VDL mode 4

V2 ADS-B "out" and "in" capability using VDL mode 4

In addition,

TBD- What is “enhanced surveillance capability” (see H, L)?

TBD- Why is extended squitter Mode S listed on both E/L and on B1, B2?



services.








capabilities.


data.









the route filed








10

ADS-C capability The existing FPL format only allows for a non-descriptive “D” for “ADS capability” in Field 10b. The

new FPL format expands Field 10b to provide a detailed accounting of ADS-C capability.

D1 ADS-C with FANS 1/A capabilities

G1 ADS-C with ATN capabilities



services.








capabilities.


data.









the route filed








2 of 6




11

FRD w/5 letter base fix The current FPL format for a Fix Radial Distance (FRD) specifies that the base fix must be a NAVAID

with a 2-3 letter name. The amendment makes use of a 2-5 character base fix allowable.

Note that some ANSPs already support 5-character base fixes.

1. Each ANSP will need to determine

whether/when they can accept Fix

Radial Distance with other than a

NAVAID as a base fix, and

communicate this to the filers.

1. If the filing system does a route

check, ensure that 5-letter base fixes

are allowed in FRDs.

1. If the FDP system does a route

check, ensure that 5-letter base fixes

are allowed in FRDs.

2. Note that an FRD can now be up

to 11 characters long.

Assess whether calculations of any

systems that receive and process

flight data will be affected.

12

DEP, DEST, and

Alternate format

PRESENT FPL does not provide explicit guidance on how to enter a departure or destination location

in Field 18 DEP/, DEST/, ALTN/, RALT/, or TALT/. The original instructions were geared towards

providing a human-readable description, and did not anticipate automation attempts to process the

location. The contents of each of these fields should contain the name of the aerodrome followed by

the location of the aerodrome The location can be either a Lat/Lon, an FRD, or a fix name, as follows:

- Name and location of departure aerodrome, if ZZZZ is inserted in Item 13, or the ATS unit from which

supplementary flight plan data can be obtained, if AFIL is inserted in Item 13. For aerodromes not

listed in the relevant Aeronautical Information Publication, indicate location as follows:

With 4 figures describing latitude in degrees and tens and units of minutes followed by “N” (North)

or “S” (South), followed by 5 figures describing longitude in degrees and tens and units of minutes,

followed by “E” (East) or “W” (West). Make up the correct number of figures,

where necessary, by insertion of zeros, e.g. 4620N07805W (11 characters).

OR

Bearing and distance from the nearest significant point, as follows:

The identification of the significant point followed by the bearing from the point in the form of 3

figures giving degrees magnetic, followed by the distance from the point in the form of 3 figures

expressing nautical miles. In areas of high latitude where it is determined by the

appropriate authority that reference to degrees magnetic is impractical, degrees true may be used.

Make up the correct number of figures, where necessary, by insertion of zeros, e.g. a point of 180°

magnetic at a distance of 40 nautical miles from VOR “DUB” should be

expressed as DUB180040.

OR

The first point of the route (name or LAT/LONG) or the marker radio beacon, if the aircraft has not

taken off from an aerodrome.

1. File DEP/, DEST/, ALTN/, and

TALT/ as instructed.

2. ANSPs should provide explicit

guidance regarding what format

"name of the aerodrome should take.

1. If the filing system automatically

creates DEP/ and DEST/ entries

based on filing a non-standard

departure or destination, need to

ensure the system adheres to this

format.

1. If DEP/ and DEST/ are processed

by the FDP system, may need to

change from processing the first

element to (likely) processing the last

element.



whether other systems (e.g. Traffic

Flow Management Systems) use the

data.

13

Required Field 18 format In the existing instructions, Field 18 is supposed to be populated in the “preferred” sequence shown.

The word preferred implied that it was not required. The amendment removes the word preferred, and

now makes the defined sequence required.

The amendment also clarifies that hyphens shall not be used within Field 18. This was already the

case, but there have been problems with filers including hyphens.

Finally, the use of oblique strokes is now limited to use in indicators. In the existing format, oblique

strokes could be used within free text portions.

1. Ensure Field 18 items are in the

required sequence.

2. Ensure no hyphens appear in Field

18.

3. Ensure that an oblique stroke is

used only as part of a valid indicator.

1. Enforce the new rules and do not

pass along messages not in

conformance with them.

1. Enforce the new rules and do not

pass along messages not in

conformance with them.

Likely to be no impact; systems

receiving data at most will see Field

18 more consistently in the

documented order.

3 of 6




14

Reason for Special

Handling (STS/)

Requirements

In the current flight plan, STS/ is a free-text field with guidance on the type of information to include.

The amendment makes this a rigidly controlled field with an enumerated list of allowed strings that can

be included. The allowed values are now:

ALTRV for a flight operated in accordance with an altitude reservation

ATFMX for a flight approved for exemption from ATFM measures by the appropriate ATS authority

FFR fire-fighting

FLTCK flight check for calibration of navaids

HAZMAT for a flight carrying hazardous material

HEAD a flight with Head of State status

HOSP for a medical flight declared by medical authorities

HUM for a flight operating on a humanitarian mission

MARSA for a flight for which a military entity assumes responsibility for separation of military aircraft

MEDEVAC for a life critical medical emergency evacuation

NONRVSM for a non-RVSM capable flight intending to operate in RVSM airspace

SAR for a flight engaged in a search and rescue mission

STATE for a flight engaged in military, customs, or police services

1. File only the designated items in

STS/, per instructions.




capabilities.

2. Modify system as necessary to

accept and send the new data.

3. Enforce that STS/ contains only the

allowed items.



2. Enforce that STS/ contains only the

allowed items.


interface to view and modify this data.

Likely to be no impact required since

the field was previously free text.

Depending on the ANSP needs, there

could be an opportunity to automate

detection of certain conditions of

interest.

15

Performance Based

Navigation capability

(PBN/)

The amendment provides a mechanism for filing the capabilities of the aircraft/crew/FMS for

Performance Based Navigation in a new indicator PBN/ in Field 18. Each capability is represented by

a letter-digit code:

RNAV SPECIFICATIONS

A1 RNAV 10 (RNP 10)

B1 RNAV 5 all permitted sensors

B2 RNAV 5 GNSS

B3 RNAV 5 DME/DME

B4 RNAV 5 VOR/DME

B5 RNAV 5 INS or IRS

B6 RNAV 5 LORANC

C1 RNAV 2 all permitted sensors

C2 RNAV 2 GNSS

C3 RNAV 2 DME/DME

C4 RNAV 2 DME/DME/IRU

D1 RNAV 1 all permitted sensors

D2 RNAV 1 GNSS

D3 RNAV 1 DME/DME

D4 RNAV 1 DME/DME/IRU

RNP SPECIFICATIONS

L1 RNP 4

O1 Basic RNP 1 all permitted sensors

O2 Basic RNP 1 GNSS

O3 Basic RNP 1 DME/DME

O4 Basic RNP 1 DME/DME/IRU

S1 RNP APCH

S2 RNP APCH with BARO-VNAV

T1 RNP AR APCH with RF (special authorization required)

T2 RNP AR APCH without RF (special authorization required)

1. File the new PBN/ codes as


services.


evaluate whether it has procedures or

automation that require filing of this

information.




capabilities.


data.









the route filed

4. Assess whether the automation

needs to change to use PBN/ data in

preference to current user of Field 10

and/or NAV/ data.







any of the new information. Note that

systems currently using NAV/ data

may have to change to use PBN/ data

instead.

4 of 6




16

Delay at a fix (DLE/)

Capability

The amendment introduces the ability to specify (in Field 18, after DLE/) a delay at a significant point.

The significant point must be a point in the route.

1. File in accordance with instructions.

2. NOTE: Each ANSP needs to

assess whether they have Air Traffic

procedures that warrant the use of

DLE/ data, and should instruct users

accordingly.




capabilities.


data.

3. Validate the data as necessary,

e.g. check that the significant point is

within Field 18.

1. FDP system is impacted if the

ANSP plans to allow use of this

feature.

2. Calculation of estimated times at

significant points need to reflect the

anticipated delay.

3. Need to decide whether/how to

validate the significant point.

4. For automated interfaces between

ANSPs, it is possible that a filed DLE/

is for a significant point before the

boundary. Need to work with interface

partners to establish whether such

DLE/ data must be removed before

forwarding a CPL, or will ignored by

the recipient if the significant point is

not in the route.


highly ANSP-specific. If DLE/ is

supported, then any systems that

perform route/trajectory processing

will need to be able to process the

delay data.

17

Alternate Take-Off

Airport (TALT/)

The amendment introduces the capability to specify an alternate departure airport in Field 18, using the

new indicator TALT/. The rules for content of this field will be essentially the same as for DEP/ and

DEST/. This is to specify an airport within an hour of the departure point at which the aircraft would

plan to land if needed-- mostly for use when the departure airport is below arrival minimums.

1. File in accordance with instructions. 1. Modify user interface as necessary


pilots/dispatchers for filing the

information.


data.












18

EOBT in Flight Data

change messages

Currently, the Doc. 4444 specification of CHG, DLA and CNL messages indicates that Field 13 in

those messages should include only 13a (the departure airport) and not 13b (the departure time).

Many ANSPs allow filers to include Field 13b to help differentiate between multiple proposed flight

plans for the same ACID. The amendment changes the message definitions to include 13b.

Note: ARR and RQS messages are also changed.

This will not be an optional element after the change; it will be required.

1. Likely not a direct impact to filers 1. Include the EOBT from the

previously filed FPL in CHG, DLA,

CNL, ARR, and RQS messages sent

to an FDP system.

2. Once an EOBT has been

amended, include the amended EOBT

in subsequent change messages.

1. Need to accept the EOBT in

incoming CHG, DLA, CNL, ARR, and

RQS messages.

2. Add processing to use EOBT to

differentiate which flight plan is being

referenced when there are multiple

flight plan matches (same Aircraft

identification in Field 7, and same

Departure and Destination

Aerodrome).

Unlikely to be any impact unless these

messages are passed directly to flight

data users.

19

DOF in flight data change

messages

By accepting a date of flight in a FPL, the date of flight must also be provided in second order

messages (CHG, DLA, and CNL). The specification indicates Field 18 should be included in the

messages; this has been clarified to mean only the DOF/ indicator from Field 18. Note that when

DOF/ is not present, a Field 18 of -0 should be included.

1. Likely not a direct impact to filers 1. When DOF/ was filed in a FPL,

make sure any CHG, CNL, or DLA

message includes it.

2. When no DOF/ was filed, make

sure a -0 is sent in CHG, CNL, or DLA

messages.

1. Accept Field 18 as an optional item

in CHG, CNL, and DLA.

2. When present, use DOF/ to match

a previously filed FPL.

3. Evaluate need for change in

relevant ICDs (e.g. PAC, NAT, NAM,

and CAR/SAM).

Unlikely to be any impact unless these

messages are passed directly to flight

data users.

20

Standard Equipment

definition

The current definition of S in Field 10a is ADF, VOR, VHF RTF, and ILS. The amendment changes

this to VOR, VHF RTF, and ILS. ADF has been removed.

1. File in accordance with the new

instructions. "S" can be used in more

cases, and ADF must always be

explicitly filed.

1. Ensure that an F is filed if ADF

capability is present.

2. Be aware that S can be filed

without the need for ADF capability.

1. Change validation rules as

necessary if ADF is an item that the

automation checks for.


highly ANSP-specific. If a system

checks for ADF capability, need to

change so that an F must be present

in Field 10a (i.e. an S no longer

denotes ADF capability).

21

Meaning of "other"

equipment

An item “Z” in ICAO Field 10a indicates that there is additional information in Field 18. The

amendment slightly changes what it is referring to; a Z used to refer to additional data in COM/ or

NAV/; it now indicates there is additional data in COM/, NAV/, or DAT/.


instructions. If DAT/ is included, be

aware that the Z is required in 10a

(instead of "J" as currently required).

1. If the system validates consistency

of Field 10a and Field 18, then check

for a Z in 10a when DAT/ is present

(or insert the Z if this processing is

automated).

1. If the system validates consistency

of Field 10a and Field 18, then check

for a Z in 10a when DAT/ is present

(or insert the Z if this processing is

automated).

Unlikely to be any impact.

5 of 6




22

Required Comm.

Performance

The RCP concept characterizes the performance required for communication capabilities that support

ATM functions without reference to any specific technology and is open to new technology. An RCP

type is a label (e.g., RCP 240) that defines a performance standard for operational communication

transactions. Each RCP type denotes values for communication transaction time, continuity,

availability, and integrity applicable to the most stringent operational communication transaction

supporting an ATM function. RCP is not yet implemented, but several Field 10a items have been

reserved for expressing the capability.

1. Future- no changes now. 1. Future- no changes now. 1. Future- no changes now. Changes for flight data users will be







23

Additional Surveillance

Capabilities (SUR/)

The amendment introduces the ability to file a new indicator SUR/ in Field 18, to describe any

additional surveillance capabilities not listed in Field 10b. There is no letter in 10b to indicate a SUR/

entry exists. There are no format or content requirements for SUR/; it is essentially free-text.

1. File data in SUR/ when required


determine whether capabilities not

addressed by Field 10b need to be

filed.



pilots/dispatchers for filing the

information.


data.









the route filed








24

Content of Field 18

(TYP/) Type of Aircraft

The amendment provides direction for how to include multiple aircraft types for formation flights, and

the number of each aircraft type in the formation. This information is to be specified in TYP/ in Field

18.


instructions.

1. Should be no impact; TYP/ already

exists.

2. Consider providing a user interface

that guides the content of Field 07 and

TYP/ (e.g. enforce the specified

syntax for formation flight filing.)

1. Should be no impact; TYP/ already

exists.

2. Consider providing a user interface

that guides the content of Field 07 and

TYP/ (e.g. enforce the specified

syntax for formation flight filing.)

No impact anticipated.

25

Message Originator

(ORGN/)

The amendment adds an ORGN/ indicator in Field 18. This indicator is intended to be used by a

FPLning service, to indicate the AFTN address or other contact information for the filer that originated

the FPL, since the FDP system receiving the FPL will see it as coming from the filing service.

1. No impacts. This field is populated

by automation.

1. No impacts unless the filing service

finds it advantageous to use this field

to document the AFTN address of a

filer.




interface to view this data








26

A/C Performance (PER/) The existing requirements for PER/ in Field 18 are simply to include information as required by ATS

units; it is essentially a free text field. The amendment changes this to require a single letter category

per ICAO Document 8168, Volume 1. Section 1.3 describes the categories, that section is replicated

in another tab.


instructions.

1. Enforce only one character allowed

in PER/

2. Ideally, provide a user interface that

assists in entering the data.

1. Enforce only one character allowed

in PER/.

2. If data is used, (maybe oceanic)

then provide improved air traffic

controller interface..

3. If data is used in flight plan

trajectory modeling or other

processing, requisite logic will be

needed.








27

Enhanced Mode-S

Surveillance Capability

Enhanced Surveillance entails the use of Downlink Aircraft Parameters (DAPs) in support of a number

of ATM applications. The Controller Access Parameter (CAP) Service is the most prominent one.

System improvements such as a Level Bust Alerting Tool, enhanced tracking and improved safety

nets are also considered. These all relate to improvements in tactical ATC operations particularly

relevant in the high-density airspace of Europe where Mode S Elementary Surveillance is already

being implemented.


instructions.

1. Modify CHI as necessary to provide

reasonable interface to pilots for filing

the new capabilities.


data.









the route filed








6 of 6

Part III - Checklist Appendix A to


New Requirement DescriptionAre any changes to

filing requirements

needed?

Does this affect

Automation

Systems?

Description of

systems impact if

affected

Are there procedures

and/or LOA's

impacted by this

change?

Description of impact

if affected

1Date of Flight

Requirements

A new field 18 item, DOF/, will be optionally allowed in an FPL. Furthermore, filing up to 120 hours (5

days) in advance of the flight will be permitted.

2

ACID format (Field 07) The existing requirement is clarified to indicate that only letters and numbers are permitted. No

hyphens or other special characters are allowed. Since registration numbers in some countries are

expressed with hyphens, it appears they wanted to clarify this. There is no change to the existing

requirement.

3

Field 10 format The permitted field 10 format used to be a series of 1 to 25 letters followed by an oblique stroke

followed by 1 to 2 letters. Now, not only are the maximum lengths of the subfields before and after

the stroke increased but the format will include letter-digit combinations in addition to single letters.

Note that for any letter, it either always occurs alone or always occurs with a following digit.

4


Landing Capability

There are two new capabilities expressed in ICAO Field 10a:

A: GBAS Landing System

B: LPV (APV with SBAS)

GBAS is Ground-Based Augmentation System.

The purpose of LPV (Localizer Performance with Vertical guidance) is to fly ILS look-alike procedures

published as RNAV GNSS with LPV minima, by using SBAS (Space Based Augmentation System) or

ABAS (Aircraft Based Augmentation System).

5

ACARS capability Aircraft Communications Addressing and Reporting System (ACARS) is a digital datalink system for

transmission of short, relatively simple messages between aircraft and ground stations via radio or

satellite.

Three new Field 10a designators have been added to describe ACARS capability of an aircraft:

E1: FMC WPR ACARS- This is the capability to send FMC Waypoint Reports via ACARS. Some

NAT FIRs presently accept ACARS FMC Waypoint Reports (FMC WPR) as an alternative to ADS for

aircraft that do not support ADS.

E2: D-FIS ACARS- The ability to receive airfield and weather information via the automatic terminal

information service (ATIS), and regular meteorological information (VOLMET) through ACARS.

E3: PDC ACARS- The ability to receive Pre-Departure Clearance messages through ACARS.

6

CPDLC capability Controller Pilot Data Link Communications (CPDLC) used to be designated by a “J” in ICAO Field

10a, with details of the capability described in Field 18. Now, most of those details are designated

within Field 10a through the following designators:

J1 CPDLC ATN VDL Mode 2

J2 CPDLC ATN FANS 1/A HFDL

J3 CPDLC ATN FANS 1/A VDL Mode A

J4 CPDLC FANS 1/A VDL Mode 2

J5 CPDLC FANS 1/A SATCOM(INMARSAT)

J6 CPDLC FANS 1/A SATCOM(MTSAT)

J7 CPDLC FANS 1/A SATCOM(Iridium)

1 of 7




filing requirements

needed?

Does this affect

Automation

Systems?

Description of

systems impact if

affected


and/or LOA's

impacted by this

change?


if affected

7

Satellite RTF The FPL will now allow a filer to specify one of several satellite communication capabilities:

M1 ATC RTF SATCOM(INMARSAT)—ATC radiotelephone capability via INMARSAT

M2 ATC RTF (MTSAT)—ATC radiotelephone capability via MTSAT

M3 ATC RTF (Iridium)—ATC radiotelephone capability via Iridium

8

VHF/8.33 kHz VHF channel spacing in some airspace (e.g. within Europe) has been reduced from 25 kHz to 8.33

kHz to allow for more capacity. The United States has not made this change and therefore the

capability is not relevant to U.S. operations.

The amendment designates the letter “Y” for this capability. Note that Y was previously used “as

prescribed by ATS” and was sometimes used to denote Canadian MNPS capability.

9

ADS-B capability The existing FPL format only allows for a non-descriptive “D” for “ADS capability” in Field 10b. The

new FPL format expands Field 10b to provide a detailed accounting of ADS-B capability.

E Transponder Mode S including aircraft identification, pressure-altitude and extended squitter(ADS-

B)capability

B1 ADS-B with dedicated 1090 MHz ADS-B "out" capability

B2 ADS-B with dedicated 1090 MHz ADS-B "out" and "in" capability

U1 ADS-B "out" capability using UAT

U2 ADS-B out and in capability using UAT

V1 ADS-B "out" capability using VDL mode 4

V2 ADS-B "out" and "in" capability using VDL mode 4

In addition,

TBD- What is “enhanced surveillance capability” (see H, L)?

TBD- Why is extended squitter Mode S listed on both E/L and on B1, B2?

10

ADS-C capability The existing FPL format only allows for a non-descriptive “D” for “ADS capability” in Field 10b. The

new FPL format expands Field 10b to provide a detailed accounting of ADS-C capability.

D1 ADS-C with FANS 1/A capabilities

G1 ADS-C with ATN capabilities

11

FRD w/5 letter base fix The current FPL format for a Fix Radial Distance (FRD) specifies that the base fix must be a NAVAID

with a 2-3 letter name. The amendment makes use of a 2-5 character base fix allowable.

Note that some ANSPs already support 5-character base fixes.

2 of 7




filing requirements

needed?

Does this affect

Automation

Systems?

Description of

systems impact if

affected


and/or LOA's

impacted by this

change?


if affected

12

DEP, DEST, and

Alternate format

PRESENT FPL does not provide explicit guidance on how to enter a departure or destination location

in Field 18 DEP/, DEST/, ALTN/, RALT/, or TALT/. The original instructions were geared towards

providing a human-readable description, and did not anticipate automation attempts to process the

location. The contents of each of these fields should contain the name of the aerodrome followed by

the location of the aerodrome The location can be either a Lat/Lon, an FRD, or a fix name, as

follows:

- Name and location of departure aerodrome, if ZZZZ is inserted in Item 13, or the ATS unit from

which supplementary flight plan data can be obtained, if AFIL is inserted in Item 13. For aerodromes

not listed in the relevant Aeronautical Information Publication, indicate location as follows:

With 4 figures describing latitude in degrees and tens and units of minutes followed by “N” (North)

or “S” (South), followed by 5 figures describing longitude in degrees and tens and units of minutes,

followed by “E” (East) or “W” (West). Make up the correct number of figures,

where necessary, by insertion of zeros, e.g. 4620N07805W (11 characters).

OR

Bearing and distance from the nearest significant point, as follows:

The identification of the significant point followed by the bearing from the point in the form of 3

figures giving degrees magnetic, followed by the distance from the point in the form of 3 figures

expressing nautical miles. In areas of high latitude where it is determined by the

appropriate authority that reference to degrees magnetic is impractical, degrees true may be used.

Make up the correct number of figures, where necessary, by insertion of zeros, e.g. a point of 180°

magnetic at a distance of 40 nautical miles from VOR “DUB” should be


OR

The first point of the route (name or LAT/LONG) or the marker radio beacon, if the aircraft has not

taken off from an aerodrome.

13

Required Field 18 format In the existing instructions, Field 18 is supposed to be populated in the “preferred” sequence shown.

The word preferred implied that it was not required. The amendment removes the word preferred,

and now makes the defined sequence required.

The amendment also clarifies that hyphens shall not be used within Field 18. This was already the

case, but there have been problems with filers including hyphens.

Finally, the use of oblique strokes is now limited to use in indicators. In the existing format, oblique

strokes could be used within free text portions.

3 of 7




filing requirements

needed?

Does this affect

Automation

Systems?

Description of

systems impact if

affected


and/or LOA's

impacted by this

change?


if affected

14

Reason for Special

Handling (STS/)

Requirements

In the current flight plan, STS/ is a free-text field with guidance on the type of information to include.

The amendment makes this a rigidly controlled field with an enumerated list of allowed strings that

can be included. The allowed values are now:

ALTRV for a flight operated in accordance with an altitude reservation

ATFMX for a flight approved for exemption from ATFM measures by the appropriate ATS authority

FFR fire-fighting

FLTCK flight check for calibration of navaids

HAZMAT for a flight carrying hazardous material

HEAD a flight with Head of State status

HOSP for a medical flight declared by medical authorities

HUM for a flight operating on a humanitarian mission

MARSA for a flight for which a military entity assumes responsibility for separation of military aircraft

MEDEVAC for a life critical medical emergency evacuation

NONRVSM for a non-RVSM capable flight intending to operate in RVSM airspace

SAR for a flight engaged in a search and rescue mission

STATE for a flight engaged in military, customs, or police services

4 of 7




filing requirements

needed?

Does this affect

Automation

Systems?

Description of

systems impact if

affected


and/or LOA's

impacted by this

change?


if affected

15

Performance Based

Navigation capability

(PBN/)

The amendment provides a mechanism for filing the capabilities of the aircraft/crew/FMS for

Performance Based Navigation in a new indicator PBN/ in Field 18. Each capability is represented by

a letter-digit code:

RNAV SPECIFICATIONS

A1 RNAV 10 (RNP 10)

B1 RNAV 5 all permitted sensors

B2 RNAV 5 GNSS

B3 RNAV 5 DME/DME

B4 RNAV 5 VOR/DME

B5 RNAV 5 INS or IRS

B6 RNAV 5 LORANC

C1 RNAV 2 all permitted sensors

C2 RNAV 2 GNSS

C3 RNAV 2 DME/DME

C4 RNAV 2 DME/DME/IRU

D1 RNAV 1 all permitted sensors

D2 RNAV 1 GNSS

D3 RNAV 1 DME/DME

D4 RNAV 1 DME/DME/IRU

RNP SPECIFICATIONS

L1 RNP 4

O1 Basic RNP 1 all permitted sensors

O2 Basic RNP 1 GNSS

O3 Basic RNP 1 DME/DME

O4 Basic RNP 1 DME/DME/IRU

S1 RNP APCH

S2 RNP APCH with BARO-VNAV

T1 RNP AR APCH with RF (special authorization required)

T2 RNP AR APCH without RF (special authorization required)

5 of 7




filing requirements

needed?

Does this affect

Automation

Systems?

Description of

systems impact if

affected


and/or LOA's

impacted by this

change?


if affected

16


Capability

The amendment introduces the ability to specify (in Field 18, after DLE/) a delay at a significant point.

The significant point must be a point in the route.

17

Alternate Take-Off

Airport (TALT/)

The amendment introduces the capability to specify an alternate departure airport in Field 18, using

the new indicator TALT/. The rules for content of this field will be essentially the same as for DEP/

and DEST/. This is to specify an airport within an hour of the departure point at which the aircraft

would plan to land if needed-- mostly for use when the departure airport is below arrival minimums.

18

EOBT in Flight Data

change messages

Currently, the Doc. 4444 specification of CHG, DLA and CNL messages indicates that Field 13 in

those messages should include only 13a (the departure airport) and not 13b (the departure time).

Many ANSPs allow filers to include Field 13b to help differentiate between multiple proposed flight

plans for the same ACID. The amendment changes the message definitions to include 13b.

Note: ARR and RQS messages are also changed.

This will not be an optional element after the change; it will be required.

19

DOF in flight data

change messages

By accepting a date of flight in a FPL, the date of flight must also be provided in second order

messages (CHG, DLA, and CNL). The specification indicates Field 18 should be included in the

messages; this has been clarified to mean only the DOF/ indicator from Field 18. Note that when

DOF/ is not present, a Field 18 of -0 should be included.

20Standard Equipment

definition

The current definition of S in Field 10a is ADF, VOR, VHF RTF, and ILS. The amendment changes

this to VOR, VHF RTF, and ILS. ADF has been removed.

21

Meaning of "other"

equipment

An item “Z” in ICAO Field 10a indicates that there is additional information in Field 18. The

amendment slightly changes what it is referring to; a Z used to refer to additional data in COM/ or

NAV/; it now indicates there is additional data in COM/, NAV/, or DAT/.

6 of 7




filing requirements

needed?

Does this affect

Automation

Systems?

Description of

systems impact if

affected


and/or LOA's

impacted by this

change?


if affected

22

Required Comm.

Performance

The RCP concept characterizes the performance required for communication capabilities that support

ATM functions without reference to any specific technology and is open to new technology. An RCP

type is a label (e.g., RCP 240) that defines a performance standard for operational communication

transactions. Each RCP type denotes values for communication transaction time, continuity,

availability, and integrity applicable to the most stringent operational communication transaction

supporting an ATM function. RCP is not yet implemented, but several Field 10a items have been

reserved for expressing the capability.

23


Capabilities (SUR/)

The amendment introduces the ability to file a new indicator SUR/ in Field 18, to describe any

additional surveillance capabilities not listed in Field 10b. There is no letter in 10b to indicate a SUR/

entry exists. There are no format or content requirements for SUR/; it is essentially free-text.

24

Content of Field 18

(TYP/) Type of Aircraft

The amendment provides direction for how to include multiple aircraft types for formation flights, and

the number of each aircraft type in the formation. This information is to be specified in TYP/ in Field

18.

25

Message Originator

(ORGN/)

The amendment adds an ORGN/ indicator in Field 18. This indicator is intended to be used by a

FPLning service, to indicate the AFTN address or other contact information for the filer that originated

the FPL, since the FDP system receiving the FPL will see it as coming from the filing service.

26

A/C Performance (PER/) The existing requirements for PER/ in Field 18 are simply to include information as required by ATS

units; it is essentially a free text field. The amendment changes this to require a single letter category

per ICAO Document 8168, Volume 1. Section 1.3 describes the categories, that section is replicated

in another tab.

27

Enhanced Mode-S


Enhanced Surveillance entails the use of Downlink Aircraft Parameters (DAPs) in support of a

number of ATM applications. The Controller Access Parameter (CAP) Service is the most prominent

one. System improvements such as a Level Bust Alerting Tool, enhanced tracking and improved

safety nets are also considered. These all relate to improvements in tactical ATC operations

particularly relevant in the high-density airspace of Europe where Mode S Elementary Surveillance is

already being implemented.

7 of 7

Part IV - Detailed changes Appendix A to


Para/Item Ref Topic PRESENT NEW Automation Change Change Reference

4.4.1.3 FPL instructions Comply with instructions … plus constraints in AIP Editorial/Clarification

4.4.2.1.1FPL submission prior

to departure

Not more than 24 hours Not more than 120 hours Date of Flight Requirements

11.4.2.2.2.5 DOF in Item 18

Hold FPL in abeyance if filed

more than 24 hours in

advance

DOF shall be inserted in Item

18 if FPL filed more than 24

hours in advance

Date of Flight Requirements

11.4.2.2.4 CHG Message N/A Editorial clarification Editorial/Clarification

2.2 Insertion of ATS DataN/A Note 2 regarding constraints VHF/8.33 kHz

Item 7 ACID

7 characters 7 alphanumerics without

hyphens or symbols

Reject FPL filed with hyphen

or symbol in Item 7

ACID format (Field 07)

Item 8 Flight Rules N/A Editorial clarification Editorial/Clarification

Item 8 Type of flightN/A Note added referring to STS

in Item 18


Item 10 Title(editorial)Equipment Equipment and Capabilities Field 10 format

Item 10 Title(editorial) Equipment

Item 10 Title(editorial)

Equipment Addition of words

"serviceable" and "and

capabilities"


Landing Capability

Item 10 Qualifiers

Only alphas Can include alphanumerics;

many additional items added

Change code to allow

alphanumerics vice only

alphas

Field 10 format

Item 10 Title(Editorial) Radio, Nav, App Aid

equipment

Radio, Nav, App Aid

equipment and capabilities

Editorial/Clarification

Radio, Nav, App Aid

equipment and

capabilities

S

Standard Equipment of VHF

RTF, ADF, VOR, and ILS

Standard equipment of VHF

RTF,VOR and ILS

Only indicate ADF when

Code "F" is used

Standard Equipment

definition

Radio, Nav, App Aid

equipment and

capabilities

Z

The equipment carried is to

be specified in Item

18,preceded by COM/ and/or

NAV/ as appropriate

Specify in Item 18 the other

equipment carried or other

capabilities preceded by

COM/ NAV/ and/or DAT, as

appropriate

Ensure DAT/ is accepted

into Item 18

Meaning of "other"

equipment

Radio, Nav, App Aid

equipment and

capabilities

A

Not allocated GBAS landing system Ensure A is accepted GPS Augmentation for

Landing Capability

Radio, Nav, App Aid

equipment and

capabilities

B

Not allocated LPV (APV with SBAS) Ensure B is accepted GPS Augmentation for

Landing Capability

1 of 16




Radio, Nav, App Aid

equipment and

capabilities

E

Not allocated This character has been

removed

Ensure E is removed and will

reject if used.

Field 10 format

Radio, Nav, App Aid

equipment and

capabilities

E1

Not allocated FMC WPR ACARS Ensure E1 is accepted ACARS capability

Radio, Nav, App Aid

equipment and

capabilities

E2

Not allocated D-FIS ACARS Ensure E2 is accepted ACARS capability

Radio, Nav, App Aid

equipment and

capabilities

E3

Not allocated PDC ACARS Ensure E3 is accepted ACARS capability

Radio, Nav, App Aid

equipment and

capabilities

J

Data Link This character has been

removed

Ensure J is removed and will

reject if used.

Field 10 format

Radio, Nav, App Aid

equipment and

capabilities

J1

Not allocated CPDLC ATN VDL Mode 2 Ensure J1 is accepted CPDLC capability

Radio, Nav, App Aid

equipment and

capabilities

J2

Not allocated CPDLC ATN FANS 1/A

HFDL

Ensure J2 is accepted CPDLC capability

Radio, Nav, App Aid

equipment and

capabilities

J3

Not allocated CPDLC ATN FANS 1/A VDL

Mode A


Radio, Nav, App Aid

equipment and

capabilities

J4

Not allocated CPDLC FANS 1/A VDL

Mode 2


Radio, Nav, App Aid

equipment and

capabilities

J5

Not allocated CPDLC FANS 1/A

SATCOM(INMARSAT)


Radio, Nav, App Aid

equipment and

capabilities

J6


SATCOM(MTSAT)


Radio, Nav, App Aid

equipment and

capabilities

J7


SATCOM(Iridium)


Radio, Nav, App Aid

equipment and

capabilities

M

Omega This character has been

removed

Ensure M is removed and

will reject from system if

used.

Field 10 format

2 of 16




Radio, Nav, App Aid

equipment and

capabilities

M1

Not allocated ATC RTF

SATCOM(INMARSAT)

Ensure M1 is accepted Satellite RTF

Radio, Nav, App Aid

equipment and

capabilities

M2

Not allocated ATC RTF (MTSAT) Ensure M2 is accepted Satellite RTF

Radio, Nav, App Aid

equipment and

capabilities

M3

Not allocated ATC RTF (Iridium) Ensure M3 is accepted Satellite RTF

Radio, Nav, App Aid

equipment and

capabilities

P


removed

Field 10 format

Radio, Nav, App Aid

equipment and

capabilities

P1-P9

Not allocated Reserved for RCP Ensure P1 thru P9 are

accepted

Required Comm.

Performance

Radio, Nav, App Aid

equipment and

capabilities

Q


removed

Field 10 format

Radio, Nav, App Aid

equipment and

capabilities

R

RNP type certification PBN approved(IF R is used

then specify in Item 18 PBN/)

Performance Based

Navigation capability (PBN/)

Radio, Nav, App Aid

equipment and

capabilities

W

When prescribed by ATS RVSM approved Editorial/Clarification

Radio, Nav, App Aid

equipment and

capabilities

X

When prescribed by ATS MNPS approved Editorial/Clarification

Radio, Nav, App Aid

equipment and

capabilities

Y

When prescribed by ATS VHF with 8.33 kHz channel

spacing capability

VHF/8.33 kHz

Radio, Nav, App Aid

equipment and

capabilities

Z

Other equipment carried Other equipment carried or

other capabilities


Surveillance TitleSurveillance Surveillance and capabilities Editorial/Clarification

Surveillance and

capabilitiesNumber of characters

1 or 2 characters Maximum of 20 characters Ensure category will allow 20

characters

Field 10 format

3 of 16




Surveillance and

capabilitiesAlphas

limited list of alphas Alphanumerics, adding

categories for SSR Modes A

and C, SSR Mode S, ADS-B,

ADS-C

Field 10 format

Surveillance and

capabilitiesRename of section

SSR equipment SSR Modes A and C Editorial/Clarification

Surveillance and

capabilitiesAddition of section

Not allocated SSR Mode S Editorial/Clarification

Surveillance and

capabilitiesN

Nil No surveillance equipment

for the route to be flown is

carried or the equipment is

unserviceable


Surveillance and

capabilitiesX

Transponder Mode S without

both aircraft identification

and pressure altitude

transmission

Transponder Mode S with

neither aircraft identification

nor pressure-altitude

capability


Surveillance and

capabilitiesE

Not allocated Transponder Mode S

including aircraft

identification, pressure-

altitude and extended

squitter(ADS-B)capability

Ensure E is accepted TBD

Why is extended squitter

ADS-B listed here?

Surveillance and

capabilitiesH

Not allocated Transponder Mode S

including aircraft


altitude and enhanced

surveillance capability

Ensure H is accepted Enhanced Mode-S


Surveillance and

capabilitiesI (editorial)

Transponder Mode S

including aircraft

identification transmission,

but no pressure altitude

transmission

Transponder Mode S

including aircraft

identification, but no

pressure-altitude capability


Surveillance and

capabilitiesL

Not allocated Transponder Mode S,

including aircraft


altitude, extended squitter

capability(ADS-B)and

enhanced surveillance

capability

Ensure L is accepted Enhanced Mode-S


Why is extended squitter

ADS-B listed here?

Surveillance and

capabilitiesDeleted category

ADS equipment This category has been

removed

Field 10 format

4 of 16




Surveillance and

capabilitiesD

ADS capability This character has been

removed

Ensure D is removed and will

reject if filed

Field 10 format

Surveillance and

capabilitiesAddition of category

Not allocated ADS-B Editorial/Clarification

Surveillance and

capabilitiesB1

Not allocated ADS-B with dedicated 1090

MHz ADS-B "out" capability

Ensure B1 is accepted ADS-B capability

Surveillance and

capabilitiesB2

Not allocated ADS-B with dedicated 1090

MHz ADS-B "out" and "in"

capability

Ensure B2 is accepted ADS-B capability

Surveillance and

capabilitiesU1

Not allocated ADS-B "out" capability using

UAT

Ensure U1 is accepted ADS-B capability

Surveillance and

capabilitiesU2

Not allocated ADS-B out and in capability

using UAT

Ensure U2 is accepted ADS-B capability

Surveillance and

capabilitiesV1

Not allocated ADS-B "out" capability using

VDL mode 4

Ensure V1 is accepted ADS-B capability

Surveillance and

capabilitiesV2

Not allocated ADS-B "out" and "in"

capability using VDL mode 4

Ensure V2 is accepted ADS-B capability

Surveillance and

capabilitiesAddition of category

Not allocated ADS-C ADS-C capability

Surveillance and

capabilitiesD1

Not allocated ADS-C with FANS 1/A

capabilities

Ensure D1 is accepted ADS-C capability

Surveillance and

capabilitiesG1

Not allocated ADS-C with ATN capabilities Ensure G1 is accepted ADS-C capability

Surveillance and

capabilitiesNew indicator

N/A Note additional surveillance

application should be listed

in Item 18 after SUR/

Ensure SUR/ is accepted in

Item 18

Required Comm.

Performance

Item 13Departure Aerodrome

(Editorial)

Insert the ICAO four letter

location of the departure

aerodrome


location of the departure

aerodrome as specified in

Doc7910

Ensure departure aerodrome

accepted are from DOC7910

DEP, DEST, and Alternate

format

5 of 16




Item 13 Departure Aerodrome

If no location indicator then

insert ZZZZ and specify in

item 18 the name of the

aerodrome preceded by

DEP/



Item 18 the name and

location of the aerodrome

preceded by DEP/ or the

first point of the route or

the marker radio beacon

preceded by DEP/ if the

aircraft has taken off from

the aerodrome

Ensure departure aerodrome

are accepted with this

procedure


format

Item 15 ( 2 )Route-Bearing and

distance

Bearing and distance from a

navigation aid

Bearing and distance from a

significant point

FRD w/5 letter base fix

Item 15 (3)

Route-Change of

speed or

level(Editorial)

Insert where change of route,

speed, flight level and or

flight rules is planned

Is planned to commence Editorial/Clarification

Item 16 Title(Editorial)

Destination Aerodrome, Total

Elapsed Time, Alternate

Aerodrome(s)

Destination Aerodrome, Total

Elapsed Time, Destination

Alternate Aerodrome(s)


Item 16

Destination

Aerodrome and Total

elapsed time

Insert the four letter location

indicator of the destination

aerodrome

as specified in DOC7910

Location Indicators


format

Item 16

Destination

Aerodrome and Total

elapsed time


insert ZZZZ and without a

space the total elapsed time

and Specify in Item 18 the

name of the aerodrome,

preceded by DEST/



Item 18 the name and

location of the aerodrome

preceded by DEST/ then

without a space insert the

total elapsed time.


format

Item 16Destination alternate

aerodrome(s)


location indicator(s) of not

than two alternate

aerodromes, separated by a

space

as specified in DOC7910

Location Indicators

Ensure that destination

alternate aerodromes are

from Doc7910 Location

indicators


6 of 16




Item 16 Destination alternate

aerodrome(s)

If no location indicator insert

ZZZZ and specify in Item 18

name of the aerodrome

preceded by ALTN/

If no location indicator insert

ZZZZ and specify in Item 18

name and location of the

destination alternate

aerodrome preceded by

ALTN/


format

Item 18 Other InformationN/A Add clarification using

hyphens & obliques

Required Field 18 format

Item 18 Other Information preferred sequence in the sequence shown Required Field 18 format

Item 18 STS/

free text Specific entries: ALTRV,

ATFMX, FFR, FLTCK,

HAZMAT, HEAD, HOSP,

HUM, MARSA, MEDEVAC,

NONRVSM, SAR, STATE;

other reasons for special

handling by ATS shall be

denoted with the designator

RMK/

Ensure when using item 18

STS/ these are the only

codes that can be used

Ensure when using item 18

STS/ these are the only

codes that can be used

Reason for Special Handling

(STS/) Requirements

Item 18 ALTRV

Not allocated for a flight operated in

accordance with an altitude

reservation

Ensure ALTRV is accepted

in Item 18 after STS/


(STS/) Requirements

Item 18 ATFMX

Not allocated for a flight approved for

exemption from ATFM

measures by the appropriate

ATS authority

Ensure ATFMX is accepted



(STS/) Requirements

Item 18 FFR

Not allocated fire-fighting Ensure FFR is accepted in

Item 18 after STS/n Item 18

after STS/


(STS/) Requirements

Item 18 FLTCK

Not allocated flight check for calibration of

navaids

Ensure FLTCK is accepted in

Item 18 after STS/


(STS/) Requirements

Item 18 HAZMAT

Not allocated for a flight carrying

hazardous material

Ensure Hazmat is accepted



(STS/) Requirements

Item 18 HEAD

Not allocated a flight with Head of State

status

Ensure HEAD is accepted in

Item 18 after STS/


(STS/) Requirements

7 of 16




Item 18 HOSP

Not allocated for a medical flight declared

by medical authorities

Ensure HOSP is accepted in

Item 18 after STS/


(STS/) Requirements

Item 18 HUM

Not allocated for a flight operating on a

humanitarian mission

Ensure HUM is accepted in

Item 18 after STS/


(STS/) Requirements

Item 18 MARSA

Not allocated for a flight for which a military

entity assumes responsibility

for separation of military

aircraft

Ensure MARSA is accepted



(STS/) Requirements

Item 18 MEDEVAC

Not allocated for a life critical medical

emergency evacuation

Ensure MEDEVAC is

accepted in Item 18 after

STS/


(STS/) Requirements

Item 18 NONRVSM

Not allocated for a non-RVSM capable

flight intending to operate in

RVSM airspace

Ensure NONRVSM is

accepted in Item 18 after

STS/


(STS/) Requirements

Item 18 SAR

Not allocated for a flight engaged in a

search and rescue mission

Ensure SAR is accepted in

Item 18 after STS/


(STS/) Requirements

Item 18 STATE

Not allocated for a flight engaged in

military, customs, or police

services

Ensure STATE is accepted



(STS/) Requirements

Item 18 PBN/

Not allocated Indication of RNAV and/ or

RNP capabilities-total of

eight entries not more than

16 characters

Ensure PBN/ is accepted in

Item 18

Performance Based


Item 18 RNAV

specificationsA1

Not allocated RNAV10(RNP 10) Ensure A1 is accepted in

Item 18 after PBN/

Performance Based


Item 18 RNAV

specificationsB1

Not allocated RNAV 5 all permitted

sensors

Ensure B1 is accepted in

Item 18 after PBN/

Performance Based


Item 18 RNAV

specificationsB2

Not allocated RNAV 5 GNSS Ensure B2 is accepted in

Item 18 after PBN/

Performance Based


Item 18 RNAV

specificationsB3

Not allocated RNAV 5 DME/DME Ensure B3 is accepted in

Item 18 after PBN/

Performance Based


8 of 16




Item 18 RNAV

specificationsB4

Not allocated RNAV 5 VOR/DME Ensure B4 is accepted in

Item 18 after PBN/

Performance Based


Item 18 RNAV

specificationsB5

Not allocated RNAV 5 INS or IRS Ensure B5 is accepted in

Item 18 after PBN/

Performance Based


Item 18 RNAV

specificationsB6

Not allocated RNAV 5 LORANC Ensure B6 is accepted in

Item 18 after PBN/

Performance Based


Item 18 RNAV

specificationsC1


sensors

Ensure C1 is accepted in

Item 18 after PBN/

Performance Based


Item 18 RNAV

specificationsC2

Not allocated RNAV 2 GNSS Ensure C2 is accepted in

Item 18 after PBN/

Performance Based


Item 18 RNAV

specificationsC3

Not allocated RNAV 2 DME/DME Ensure C3 is accepted in

Item 18 after PBN/

Performance Based


Item 18 RNAV

specificationsC4

Not allocated RNAV 2 DME/DME/IRU Ensure C4 is accepted in

Item 18 after PBN/

Performance Based


Item 18 RNAV

specificationsD1


sensors

Ensure D1 is accepted in

Item 18 after PBN/

Performance Based


Item 18 RNAV

specificationsD2

Not allocated RNAV 1 GNSS Ensure D2 is accepted in

Item 18 after PBN/

Performance Based


Item 18 RNAV

specificationsD3

Not allocated RNAV 1 DME/DME Ensure D3 is accepted in

Item 18 after PBN/

Performance Based


Item 18 RNAV

specificationsD4

Not allocated RNAV 1 DME/DME/IRU Ensure D4 is accepted in

Item 18 after PBN/

Performance Based


Item 18 RNP

specifications L1

Not allocated RNP 4 Ensure L1 is accepted in

Item 18 after PBN/

Performance Based


Item 18 RNP

specificationsO1

Not allocated Basic RNP 1 all permitted

sensors

Ensure O1 is accepted in

Item 18 after PBN/

Performance Based


9 of 16




Item 18 RNP

specificationsO2

Not allocated Basic RNP 1 GNSS Ensure O2 is accepted in

Item 18 after PBN/

Performance Based


Item 18 RNP

specificationsO3

Not allocated Basic RNP 1 DME/DME Ensure O3 is accepted Performance Based


Item 18 RNP

specificationsO4

Not allocated Basic RNP 1 DME/DME/IRU Ensure O4 is accepted in

Item 18 after PBN/

Performance Based


Item 18 RNP

specificationsS1

Not allocated RNP APCH Ensure S1 is accepted in

Item 18 after PBN/

Performance Based


Item 18 RNP

specificationsS2

Not allocated RNP APCH with BARO-

VNAV

Ensure S2 is accepted in

Item 18 after PBN/

Performance Based


Item 18 RNP

specificationsT1

Not allocated RNP AR APCH with

RF(special authorization

required)

Ensure T1 is accepted in

Item 18 after PBN/

Performance Based


Item 18 RNP

specificationsT2

Not allocated RNP AR APCH without

RF(special authorization

required)

Ensure T2 is accepted in

Item 18 after PBN/

Performance Based


Item 18 NAV/

Significant Data related to

navigation equipment as

required by the appropriate

ATS authority


navigation equipment, other

than specified in PBN/,as


ATS authority. Indicate

GNSS augmentation under

this indicator, with a space

between two or more

methods of augmentation


Item 18 COM/


communication equipment as


ATS authority

Indicate communications

applications or capabilities

not specified in Item 10a


10 of 16




Item 18 DAT/

Significant data related to

data link capability, using

one or more of the letters S,

H, V and M, e.g. DAT/S for

satellite data link, DAT/H for

HF data link, DAT/V for VHF

data link, DAT/M for SSR

Mode S data link.

Indicate data applications or

capabilities not specified in

Item 10a


Item 18 SUR/

Not allocated Indicate surveillance

applications or capabilities

not specified in Item 10b


Capabilities (SUR/)

Item 18 DEP/

Name of departure

areodrome, if ZZZZ is

inserted in Item 13,or the

ICAO four-letter indicator of

the location of the ATS unit

from which supplementary

flight plan data can be

obtained, if AFIL is inserted

in Item 13

Name and location of

departure aerodrome, if

ZZZZ is inserted in Item 13

or the ATS unit from which

supplementary flight plan

data can be obtained if AFIL

is inserted in Item 13


format

Item 18

DEP/ aerodromes not

listed in the relevant

AIP

Name of departure








in Item 13

With 4 figures describing

latitude in degrees and tens

and units of minutes followed

by ―N‖

(North) or ―S‖ (South),

followed by 5 figures

describing longitude in

degrees and tens and units

of minutes, followed by ―E‖

(East) or ―W‖ (West).

4620N07805W (11

characters).

Ensure Latitude and

Longitude are accepted after

DEP/ in Item 18


format

11 of 16




Item 18

DEP/ aerodromes not


AIP

Name of departure








in Item 13

OR, Bearing and distance

from the nearest

significant point, as follows:

The identification of the

significant point followed by

the bearing 3 figures

degrees magnetic, followed

by the distance from the

point 3 figures nautical

miles. In areas of high

latitude where it is

determined by the

appropriate authority that

reference to degrees

magnetic is impractical,

degrees true may be used.

A point of 180° magnetic at a

distance of 40 nautical miles

from VOR ―DUB‖ should be


Ensure bearing and distance

are accepted after DEP/ in

Item 18


format

Item 18

DEP/ aerodromes not


AIP

Name of departure








in Item 13

OR, The first point of the

route (name or LAT/LONG)

or the marker radio beacon,

if the aircraft has not taken

off from an aerodrome


format

12 of 16




Item 18 DEST/

Name of destination

aerodrome, if ZZZZ is

inserted in Item 16..

DEST/ Name and location of

destination aerodrome, if

ZZZZ is inserted in Item 16.

For aerodromes not listed in

the relevant Aeronautical

Information Publication,

indicate location in

LAT/LONG or bearing and

distance from the nearest

significant point, as

described under DEP/ above

Ensure Lattiude, Longigtude,

or bearing and distance can

be entered after DEST/ in

Item 18.


format

Item 18 DOF in Item 18

Not allocated Insert Date of flight departure

in a six figure

format(YYMMDD,YY=YEAR

MM=MONTH and

DD=DAY)When departure is

more than 24 hours but less

than 120 hours.

Ensure DOF is accepted in

Item 18 and ATC flight plans

can be filed 120 HOURS in

advance


Item 18 REG/

The registration markings of

the aircraft, if different from

the aircraft identification in

Item 7.

The nationality or common

mark and registration mark of

the aircraft, if different from

the aircraft identification in

Item 7.


Item 18 EET/ (Editorial)

Accumulated elapsed times

to such points or FIR

boundaries

Accumulated elapsed times

from take-off to such points

or FIR boundaries


Item 18 SEL/ (Editorial)

SELCAL code, if so

prescribed by the appropriate

ATS authority

SELCAL code, for aircraft so

equipped


Item 18 TYP/ (Editorial)

Type(s) of aircraft, preceded

if necessary by number(s) of

aircraft if ZZZZ is inserted in

Item 9

Type(s)of aircraft preceded if

necessary without a space

by number(s) of aircraft,

preceded if necessary

without a space by

number(s) of aircraft and

separated by one space, if

ZZZZ is inserted in Item

9.Example: –TYP/2F15 5F5

3B2

Content of Field 18 (TYP/)

Type of Aircraft

13 of 16




Item 18 DLE/

Not allocated Enroute delay or holding,

insert the significant point(s)

on the route where a delay is

planned to occur, followed by

the length of delay using four

figure time in hours and

minutes (hhmm).Example:

–DLE/MDG0030

Ensure DLE/ is accepted into

Item 18


Capability

Item 18 OPR/

Name of the operator, if not

obvious from the aircraft

identification in Item 7

ICAO designator or name of

the aircraft operating agency,

if different from the aircraft

identification in item 7.


Item 18 ORGN/

Not allocated The originator’s 8 letter

AFTN address or other

appropriate contact details,

in cases where the originator

of the flight plan may not be

readily identified, as required

by the appropriate ATS

authority. Note.— In some

areas, flight plan reception

centers may insert the

ORGN/ identifier and

originator’s AFTN address

automatically.

Ensure ORGN/ is accepted

into Item 18.

Content of Field 18 (TYP/)

Type of Aircraft

Item 18 PER/

Aircraft performance data, if

so prescribed by the

appropriate ATS authority

Aircraft performance data,

indicated by a single letter as

specified in the Procedures

for Air

Navigation Services —

Aircraft Operations (PANS-

OPS, Doc 8168), Volume I

— Flight Procedures, if so

prescribed by the appropriate

ATS authority

A/C Performance (PER/)

14 of 16




Item 18 ALTN/

Name of destination

alternate, if ZZZZ is inserted

in Item 16.

Name of destination

alternate aerodrome(s), if

ZZZZ is inserted in Item 16.

For aerodromes not


Aeronautical Information

Publication, indicate location

in LAT/LONG or bearing and



described in DEP/ earlier.

Ensure changes to ALTN/

are accepted into Item 18


format

Item 18 RALT/

Name of en-route alternate

aerodrome(s).

ICAO four letter indicator(s)

for en-route alternate(s), as

specified in Doc 7910,

Location

Indicators, or name(s) of en-

route alternate aerodrome(s),

if no indicator is allocated.

For

aerodromes not listed in the

relevant Aeronautical

Information Publication,

indicate location in

LAT/LONG or bearing and





format

15 of 16




Item 18 TALT/

Not allocated ICAO four letter indicator(s)

for take-off alternate, as

specified in Doc 7910,

Location Indicators, or name

of take-off alternate

aerodrome, if no indicator is

allocated. For aerodromes

not listed in the relevant

Aeronautical Information

Publication, indicate location

in LAT/LONG or bearing and




Ensure TALT/ is accepted in

Item 18

Alternate Take-Off Airport

(TALT/)

p24 Message format

DLA CHG CNL ARR RQS

currently do not require

EOBT

DLA CHG CNL ARR RQS

now require the estimated off

blocks time (EOBT)

Ensure (EOBT) is accepted

in DLA CHG CNL ARR RQS

EOBT in Flight Data change

messages

p25 Message format

DLA CHG CNL ARR RQS

end after Item 16

Now require Item 18 info;

DOF/ only

Ensure Item 18 is accepted

in DLA CHG CNL ARR RQS


messages

p36 Message format

N/A CNL,DLA,DEP,RQP,RQS

Include a -0 for Field 18 if

there is no DOF/


messages

16 of 16

Part V - Aircraft performance categories Appendix A to


1.3 CATEGORIES OF AIRCRAFT

1.3.1 Aircraft performance has a direct effect on the airspace and visibility required for the various manoeuvres associated with the conduct of instrument approach

procedures. The most significant performance factor is aircraft speed.

1.3.2 Accordingly, categories of typical aircraft have been established. These categories provide a standardized basis for relating aircraft manoeuvrability to specific

instrument approach procedures. For precision approach procedures, the dimensions of the aircraft are also a factor for the calculation of the obstacle clearance

height (OCH). For Category DL aircraft, an additional obstacle clearance altitude/height (OCA/H) is provided, when necessary, to take into account the specific

dimensions of these aircraft (see Part II, Section 1, Chapter 1, 1.3).

1.3.3 The criterion taken into consideration for the classification of aeroplanes by categories is the indicated airspeed at threshold (Vat), which is equal to the stall

speed Vso multiplied by 1.3, or stall speed Vs1g multiplied by 1.23 in the landing configuration at the maximum certificated landing mass. If both Vso and Vs1g are

available, the higher resulting Vat shall be applied.

1.3.4 The landing configuration that is to be taken into consideration shall be defined by the operator or by the aeroplane manufacturer.

1.3.5 Aircraft categories will be referred to throughout this document by their letter designations as follows:

Category A: less than 169 km/h (91 kt) indicated airspeed (IAS)

Category B: 169 km/h (91 kt) or more but less than 224 km/h (121 kt) IAS

Category C: 224 km/h (121 kt) or more but less than 261 km/h (141 kt) IAS

Category D: 261 km/h (141 kt) or more but less than 307 km/h (166 kt) IAS

Category E: 307 km/h (166 kt) or more but less than 391 km/h (211 kt) IAS

Category H: see 1.3.10, “Helicopters”.

1.3.6 Permanent change of category (maximum landing mass). An operator may impose a permanent lower landing mass, and use of this mass for determining Vat if

approved by the State of the Operator. The category defined for a given aeroplane shall be a permanent value and thus independent of changing day-to-day

operations.

1.3.7 As indicated in Tables I-4-1-1 and I-4-1-2, a specified range of handling speeds for each category of aircraft has been assumed for use in calculating airspace

and obstacle clearance requirements for each procedure.

1.3.8 The instrument approach chart (IAC) will specify the individual categories of aircraft for which the procedure is approved. Normally, procedures will be designed

to provide protected airspace and obstacle clearance for aircraft up to and including Category D. However, where airspace requirements are critical, procedures may

be restricted to lower speed categories.

1.3.9 Alternatively, the procedure may specify a maximum IAS for a particular segment without reference to aircraft category. In any case, it is essential that pilots

comply with the procedures and information depicted on instrument flight charts and the appropriate flight parameters shown in Tables I-4-1-1 and I-4-1-2 if the

aircraft is to remain in the areas developed for obstacle clearance purposes.

1 of 1

fpl 2012 worksheet - icao.int meetings seminars and workshops/fpl... · in amendment 1 to doc 4444,...

Documents