1.2.1 Commercial aviation

1. Slot requests for commercial aviation must be filed in the slot clearance request (SCR) format according the IATA standard schedule information manual (SSIM) Chapter 6.
2. The requests must include information about the flight number or registration number and the desired date/time.
3. Slot requests shall be submitted to:
   Airport Coordination Netherlands (ACNL)

   Email: [email protected]

4. Contact information ACNL during office hours:

   Tel: +31 (0)20 405 9730

   URL: https://www.slotcoordination.nl

1.2.2 General aviation

General aviation is co-ordinated through PPR. An allocated PPR number should be filed in item 18 of the flight plan. General aviation flights are prohibited to operate to and from Eindhoven Airport without a valid PPR number. Requests for PPR must be filed at https://ppr.eindhovenairport.nl/customer/account/login/reference. The PPR procedures for general aviation and business aviation are available on: https://www.eindhovenairport.nl/en/general-aviation-business-aviation.

1.2.3 Business aviation

Business aviation flights are prohibited to operate to and from Eindhoven Airport without a valid approval from Eindhoven Airport. Business aviation flight requests to be send to:

1.2.1 Start-up and push-back permission

A request for start-up and push-back shall be made to Eindhoven Ground, this request shall include:

• aircraft identification (e.g. KLM001).
• position (e.g. S1).
• ATIS information (e.g. information "F").
• flight rules (e.g. IFR).
• destination (e.g. Amsterdam).
• request start-up (e.g. request start-up in 5 minutes).

Permission for start-up will be issued as soon as possible after the request has been made to Eindhoven Ground. The pilot shall be able to comply with the start-up and taxi permission, since ATC planning of outbound traffic (involving en-route clearance and co-ordination with adjacent ATC units) is based on the start-up time. Any delay in start-up or taxiing shall be reported to ATC immediately. In case of indefinite delay, the probable duration of delay will be given.

In case of push-back, the flight crew shall read back to ATC all instructions contained in the push-back clearance. As the flight crew is part of the communication chain between ground controller and truck driver, the flight crew shall also ensure that the complete push-back clearance from ATC is communicated word-for-word to the push-back crew. Therefore, the use of a ground engineer with an intercom connection is recommended. When intercom connection with a ground engineer is not possible, the pilot shall inform Eindhoven Ground.

Standard push-back directions from the stands are in force. To expedite traffic flow, instructions can be given for an “alternative push-back”. The aircraft will then be pushed in the direction and location instructed by Eindhoven Ground.

During ATIS OPR HR (see EHEH AD 2.18) no MET information will be issued to departing aircraft, except RVR.

1.2.2 En-route clearance

1.4.1 General remarks

• Transition altitude: 3000 FT AMSL.
• Turn radii based on a 25° bank angle.
• Radial interception angle: 45°.
• The SIDs are based on an average climb rate of 2000 FT/MIN.
• For continuous routings and crossing conditions on ATS routes as applicable see paragraph 1.4.3.
• SIDs have to be considered as minimum noise routings which shall be strictly adhered to.
• MAX 250 KIAS below FL 100 unless otherwise instructed.
• Initiate turns in due time in order not to overshoot radials.
• Additional departure instructions: especially propeller-driven aircraft can expect additional departure instructions. These instructions may be added to the en-route or take-off clearance and may comprise a specific heading or temporary altitude restriction. Such additives amend the relevant part of the SID only.
• RNAV: the Netherlands highly recommends the use of pre-programmed (RNAV) routes on board of aircraft. Within the TMAs these RNAV routes shall be considered as overlays of conventional routes, except the ABNED #S, INKET #S, PESER #S, TULIP #S and WOODY #S SIDs. An RNAV route may result in a different flight path (vertically: turn altitudes and/or laterally: turn anticipation effects) compared to the conventional route. By making use of the FMS route functionalities, a significant part of the noise production is shifted to less sensitive noise areas. Therefore, using RNAV will not result in route violations.
  The description of the published SIDs is extended with additional information intended for database coding only. The ABNED #S, INKET #S, PESER #S, TULIP #S and WOODY #S SIDs however, are mandatory for aircraft with an RNAV 1 approval. The SIDs are provided with:
  1. EH-waypoints. These points define unnamed intersections, turning points, positions etc.
  2. Route definition by means of publishing the sequence of relevant waypoints. It is prohibited to code other waypoints.
  3. A FMS-coding advice for B-737 aircraft as result of trials with the PDT (Procedure Design Tool) which is a FMS simulator for PCs predicting flight path. With the help of PDT all departures at Eindhoven AP have been checked on flyability and adherence to the desired ground path (within acceptable limits), covering more extreme flight conditions.
  Furthermore:
  • Database programmers must be aware that due to algorithms built-in FMCs not all conventional NAV instructions need to be part of the coding in order to work properly.
  • Due to the computer algorithms the flightpath of aircraft using RNAV overlays may deviate slightly from the conventional route. This will occur particularly during turns.
  • Connect FMS and autopilot as early as possible
  • The EH-waypoints shall not be used in RTF procedures.
  • Turn anticipation is mandatory for all waypoints except those which are underlined, these waypoints shall be overflown.
  • The navigation aid (e.g. VOR) mentioned in the column "Expected path terminator" is for selection of MAG station declination only.

