en-GB AIP for Belgium and G.D. of Luxembourg (section ENR-1.10)

18 Pages·2013·0.29 MB·English

AIP Belgium and G.D. of Luxembourg ENR 1.10-1
15 NOV 2012
~~~eaip-amdt~~~AIRAC-2012-10
ENR 1.10 Flight planning
1 FLIGHT PLAN
1.1 GENERAL
Information relative to an intended FLTor portion of a FLT, to be provided to ATSunits, shall be in the form of a FLTplan.
1.2 FLIGHT PLAN FORM
A flight plan form based on the model shown hereafter shall be provided and shall be used by operators and ATSunits for the
purpose of completing flight plans.
If the flight plan is transmitted by FAX, a special flight plan model shall be used. This form can be obtained from EBBRor ELLX
ARO.
2 REQUIREMENT TO SUBMIT A FLIGHT PLAN
A flight plan shall be submitted prior to operating:
a. any FLTor portion thereof to be provided with ATCservice
b. any FLTabove FL660
c. any FLTacross international borders
d. any VFRFLTat night.
Note 1: A pilot may, if he wishes, submit a flight plan for any FLT. A pilot is advised to submit a flight plan if he intends to fly
over sparsely populated areas, particularly if his ACFTis not equipped with radio.
Note 2: With regard to point a) above, a pilot is not required to use the flight plan form for the purpose of obtaining an ATCCLR
for a FLTto be provided with ADcontrol service only. He should however, either in person, by telephone or by radio, submit
the limited information required by the appropriate ATSunit.
Note 3: A pilot who has submitted a flight plan for a FLTdeparting from a private ADis responsible for the forwarding of the
associated messages either by TELor by radio to the ATSunit to which the flight plan was sent.
3 SUBMISSION OF A FLIGHT PLAN
←
3.1 IFR FLIGHT PLAN
Except for RPLs, a flight plan shall be submitted prior to DEPeither to the IFPSor to an ARO, or during flight to an appropriate
ATSunit.
The IFPSis the responsible unit for accepting IFR/GATflight plans, for FLTs conducted within the IFPS-Zone. Unless a flight
plan has been received and accepted by the IFPS(i.e. an ACKmessage has been received), the requirement to submit a flight
plan for an IFR/GATFLTintending to operate into the IFPS-Zone will not have been satisfied and no ATCCLRwill be issued
for such a FLT.
Aircraft Operators shall file their flight plans and associated messages for IFR/GAT FLTs directly with the IFPS, whenever
possible, or they can use the intermediate of a local ARO. The IFPS will send back "Operational Reply Messages" to the
message originator (Aircraft Operator or ARO), indicating the status of processing of his flight plan or associated message:
• an acknowledge message (ACK) will indicate the successful processing of the message
• a reject message (REJ) indicates that the submitted message could not be processed and that the message originator
should file a new corrected message
• a manual message (MAN) means that the message contains errors and that it will be presented to an IFPSoperator for
manual processing. A MAN message will be followed either by an ACK message, if the message has been corrected
successfully by the IFPSoperator, or by a REJmessage, if the error(s) could not be solved.
Detailed information on flight plan filing procedures with the IFPSis published in the IFPS Users ManualCFMU Handbook. It
can be obtained from EUROCONTROL Library (see ENR 1.9, ATFM Documentation).
3.2 VFR FLIGHT PLAN
A VFRflight plan shall be sent prior to departure via:
• AFTN
• FAX
• TEL
• dedicated workstations
• the internet
• in person
© BELGOCONTROL AIM, 2012 AIRAC AMDT 10/2012
ENR 1.10-2 AIP Belgium and G.D. of Luxembourg
15 NOV 2012
~~~eaip-amdt~~~AIRAC-2012-10
A VFRflight plan may also be filed in flight.
3.3 PROCEDURES FOR SUBMITTING FLIGHT PLANS PRIOR TO DEPARTURE
3.3.1 FLIGHT PLANS SUBMITTED VIA AFTNAND SITA
3.3.1.1 IFR/GATFLTS CONDUCTED IN THE IFPS-ZONE
Such flight plans shall be submitted to the IFPSonly via:
• AFTNto EUCHZMFP and EUCBZMFP
• SITAto BRUEP7X and PAREP7X
3.3.1.2 IFR/GATFLTS LEAVING THE IFPS-ZONE AND/OR MIXED RULES FLIGHT PLANS
IFR/VFRor vice versa = flight rules Y or Z.
Message originators able to file the addresses for the portion of their FLToutside the IFPS-Zone and/or for the VFRportion
of their FLTshould file to the IFPSonly via:
• AFTNto EUCHZMFP and EUCBZMFP
• SITAto BRUEP7X and PAREP7X
Such message originators should fill in the non-IFPS addresses or the VFR addresses in AFTN-format below the
date/time/originator line - using the re-addressing procedure - as specified in the CFMUHandbook, Part IFPSUsers Manual.
Message originators not able to file the addresses for the portion of their FLToutside the IFPS-Zone and/or for the VFRportion
of their FLTshould file to the AROonly via:
• AFTNto EBBRZPZX (DEPfrom Belgium) or ELLXZPZX (DEPfrom the G.D. of Luxembourg)
• SITAnot possible
The AROwill address the IFRor mixed rules flight plan to both IFPSunits in accordance with the re-addressing procedure.
Note 1: Aircraft Operators filing via an AROshall never submit the same flight plan simultaneously to the IFPS.
Note 2: If a REJmessage is received from the IFPS, the AROwill transmit this REJmessage to the message originator's AFS
address for corrective action.
3.3.1.3 VFR FLIGHT PLANS SHALL ALWAYS BE TRANSMITTED TO THE RESPONSIBLE AROONLY VIA:
• AFTNto EBBRZPZX (DEPfrom Belgium) or ELLXZPZX (DEPfrom the G.D. of Luxembourg)
• SITAnot possible
3.3.2 FLIGHT PLANS SUBMITTED BY FAX, TEL OR IN PERSON.
Regardless the flight rules, flight plans can only be submitted by FAX, TEL or in person at the AROs of EBBRand ELLX. Such
flight plans cannot be submitted directly with the IFPS.
Note: All flight plan forms sent by FAX should be filled out in capital letters using a black ballpoint.
It is the Aircraft Operator's responsibility to ensure himself of the correct reception of his telefax flight plan at the appropriate
ARO.
Operators of IFR/GAT flight filing their flight plan by FAX, TEL or in person shall in any case contact the appropriate ARO
(preferably 15 MINafter filing) to obtain confirmation on the acceptance of their flight plan by the IFPS(ACKmessage received
at the ARO).
Operators of IFR/GATflight filing their flight plan by FAX, TELor in person shall leave a (mobile) telephone number at the ARO,
where they can be contacted in case the originally filed flight plan would be changed by the IFPS(especially when in Item 18
"RMK/IFPS REROUTE ACCEPTED" has been included).
EBBRAROcan be contacted at:
• Tel:++32 (2) 206 25 40 or 41
• Fax: ++32 (2) 206 25 39
ELLXAROcan be contacted at:
• Tel:++352 4798 2301 1
• Fax: ++352 4798 2309 0
AIRAC AMDT 10/2012 © BELGOCONTROL AIM, 2012
AIP Belgium and G.D. of Luxembourg ENR 1.10-3
15 NOV 2012
~~~eaip-amdt~~~AIRAC-2012-10
3.3.3 FLIGHT PLANS SUBMITTED VIA DEDICATED WORKSTATIONS OR VIA THE INTERNET.
Regardless the flight rules, flight plans can solely be submitted at the Brussels ARO via dedicated workstations or via the
Internet.
Dedicated workstations for filing of flight plans are installed at EBAW, EBCI, EBLGand EBOS. Aircraft Operators filing a flight
plan on one of these workstations will automatically receive a hard copy of their flight plan on the printer next to the workstation,
when the flight plan is accepted by Brussels ARO. If the flight plan is not accepted, a reject message will be received on the
same printer, requesting to contact Brussels AROvia TELfor corrective action.
Aircraft Operators intending to use the Internet for the submission of their flight plan, shall exclusively use the electronic flight
plan form made available on the Belgocontrol website.
URL: http://www.belgocontrol.be
It is the Aircraft Operator's responsibility to ensure himself of the correct reception of his internet flight plan at the Brussels
ARO.
Operators of IFR/GATFLTfiling their flight plan via either a dedicated workstation or via the Internet shall in any case contact
Brussels ARO(preferably 15 MINafter filing) to obtain confirmation on the acceptance of their flight plan by the IFPS(ACK
message received at the ARO).
Operators of IFR/GAT FLT filing their flight plan either via a dedicated workstation or via the Internet shall leave a (mobile)
telephone number at the ARO, where they can be contacted in case the originally filed flight plan would be changed by the
IFPS(especially when in Item 18 "RMK/IFPS REROUTE ACCEPTED" has been included).
For flight planning problems contact Brussels ARO
Tel: ++32 (2) 206 25 40 or 41
In case of technical problems contact Flight Support Help Desk
Tel: ++32 (2) 206 25 48
← 3.3.4 SUBMISSION TIME
A flight plan for a FLTto be provided with ATCservice shall be submitted at least 30 MINbefore the EOBT, furthermore all
IFR/GATflight plans shall be submitted at least 1 HRbefore the EOBT. See ENR 1.9for ATFMpurposes.
A flight plan shall not be submitted more than 120 HR(5 days) prior to the EOBT.
Note: If a flight plan for a FLTconducted wholly in the EUR Region is filed more than 24 HRin advance of the EOBT, it is
mandatory to provide the date of the FLT.
Even if the flight plan is filed less than 24 HRin advance of the EOBT, it is strongly recommended to insert the date of the FLT
in Item 18 of the flight plan in the form of a 3-letter indicator (DOF) followed by an oblique stroke and the date of the FLTin a
6-figure group format: DOF/YYMMDD (YY = year; MM = month; DD = date).
In the event of a delay of 15 MINin excess of the EOBTfor a controlled FLTor a delay of 60 MINfor a non-controlled FLTfor
which a flight plan has been submitted, the flight plan shall be amended or a new flight plan shall be submitted and the old one
should be cancelled.
3.4 PROCEDURES FOR SUBMITTING FLIGHT PLANS DURING FLIGHT (AFIL)
A flight plan submitted during flight should normally be transmitted to the ATSunit in charge of the FIRor CTAin which the
ACFTis flying, or in, or through which the ACFTwhishes to fly.
In case of an AFIL, the ATSunit receiving the flight plan will be responsible for addressing the flight plan message in accordance
with the PROCs described above.
An AFILfor a FLTto be provided with ATCservice shall be submitted at a time which will ensure its receipt by the appropriate
ATS unit at least 10 MINbefore the ACFTis estimated to reach:
• the intended point of entry into a CTA
• the point of crossing an airway.
Note: If the flight plan is submitted for the purpose of obtaining ATCservice, the ACFTis required to wait for an ATCCLRprior
to proceed under the conditions requiring compliance with ATCprocedures.
4 CONTENTS OF A FLIGHT PLAN
A flight plan shall comprise information regarding such of the following items considered relevant by the appropriate ATSunit:
• ACFTidentification
• Flight rules and type of FLT
• Number and type(s) of ACFTand wake turbulence category
© BELGOCONTROL AIM, 2012 AIRAC AMDT 10/2012
ENR 1.10-4 AIP Belgium and G.D. of Luxembourg
15 NOV 2012
~~~eaip-amdt~~~AIRAC-2012-10
• Equipment
← • ADof DEP(see Note 1)
• EOBT(see Note 2)
• Cruising speed(s)
• Cruising level(s)
• Route to be followed
• ADof DESTand total elapsed time
• Alternate AD(s)
• Fuel endurance
• Total number of persons on board
• Emergency and survival equipment
• Other information.
Note 1: For an AFIL, the information to be provided in respect of this item will be an indication of the location from which
supplementary information concerning the FLTmay be obtained, if required.
Note 2: For an AFIL, the information to be provided in respect of this item will be the time over the first point of the route to
which the flight plan relates.
Note 3: The term "aerodrome" where used in the flight plan is intended to cover also sites other than ADs which may be used
by certain types of ACFT(e.g. helicopters or balloons).
5 COMPLETION OF A FLIGHT PLAN
5.1 GENERAL
Whatever the purpose for which it is submitted, a flight plan shall contain information, as applicable, on relevant items up to
and including "alternate aerodrome(s)" regarding the whole route or the portion thereof for which the flight plan is submitted.
5.2 INFORMATION REGARDING ALERTING AND SAR SERVICES
It shall, in addition, contain information, as applicable, on all other items given under "CONTENTS OF A FLIGHT PLAN" above,
when submitted either for facilitating the provision of alerting and SARservices, or prior to DEPfor an IFRFLT.
5.3 INSTRUCTIONS FOR THE COMPLETION OF A FLIGHT PLAN FORM
5.3.1 GENERAL
• Adhere closelyto the prescribed formats and manner of specifying data.
• Commence inserting data in the first space provided. Where excess space is available, leave unused spaces blank.
• Insertall clock times in4 figures UTC.
• Insert all estimated elapsed times in 4 figures (HRand MIN).
• Shaded area preceding Item 3. - To be completed by ATS and COMservices, unless the responsibility for originating
flight plan messages has been delegated.
5.3.2 INSTRUCTIONS FOR INSERTION OF ATS DATA
• Complete Items 7 to 18as indicated hereunder.
• Complete also Item 19as indicated hereunder, when so required by the appropriate ATS authority or when otherwise
deemed necessary.
Note: Item numbers on the form are not consecutive, as they respond to Field Type numbers in ATS messages.
5.3.2.1 ITEM 7: AIRCRAFT IDENTIFICATION (MAX7 CHARACTERS)
Insertone of the following ACFTidentifications, not exceeding 7 alphanumeric characters and without hyphens or symbols:
a. the ICAO designator for the ACFToperating agency followed by the flight identification (e.g. BEL511, NGA213) when in
RTFthe call sign to be used by the ACFTwill consist of the ICAO telephony designator for the operating agency followed
by the flight identification (e.g. BEELINE 511, NIGERIA 213) and SPECIFY in Item 18 the registration marking of the ACFT
preceded by REG/.
← b. the nationality or common mark and registration mark of the ACFT(e.g. EIAKO, 4XBCD, OOSDE, N2567GA), when:
← ∗ in RTFthe call sign to be used by the ACFTwill consist of this identification alone (e.g. OOSDE), or preceded by the
ICAO telephony designator for the ACFToperating agency (e.g. BEELINE OOSDE) and SPECIFY in Item 18 the
name of the operator preceded by OPR/
∗ the ACFTis not equipped with radio
AIRAC AMDT 10/2012 © BELGOCONTROL AIM, 2012
AIP Belgium and G.D. of Luxembourg ENR 1.10-5
15 NOV 2012
~~~eaip-amdt~~~AIRAC-2012-10
Note: Provisions for the use of RTFcall signs are contained in ICAO Annex 10, Volume II, "Aeronautical Telecommunications",
Chapter 5. ICAO designators for aircraft operating agencies are contained in Doc 8585, "Designators for Aircraft Operating
Agencies, Aeronautical Authorities and Services".
5.3.2.2 ITEM 8: FLIGHT RULES AND TYPE OF FLIGHT (1 OR 2 CHARACTERS)
FLIGHT RULES
Insertone of the following letters to denote the CATof flight rules with which the pilot intends to comply:
← • I if it is intended that the entire flight will be operated under IFR
← • V if it is intended that the entire flight will be operated under VFR
← • Y if the flight initially will be operated under IFR, followed by one or more subsequent changes of flight rules or
← • Z if the flight initially will be operated under VFR, followed by one or more subsequent changes of flight rules
Note: Specify in Item 15 the point(s) where a change of flight rules is planned.
TYPE OF FLIGHT
Insertone of the following letters to denote the type of FLT:
• S - Scheduled Air Service
• N - Non-scheduled Air Transport Operation
• G - General Aviation
• M - Military (see Note 1)
• X - other than any of the defined CATs above (see Note 2)
Note 1: In addition to MILoperations, operators of customs or police ACFTshall insert the letter "M" in item 8 of the ICAO Flight
Plan Form.
Note 2: Specify status of a flight following the indicator STS/ in Item 18, or when necessary to denote other reasons for specific
handling by ATS, indicate the reason following the indicator RMK/ in Item 18.
←
5.3.2.3 ITEM 9: NUMBER AND TYPE OF AIRCRAFT AND WAKE TURBULENCE CATEGORY
NUMBER OF AIRCRAFT (1 or 2 characters)
Insertthe number of ACFT, if more than one.
TYPE OF AIRCRAFT (2 or 4 characters)
Insertthe appropriate designator as specified in ICAO Doc 8643, "Aircraft Type Designators".
If no such designator has been assigned, or in case of formation FLTs comprising more than one type,
Insert"ZZZZ" and Specifyin Item 18 the (numbers and) type(s) of ACFTpreceded by TYP/.
WAKE TURBULENCE CATEGORY (1 character)
Insertan oblique stroke followed by one of the following letters to indicate the wake turbulence category of the ACFT:
• H - HEAVY, to indicate an ACFTtype with a MTOWof 136 000 kg or more
• M - MEDIUM, to indicate an ACFTtype with a MTOWof less than 136 000 kg but more than 7 000 kg
• L - LIGHT, to indicate an ACFTtype with a MTOWof 7 000 kg or less.
5.3.2.4 ITEM 10: EQUIPMENT AND CAPABILITIES
Capabilities comprise the following elements:
a. presence of relevant serviceable equipment on board the aircraft
b. equipment and capabilities commensurate with flight crew qualifications; and
c. where applicable, authorization from the appropriate authority.
← 5.3.2.4.1 Provisions applicable to ITEM 10a (Radio Communication, Navigation and Approach Aid Equipment)
Insertone letter as follows:
N if no COM/NAV/APCHaid equipment for the route to be flown is carried, or the equipment is unserviceable
OR
S if standard COM/NAV/APCHaid equipment for the route to be flown is carried and serviceable (see note 1). If required, the
inclusion of letter S must be the first one of the field 10a.
AND/OR
© BELGOCONTROL AIM, 2012 AIRAC AMDT 10/2012
ENR 1.10-6 AIP Belgium and G.D. of Luxembourg
15 NOV 2012
~~~eaip-amdt~~~AIRAC-2012-10
Insertone or more of the following letters to indicate the serviceable COM/NAV/APCHaid equipment and capabilities AVBL:
A GBASlanding system J7 CPDLCFANS 1/A SATCOM(Iridium)
B LVP(APVwith SBAS) K MLS
C LORAN C L ILS
D DME M1 ATCRTFSATCOM (INMARSAT)
E1 FMCWPR ACARS M2 ATCRTF(MTSAT)
E2 D-FIS ACARS M3 ATCRTF(Iiridium)
E3 PDCACARS O VOR
F ADF P1-P9 Reserved for RCP
G GNSS(see note 2) R PBNapproved (see Note 4)
H HFRTF T TACAN
I Inertial Navigation U UHFRTF
J1 CPDLCATNVDL Mode 2 (see note 3) V VHFRTF
J2 CPDLCFANS 1/A HFDL W RVSMapproved
J3 CPDLCFANS 1/A VDL Mode 4 X MNPSapproved
J4 CPDLCFANS 1/A VDL Mode 2 Y VHFwith 8.33 kHzchannel spacing capability
J5 CPDLCFANS 1/A SATCOM(INMARSAT) Z Other equipment carried or other capabilities (see
note 5)
J6 CPDLCFANS 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, VORand ILS, unless another combination
is prescribed by the appropriate ATS authority.
Note 2: If the letter G is used, the types of external GNSSaugmentation, 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 shall be 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, CPDLCand 8.33 kHzare to be indicated by inserting the letter Z in Item
10a and then inserting the appropriate descriptors in the following indicators in Item 18:
a) insert EXM833 following COM/;
b) insert RNAVX or RNAVINOP as appropriate following NAV/; and/or
c) insert CPDLCX following DAT/.
Note 6: Information on navigation capability is provided to ATCfor clearance and routing purposes.
← 5.3.2.4.2 Provisions applicable to ITEM 10b (Surveillance Equipment and Capabilities)
InsertN 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 Modes A and C
∗ A Transponder — Mode A (4 digits — 4 096 codes)
∗ C Transponder — Mode A (4 digits — 4 096 codes) and Mode C
• SSR Mode S
∗ E Transponder — Mode S, including aircraft identification, pressure-altitude and extended squitter (ADS-B) capability
∗ H Transponder — Mode S, including aircraft identification, pressure-altitude and enhanced surveillance capability
∗ I Transponder — Mode S, including aircraft identification, but no pressure-altitude capability
AIRAC AMDT 10/2012 © BELGOCONTROL AIM, 2012
AIP Belgium and G.D. of Luxembourg ENR 1.10-7
15 NOV 2012
~~~eaip-amdt~~~AIRAC-2012-10
∗ L Transponder — Mode S, including aircraft identification, pressure-altitude, extended squitter (ADS-B) and enhanced
surveillance capability
∗ P Transponder — Mode S, including pressure-altitude, but no aircraft identification capability
∗ S Transponder — Mode S, including both pressure altitude and aircraft identification capability
∗ X Transponder — 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-B
∗ B1 ADS-B with dedicated 1090 MHzADS-B “out” capability
∗ B2 ADS-B with dedicated 1090 MHzADS-B “out” and “in” capability
∗ U1 ADS-B “out” capability using UAT
∗ U2 ADS-B “out” and “in” capability using UAT
∗ V1 ADS-B “out” capability using VDL Mode 4
∗ V2 ADS-B “out” and “in” capability using VDL Mode 4
• ADS-C
∗ D1 ADS-C with FANS 1/A capabilities
∗ G1 ADS-C with ATN capabilities
Alphanumeric characters not indicated above are reserved (e.g. ADE3RV/HB2U2V2G1).
Note: Additional surveillance application should be listed in Item 18 following the indicator SUR/ .
← 5.3.2.5 ITEM 13: DEPARTURE AERODROME AND TIME (8 CHARACTERS)
Insertthe ICAOfour-letter code of the DEPAD.
Or, if no location indicator has been assigned,
insert"ZZZZ" and specifyin Item 18 the name and location of the ADpreceded by DEP/.
Or, if the flight plan is received from an ACFTin flight,
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,
insertAFILand specifyin Item 18 the ICAOfour-letter location indicator of the location of the ATSunit from which supplementary
flight plan data can be obtained, preceded by DEP/.
Then, without a space,
insertfor a flight plan submitted before DEP, the EOBT,
or, for a flight plan received from an ACFTin flight, the actual or estimated time over the first point of the route to which the
flight plan applies.
5.3.2.6 ITEM 15: ROUTE
Insertthe first cruising speed as in a) and the first cruising level as in b), without a space between them.
Then, following the arrow,insertthe route description as in c).
a ) CRUISING SPEED (MAX5 characters)
Insertthe TASfor the first or the whole cruising portion of the FLT, in terms of:
• kilometers per hour, expressed as "K" followed by 4 figures (e.g. K0830)
• knots, expressed as "N" followed by 4 figures (e.g. N0485)
• Mach number, when so prescribed by the appropriate ATSauthority, to the nearest hundredth of unit Mach, expressed
as "M" followed by 3 figures (e.g. M082).
b ) CRUISING LEVEL (MAX5 characters)
Insertthe planned cruising level for the first or the whole portion of the route to be flown, in terms of:
• flight level, expressed as "F" followed by 3 figures (e.g. F085, F330)
• Standard Metric Level in tens of meters, expressed as "S" followed by 4 figures (e.g. S1130), when so prescribed by the
appropriate ATSauthorities
• Altitude in hundreds of feet, expressed as "A" followed by 3 figures (e.g. A045, A100)
• Altitude in tens of metres, expressed as "M" followed by 4 figures (e.g. M0840)
• for uncontrolled VFRFLTs, the letters VFR.
© BELGOCONTROL AIM, 2012 AIRAC AMDT 10/2012
ENR 1.10-8 AIP Belgium and G.D. of Luxembourg
15 NOV 2012
~~~eaip-amdt~~~AIRAC-2012-10
c ) ROUTE (including changes of speed, level and/or flight rules)
← • RVSMairspace
Operators of RVSMapproved ACFTand non-RVSMapproved State ACFTintending to operate within EUR RVSMairspace
shall include the following in Item 15:
∗ the entry point at the lateral limits of the EUR RVSM airspace and the requested FL for that portion of the route
commencing immediately after the RVSMentry point
← ∗ the exit point at the lateral limits of the EUR RVSM airspace and the requested FL for that portion of the route
commencing immediately after the RVSMexit point. When the RVSMexit point is situated in the planned final descent
trajectory, the requirement to include a requested FLis withdrawn. Where appropriate, a co-located STARmay be
included after the RVSMexit point.
← • FLTs along designated ATSroutes or direct routes (DCT)
Insert,if the DEPis located on or connected to the ATSroute or direct route, the significant route at the end of the SID.
Or, if the DEPADis not on or connected to the ATSroute or direct route, insertthe letters "DCT" followed by the point of
joining the first ATSroute or direct route, followed by the designator of the ATSroute or the direct route.
Then, inserteach point at which either a change of speed or and/or level is planned to commence, or a change of ATS
route or direct route, and/or a change of flight rules is planned.
Note: When a transition is planned between a lower and upper ATSroute and the routes are oriented in the same direction,
the point of transition need not be inserted.
Followed in each caseby the designator of the next ATSroute segment, even if the same as the previous one,
or by "DCT", if the FLTto the next point will be outside a designated route, unless both points are defined by geographical
co-ordinates.
Note: If a STARis prescribed for the ADof DEST, the last point of the route shall be the first point of a STAR.
← • FLTs outside designated ATSroutes
Insertpoints normally not more than 30 MINflying 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 appropriate ATSauthority(ies),
Definethe track of FLTs 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 FLTs operating in areas outside those latitudes, the tracks shall be defined by significant points
formed by the intersection of parallels of latitude with meridians normally spaced at 20 degrees of longitude. The DIST
between significant points shall, as far as possible, not exceed one HRflight time. Additional significant points shall be
established as deemed necessary.
For FLTs operating predominantly in a North - South direction, definetracks 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
DIST.
Use only the conventions in 1. to 5. below and separateeach sub-time by a space.
1. ATSroute (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 (e.g. BCN 1, B1, R14, UB10, KODAP2A).
Note: Provisions for the application of route designators are contained in ICAOAnnex 11, "Air Traffic Management",
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 ICAODoc. 9613, "Manual on Required Navigation Performance (RNP)".
← 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:
− Degrees only (7 characters): 2 figures describing latitude in degrees, followed by "N" (North) or "S" (South),
followed by 3 figures describing longitude in degrees, followed by "E" (East) or "W" (West). Make up the correct
number of figures, where necessary, by insertion of zeros (e.g. 46N078W).
AIRAC AMDT 10/2012 © BELGOCONTROL AIM, 2012
AIP Belgium and G.D. of Luxembourg ENR 1.10-9
15 NOV 2012
~~~eaip-amdt~~~AIRAC-2012-10
− Degrees and minutes (11 characters): 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).
← − Bearing and DISTfrom a significant point: The identification of the significant point followed by the bearing from
the point in the form of 3 figures giving degrees MAG, followed the DISTfrom the point in the form of 3 figures
← expressing NM. Make up the correct number of figures, where necessary, by insertion of zeros (e.g. a point
180°MAGat a DISTof 40 NMfrom VOR "DUB" should be expressed as DUB180040).
← 3. Change of speed or level (MAX21 characters)
The point at which a change of speed (5% TASor 0.01 Mor more) or a change of level is planned to commence,
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 4602N07805W/N0500F350
HADDY/N0420F330 DUB180040/N0350M0840
MAY/N0305F180 46N078W/M082F330
4. Change of flight rules (3 MAXcharacters)
The point at which the change of flight rules is planned, expressed exactly as in 2. and 3. above as appropriate,
followed by a space and one of the following:
- VFRif from IFRto VFR
- IFRif from VFRto IFR
Examples:
− LN VFR
− LN/N0284A050 IFR
5. Cruise climb (MAX28 characters)
The letter "C" followed by an oblique stroke; thenthe point at which 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 LVLs defining the layer to be occupied during cruise climb, each LVLexpressed
exactly as in b) above, or theLVL 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
5.3.2.7 ITEM 16: DESTINATION AERODROME, TOTAL ESTIMATED ELAPSED TIME AND ALTERNATE DESTINATION
AERODROME(S)
DESTINATION ADAND TOTAL ESTIMATED ELAPSED TIME (8 characters)
Insertthe ICAOfour-letter location indicator of the DESTADfollowed, without a space, by the total estimated elapsed time,
or, if no location indicator has been assigned,
insert"ZZZZ" followed, without a space, by the total estimated elapsed time, and specifyin Item 18 the name and location of
the AD, preceded by DEST/.
Note: For a flight plan received from an ACFTin 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.
ALTERNATE DESTINATION AD(S) (4 characters)
Insertthe ICAOfour-letter location indicator(s) of not more than two alternate destination ADs, separated by a space,
or, if no location indicator has been assigned to the alternate AD,
© BELGOCONTROL AIM, 2012 AIRAC AMDT 10/2012
ENR 1.10-10 AIP Belgium and G.D. of Luxembourg
15 NOV 2012
~~~eaip-amdt~~~AIRAC-2012-10
insert"ZZZZ" and specifyin Item 18 the name and location of the alternate destination, preceded by ALTN/.
←
5.3.2.8 ITEM 18: OTHER INFORMATION
← Operators are warned that the use of indicators not included in the provisions may result in data being rejected, processed
incorrectly or lost.
← Only indicators described in the 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:
• ALTRV: for a flight operated in accordance with an altitude reservation;
• ATFMX: for a flight approved for exemption from ATFMmeasures by the appropriate ATSauthority;
• FFR: fire-fighting;
• FLTCK: flight check for calibration of navaids;
• HAZMAT: for a flight carrying hazardous material;
• HEAD: a flight with Head of State status;
• HOSP: for a medical flight declared by medical authorities;
• HUM: for a flight operating on a humanitarian mission;
• MARSA: for a flight for which a military entity assumes responsibility for separation of military aircraft;
• MEDEVAC: for a life critical medical emergency evacuation;
• NONRVSM: for a non-RVSM capable flight intending to operate in RVSMairspace;
• SAR: for a flight engaged in a search and rescue mission; and
• STATE: for a flight engaged in military, customs or police services.
Other reasons for special handling by ATSshall 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 RNP SPECIFICATIONS
A1 RNAV10 (RNP10) L1 RNP4
B1 RNAV5 all permitted sensors O1 Basic RNP1 all permitted sensors
B2 RNAV5 GNSS O2 Basic RNP1 GNSS
B3 RNAV5 DME/DME O3 Basic RNP1 DME/DME
B4 RNAV5 VOR/DME O4 Basic RNP1 DME/DME/IRU
B5 RNAV5 INSor IRS S1 RNPAPCH
B6 RNAV5 LORANC S2 RNPAPCHwith BARO-BNAV
C1 RNAV2 all permitted sensors T1 RNPAR APCHwith RF(special authorization
required)
C2 RNAV2 GNSS T2 RNPAR APCHwithout RF(special authorization
required)
C3 RNAV2 DME/DME
C4 RNAV2 DME/DME/IRU
D1 RNAV1 all permitted sensors
D2 RNAV1 GNSS
D3 RNAV1 DME/DME
D4 RNAV1 DME/DME/IRU
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 GNSSaugmentation 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 described in the European Regional Supplementary
Procedures (EUR SUPPs, Doc 7030), Chapter 2.
← COM/: Indicate communications applications or capabilities not specified in Item 10a. If appropriate, insert EXM833 as described
in the European Regional Supplementary Procedures (EUR SUPPs, Doc 7030), Chapter 2.
← DAT/: Indicate data applications or capabilities not specified in 10a. If appropriate, insert CPDLCX, as described in the European
Regional Supplementary Procedures (EUR SUPPs, Doc 7030), Chapter 2.
← SUR/: Include surveillance applications or capabilities not specified in Item 10b.
←
AIRAC AMDT 10/2012 © BELGOCONTROL AIM, 2012