ENR 1.10  Flight Planning

1.10.1   Procedures for the submission of flight plan

General

Lisboa and Santa Maria FIRs are part of the EUROCONTROL IFPS Zone and comply with the procedures and rules of the Network Manager (NM).
As published in the Network Operations Handbook/IFPS Users Manual, Flight Plan and associated messages related to flight under IFR/General Air Traffic (GAT), mixed IFR/VFR or GAT/Operational Air Traffic (OAT) are required to be submitted only to the IFPS.
The submission of VFR Flight Plan shall be made to an appropriate NAV Portugal service, FPL and Briefing or ARO facility (see LPPT, LPPR, LPFR, LPMA or LPPD AD 2.3), which will forward the message to the ATS Units concerned and to other addresses supplied with the Flight Plan.
Messages sent by email to LPPR, LPPT, LPFR, LPMA or LPPD ARO units shall only be considered submitted after the reception of their validation by email acknowledgement.
The IFPS will further process, ACK and disseminate the Flight Plan data to the ATS Units concerned within the IFPS Zone and to other addresses supplied with the Flight Plan.
Further details concerning Network Management/IFPS may be obtained, under Network Management, via the EUROCONTROL website:

Time and place of submission

Special Flight Planning Requirements for Santa Maria FIR

Operators shall comply with the instructions contained in the ICAO NAT Regional Supplementary Procedures (Doc. 7030 - NAT) and in the North Atlantic Operations and Airspace Manual (NAT Doc. 007), except if otherwise specified herein.

The table of cruising levels published on Appendix 3 of ICAO Annex 2, as well as those published on AIP Portugal, ENR 1.7.5 (Altimeter Setting Procedures) are not applied on Santa Maria Oceanic FIR.
From Santa Maria FIR entry and along the route within the FIR, all levels may be planned 24/7, using 1000ft increments, whatever the direction of the flight. Caution is always recommended regarding the flight level rules applied in the downstream FIRs because flights will always have to exit Santa Maria FIR at the level approved by the following ATC Unit.

Step climbs, cruise climbs, altitude block and route change requests are accepted as part of Santa Maria OAC normal operations. The ATC procedures, upon a request by the pilot, are to always try to provide the requested level and route. The controller decision to authorize a level and/or route change is always dependent of the non-existence of conflicting traffic and the approval from the downstream ATC Unit.

To improve the safety and efficiency in service provision, from 45N013W to 2218N04000W, along Santa Maria’s East and South FIR boundaries, all operators shall flight plan to enter and leave the LPPO FIR (SFC - UNL) through the designated FIR boundary points, as published in AIP Portugal ENR 6.01-9 - En-route Chart - Santa Maria Oceanic FIR (LPPO) and ENR 4.4 - Name Code Designators for Significant Points.

With the exception of the recommendation to make use of the existing designated boundary waypoints, within Santa Maria FIR, –non-FANS 1/A equipped flights should flight plan their User-Preferred Route (UPR), with the following restrictions:

  1. Flights which generally route in an eastbound or westbound direction should normally be flight planned so that specified ten degrees of longitude (020W, 030W, 040W.) are crossed at whole or half degrees of latitude; and
  2. Generally northbound or southbound flights should normally be flight planned so that specified parallels of latitude spaced at five degree intervals (20N, 30N, 35N) are crossed at whole degrees of longitude.