1.4.2 Specific remarks

1. Only for aircraft with destination EBBR or EBAW.
2. Only for aircraft with destination EHRD, MAX FL 075.
3. Only for aircraft with destination EHBK.
4. Only for aircraft with destination EHAM, MAX FL 075.
5. Only for aircraft with destination EHGG and EHLE, MAX FL 095.
6. Prohibited for aircraft operators with RNAV 1 approval and able to comply with crossing conditions prescribed in the SID operating with aircraft with 2 or more engines.
7. RNAV 1 required.

1.4.3 Continuous routings for SIDs with crossing conditions on ATS routes as applicable

1.4.4 SIDs RWY 03

1.4.5 SIDs RWY 21

2.2.1 Arrival clearance

Before entering the Nieuw Milligen TMA D, an arrival clearance will be issued by Amsterdam ACC or MILATCC Schiphol containing:

1. Standard arrival route1) or direct route.
2. Main landing runway2).
3. Level instructions (normally descent instructions).
4. Any other necessary instructions or information.

1. when cleared via a standard arrival route (STAR), the clearance limit is the initial approach fix (lAF).
2. issued by ATIS (see EHEH AD 2.18) or ATC.

2.2.2 Level restriction

Flights via DENUT should comply with the following crossing condition: cross DENUT at FL 180 or below, unless otherwise instructed.

2.2.3 STAR descriptions

See charts AD 2.EHEH-STAR-1 and AD 2.EHEH-STAR-2.

2.2.4 Holding descriptions

Standard holding is located at the IAF EHOJI. The GILIV holding may be used at ATC discretion. Transition to and from the GILIV holding by ATC radar vectors.

2.3.1 General procedures

Holding and entry procedures and the calculations of the associated protected areas are in accordance with PANS-OPS Volume II, part 4. Since separation is based on the calculated areas, compliance with these in-flight procedures is essential.

2.3.2 Approach instructions

Approach instructions will contain as applicable:

1. Additional instructions with respect to clearance limit, route and level.
2. Approach procedure.
3. Runway in use1).
4. EAT, if holding procedures are applied.
5. QNH.
6. Transition level1).
7. MET information1).
8. Runway condition1).

1. During ATIS OPR HR (see EHEH AD 2.18) this item may be omitted when included in the ATIS broadcast.

2.3.3 RNAV approach procedures

An RNAV approach procedure will be initiated by ATC in order to reduce noise nuisance, fuel consumption, and to provide flexible and efficient ATC dispatch.

2.3.4 Radar service

During the initial and intermediate approach, radar service will be provided by RAPCON South and/or Eindhoven Arrival. Outside operating hours of these radar service units, MILATCC Schiphol (Dutch MIL) will provide radar approach service.

2.4.1 Final approach procedures

2.4.2 Missed approach procedure

2.5.1 General

• Select transponder code 7600.
• If possible call Amsterdam ACC Supervisor on telephone number +31 (0)20 406 3999.
  Use telephone connection to mitigate COM failure only. All telephone calls will be automatically recorded.
• If telephone connection is disconnected prematurely (before read-back), revert to general communication failure procedure.

