Get documents about "How to Use This Spreadsheet Guidance The Guidance Tab contains Checklist The checklist tab conta
Description
Aip Icao Template document sample
Document Sample
How to Use This Spreadsheet
Guidance: The Guidance Tab contains Checklist: The checklist tab contains a Detailed Changes: The Detailed A/C Perf Cat: The A/C Perf Cat tab
a description of each of the 27 spreadsheet which details the 27 Changes tab lists all of the provides a description of ICAO aircraft
substantive (i.e., non-editorial) changes substantive changes, their descriptions approximately 150 changes in performance categories referrenced in
Description in Amendment 1 to DOC 4444, along and a series of impact questions to Amendment 1, including editorial Attachment 1 (informational only).
of the with descriptions of the probable answer. changes. Each is mapped to one of the
Tabs impacts to each of the system identified 27 substantive changes or to
categories described below. "Editorial/Clarification".
Step 1. Evaluate each change. In the Step 2. In evaluating a change, you can Step 3. The results of the evaluation
"Guidance" tab, each new requirement go to the "Detailed Changes" tab and should be tabulated on the "checklist"
Instructions is summarized and guidance is provided filter on the change being evaluated. spreadsheet.
How to use the for each of the four types of systems Each line-by-line amendments relating
checklist to evaluate (described below). to that change is shown.
changes imposed by
Amendment 1
Filers: An individual or organization Flight Planning Services: A system FDP (Flight Data Processing) Flight Data Users: A system that
that files an FPL or related ATS that electronically sends an FPL or Systems: A system that accepts and receives data from FDP systems which
Description message. related ATS message over processes an FPL or related ATS has been derived from an FPL or related
of the NADIN/AFTN to an FDP (e.g., flight message for ATC purposes. ATS message, but does not directly
System services organizations, commercial receive FPLs or related ATS messages.
Categories services, etc.).
Overview 1 of 29
New Requirement Description Filers Flight Planning Services FDP Systems Flight Data Users
Date of Flight A new field 18 item, DOF/, will be optionally allowed in an FPL. Furthermore, filing up to 120 hours (5 1. Include the date of flight when the 1. If your interface already allows for 1. Accept DOF/ in messages (most 1. No change in when flight data is
Requirements days) in advance of the flight will be permitted. proposed time is more than 24 hours date of flight entry, use that to already do). distributed.
in advance. populate DOF/ when flight is more 2. If present, use DOF/ instead of 2. CMS users: Expect DOF/ in field 18-
than 24 hours in advance. NDTI calculation already get it today.
2. At this time, no change in rules for 3. On Field 06 amendments, re- 3. Other users- No change in
1 filing with the En Route system are determine DOF/ when necessary. interface. Data is not sent to other
anticipated. 4. Q: How does controller CHI need to ATC systems more than 24 hours in
change for Field 07 amendments? advance, so no date information
should be needed on those
interfaces.
ACID format (Field 07) The existing requirement is clarified to indicate that only letters and numbers are permitted. No 1. No change- file per current rules. 1. No change expected. 1. No change expected. 1. No change expected.
hyphens or other special characters are allowed. Since registration numbers in some countries are Make sure to omit any hyphens or
2 expressed with hyphens, it appears they wanted to clarify this. There is no change to the existing spaces in registration numbers
requirement.
Field 10 format The permitted field 10 format used to be a series of 1 to 25 letters followed by an oblique stroke 1. Follow the new format 1. Modify accept and send the new 1. Modify to accept and send the new 1. Extended NAS FP and CMS
followed by 1 to 2 letters. Now, not only are the maximum lengths of the subfields before and after the format. format. recipients: Expect new format for EQP
3 stroke increased but the format will include letter-digit combinations in addition to single letters. Note 2. Need to change all affected ICDs data.
that for any letter, it either always occurs alone or always occurs with a following digit. including NAT, PAC, NAM.
GPS Augmentation for There are two new capabilities expressed in ICAO Field 10a: 1. Q: Does the FAA require this 1. Modify CHI as necessary to provide 1. Accept, store, and forward these 1. Extended NAS and CMS recipients
Landing Capability A: GBAS Landing System information? All domains need to reasonable interface to pilots for filing items in flight data messages. will automatically receive this data.
B: LPV (APV with SBAS) answer. the new capabilities. 2. Provide controller CHI on relevant 2. Other users- no change expected
GBAS is Ground-Based Augmentation System. 2. Modify to accept and send the new equipment template(s) and cmd line unless a critical need to get this
The purpose of LPV (Localizer Performance with Vertical guidance) is to fly ILS look-alike procedures data. 3. No enroute or oceanic processing information is identified.
4 published as RNAV GNSS with LPV minima, by using SBAS (Space Based Augmentation System) or currently requires or is anticipated to
ABAS (Aircraft Based Augmentation System). require this data.
ACARS capability Aircraft Communications Addressing and Reporting System (ACARS) is a digital datalink system for 1. Q: Does the FAA require this 1. Modify CHI as necessary to provide 1. Accept, store, and forward these 1. Extended NAS and CMS recipients
transmission of short, relatively simple messages between aircraft and ground stations via radio or information? All domains need to reasonable interface to pilots for filing items in flight data messages. will automatically receive this data.
satellite. answer. the new capabilities. 2. Provide controller CHI on relevant 2. Other users- no change expected
Three new Field 10a designators have been added to describe ACARS capability of an aircraft: 2. Modify to accept and send the new equipment template(s) and cmd line unless a critical need to get this
E1: FMC WPR ACARS- This is the capability to send FMC Waypoint Reports via ACARS. Some NAT data. 3. No enroute processing currently information is identified.
FIRs presently accept ACARS FMC Waypoint Reports (FMC WPR) as an alternative to ADS for requires this data. In the future, PDC
aircraft that do not support ADS. capability may be of interest, but not
5 E2: D-FIS ACARS- The ability to receive airfield and weather information via the automatic terminal initially.
information service (ATIS), and regular meteorological information (VOLMET) through ACARS. 4. Oceanic systems need to evaluate
E3: PDC ACARS- The ability to receive Pre-Departure Clearance messages through ACARS. whether any of these- E1 in particular-
are needed.
Guidance 2 of 29
New Requirement Description Filers Flight Planning Services FDP Systems Flight Data Users
CPDLC capability Controller Pilot Data Link Communications (CPDLC) used to be designated by a ―J‖ in ICAO Field 1. Q: Does the FAA require this 1. Modify CHI as necessary to provide 1. Accept, store, and forward these 1. Extended NAS and CMS recipients
10a, with details of the capability described in Field 18. Now, most of those details are designated information? All domains need to reasonable interface to pilots for filing items in flight data messages. will automatically receive this data.
within Field 10a through the following designators: answer. Not currently needed for En the new capabilities. 2. Provide controller CHI on relevant 2. Other users- no change expected.
J1 CPDLC ATN VDL Mode 2 Route or Terminal operations. 2. Modify to accept and send the new equipment template(s) and cmd line No current need anywhere in the
J2 CPDLC ATN FANS 1/A HFDL data. 3. No enroute processing currently domestic NAS.
J3 CPDLC ATN FANS 1/A VDL Mode A requires this data. In the future it will
6 J4 CPDLC FANS 1/A VDL Mode 2 likely be needed.
J5 CPDLC FANS 1/A SATCOM(INMARSAT) 4. Oceanic FDP systems need to
J6 CPDLC FANS 1/A SATCOM(MTSAT) evaluate whether this information is
J7 CPDLC FANS 1/A SATCOM(Iridium) needed.
CPDLC is not yet implemented in domestic U.S., however it is in use in the two Oceanic centers
(Oakland and New York) and in Anchorage Center.
Satellite RTF The FPL will now allow a filer to specify one of several satellite communication capabilities: 1. Q: Does the FAA require this 1. Modify CHI as necessary to provide 1. Accept, store, and forward these 1. Extended NAS and CMS recipients
M1 ATC RTF SATCOM(INMARSAT)—ATC radiotelephone capability via INMARSAT information? All domains need to reasonable interface to pilots for filing items in flight data messages. will automatically receive this data.
M2 ATC RTF (MTSAT)—ATC radiotelephone capability via MTSAT answer. Not currently needed for En the new capabilities. 2. Provide controller CHI on relevant 2. Other users- no change expected.
M3 ATC RTF (Iridium)—ATC radiotelephone capability via Iridium Route or Terminal operations. 2. Modify to accept and send the new equipment template(s) and cmd line No current need anywhere in the
data. 3. No enroute processing currently domestic NAS.
7 requires this data.
4. Oceanic systems need to evaluate
whether they have any need.
VHF/8.33 kHz VHF channel spacing in some airspace (e.g. within Europe) has been reduced from 25 kHz to 8.33 1. No need for this information by the 1. Modify CHI as necessary to provide 1. Accept, store, and forward these 1. Extended NAS and CMS recipients
kHz to allow for more capacity. The United States has not made this change and therefore the FAA. Domestic filers can ignore it. reasonable interface to pilots for filing items in flight data messages. will automatically receive this data.
capability is not relevant to U.S. operations. File as required for international the new capabilities. 2. Provide controller CHI on relevant 2. Other users- no change expected.
The amendment designates the letter ―Y‖ for this capability. Note that Y was previously used ―as flights. 2. Modify to accept and send the new equipment template(s) and cmd line No current need anywhere in the
8 prescribed by ATS‖ and was sometimes used to denote Canadian MNPS capability. data. 3. No enroute or oceanic processing domestic NAS.
currently requires this data.
ADS-B capability The existing FPL format only allows for a non-descriptive ―D‖ for ―ADS capability‖ in Field 10b. The 1. File ADS-B capability as described. 1. Modify CHI as necessary to provide 1. Accept, store, and forward these 1. Extended NAS and CMS recipients
new FPL format expands Field 10b to provide a detailed accounting of ADS-B capability. File this data instead of equivalent reasonable interface to pilots for filing items in flight data messages. will automatically receive this data.
E Transponder Mode S including aircraft identification, pressure-altitude and extended squitter(ADS- data in COM/ that was earlier the new capabilities. 2. Provide controller CHI on relevant 2. Terminal systems will get this data
B)capability directed. 2. Modify to accept and send the new equipment template(s) and cmd line per the agreed interface- no impact
B1 ADS-B with dedicated 1090 MHz ADS-B "out" capability data. 3. Enroute processing will have to expected.
B2 ADS-B with dedicated 1090 MHz ADS-B "out" and "in" capability change to get ADS-B capability from 3. No other system interface changes
9 U1 ADS-B "out" capability using UAT Field 10b instead of from COM/. expected.
U2 ADS-B out and in capability using UAT 4. Oceanic systems need to assess.
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?
ADS-C capability The existing FPL format only allows for a non-descriptive ―D‖ for ―ADS capability‖ in Field 10b. The 1. File ADS-C capability as described. 1. Modify CHI as necessary to provide
new FPL format expands Field 10b to provide a detailed accounting of ADS-C capability. 2. Q: Are there current instructions reasonable interface to pilots for filing
D1 ADS-C with FANS 1/A capabilities that need to be replaced? the new capabilities.
10
G1 ADS-C with ATN capabilities 2. Modify to accept and send the new
data.
FRD w/5 letter base fix The current FPL format for a Fix Radial Distance specifies that the base fix must be a NAVAID with a 1. No change expected; FAA already 1. If the filing system does a route 1. No changes expected; FAA already 1. No changes expected; FAA already
2-3 letter name. The amendment makes use of a 2-5 character base fix allowable. allows this. check, ensure that 5-letter base fixes allows this. allows this.
Note that the FAA already supports 25 character base fixes; this makes the Document 4444 are allowed in FRDs.
11
consistent with our current practice.
Guidance 3 of 29
New Requirement Description Filers Flight Planning Services FDP Systems Flight Data Users
DEP, DEST, and PRESENT FPL does not provide explicit guidance on how to enter a departure or destination location 1. File DEP/, DEST/, ALTN/, and 1. If the filing system automatically 1. If DEP/ and DEST/ are processed, 1. The processing associated with
Alternate format in Field 18 DEP/, DEST/, ALTN/, RALT/, or TALT/. The original instructions were geared towards TALT/ as instructed. creates DEP/ and DEST/ entries need to change from processing the DEP/ and DEST/ is transparent to
providing a human-readable description, and did not anticipate automation attempts to process the 2. FAA may need to issue more based on filing a non-standard first element to (likely) processing the flight data users; the FDP systems
location. The contents of each of these fields should contain the name of the airport followed by the precise guidance that is compliant departure or destination, need to last element. handle it.
location of the airport. The location can be either a Lat/Lon, an FRD, or a fix name, as follows: with this; need to assess. adhere to this format. 2. En route systems can auto- 2. If there is any use made of ALTN/
- Name and location of departure aerodrome, if ZZZZ is inserted in Item 13, or the ATS unit from 3. Q: Do we need to limit how the 2. Q: What should the name of the populate DEP/ and DEST/ on output; or TALT/ data, the systems need to
which supplementary flight plan data can be obtained, if AFIL is inserted in Item 13. For aerodromes airport name is entered? (e.g. blanks airport be if a non-standard departure need to agree with NAM ICD be aware of the new content.
not listed in the relevant Aeronautical Information Publication, indicate location as follows: allowed or not?) point and no other info is filed? neighbors on what to use for "name".
With 4 figures describing latitude in degrees and tens and units of minutes followed by ―N‖ (North) as well as agreeing on details of the
or ―S‖ (South), followed by 5 figures describing longitude in degrees and tens and units of minutes, content.
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).
12 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.
Required Field 18 format In the existing instructions, Field 18 is supposed to be populated in the ―preferred‖ sequence shown. 1. Ensure Field 18 items are in the 1. Enforce the new rules and do not 1. Enforce the new rules and do not 1. No significant changes expected.
The word preferred implied that it was not required. The amendment removes the word preferred, required sequence. pass along messages not in pass along messages not in En route systems already output data
and now makes the defined sequence required. 2. Ensure no hyphens appear in Field conformance with them. conformance with them. in preferred sequence. Today, could
The amendment also clarifies that hyphens shall not be used within Field 18. This was already the 18. receive oblique strokes that should no
13
case, but there have been problems with filers including hyphens. 3. Ensure that an oblique stroke is longer be present.
Finally, the use of oblique strokes is now limited to use in indicators. In the existing format, oblique used only as part of a valid indicator.
strokes could be used within free text portions.
Reason for Special In the current flight plan, STS/ is a free-text field with guidance on the type of information to include. 1. File only the designated items in 1. Modify CHI as necessary to provide 1. Accept, store, and forward these 1. Extended NAS and CMS recipients
Handling (STS/) The amendment makes this a rigidly controlled field with an enumerated list of allowed strings that can STS/, per instructions. reasonable interface to pilots for filing items in flight data messages. will automatically receive this data.
Requirements be included. The allowed values are now: 2. Q: How do we reconcile HOSP and the new capabilities. 2. Provide controller CHI on relevant 2. Terminal systems will get this data
ALTRV for a flight operated in accordance with an altitude reservation MEDEVAC with LIFEGUARD 2. Modify to accept and send the new equipment template(s) and cmd line on FDIO flight strips per current
ATFMX for a flight approved for exemption from ATFM measures by the appropriate ATS authority data. requirements.
FFR fire-fighting 3. Enforce that STS/ contains only the 3. STS/ data exists today; presumably
FLTCK flight check for calibration of navaids allowed items. any system that needs it is getting it
HAZMAT for a flight carrying hazardous material and therefore no change is expected.
HEAD a flight with Head of State status
14 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
Guidance 4 of 29
New Requirement Description Filers Flight Planning Services FDP Systems Flight Data Users
Performance Based The amendment provides a mechanism for filing the capabilities of the aircraft/crew/FMS for 1. File in accordance with instructions. 1. Modify CHI as necessary to provide 1. Accept, store, and forward these 1. Extended NAS and CMS recipients
Navigation capability Performance Based Navigation in a new indicator PBN/ in Field 18. Each capability is represented by 2. FAA needs to determine whether reasonable interface to pilots for filing items in flight data messages. will automatically receive this data.
(PBN/) a letter-digit code: filing D2 or D4 can substitute for NAV/ the new capabilities. 2. Provide controller CHI on relevant 2. Terminal systems are aware of
RNAV SPECIFICATIONS information as currently filed. 2. Modify to accept and send the new equipment template(s) and cmd line PBN capability indirectly through the
A1 RNAV 10 (RNP 10) 3. FAA needs to determine whether data. 3. Enroute processing will have to fix pair sent in the ARTS flight plan.
B1 RNAV 5 all permitted sensors NAV/ data will still be used in new change to use PBN/ data in lieu of No change to the data shared is
B2 RNAV 5 GNSS format, and if so, whether NAV/ or NAV/ data, new requirements are still expected due to this change.
B3 RNAV 5 DME/DME PBN/ takes precedence. TBD. 3. If any of the new items are critically
B4 RNAV 5 VOR/DME 4. Oceanic systems need to evaluate needed (e.g. S1, S2, T1, T2), this
B5 RNAV 5 INS or IRS which data is to be used in lieu of needs to be identified.
B6 RNAV 5 LORANC current filed data in NAV/.
C1 RNAV 2 all permitted sensors
C2 RNAV 2 GNSS
C3 RNAV 2 DME/DME
C4 RNAV 2 DME/DME/IRU
15 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)
Delay at a fix (DLE/) In domestic format flight plans, a delay can be filed at any fix in the route. The amendment introduces 1. File in accordance with instructions. 1. Modify CHI as necessary to provide 1. Accept DLE/ element and translate 1. No changes expected; Data
Capability the ability to specify a delay at a fix in Field 18. The En Route automation will likely attempt to re- 2. Q: Should FAA require that fix in a reasonable interface to pilots for filing to a delay in the route field. received from FDP will be as today,
format this into a domestic format delay on the corresponding fix in the route. DLE/ be a filed fix in Field 15c? the new capabilities. 2. Q: If fix does not exist, should FPL with delays in the route.
2. Modify to accept and send the new be rejected, or DLE/ ignored?
data. 3. Q: If fix is not filed but is on an
airway that was filed, what should the
automation do? (Insert the fix into the
16 filed route?)
4. Translate fix delays into DLE/
elements on outbound CPL, FPL, etc.
5. Oceanic systems may need to
consider a different approach, since
Ocean21 is "natively" ICAO.
Alternate Take-Off The amendment introduces the capability to specify an alternate departure airport in Field 18, using 1. File in accordance with instructions. 1. Modify CHI as necessary to provide 1. Accept, store, and forward these 1. Extended NAS and CMS recipients
Airport (TALT/) the new indicator TALT/. The rules for content of this field will be essentially the same as for DEP/ 2.Q: Does the FAA need to require reasonable interface to pilots for filing items in flight data messages. will automatically receive this data.
and DEST/. This is to specify an airport within an hour of the departure point at which the aircraft filing this to comply with current rules the new capabilities. 2. Provide controller CHI on relevant 2. Other systems will not get this data.
would plan to land if needed-- mostly for use when the departure airport is below arrival minimums. regarding having a take off alternate? 2. Modify to accept and send the new equipment template(s) and cmd line No changes anticipated unless
17
Current thought is no. data. someone identifies a critical need for
the data.
Guidance 5 of 29
New Requirement Description Filers Flight Planning Services FDP Systems Flight Data Users
EOBT in 2nd order msgs Currently, the Doc. 4444 specification of CHG, DLA and CNL messages indicates that Field 13 in 1. Can optionally provide this element 1. Probably would be good practice to 1. Need to accept the EOBT in 1. Should be no impact to secondary
those messages should include only 13a (the departure airport) and not 13b (the departure time). in CHG, DLA, and CNL messages regularly include this item, assuming incoming messages. receivers of flight data.
Many ANSPs allow filers to include Field 13b to help differentiate between multiple proposed flight sent to FAA. the original filed data is still retained. 2. Add processing to use EOBT is a
plans for the same ACID. The amendment changes the message definitions to include 13b. 2. Note that if message number in Field 03 message number is not
18 Note: ARR and RQS messages are also changed. The FAA does not currently process these Field 3b is used, this is completely provided and there are multiple flight
messages. unnecessary but will be accepted. plan matches (same AID, same
This will not be an optional element after the change; it will be required. dep/dest).
DOF in 2nd order msgs By accepting a date of flight in a FPL, the date of flight must also be provided in second order 1. Provide DOF/ when required. 1. When DOF/ was filed in a FPL, 1. Accept Field 18 as an optional item 1. Should be no impact to secondary
messages (CHG, DLA, and CNL). The specification indicates Field 18 should be included in the make sure any CHG, CNL, or DLA in CHG, CNL, and DLA. receivers of flight data.
messages; this has been clarified to mean only the DOF/ indicator from Field 18. Note that when message includes it. 2. When present, use DOF/ to match
DOF/ is not present, a Field 18 of -0 should be included. 2. When no DOF/ was filed, make a previously filed FPL.
19 sure a -0 is sent in CHG, CNL, or DLA 3. Q: Is this change needed in NAM,
messages. NAT, PAC ICDs? Plans are never
sent more than 24 hours in advance...
Standard Equipment The current definition of S in Field 10a is ADF, VOR, VHF RTF, and ILS. The amendment changes 1. File in accordance with the new 1. No change expected. 1. Change translation tables, 1. Be aware of the change in
definition this to VOR, VHF RTF, and ILS. ADF has been removed. instructions. "S" can be used in more validation tables as necessary. definition. No interface changes
20
cases, and ADF must always be expected.
explicitly filed.
Meaning of "other" An item ―Z‖ in ICAO Field 10a indicates that there is additional information in Field 18. The 1. File in accordance with the new 1. If the system enforces 10a/18 1. If the system enforces 10a/18 1. Be aware of the change in
equipment amendment slightly changes what it is referring to; a Z used to refer to additional data in COM/ or instructions. If DAT/ is included, be compatibility, then check for a Z in compatibility, then check for a Z in definition. No interface changes
NAV/; it now indicates there is additional data in COM/, NAV/, or DAT/. aware that the Z is required in 10a 10a when DAT/ is present. 10a when DAT/ is present. expected.
21 (instead of "J" as currently required). 2. At least some current systems do
not enforce this relationship.
3. Q: Is the status quo OK, or do we
need to force this check?
Required Comm. The RCP concept characterizes the performance required for communication capabilities that support 1. Future- no changes now. 1. Future- no changes now. 1. Future- no changes now. 1. Future- no changes now.
Performance 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,
22 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.
Additional Surveillance The amendment introduces the ability to file a new indicator SUR/ in Field 18, to describe any 1. FAA anticipates no need to file any 1. Modify CHI as necessary to provide 1. Accept, store, and forward these 1. Extended NAS and CMS recipients
Capabilities (SUR/) additional surveillance capabilities not listed in Field 10b. There is no letter in 10b to indicate a SUR/ data in this field. reasonable interface to pilots for filing items in flight data messages. will automatically receive this data.
entry exists. There are no format or content requirements for SUR/; it is essentially free-text. the new capabilities. 2. Provide controller CHI on relevant 2. Other users- no change expected.
23 2. Modify to accept and send the new equipment template(s) and cmd line No current need anywhere in the
data. domestic NAS.
Content of Field 18 The amendment provides direction for how to include multiple aircraft types for formation flights, and 1. File in accordance with the new 1. Should be no impact; TYP/ already 1. Should be no impact; TYP/ already 1. Extended NAS and CMS recipients
(TYP/) Type of Aircraft the number of each aircraft type in the formation. This information is to be specified in TYP/ in Field instructions. exists. exists. will automatically receive this data.
18. 2. Q: Is there any reason to validate 2. Other users- no change expected.
24 content per the instructions (i.e. only Need to identify if there is a critical
allow 0-2 digits followed by a valid need for this information.
A/C type)
Message Originator The amendment adds an ORGN/ indicator in Field 18. This indicator is intended to be used by a 1. No impacts. 1. Q: Should we recommend/require 1. Consider removing from adapted 1. Extended NAS and CMS recipients
(ORGN/) FPLning service, to indicate the AFTN address or other contact information for the filer that originated that flight planning services add an list of indicators and make "standard". will automatically receive this data.
the FPL, since the FDP system receiving the FPL will see it as coming from the filing service. ORGN/ indicator? 2. Remove from any list of indicators 2. Other users- no change expected.
25 to not coordinate with Mexico. No current need anywhere in the
domestic NAS.
Guidance 6 of 29
New Requirement Description Filers Flight Planning Services FDP Systems Flight Data Users
A/C Performance (PER/) The existing requirements for PER/ in Field 18 are simply to include information as required by ATS 1. File in accordance with the new 1. Enforce only one character allowed 1. Enforce only one character allowed 1. Extended NAS and CMS recipients
units; it is essentially a free text field. The amendment changes this to require a single letter category instructions. in PER/ in PER/. will automatically receive this data.
per ICAO Document 8168, Volume 1. Section 1.3 describes the categories, that section is replicated 2. Per instructions, only needed as 2. Ideally, provide CHI that assists in 2. If data is used, (maybe oceanic) 2. Other users- no change expected.
in another tab. required by ANSP-- FAA has no entering the data (but might not be then provide improved controller CHI. Need to identify if there is a critical
26 identified need at this time (Oceanic- important) 3. If data is used in trajectory need for this information.
what about you?) modeling or other processing,
requisite logic will be needed.
Enhanced Mode-S Enhanced Surveillance entails the use of Downlink Aircraft Parameters (DAPs) in support of a number 1. File in accordance with the new 1. Modify CHI as necessary to provide 1. Accept, store, and forward these 1. Extended NAS and CMS recipients
Surveillance Capability of ATM applications. The Controller Access Parameter (CAP) Service is the most prominent one. instructions. reasonable interface to pilots for filing items in flight data messages. will automatically receive this data.
System improvements such as a Level Bust Alerting Tool, enhanced tracking and improved safety 2. The FAA does not use this the new capabilities. 2. Provide controller CHI on relevant 2. Other users- no change expected.
nets are also considered. These all relate to improvements in tactical ATC operations particularly capability currently, and therefore has 2. Modify to accept and send the new equipment template(s) and cmd line No current need anywhere in the
relevant in the high-density airspace of Europe where Mode S Elementary Surveillance is already no need for this information. data. 3. No enroute or oceanic FDP domestic NAS.
27 being implemented. processing currently requires this
data.
Guidance 7 of 29
Are there procedures
Are any changes to Does this affect Description of
and/or LOA's Description of impact
New Requirement Description filing requirements Automation systems impact if
impacted by this if affected
needed? Systems? affected
change?
Date of Flight A new field 18 item, DOF/, will be optionally allowed in a flight plan. Furthermore, filing up to 120
1 Requirements hours (5 days) in advance of the flight will be permitted.
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
2 expressed with hyphens, it appears they wanted to clarify this. There is no change to the existing
requirement.
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
3 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.
GPS Augmentation for There are two new capabilities expressed in ICAO Field 10a:
Landing Capability A: GBAS Landing System
B: LPV (APV with SBAS)
4 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).
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
5 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.
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
6 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)
CPDLC is not yet implemented in domestic U.S., however it is in use in the two Oceanic centers
(Oakland and New York) and in Anchorage Center.
Checklist 8 of 29
Are there procedures
Are any changes to Does this affect Description of
and/or LOA's Description of impact
New Requirement Description filing requirements Automation systems impact if
impacted by this if affected
needed? Systems? affected
change?
Satellite RTF The flight plan will now allow a filer to specify one of several satellite communication capabilities:
M1 ATC RTF SATCOM(INMARSAT)—ATC radiotelephone capability via INMARSAT
7 M2 ATC RTF (MTSAT)—ATC radiotelephone capability via MTSAT
M3 ATC RTF (Iridium)—ATC radiotelephone capability via Iridium
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
8 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.
ADS-B capability The existing flight plan format only allows for a non-descriptive ―D‖ for ―ADS capability‖ in Field 10b.
The new flight plan 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
9
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?
ADS-C capability The existing flight plan format only allows for a non-descriptive ―D‖ for ―ADS capability‖ in Field 10b.
The new flight plan format expands Field 10b to provide a detailed accounting of ADS-C capability.
10 D1 ADS-C with FANS 1/A capabilities
G1 ADS-C with ATN capabilities
FRD w/5 letter base fix The current flight plan format for a Fix Radial Distance 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.
11 Note that the FAA already supports 25 character base fixes; this makes the Document 4444 consistent
with our current practice.
Checklist 9 of 29
Are there procedures
Are any changes to Does this affect Description of
and/or LOA's Description of impact
New Requirement Description filing requirements Automation systems impact if
impacted by this if affected
needed? Systems? affected
change?
DEP, DEST, and The current flight plan does not provide explicit guidance on how to enter an departure or destination
Alternate format 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 airport followed by the location of
the airport. 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,
12 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.
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.
13 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.
Checklist 10 of 29
Are there procedures
Are any changes to Does this affect Description of
and/or LOA's Description of impact
New Requirement Description filing requirements Automation systems impact if
impacted by this if affected
needed? Systems? affected
change?
Reason for Special In the current flight plan, STS/ is a free-text field with guidance on the type of information to include.
Handling (STS/) The amendment makes this a rigidly controlled field with an enumerated list of allowed strings that can
Requirements 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
14
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
Performance Based The amendment provides a mechanism for filing the capabilities of the aircraft/crew/FMS for
Navigation capability Performance Based Navigation in a new indicator PBN/ in Field 18. Each capability is represented by
(PBN/) 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
15 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)
Checklist 11 of 29
Are there procedures
Are any changes to Does this affect Description of
and/or LOA's Description of impact
New Requirement Description filing requirements Automation systems impact if
impacted by this if affected
needed? Systems? affected
change?
Delay at a fix (DLE/) In domestic format flight plans, a delay can be filed at any fix in the route. The amendment introduces
16 ability the ability to specify a delay at a fix in Field 18. The En Route automation will likely attempt to re-
format this into a domestic format delay on the corresponding fix in the route.
Alternate Take-Off The amendment introduces the capability to specify an alternate departure airport in Field 18, using
17 Airport (TALT/) the new indicator TALT/. The rules for content of this field will be essentially the same as for DEP/ and
DEST/.
EOBT in 2nd order msgs 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.
18 Note: ARR and RQS messages are also changed. The FAA does not currently process these
messages.
This will not be an optional element after the change; it will be required.
DOF in 2nd order msgs By accepting a date of flight in a flight plan, 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
19 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.
Standard Equipment The current definition of S in Field 10a is ADF, VOR, VHF RTF, and ILS. The amendment changes
20 definition this to VOR, VHF RTF, and ILS. ADF has been removed.
Meaning of "other" An item ―Z‖ in ICAO Field 10a indicates that there is additional information in Field 18. The
21 equipment 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/.
Checklist 12 of 29
Are there procedures
Are any changes to Does this affect Description of
and/or LOA's Description of impact
New Requirement Description filing requirements Automation systems impact if
impacted by this if affected
needed? Systems? affected
change?
Required Comm. The RCP concept characterizes the performance required for communication capabilities that support
Performance 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,
22
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.
Additional Surveillance The amendment introduces the ability to file a new indicator SUR/ in Field 18, to describe any
23 Capabilities (SUR/) 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.
Content of Field 18 The amendment provides direction for how to include multiple aircraft types for formation flights, and
24 (TYP/) Type of Aircraft the number of each aircraft type in the formation. This information is to be specified in TYP/ in Field
18.
Message Originator The amendment adds an ORGN/ indicator in Field 18. This indicator is intended to be used by a flight
(ORGN/) planning service, to indicate the AFTN address or other contact information for the filer that originated
25 the flight plan, since the FDP system receiving the flight plan will see it as coming from the filing
service.
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
26 per ICAO Document 8168, Volume 1. Section 1.3 describes the categories, that section is replicated
in another tab.
Enhanced Mode-S Enhanced Surveillance entails the use of Downlink Aircraft Parameters (DAPs) in support of a number
Surveillance Capability 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
27
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.
Checklist 13 of 29
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
FPL submission prior Not more than 24 hours Not more than 120 hours Date of Flight Requirements
4.4.2.1.1
to departure
Hold FPL in abeyance if filed DOF shall be inserted in Item Date of Flight Requirements
11.4.2.2.2.5 DOF in Item 18 more than 24 hours in 18 if FPL filed more than 24
advance hours in advance
11.4.2.2.4 CHG Message N/A Editorial clarification Editorial/Clarification
N/A Note 2 regarding constraints VHF/8.33 kHz
2.2 Insertion of ATS Data
7 characters 7 alphanumerics without Reject FPL filed with hyphen ACID format (Field 07)
Item 7 ACID hyphens or symbols or symbol in Item 7
Item 8 Flight Rules N/A Editorial clarification Editorial/Clarification
N/A Note added referring to STS Date of Flight Requirements
Item 8 Type of flight
in Item 18
Equipment Equipment and Capabilities Field 10 format
Item 10 Title(editorial)
Equipment What size limit will we use What size limit will we use Field 10 format
Item 10 Title(editorial)
since none is specified? since none is specified?
Equipment Addition of words GPS Augmentation for
Item 10 Title(editorial) "serviceable" and "and Landing Capability
capabilities"
Only alphas Can include alphanumerics; Change code to allow Field 10 format
Item 10 Qualifiers many additional items added alphanumerics vice only
alphas
Radio, Nav, App Aid Radio, Nav, App Aid Editorial/Clarification
Item 10 Title(Editorial)
equipment equipment and capabilities
Radio, Nav, App Aid Standard Equipment of VHF Standard equipment of VHF Only indicate ADF when Standard Equipment
equipment and S RTF, ADF, VOR, and ILS RTF,VOR and ILS Code "F" is used definition
capabilities
The equipment carried is to Specify in Item 18 the other Ensure DAT/ is accepted Meaning of "other"
Radio, Nav, App Aid be specified in Item equipment carried or other into Item 18 equipment
equipment and Z 18,preceded by COM/ and/or capabilities preceded by
capabilities NAV/ as appropriate COM/ NAV/ and/or DAT, as
appropriate
Radio, Nav, App Aid Not allocated GBAS landing system Ensure A is accepted GPS Augmentation for
equipment and A Landing Capability
capabilities
Radio, Nav, App Aid Not allocated LPV (APV with SBAS) Ensure B is accepted GPS Augmentation for
equipment and B Landing Capability
capabilities
Detailed Changes 14 of 29
Para/Item Ref Topic PRESENT NEW Automation Change Change Reference
Radio, Nav, App Aid Not allocated This character has been Ensure E is removed and will Field 10 format
equipment and E removed reject if used.
capabilities
Radio, Nav, App Aid Not allocated FMC WPR ACARS Ensure E1 is accepted ACARS capability
equipment and E1
capabilities
Radio, Nav, App Aid Not allocated D-FIS ACARS Ensure E2 is accepted ACARS capability
equipment and E2
capabilities
Radio, Nav, App Aid Not allocated PDC ACARS Ensure E3 is accepted ACARS capability
equipment and E3
capabilities
Radio, Nav, App Aid Data Link This character has been Ensure J is removed and will Field 10 format
equipment and J removed reject if used.
capabilities
Radio, Nav, App Aid Not allocated CPDLC ATN VDL Mode 2 Ensure J1 is accepted CPDLC capability
equipment and J1
capabilities
Radio, Nav, App Aid Not allocated CPDLC ATN FANS 1/A Ensure J2 is accepted CPDLC capability
equipment and J2 HFDL
capabilities
Radio, Nav, App Aid Not allocated CPDLC ATN FANS 1/A VDL Ensure J3 is accepted CPDLC capability
equipment and J3 Mode A
capabilities
Radio, Nav, App Aid Not allocated CPDLC FANS 1/A VDL Ensure J4 is accepted CPDLC capability
equipment and J4 Mode 2
capabilities
Radio, Nav, App Aid Not allocated CPDLC FANS 1/A Ensure J5 is accepted CPDLC capability
equipment and J5 SATCOM(INMARSAT)
capabilities
Radio, Nav, App Aid Not allocated CPDLC FANS 1/A Ensure J6 is accepted CPDLC capability
equipment and J6 SATCOM(MTSAT)
capabilities
Radio, Nav, App Aid Not allocated CPDLC FANS 1/A Ensure J7 is accepted CPDLC capability
equipment and J7 SATCOM(Iridium)
capabilities
Radio, Nav, App Aid Omega This character has been Ensure M is removed and will Field 10 format
equipment and M removed reject from system if used.
capabilities
Radio, Nav, App Aid Not allocated ATC RTF Ensure M1 is accepted Satellite RTF
equipment and M1 SATCOM(INMARSAT)
capabilities
Detailed Changes 15 of 29
Para/Item Ref Topic PRESENT NEW Automation Change Change Reference
Radio, Nav, App Aid Not allocated ATC RTF (MTSAT) Ensure M2 is accepted Satellite RTF
equipment and M2
capabilities
Radio, Nav, App Aid Not allocated ATC RTF (Iridium) Ensure M3 is accepted Satellite RTF
equipment and M3
capabilities
Radio, Nav, App Aid Not allocated This character has been Field 10 format
equipment and P removed
capabilities
Radio, Nav, App Aid Not allocated Reserved for RCP Ensure P1 thru P9 are Required Comm.
equipment and P1-P9 accepted Performance
capabilities
Radio, Nav, App Aid Not allocated This character has been Field 10 format
equipment and Q removed
capabilities
Radio, Nav, App Aid RNP type certification PBN approved(IF R is used Performance Based
equipment and R then specify in Item 18 PBN/) Navigation capability (PBN/)
capabilities
Radio, Nav, App Aid When prescribed by ATS RVSM approved Editorial/Clarification
equipment and W
capabilities
Radio, Nav, App Aid When prescribed by ATS MNPS approved Editorial/Clarification
equipment and X
capabilities
Radio, Nav, App Aid When prescribed by ATS VHF with 8.33 kHz channel VHF/8.33 kHz
equipment and Y spacing capability
capabilities
Radio, Nav, App Aid Other equipment carried Other equipment carried or Editorial/Clarification
equipment and Z other capabilities
capabilities
Surveillance Surveillance and capabilities Editorial/Clarification
Surveillance Title
Surveillance and 1 or 2 characters Maximum of 20 characters Ensure category will allow 20 Field 10 format
Number of characters
capabilities characters
limited list of alphas Alphanumerics, adding Field 10 format
Surveillance and categories for SSR Modes A
Alphas
capabilities and C, SSR Mode S, ADS-B,
ADS-C
Surveillance and SSR equipment SSR Modes A and C Editorial/Clarification
Rename of section
capabilities
Surveillance and Not allocated SSR Mode S Editorial/Clarification
Addition of section
capabilities
Detailed Changes 16 of 29
Para/Item Ref Topic PRESENT NEW Automation Change Change Reference
Nil No surveillance equipment Editorial/Clarification
Surveillance and for the route to be flown is
N
capabilities carried or the equipment is
unserviceable
Transponder Mode S without Transponder Mode S with Editorial/Clarification
Surveillance and both aircraft identification and neither aircraft identification
X
capabilities pressure altitude nor pressure-altitude
transmission capability
Not allocated Transponder Mode S Ensure E is accepted TBD
including aircraft
Surveillance and
E identification, pressure- Why is extended squitter
capabilities
altitude and extended ADS-B listed here?
squitter(ADS-B)capability
Not allocated Transponder Mode S Ensure H is accepted Enhanced Mode-S
including aircraft Surveillance Capability
Surveillance and
H identification, pressure-
capabilities
altitude and enhanced
surveillance capability
Transponder Mode S Transponder Mode S Editorial/Clarification
including aircraft including aircraft
Surveillance and
I (editorial) identification transmission, identification, but no pressure-
capabilities
but no pressure altitude altitude capability
transmission
Not allocated Transponder Mode S, Ensure L is accepted Enhanced Mode-S
including aircraft Surveillance Capability
identification, pressure-
Surveillance and
L altitude, extended squitter Why is extended squitter
capabilities
capability(ADS-B)and ADS-B listed here?
enhanced surveillance
capability
Surveillance and ADS equipment This category has been Field 10 format
Deleted category
capabilities removed
Surveillance and ADS capability This character has been Ensure D is removed and will Field 10 format
D
capabilities removed reject if filed
Surveillance and Not allocated ADS-B Editorial/Clarification
Addition of category
capabilities
Not allocated ADS-B with dedicated 1090 Ensure B1 is accepted ADS-B capability
Surveillance and
B1 MHz ADS-B "out" capability
capabilities
Not allocated ADS-B with dedicated 1090 Ensure B2 is accepted ADS-B capability
Surveillance and
B2 MHz ADS-B "out" and "in"
capabilities
capability
Detailed Changes 17 of 29
Para/Item Ref Topic PRESENT NEW Automation Change Change Reference
Surveillance and Not allocated ADS-B "out" capability using Ensure U1 is accepted ADS-B capability
U1
capabilities UAT
Surveillance and Not allocated ADS-B out and in capability Ensure U2 is accepted ADS-B capability
U2
capabilities using UAT
Surveillance and Not allocated ADS-B "out" capability using Ensure V1 is accepted ADS-B capability
V1
capabilities VDL mode 4
Not allocated ADS-B "out" and "in" Ensure V2 is accepted ADS-B capability
Surveillance and
V2 capability using VDL mode 4
capabilities
Surveillance and Not allocated ADS-C ADS-C capability
Addition of category
capabilities
Surveillance and Not allocated ADS-C with FANS 1/A Ensure D1 is accepted ADS-C capability
D1
capabilities capabilities
Surveillance and Not allocated ADS-C with ATN capabilities Ensure G1 is accepted ADS-C capability
G1
capabilities
N/A Note additional surveillance Ensure SUR/ is accepted in Required Comm.
Surveillance and application should be listed in Item 18 Performance
New indicator
capabilities Item 18 after SUR/
Insert the ICAO four letter Insert the ICAO four letter Ensure departure aerodrome DEP, DEST, and Alternate
Departure location of the departure location of the departure accepted are from DOC7910 format
Item 13
Aerodrome (Editorial) aerodrome aerodrome as specified in
Doc7910
If no location indicator then If no location indicator then Ensure departure aerodrome DEP, DEST, and Alternate
insert ZZZZ and specify in insert ZZZZ and specify in are accepted with this format
item 18 the name of the Item 18 the name and procedure
aerodrome preceded by location of the aerodrome
DEP/ preceded by DEP/ or the
Departure
Item 13 first point of the route or
Aerodrome
the marker radio beacon
preceded by DEP/ if the
aircraft has taken off from
the aerodrome
Route-Bearing and Bearing and distance from a Bearing and distance from a FRD w/5 letter base fix
Item 15 ( 2 )
distance navigation aid significant point
Insert where change of route, Is planned to commence Editorial/Clarification
Route-Change of
speed, flight level and or
Item 15 (3) speed or
flight rules is planned
level(Editorial)
Detailed Changes 18 of 29
Para/Item Ref Topic PRESENT NEW Automation Change Change Reference
Destination Aerodrome, Total Destination Aerodrome, Total Editorial/Clarification
Elapsed Time, Alternate Elapsed Time, Destination
Item 16 Title(Editorial)
Aerodrome(s) Alternate Aerodrome(s)
Destination Insert the four letter location as specified in DOC7910 DEP, DEST, and Alternate
Item 16 Aerodrome and Total indicator of the destination Location Indicators format
elapsed time aerodrome
If no location indicator then If no location indicator then DEP, DEST, and Alternate
insert ZZZZ and without a insert ZZZZ and specify in format
space the total elapsed time Item 18 the name and
Destination
and Specify in Item 18 the location of the aerodrome
Item 16 Aerodrome and Total
name of the aerodrome, preceded by DEST/ then
elapsed time
preceded by DEST/ without a space insert the
total elapsed time.
Insert the ICAO four letter as specified in DOC7910 Ensure that destination Editorial/Clarification
location indicator(s) of not Location Indicators alternate aerodromes are
Destination alternate
Item 16 than two alternate from Doc7910 Location
aerodrome(s)
aerodromes, separated by a indicators
space
If no location indicator insert If no location indicator insert DEP, DEST, and Alternate
ZZZZ and specify in Item 18 ZZZZ and specify in Item 18 format
name of the aerodrome name and location of the
Destination alternate
Item 16 preceded by ALTN/ destination alternate
aerodrome(s)
aerodrome preceded by
ALTN/
N/A Add clarification using Required Field 18 format
Item 18 Other Information
hyphens & obliques
Item 18 Other Information preferred sequence in the sequence shown Required Field 18 format
free text Specific entries: ALTRV, Ensure when using item 18 Reason for Special Handling
ATFMX, FFR, FLTCK, STS/ these are the only (STS/) Requirements
HAZMAT, HEAD, HOSP, codes that can be used
HUM, MARSA, MEDEVAC, Ensure when using item 18
NONRVSM, SAR, STATE; STS/ these are the only
Item 18 STS/
other reasons for special codes that can be used
handling by ATS shall be
denoted with the designator
RMK/
Not allocated for a flight operated in Ensure ALTRV is accepted in Reason for Special Handling
Item 18 ALTRV accordance with an altitude Item 18 after STS/ (STS/) Requirements
reservation
Detailed Changes 19 of 29
Para/Item Ref Topic PRESENT NEW Automation Change Change Reference
Not allocated for a flight approved for Ensure ATFMX is accepted Reason for Special Handling
exemption from ATFM in Item 18 after STS/ (STS/) Requirements
Item 18 ATFMX
measures by the appropriate
ATS authority
Not allocated fire-fighting Ensure FFR is accepted in Reason for Special Handling
Item 18 FFR Item 18 after STS/n Item 18 (STS/) Requirements
after STS/
Not allocated flight check for calibration of Ensure FLTCK is accepted in Reason for Special Handling
Item 18 FLTCK navaids Item 18 after STS/ (STS/) Requirements
Not allocated for a flight carrying Ensure Hazmat is accepted Reason for Special Handling
Item 18 HAZMAT hazardous material in Item 18 after STS/ (STS/) Requirements
Not allocated a flight with Head of State Ensure HEAD is accepted in Reason for Special Handling
Item 18 HEAD status Item 18 after STS/ (STS/) Requirements
Not allocated for a medical flight declared Ensure HOSP is accepted in Reason for Special Handling
Item 18 HOSP by medical authorities Item 18 after STS/ (STS/) Requirements
Not allocated for a flight operating on a Ensure HUM is accepted in Reason for Special Handling
Item 18 HUM humanitarian mission Item 18 after STS/ (STS/) Requirements
Not allocated for a flight for which a military Ensure MARSA is accepted Reason for Special Handling
entity assumes responsibility in Item 18 after STS/ (STS/) Requirements
Item 18 MARSA for separation of military
aircraft
Not allocated for a life critical medical Ensure MEDEVAC is Reason for Special Handling
Item 18 MEDEVAC emergency evacuation accepted in Item 18 after (STS/) Requirements
STS/
Not allocated for a non-RVSM capable Ensure NONRVSM is Reason for Special Handling
Item 18 NONRVSM flight intending to operate in accepted in Item 18 after (STS/) Requirements
RVSM airspace STS/
Not allocated for a flight engaged in a Ensure SAR is accepted in Reason for Special Handling
Item 18 SAR search and rescue mission Item 18 after STS/ (STS/) Requirements
Not allocated for a flight engaged in Ensure STATE is accepted in Reason for Special Handling
Item 18 STATE military, customs, or police Item 18 after STS/ (STS/) Requirements
services
Detailed Changes 20 of 29
Para/Item Ref Topic PRESENT NEW Automation Change Change Reference
Not allocated Indication of RNAV and/ or Ensure PBN/ is accepted in Performance Based
RNP capabilities-total of Item 18 Navigation capability (PBN/)
Item 18 PBN/
eight entries not more than
16 characters
Not allocated RNAV10(RNP 10) Ensure A1 is accepted in Performance Based
Item 18 RNAV
A1 Item 18 after PBN/ Navigation capability (PBN/)
specifications
Not allocated RNAV 5 all permitted Ensure B1 is accepted in Performance Based
Item 18 RNAV
B1 sensors Item 18 after PBN/ Navigation capability (PBN/)
specifications
Not allocated RNAV 5 GNSS Ensure B2 is accepted in Performance Based
Item 18 RNAV
B2 Item 18 after PBN/ Navigation capability (PBN/)
specifications
Not allocated RNAV 5 DME/DME Ensure B3 is accepted in Performance Based
Item 18 RNAV
B3 Item 18 after PBN/ Navigation capability (PBN/)
specifications
Not allocated RNAV 5 VOR/DME Ensure B4 is accepted in Performance Based
Item 18 RNAV
B4 Item 18 after PBN/ Navigation capability (PBN/)
specifications
Not allocated RNAV 5 INS or IRS Ensure B5 is accepted in Performance Based
Item 18 RNAV
B5 Item 18 after PBN/ Navigation capability (PBN/)
specifications
Not allocated RNAV 5 LORANC Ensure B6 is accepted in Performance Based
Item 18 RNAV
B6 Item 18 after PBN/ Navigation capability (PBN/)
specifications
Not allocated RNAV 2 all permitted Ensure C1 is accepted in Performance Based
Item 18 RNAV
C1 sensors Item 18 after PBN/ Navigation capability (PBN/)
specifications
Not allocated RNAV 2 GNSS Ensure C2 is accepted in Performance Based
Item 18 RNAV
C2 Item 18 after PBN/ Navigation capability (PBN/)
specifications
Not allocated RNAV 2 DME/DME Ensure C3 is accepted in Performance Based
Item 18 RNAV
C3 Item 18 after PBN/ Navigation capability (PBN/)
specifications
Not allocated RNAV 2 DME/DME/IRU Ensure C4 is accepted in Performance Based
Item 18 RNAV
C4 Item 18 after PBN/ Navigation capability (PBN/)
specifications
Not allocated RNAV 1 all permitted Ensure D1 is accepted in Performance Based
Item 18 RNAV
D1 sensors Item 18 after PBN/ Navigation capability (PBN/)
specifications
Detailed Changes 21 of 29
Para/Item Ref Topic PRESENT NEW Automation Change Change Reference
Not allocated RNAV 1 GNSS Ensure D2 is accepted in Performance Based
Item 18 RNAV
D2 Item 18 after PBN/ Navigation capability (PBN/)
specifications
Not allocated RNAV 1 DME/DME Ensure D3 is accepted in Performance Based
Item 18 RNAV
D3 Item 18 after PBN/ Navigation capability (PBN/)
specifications
Not allocated RNAV 1 DME/DME/IRU Ensure D4 is accepted in Performance Based
Item 18 RNAV
D4 Item 18 after PBN/ Navigation capability (PBN/)
specifications
Not allocated RNP 4 Ensure L1 is accepted in Performance Based
Item 18 RNP
L1 Item 18 after PBN/ Navigation capability (PBN/)
specifications
Not allocated Basic RNP 1 all permitted Ensure O1 is accepted in Performance Based
Item 18 RNP
O1 sensors Item 18 after PBN/ Navigation capability (PBN/)
specifications
Not allocated Basic RNP 1 GNSS Ensure O2 is accepted in Performance Based
Item 18 RNP
O2 Item 18 after PBN/ Navigation capability (PBN/)
specifications
Not allocated Basic RNP 1 DME/DME Ensure O3 is accepted Performance Based
Item 18 RNP
O3 Navigation capability (PBN/)
specifications
Not allocated Basic RNP 1 DME/DME/IRU Ensure O4 is accepted in Performance Based
Item 18 RNP
O4 Item 18 after PBN/ Navigation capability (PBN/)
specifications
Not allocated RNP APCH Ensure S1 is accepted in Performance Based
Item 18 RNP
S1 Item 18 after PBN/ Navigation capability (PBN/)
specifications
Not allocated RNP APCH with BARO- Ensure S2 is accepted in Performance Based
Item 18 RNP
S2 VNAV Item 18 after PBN/ Navigation capability (PBN/)
specifications
Not allocated RNP AR APCH with Ensure T1 is accepted in Performance Based
Item 18 RNP
T1 RF(special authorization Item 18 after PBN/ Navigation capability (PBN/)
specifications
required)
Not allocated RNP AR APCH without Ensure T2 is accepted in Performance Based
Item 18 RNP
T2 RF(special authorization Item 18 after PBN/ Navigation capability (PBN/)
specifications
required)
Detailed Changes 22 of 29
Para/Item Ref Topic PRESENT NEW Automation Change Change Reference
Significant Data related to Significant Data related to Editorial/Clarification
navigation equipment as navigation equipment, other
required by the appropriate than specified in PBN/,as
ATS authority required by the appropriate
ATS authority. Indicate
Item 18 NAV/
GNSS augmentation under
this indicator, with a space
between two or more
methods of augmentation
Significant Data related to Indicate communications Editorial/Clarification
communication equipment as applications or capabilities
Item 18 COM/
required by the appropriate not specified in Item 10a
ATS authority
Significant data related to Indicate data applications or Editorial/Clarification
data link capability, using one capabilities not specified in
or more of the letters S, H, V Item 10a
and M, e.g. DAT/S for
Item 18 DAT/ satellite data link, DAT/H for
HF data link, DAT/V for VHF
data link, DAT/M for SSR
Mode S data link.
Not allocated Indicate surveillance Additional Surveillance
Item 18 SUR/ applications or capabilities Capabilities (SUR/)
not specified in Item 10b
Name of departure Name and location of DEP, DEST, and Alternate
areodrome, if ZZZZ is departure aerodrome, if format
inserted in Item 13,or the ZZZZ is inserted in Item 13
ICAO four-letter indicator of or the ATS unit from which
Item 18 DEP/ the location of the ATS unit supplementary flight plan
from which supplementary data can be obtained if AFIL
flight plan data can be is inserted in Item 13
obtained, if AFIL is inserted
in Item 13
Detailed Changes 23 of 29
Para/Item Ref Topic PRESENT NEW Automation Change Change Reference
Name of departure With 4 figures describing Ensure Latitude and DEP, DEST, and Alternate
areodrome, if ZZZZ is latitude in degrees and tens Longitude are accepted after format
inserted in Item 13,or the and units of minutes followed DEP/ in Item 18
ICAO four-letter indicator of by ―N‖
the location of the ATS unit (North) or ―S‖ (South),
DEP/ aerodromes not
from which supplementary followed by 5 figures
Item 18 listed in the relevant
flight plan data can be describing longitude in
AIP
obtained, if AFIL is inserted degrees and tens and units
in Item 13 of minutes, followed by ―E‖
(East) or ―W‖ (West).
4620N07805W (11
characters).
Name of departure OR, Bearing and distance Ensure bearing and distance DEP, DEST, and Alternate
areodrome, if ZZZZ is from the nearest are accepted after DEP/ in format
inserted in Item 13,or the significant point, as follows: Item 18
ICAO four-letter indicator of The identification of the
the location of the ATS unit significant point followed by
from which supplementary the bearing 3 figures
flight plan data can be degrees magnetic, followed
obtained, if AFIL is inserted by the distance from the
in Item 13 point 3 figures nautical
miles. In areas of high
DEP/ aerodromes not latitude where it is
Item 18 listed in the relevant determined by the
AIP 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
expressed as DUB180040.
Detailed Changes 24 of 29
Para/Item Ref Topic PRESENT NEW Automation Change Change Reference
Name of departure OR, The first point of the DEP, DEST, and Alternate
areodrome, if ZZZZ is route (name or LAT/LONG) format
inserted in Item 13,or the or the marker radio beacon,
DEP/ aerodromes not ICAO four-letter indicator of if the aircraft has not taken
Item 18 listed in the relevant the location of the ATS unit off from an aerodrome
AIP from which supplementary
flight plan data can be
obtained, if AFIL is inserted
in Item 13
Name of destination DEST/ Name and location of Ensure Lattiude, Longigtude, DEP, DEST, and Alternate
aerodrome, if ZZZZ is destination aerodrome, if or bearing and distance can format
inserted in Item 16.. ZZZZ is inserted in Item 16. be entered after DEST/ in
For aerodromes not listed in Item 18.
the relevant Aeronautical
Information Publication,
Item 18 DEST/
indicate location in
LAT/LONG or bearing and
distance from the nearest
significant point, as
described under DEP/ above
Not allocated Insert Date of flight departure Ensure DOF is accepted in Date of Flight Requirements
in a six figure Item 18 and ATC flight plans
format(YYMMDD,YY=YEAR can be filed 120 HOURS in
Item 18 DOF in Item 18 MM=MONTH and advance
DD=DAY)When departure is
more than 24 hours but less
than 120 hours.
The registration markings of The nationality or common Editorial/Clarification
the aircraft, if different from mark and registration mark
Item 18 REG/ the aircraft identification in of the aircraft, if different
Item 7. from the aircraft identification
in Item 7.
Accumulated elapsed times Accumulated elapsed times Editorial/Clarification
Item 18 EET/ (Editorial) to such points or FIR from take-off to such points
boundaries or FIR boundaries
SELCAL code, if so SELCAL code, for aircraft so Editorial/Clarification
Item 18 SEL/ (Editorial) prescribed by the appropriate equipped
ATS authority
Detailed Changes 25 of 29
Para/Item Ref Topic PRESENT NEW Automation Change Change Reference
Type(s) of aircraft, preceded Type(s)of aircraft preceded if Content of Field 18 (TYP/)
if necessary by number(s) of necessary without a space by Type of Aircraft
aircraft if ZZZZ is inserted in number(s) of aircraft,
Item 9 preceded if necessary
without a space by
Item 18 TYP/ (Editorial)
number(s) of aircraft and
separated by one space, if
ZZZZ is inserted in Item
9.Example: –TYP/2F15 5F5
3B2
Not allocated Enroute delay or holding, Ensure DLE/ is accepted into Delay at a fix (DLE/)
insert the significant point(s) Item 18 Capability
on the route where a delay is
planned to occur, followed by
Item 18 DLE/ the length of delay using four
figure time in hours and
minutes (hhmm).Example:
–DLE/MDG0030
Name of the operator, if not ICAO designator or name of Editorial/Clarification
obvious from the aircraft the aircraft operating agency,
Item 18 OPR/ identification in Item 7 if different from the aircraft
identification in item 7.
Not allocated The originator’s 8 letter Ensure ORGN/ is accepted Content of Field 18 (TYP/)
AFTN address or other into Item 18. Type of Aircraft
appropriate contact details, in
cases where the originator of
the flight plan may not be
readily identified, as required
by the appropriate ATS
Item 18 ORGN/
authority. Note.— In some
areas, flight plan reception
centers may insert the
ORGN/ identifier and
originator’s AFTN address
automatically.
Detailed Changes 26 of 29
Para/Item Ref Topic PRESENT NEW Automation Change Change Reference
Aircraft performance data, if Aircraft performance data, A/C Performance (PER/)
so prescribed by the indicated by a single letter as
appropriate ATS authority specified in the Procedures
for Air
Navigation Services —
Item 18 PER/
Aircraft Operations (PANS-
OPS, Doc 8168), Volume I —
Flight Procedures, if so
prescribed by the appropriate
ATS authority
Name of destination Name of destination alternate Ensure changes to ALTN/ DEP, DEST, and Alternate
alternate, if ZZZZ is inserted aerodrome(s), if ZZZZ is are accepted into Item 18 format
in Item 16. inserted in Item 16. For
aerodromes not
listed in the relevant
Aeronautical Information
Item 18 ALTN/
Publication, indicate location
in LAT/LONG or bearing and
distance from the nearest
significant point, as
described in DEP/ earlier.
Name of en-route alternate ICAO four letter indicator(s) DEP, DEST, and Alternate
aerodrome(s). for en-route alternate(s), as format
specified in Doc 7910,
Location
Indicators, or name(s) of en-
route alternate aerodrome(s),
if no indicator is allocated.
For
Item 18 RALT/
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 in DEP/ earlier.
Detailed Changes 27 of 29
Para/Item Ref Topic PRESENT NEW Automation Change Change Reference
Not allocated ICAO four letter indicator(s) Ensure TALT/ is accepted in Alternate Take-Off Airport
for take-off alternate, as Item 18 (TALT/)
specified in Doc 7910,
Location Indicators, or name
of take-off alternate
aerodrome, if no indicator is
allocated. For aerodromes
Item 18 TALT/ not listed in the relevant
Aeronautical Information
Publication, indicate location
in LAT/LONG or bearing and
distance from the nearest
significant point, as
described in DEP/ earlier.
DLA CHG CNL ARR RQS DLA CHG CNL ARR RQS Ensure (EOBT) is accepted EOBT in 2nd order msgs
p24 Message format currently do not require now require the estimated off in DLA CHG CNL ARR RQS
EOBT blocks time (EOBT)
DLA CHG CNL ARR RQS Now require Item 18 info; Ensure Item 18 is accepted DOF in 2nd order msgs
p25 Message format end after Item 16 DOF/ only in DLA CHG CNL ARR RQS
N/A CNL,DLA,DEP,RQP,RQS DOF in 2nd order msgs
p36 Message format Include a -0 for Field 18 if
there is no DOF/
Detailed Changes 28 of 29
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
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.
Related docs