Unrestricted User-Preferred Routes (UPR) are available in Santa Maria FIR airspace above FL285 for FANS-1/A equipped aircraft, taking into account that:

  1. For the flights which generally route in an eastbound or westbound direction it is not mandatory to plan via specified ten degrees of longitude (020W, 030W, 040W);
  2. All generally northbound or southbound flights are not required to be planned at specified parallels of latitude spaced at five degree intervals (20N, 25N, 30N, 35N or 40N);
  3. Flights entering/exiting Santa Maria UPR via Madrid, Lisboa, Canarias, Sal or Piarco shall use a 5LNC waypoint defined at the FIR boundary, as specified in ENR 4.4 of AIP;
  4. Routes north of 45N shall comply with Gander or Shanwick published rules. When entering/exiting Santa Maria FIR from/to Gander or Shanwick FIR, there will be no need to specify the entry/exit point at 45N. However for coordination purposes, routes which are planned from a position in Santa Maria FIR directly to either Gander or Shanwick FIR are required to insert a position, at any latitude along 030W or 020W whichever is closest to the FIR boundary (this does not apply to flights routing on the OTS, on T13 or that do not cross those longitudes inside Santa Maria airspace);
  5. Routes west of 040W shall comply with New York’s published rules and the entry/exit point between New York East FIR and Santa Maria FIR shall be planned using any whole or half degree of latitude at 040W;
  6. Inbound traffic to Azores Islands should plan their user-preferred routes from Santa Maria UPR airspace entry point (or if entering Santa Maria from Shanwick or Gander, from the last point inside those FIRs) direct to the STAR initial waypoint or a specific waypoint linked to the destination aerodrome.
  7. Traffic departing from Azores Islands should plan their User-Preferred Routes starting at the appropriate SID final waypoint or a specific waypoint linked to the departure aerodrome, direct to the next appropriate waypoint defined according to rules set above.

Within Santa Maria Oceanic FIR airspace and outside surveillance area (SSR, MLAT or ADS-B, in ENR 1.6.14), to define a way point in field 15 of the flight plan, operators shall not make use of Bearing And Distance From a Navigation Aid nor Bearing and Distance From a Reference Point.

For flights conducted entirely along one of the OTS (Organized Track System), this portion of route shall be defined in field 15 of the Flight Plan by inserting the first track way point, then the abbreviation ‘NAT’ followed by the code letter assigned to the track and finally the last way point of the track.
Flights wishing to join or leave an organized track at some intermediate point are considered to be random route aircraft and full route details must be specified in the flight plan. The track letter must not be used to abbreviate any portion of the route in these circumstances.
For turbo-jet aircraft operating within Santa Maria FIR, the Mach Number planned to be used shall be specified in the Item 15 of the Flight Plan.

All RNAV 10 (RNP 10) approved aircraft shall insert the letter R in Item 10a of the flight plan and the A1 descriptor in Item 18 of the flight plan, following the PBN/ indicator. All RNP 4 approved aircraft shall insert the letter R in Item 10a of the flight plan and the L1 descriptor in Item 18 of the flight plan, following the PBN/ indicator.

All NAT HLA MNPS approved aircraft shall insert the letter X in Item 10a of the flight plan. All RVSM approved aircraft, regardless of the requested flight level, shall insert the letter W in Item 10a of the flight plan.

All FANS 1/A approved aircraft intending to use data link services shall insert in Item 10a of the flight plan the appropriate descriptor or descriptors (J2, J3, J4, J5, J7) to indicate the CPDLC capabilities and the descriptor D1 on item 10b to indicate ADS-C capability. 
All ADS-B approved aircraft shall insert the appropriate descriptor or descriptors in Item 10b of the flight plan.

All aircraft shall insert the aircraft registration in Item 18 of the flight plan, following the REG/ indicator.

All aircraft shall insert the aircraft address (expressed in the form of an alphanumerical code of six hexadecimal characters) in Item 18 of the flight plan, following the CODE/ indicator.

All SATVOICE equipped aircraft and capable of using this communication media shall insert the appropriate descriptor or descriptors in Item 10b of the flight plan.

Instructions for insertion of ATS data

The EUR RVSM flight planning requirements for the completion of the ICAO Flight Plan Form are contained in the ICAO EUR Regional Supplementary Procedures (Doc. 7030 / 4 - EUR).

Furthermore, the following requirement is in addition to the flight planning requirements contained in the ICAO EUR Regional Supplementary Procedures (Doc. 7030 / 4 - EUR):
“in addition to military operations, operators of customs or police aircraft shall insert the letter ‘M’ in item 8 of the ICAO Flight Plan Form “

Complete Item 7 to 18 and Item 19 as indicated hereunder.

NOTE: Item numbers on the form are not consecutive, as they correspond Field Type numbers in ATS messages.

ITEM 7: AIRCRAFT IDENTIFICATION (MAXIMUM 7 CHARACTERS)