For the general procedures for IFR flights see ENR 1.3 paragraph "Communication Failure". In addition, for arriving flights, the following communication failure procedures apply.

2.5.2 Inbound clearance not received

• Proceed according the current flight plan to EHOJI.
• Maintain the last cleared and acknowledged flight level.
• After arrival over EHOJI, intercept the holding pattern.
• Commence descent to 3000 FT AMSL at or as near as possible to the ETO over EHOJI.
• After reaching 3000 FT AMSL leave EHOJI and carry out an instrument approach procedure to RWY 21 (see AD 2.EHEH-IAC-xx.x). A circling procedure for the most convenient runway may be carried out (ICAO standard).

2.5.3 Inbound clearance received

2.5.4 Missed approach procedure in case of communication failure

2.6.1 Instrument approach segments RWY 03

2.6.2 Instrument approach segments RWY 21

4.2.1 General

1. Pilots must have obtained start-up clearance from ATC before starting engines. A request for start-up shall be made to Eindhoven Ground; clearance for start-up will either be issued immediately or at a specified time depending on traffic. A request for start-up includes:
   • aircraft identification (e.g. PHSPY Cessna 172).
   • position (e.g. aeroclub).
   • ATIS information (e.g. information "J").
   • flight rules (e.g. VFR).
   • destination (e.g. Hilversum).
   • request start-up.
2. Taxiing on taxiways:
   • pilots of aircraft intending to taxi on the taxiways shall obtain a clearance from Eindhoven Ground.
3. Taxiing on the apron:
   • aircraft not maintaining two-way communication and intending to taxi on the apron must obtain prior permission from ATC.

4.2.2 Aircraft with a MTOM < 2000 KG

Unless otherwise instructed or approved climb to 1000 FT AMSL.

1. ZULU Departure.
   • After take-off follow the VFR route via MIKE and VICTOR to ZULU.
2. ECHO Departure.
   • After take-off follow the VFR route via MIKE and VICTOR to ECHO.
3. WHISKEY Departure.
   • After take-off follow the VFR route via HOTEL and OSCAR to WHISKEY.
4. TANGO Departure.
   • After take-off follow the VFR route via HOTEL and OSCAR to TANGO.
5. For other directions.
   • Departure instructions will be given.

4.2.3 Aircraft with a MTOM >= 2000 KG

Unless otherwise instructed or approved climb to 1000 FT AMSL.

1. Aircraft have to remain on runway track to at least:
   • 3 DME EHV after departure from RWY 21.
   • 4 DME EHV after departure from RWY 03.
2. Left or right turn only after approval of Eindhoven TWR.

4.3.1 Aircraft with a MTOM < 2000 KG

1. Contact Eindhoven TWR 2 minutes before reaching the CTR boundary for permission to enter the CTR.
2. Enter the CTR at 1500 FT AMSL and maintain this altitude.
3. Proceed via an indicated VFR route (ZULU, ECHO, WHISKEY or TANGO) unless otherwise instructed.
4. Join the circuit as instructed by ATC.

4.3.2 Aircraft with a MTOM >= 2000 KG

In order to avoid noise nuisance aircraft with a MTOM >= 2000 KG shall perform a straight-in approach.

4.4.1 Aircraft with a MTOM < 2000 KG

Circuit direction (unless otherwise instructed by Eindhoven TWR):

• RWY 21 righthand.
• RWY 03 lefthand.

Circuit altitude: 1000 FT AMSL.

4.6.1 General

• Select transponder code 7600.
• If possible call Amsterdam ACC Supervisor on telephone number +31 (0)20 406 3999.
  Use telephone connection to mitigate COM failure only. All telephone calls will be automatically recorded.
• If telephone connection is disconnected prematurely (before read-back), revert to communication failure procedures below.

4.6.2 VFR outbound

In case of communication failure adhere strictly to the departure instructions. If the departure instructions contain a clearance limit in the CTR, act in accordance with paragraph 4.6.4.

4.6.3 VFR inbound

4.6.4 VFR crossing the CTR

In case of communication failure:

1. Leave the CTR via the shortest route.
2. Maintain altitude until outside the CTR.
3. Do not cross runway centre lines or IFR areas.
4. Proceed to an appropriate aerodrome.