INSERT one of the following aircraft identifications, not exceeding 7 characters:

  1. the registration marking of the aircraft (e.g. EIAKO, 4XBCD, 2567GA), when:
    1. in radiotelephony the call sign to be used by the aircraft will consist of this identification alone (e.g. OOTEK), or preceded by the ICAO telephony designator for the aircraft operating agency (e.g. SABENA OOTEK);
    2. the aircraft is not equipped with radio.

OR

  1. the ICAO designator for the aircraft operating agency followed by the flight identification (e.g. KLM511, NGA213, JTR25) when in radiotelephony the call sign to be used by the aircraft will consist of the ICAO telephony designator for the operating agency followed by the flight identification (e.g. KLM511, NIGERIA213, JESTER25).

NOTE: Provisions for the use of radiotelephony call signs are contained in Annex 10, Volume II, Chapter 5. ICAO designators and telephony designators for aircraft operating agencies are contained in DOC 8585 - Designators for Aircraft Operating Agencies, Aeronautical Authorities and Services.

ITEM 8: FLIGHT RULES AND TYPE OF FLIGHT (ONE OR TWO CHARACTERS)

FLIGHT RULES

INSERT one of the following letters to denote the category of flight rules with which the pilot intends to comply:

TYPE OF FLIGHT

INSERT one of the following letters to denote the type of flight when so required by the appropriate ATS authority:

ITEM 9: NUMBER AND TYPE OF AIRCRAFT AND WAKE TURBULENCE CATEGORY

NUMBER OF AIRCRAFT (1 OR 2 CHARACTERS)

INSERT the number of aircraft, if more than one.

TYPE OF AIRCRAFT (2 TO 4 CHARACTERS)

INSERT the appropriate designator as specified in ICAO DOC 8643, Aircraft Type Designators,

OR if no such designator has been assigned, or in case of formation flights comprising more than one type,

INSERT ZZZZ, and SPECIFY in Item 18, the number(s) and type(s) of aircraft preceded by TYP/.

WAKE TURBULENCE CATEGORY (1 CHARACTER)

INSERT a slash followed by one of the following letters to indicate the wake turbulence category of the aircraft;

ITEM 10: EQUIPMENT

RADIO COMMUNICATION, NAVIGATION AND APPROACH AID EQUIPMENT AND CAPABILITIES (10a)

INSERT one letter as follows:

OR

AND/OR

INSERT one or more of the following letters to indicate the serviceable COM/NAV/Approach aid equipment and capabilities available:

AGBAS landing systemJ7CPDLC FANS 1/A SATCOM (Iridium)
BLPV (APV with SBAS)KMLS
CLORAN CLILS
DDMEM1ATC RTF SATCOM (INMARSAT)
E1FMC WPR ACARSM2ATC RTF (MTSAT)
E2D-FIS ACARSM3ATC RTF (Iridium)
E3PDC ACARSOVOR
FADFP1-P9Reserved for RCP
GGNSS (see Note 2)RPBN Approved (see Note 4)
HHF RTFTTACAN
IInertial NavigationUUHF RTF
J1CPDLC ATN VDL Mode 2 (see note 3)VVHF RTF
J2CPDLC FANS 1/A HFDLWRVSM Approved
J3CPDLC FANS 1/A VDL Mode AXNAT HLA MNPS Approved
J4CPDLC FANS 1/A VDL Mode 2YVHF with 8.33 kHz channel spacing capability
J5CPDLC FANS 1/A SATCOM (INMARSAT)ZOther equipment carried or other capabilities (see Note 5)
J6CPDLC FANS 1/A SATCOM (MTSAT)

Any alphanumeric characters not indicated above are reserved.

Note 1. If the letter S is used, Standard equipment is considered to be VHF, RTF, VOR and ILS, unless another combination is prescribed by the appropriate ATS authority.

Note 2. If the letter G is used, the types of external GNSS augmentation, if any, are specified in Item 18 following the indicator NAV/ and separated by a space.

Note 3. See RTCA/EUROCAE Interoperability Requirements Standard For ATN Baseline 1 (ATN B1 INTEROP Standard– DO-280B/ED-110B) for data link services air traffic control clearance and information/air traffic control communications management/air traffic control microphone check.

Note 4. If the letter R is used, the performance based navigation levels that can be met are specified in Item 18 following the indicator PBN/. Guidance material on the application of performance based navigation to a specific route segment, route or area is contained in the Performance-Based Navigation Manual (Doc 9613).

Note 5. If the letter Z is used, specify in Item 18 the other equipment carried or other capabilities, preceded by COM, NAV/ and/or DAT/, as appropriate. Exemptions for RNAV and 8.33 kHz are to be indicated by inserting the letter Z in Item 10a and then inserting the appropriate descriptors in the following indicators in Item 18 as detailed in the IFPS Users Manual and Portuguese AIP sections ENR 1.1.2 RNAV Operations and ENR 1.8.1 Exemptions For Mandatory Carriage of 8.33 KHz Channel Spacing Equipment in The VHF Radio COM Band:

  1. insert EXM833 following COM/;
  2. insert RNAVX or RNAVINOP as appropriate following NAV/;

Note 6. Information on navigation capability is provided to ATC for clearance and routing purposes.

SURVEILLANCE EQUIPMENT AND CAPABILITES (10b)

INSERT N if no surveillance equipment for the route to be flown is carried, or the equipment is unserviceable,

OR

INSERT one or more of the following descriptors, to a maximum of 20 characters, to describe the serviceable surveillance equipment and/or capabilities on board:

SSR EQUIPMENT

SSR Modes A and C

ATransponder-Mode A (4digits-4096 codes)
CTransponder-Mode A (4digits-4096 codes) and mode C

SSR Mode S

ETransponder - Mode S, including aircraft identification, pressure-altitude and extended squitter (ADS-B) capability
HTransponder - Mode S, including aircraft identification, pressure-altitude and enhanced surveillance capability
ITransponder - Mode S, including aircraft identification, but no pressure altitude capability
LTransponder - Mode S, including aircraft identification, pressure-altitude, extended squitter (ADS-B) and enhanced surveillance capability
PTransponder - Mode S, including pressure-altitude, but no aircraft identification capability
STransponder - Mode S, including both pressure-altitude and aircraft identification capability
XTransponder — Mode S with neither aircraft identification nor pressure-altitude capability

Note. Enhanced surveillance capability is the ability of the aircraft to down-link aircraft derived data via a Mode S transponder

ADS EQUIPMENT

ADS - B

B1ADS-B with dedicated 1090 MHz ADS-B “out” capability
B2ADS-B with dedicated 1090 MHz ADS-B “out” and “in” capability
U1ADS-B “out” capability using UAT
U2ADS-B “out” and “in” capability using UAT
V1ADS-B “out” capability using VDL Mode 4
V2ADS-B “out” and “in” capability using VDL Mode 4

ADS - C

D1ADS-C with FANS 1/A capabilities
G1ADS-C with ATN capabilities

Alphanumeric characters not indicated above are reserved.
Example: ADE3RV/HB2U2V2G1
Note. Additional surveillance application should be listed in Item 18 following the indicator SUR/.

ITEM 13: DEPARTURE AERODROME AND TIME (8 CHARACTERS)

INSERT the ICAO four-letter location indicator of the departure aerodrome as specified in Doc 7910, Location Indicators,

OR, the first point of the route or the marker radio beacon preceded by DEP/..., if the aircraft has not taken off from the aerodrome,

OR, if no location indicator has been assigned,

INSERT ZZZZ and SPECIFY, in Item 18, the name 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 not taken off from the aerodrome,

OR, if the flight plan is received from an aircraft in flight,

INSERT AFIL, and SPECIFY, in Item 18, the ICAO four-letter location indicator of the location of the ATS unit from which supplementary flight plan data can be obtained, preceded by DEP/

THEN, WITHOUT A SPACE

INSERT for a flight plan submitted before departure, the estimated off-block time, (EOBT)

OR, for a flight plan received from an aircraft in flight, the actual or estimated time over the first point of the route to which the flight plan applies.

NOTE: The term “Estimated off-block time” is defined as: the estimated time at which the aircraft will commence movement associated with departure.

ITEM 15: ROUTE

INSERT the first cruising speed as in (a) and the first cruising level as in (b), without a space between them.

THEN, following the arrow, INSERT the route description as in (c).

a) CRUISING SPEED (MAXIMUM 5 CHARACTERS)

INSERT the True Air Speed for the first or the whole cruising portion of the flight, in terms of: Kilometres per hour, expressed as K followed by 4 figures (e.g. K0830), or Knots, expressed as N followed by 4 figures (e.g. N0485), or Mach Number, when so prescribed by the appropriate ATS Authority, to the nearest hundredth of unit Mach, expressed as M followed by 3 figures e.g.M082).

b) CRUISING LEVEL (MAXIMUM 5 CHARACTERS)

INSERT the planned cruising level for the first or the whole portion of the route to be flown, in terms of:

c) ROUTE (INCLUDING CHANGES OF SPEED, LEVEL AND/OR FLIGHT RULES)

FLIGHTS ALONG DESIGNATED ATS ROUTES

INSERT if the departure aerodrome is located on, or connected to the ATS route, the designator of the first ATS route, or if the departure aerodrome is not on, or connected to the ATS route, the letters DCT followed by the point of joining the first ATS route, followed by the designator of the ATS route.

Within Lisboa Free Route Airspace see ENR 1.3.1.

THEN

INSERT each point at which either a change of speed or level, a change of ATS route, and/or a change of flight rules is planned,

NOTE: When a transition is planned between a lower and upper ATS route and the routes are oriented in the same direction, the point of transition need not to be inserted.

FOLLOWED IN EACH CASE

by the designator of the next  ATS route segment, even if the same as the previous one, or

by DCT, if the flight to the next point will be outside a designated route, unless both points are defined by geographical coordinates.

FLIGHTS OUTSIDE DESIGNATED ATS ROUTES

INSERT points normally not more than 30 minutes flying time or 370 KM (200 NM) apart, including each point at which a change of speed or level, a change of track, or a change of flight rules is planned, or

when required by the appropriate ATS authority(ies).

DEFINE the track of flights operating predominantly in an east-west direction between 70ºN and 70ºS by reference to significant points formed by the intersections of half or whole degrees of latitude with meridians spaced at intervals of 10 degrees of longitude. For flights operating in areas outside those latitudes the tracks shall be defined by significant points formed by intersection of parallels of latitude with meridians normally spaced at 20degrees of longitude. The distance between significant points shall, as far as possible, not exceed one hour’s flight time. Additional significant points shall be established as deemed necessary.

For flights operating predominantly in a north-south direction, define tracks by reference to significant points formed by the intersection of whole degrees of longitude with specified parallels of latitude which are spaced at 5 degrees.

INSERT DCT between successive points unless both points are defined by geographical co-ordinates or by bearing and distance.

USE ONLY the conventions in (1) to (5) below and SEPARATE each sub-item by a space.

1) ATS ROUTE (2 TO 7 CHARACTERS)

The coded designator, assigned to the route or route segment including, where appropriate, the coded designator assigned to the standard departure or arrival route.

NOTE: Specification of last significant point of the standard departure and first significant point of the standard arrival is required for electronic data processing

Example: BEJ2V BEJ UR725 FTM UG4l VISEU Wl2 PAIVA PAIVA2A

NOTE: Provisions for the application of route designators are contained in Annex 11, Appendix 1,whilst guidance material on the application of an RNP Type to a specific route segment(s), route(s) or area is contained in the Manual on Required Navigation Performance (RNP) Doc. 9613.

2) SIGNIFICANT POINT (2 TO 11 CHARACTERS)

The coded designator (2 to 5 characters) assigned to the point (e.g. LN, MAY, HADDY), or if no coded designator has been assigned, one of the following ways:

3) CHANGE OF SPEED OR LEVEL (MAXIMUM 21 CHARACTERS)

The point at which a change of speed (5% TAS or 0.01 MACH or more) or a change of level is planned, expressed exactly as in (2) above, followed by an oblique stroke and both the cruising speed and the cruising level, expressed exactly as in (a) and (b) above, without a space between them, even when only one of these quantities will be changed.

EXAMPLES: LN/N0284A045
MAY/N0305F180
HADDY/N0420F330
4602N07805W/N0500F350
46N078W/M082F330
DUB180040/N0350M0840

4) CHANGE OF FLIGHT RULES (MAXlMUM 3 CHARACTERS)

The point at which the change of flight rules is planned, expressed exactly as in (2) or (3) above as appropriate, followed by a space and one of the following:

VFR if from IFR to VFR
IFR if from VFR to IFR

EXAMPLES: LN VFR
LN/N0284A050 IFR

5) CRUISE CLIMB (MAXIMUM 28 CHARACTERS)

The letter C followed by an oblique stroke; THEN the point at which the cruise climb is planned to start, expressed exactly as in (2) above, followed by an oblique stroke; THEN the speed to be maintained during cruise climb, expressed exactly as in (a) above, followed by the two levels defining the layer to be occupied during cruise climb, each level expressed exactly as in (b) above, or the level above which cruise climb is planned followed by the letters PLUS, without a space between them.

EXAMPLES:
C/48N050W/M082F290F350
C/48N050W/M082F290PLUS
C/52N050W/M220F580F620

ITEM 16: DESTINATION AERODROME AND TOTAL ESTIMATED ELAPSED TIME, DESTINATION ALTERNATE AERODROME(S)

DESTINATION AERODROME AND TOTAL ESTIMATED ELAPSED TIME (8 CHARACTERS)

INSERT the ICAO four-letter location indicator of the destination aerodrome as specified in Doc 7910, Location Indicators

OR, if no location indicator has been assigned,

INSERT ZZZZ and SPECIFY in Item 18 the name and location of the aerodrome, preceded by DEST/.

THEN WITHOUT A SPACE, INSERT the total estimated elapsed time

NOTE: For a flight plan received from an aircraft in flight, the total estimated elapsed time is the estimated time from the first point of the route to which the flight plan applies to the termination point of the flight plan.

DESTINATION ALTERNATE AERODROME(s) (4 CHARACTERS)

INSERT the ICAO four-letter location indicator(s) of not more than two destination alternate aerodromes, as specified in Doc 7910, Location Indicators, separated by a space, or

if no location indicator has been assigned to the destination alternate aerodrome(s),

INSERT ZZZZ and SPECIFY in Item 18 the name and location of the destination alternate aerodrome(s), preceded by ALTN/ -

ITEM 18: OTHER INFORMATION

INSERT 0 (zero) if no other information.

Hyphens “-“ or oblique strokes “/” should only be used as described.

Operators are warned that the use of indicators not included in these provisions may result in data being rejected, processed incorrectly or lost.

Only indicators described in these provisions may be used, and they must be inserted in the order shown. The indicators defined are as follows, and are listed in the order in which they are to be inserted, if used:

STS/ Reason for special handling by ATS, e.g. a search and rescue mission, as follows:

Other reasons for special handling by ATS shall be denoted under the designator RMK/. PBN/ Indication of RNAV and/or RNP capabilities. Include as many of the descriptors below, as apply to the flight, up to a maximum of 8 entries, i.e. a total of not more than 16 characters.

RNAV SPECIFICATIONS
A1RNAV 10 (RNP 10)
B1RNAV 5 all permitted sensors
B2RNAV 5 GNSS
B3RNAV 5 DME/DME
B4RNAV 5 VOR/DME
B5RNAV 5 INS or IRS
B6RNAV 5 LORANC
C1RNAV 2 all permitted sensors
C2RNAV 2 GNSS
C3RNAV 2 DME/DME
C4RNAV 2 DME/DME/IRU
D1RNAV 1 all permitted sensors
D2RNAV 1 GNSS
D3RNAV 1 DME/DME
D4RNAV 1 DME/DME/IRU
RNP SPECIFICATIONS
L1RNP 4
O1Basic RNP 1 all permitted sensors
O2Basic RNP 1 GNSS
O3Basic RNP 1 DME/DME
O4Basic RNP 1 DME/DME/IRU
S1RNP APCH
S2RNP APCH with BARO-VNAV
T1RNP AR APCH with RF (special authorization required)
T2RNP AR APCH without RF (special authorization required)

Combinations of alphanumeric characters not indicated above are reserved.

NAV/ Significant data related to navigation equipment, other than specified in PBN/, as required by the appropriate ATS authority. Indicate GNSS augmentation under this indicator, with a space between two or more methods of augmentation, e.g. NAV/GBAS SBAS. If appropriate, insert RNAVX or RNAVINOP, as detailed in the IFPS Users Manual and Portuguese AIP section ENR 1.1.2 RNAV Operations.

COM/ Indicate communications applications or capabilities not specified in Item 10a. If appropriate, insert EXM833 as detailed in the IFPS Users Manual and Portuguese AIP section ENR 1.8.1 Exemptions For Mandatory Carriage of 8.33 KHz Channel Spacing Equipment In The VHF Radio COM Band.

DAT/ Indicate data applications or capabilities not specified in Item 10a.

SUR/ Include surveillance applications or capabilities not specified in Item 10b.

DEP/ 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.

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.

DOF/ The date of flight departure in a six figure format (YYMMDD, where YY equals the year, MM equals the month and DD equals the day).

REG/ The nationality or common mark and registration mark of the aircraft, if different from the aircraft identification in Item 7.

EET/ Significant points or FIR boundary designators and accumulated estimated elapsed times from take-off to such points or FIR boundaries, when so prescribed on the basis of regional air navigation agreements, or by the appropriate ATS authority.Examples: EET/FTM0745 VFA0830, EET/LPPO0204

SEL/ SELCAL Code, for aircraft so equipped.

TYP/ Type(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/2F16 5C295 3P3

CODE/ Aircraft address (expressed in the form of an alphanumerical code of six hexadecimal characters) when required by the appropriate ATS authority. Example: “F00001” is the lowest aircraft address contained in the specific block administered by ICAO.

RVR/ The minimum RVR requirement of the flight.

Note- This provision is detailed in the European Regional Supplementary Procedures (EUR SUPPs, Doc 7030), Chapter 2.

DLE/ En-route 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/FTM0030

OPR/ ICAO designator or name of the aircraft operating agency, if different from the aircraft identification in item 7.

ORGN/ 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 Centre may insert the ORGN/ identifier and originator’s AFTN address automatically

PER/ 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.

ALTN/ Name of destination alternate aerodrome(s), 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 in DEP/ above.

RALT/ 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 distance from the nearest significant point, as described in DEP/ above.

TALT/ 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 distance from the nearest significant point, as described in DEP/ above.

RIF/ The route details to the revised destination aerodrome, following by the ICAO four-letter location indicator of the aerodrome. The revised route is subject to reclearance in flight.
Examples: RIF/PRT FTM LPPT, RIF/ESP G94 VIS LPPR

RMK/ Any other plain language remarks when required by the appropriate ATS authority or deemed necessary.

RFP/ Q followed by a digit to indicate the sequence of the replacement flight plan being submitted.

Note- This provision is detailed in the European Regional Supplementary Procedures (EUR SUPPs, Doc 7030), Chapter 2.

ITEM 19: SUPPLEMENTARY INFORMATION

ENDURANCE

After E/ INSERT a 4 figure group giving the fuel endurance in hours and minutes.

PERSONS ON BOARD

After P/ INSERT the total number of persons (passengers and crew) on board, when required by the appropriate ATS authority.
INSERT  TBN (to be notified) if the total number of persons is not known at the time of filing.

EMERGENCY AND SURVIVAL EQUIPMENT

R/ (RADIO)
CROSS OUT U if UHF on frequency 243.000 MHZ is not available.
CROSS OUT V if VHF on frequency 121.500 MHZ is not available.
CROSS OUT E if the emergency location beacon - aircraft (ELBA) is not available.

S/ (SURVIVAL EQUIPMENT)
CROSS OUT all indicators if survival equipment is not carried.
CROSS OUT P if polar survival equipment is not carried.
CROSS OUT D if desert survival equipment is not carried.
CROSS OUT M if maritime survival equipment is not carried.
CROSS OUT J if jungle survival equipment is not carried.

J/ (JACKETS)
CROSS OUT all indicators if life jackets are not carried.
CROSS OUT L if life jackets are not equipped with lights.
CROSS OUT F if life jackets are not equipped with fluorescent.
CROSS OUT U or V or both as in R/ above to indicate radio capability of jackets, if any,

D/(DINGHIES NUMBER)
CROSS OUT indicators D and C if no dinghies are carried, or
INSERT number of dinghies carried; and

(CAPACITY)
INSERT total capacity, in persons, of all dinghies carried; and

(COVER)
CROSS OUT indicator C if dinghies are not covered; and

(COLOUR)
INSERT colour of dinghies if carried.

A/ (AIRCRAFT COLOUR AND MARKINGS)
INSERT colour of the aircraft and significant markings

N/ (REMARKS)
CROSS OUT indicator N if no remarks, or INDICATE any other survival equipment carried and any other remarks regarding survival equipment.

C/ (PILOT)
INSERT name of pilot in-command.

Filed by

INSERT The name of unit, agency or person filing the flight plan.

Acceptance of the Flight Plan

Indicate acceptance of the flight plan in the manner prescribed by the appropriate ATS authority.

Instructions for insertion of COM data

Items to be completed

COMPLETE the top two shaded lines of the form, and COMPLETE the third shaded line only when necessary, in accordance with the provision in ICAO Doc. 4444 - Chapter 11 - Paragraph 11.2.1.2 unless ATS prescribes otherwise.

1.10.2   Repetitive flight plan system

NIL

1.10.3   Changes to the submitted flight plan

Replacement flight plan procedure

The replacement flight plan procedure is applicable for flights subject to ATFM.

When an individual Flight PLan (FPL) has been filed and, in the pre-flight stage (i.e. within 4 hours of EOBT, but not later than 30 minutes before EOBT), an alternative routing is selected between the same aerodromes of departure and destination, the operator or pilot shall:

  1. submit a cancellation message (CNL) which shall be transmitted with the priority ”DD” to all addresses concerned by the previous flight plan; and
  2. file a replacement Flight Plan in the form of a FPL, which shall be transmitted not less than 5 minutes after the CNL and not before the ACKnowledgement to the CNL message is received from IFPS.

The replacement flight plan shall contain inter alias the original identification (call sign), the complete new route in ITEM 15:
and, as the first element in ITEM 18:, the indication ‘RFP/Qn’, whereas:

In RTF communication, the pilot may inform an ATC unit that the aircraft is operating on a replacement flight plan if any doubt exists regarding the route to be flown.

Modification message CHG

Certain key fields within a flight plan cannot be modified by a CHG message within IFPS as they are used for message association.

These non-changeable fields are:

To change one of the above fields (except by means of a DLA to the EOBT) it is necessary to cancel the original flight plan and to refill a flight plan containing the corrected data. The RFP procedure shall not be used for such changes.

Non-observance could lead to failed or mismatched association.

Delay message DLA

Any delay of up to 20 hours can be indicated with a DLA message, but for a ”negative delay”, i.e. a new EOBT which is earlier than the original EOBT given in the flight plan, a DLA message shall not be used.

DLA messages should not be sent to IFPS to indicate a delay caused by the reception of a slot allocation message.

For flights subjected to ATFM measures, the following rules shall apply:

  1. A FPL shall be filed a minimum of 3 hours before EOBT (Estimated Off-Block Time).
  2. Any delay of more than 15 min shall be subjected to a DLA message. Negative DLAs (anticipation of the EOBT) are not permitted. The correct procedure for bringing an EOBT forward is to issue a CNL, and then re-file a new FPL.

For flights being already allocated a slot, the relevant ATFM procedures apply. Detailed information can be found in the CFMU handbook.

Departure message DEP

Within Lisboa FIR Portuguese air navigation services (TWRs or AROs) will not transmit departure messages for controlled IFR flights except when requested.
Within Santa Maria FIR a departure message is always sent to IFPS for redistribution.

Relevant requests should be submitted to the competent ATS unit or notified on the flight plan messages.

IFPS Validation

The validation of the flight plan associated messages by the IFPS is the same as for flight plans (FPL).

Closing a Flight Plan

Once the flight has ended, and if no ATS unit exists at the arrival aerodrome, the pilot shall give notice of his arrival within 30 minutes after landing, by radio to the last contacted ATS unit or via FPL and Briefing (https://fplbriefing.nav.pt), by phone or email (see AD 2.3) to any of the ATS Reporting Offices (ARO) as follows:.

Adherence to Airspace Utilization Rules and Availability

No Flight Plans shall be filled via the airspace of LPPC and LPPO FIR deviating from the State restrictions defined the Route Availability Document (RAD). This common European reference document contains all airspace utilisation rules and availability for LPPC and LPPO FIR and any reference to them shall be made via:

Figure 1.  Flight Plan Form