1.2.1  Start-up permission

Due to the proximity of the apron to the runway and the complex ATC co-ordination procedures, a request for start-up shall be made to Eindhoven Ground, 10 minutes prior to start-up. The request shall include:

• aircraft identification (e.g. KLM001).
• position (e.g. B1).
• ATIS information (e.g. information "F").
• number of persons on board (e.g. POB 16).
• flight rules (e.g. IFR).
• destination (e.g. Amsterdam).
• request start-up (e.g. request start-up in 10 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 the delay will be given.

During the hours of the ATIS broadcast no MET information will be issued to departing aircraft except RVR (see EHEH AD 2.18).

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 speed below FL 100: 250 KT IAS.
• 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 encourages the use of pre-programmed routes on board of aircraft. However as yet in the TMAs such routes must be considered as overlays of conventional routes. Pilots have the obligation to cross-check the lateral accuracy with the conventional navigation aids to remain within acceptable limits. The description of the SIDs is extended with additional information intended for database coding only. 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.
  • The EH-waypoints shall not be used in RTF procedures.
  • Connect FMS and autopilot as early as possible.
  • Turn anticipation is mandatory for all waypoints except those which are underlined. Underlined waypoints must be overflown.

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 EHTW, MAX FL 095.
6. Only for aircraft with destination EHGG, MAX FL 095.

1.4.3  Continuous routings with crossing conditions on ATS routes as applicable

1.4.4  SIDs RWY 04

1.4.5  SIDs RWY 22

2.2.1  Inbound clearance

Upon initial contact at or before entering the Nieuw Milligen TMA D, Amsterdam ACC or AOCS Nieuw Milligen (Dutch MIL) will issue an inbound clearance containing:

1. Clearance limit.
2. Route.
3. Level (flight level or altitude).
4. Runway in use1)
5. EAT, when a delay of 30 minutes or more is expected.
6. SSR code.

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 the hours of ATIS broadcast (see EHEH AD 2.18) this item may be omitted as far as it is included in the ATIS broadcast.

2.3.3  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, AOCS Nieuw Milligen (Dutch MIL) will provide radar approach service.

2.4.1  Final approach procedures

2.4.2  Missed approach procedure

2.5.1  General

The pilot of an IFR flight shall follow 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 NDB EHN.
• Maintain the last cleared and acknowledged flight level.
• After arrival over NDB EHN, intercept the holding pattern.
• Commence descent to 2000 ft AMSL at or as near as possible to the ETO over NDB EHN.
• After reaching 2000 ft AMSL leave NDB EHN and carry out an instrument approach procedure to RWY 22 (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

1. Depends upon the RNAV system. Final segment is the only place in the procedure where a CF coding may be used.
2. The use of this EH waypoint depends on the RNAV system used.

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).
   • number of persons on board (e.g. POB 2).
   • destination (e.g. Hilversum).
   • request start-up (e.g. 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 MTOW < 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. YANKEE Departure.
   • After take-off follow the VFR route via MIKE and VICTOR to YANKEE.
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 MTOW >= 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 22.
   • 4 DME EHV after departure from RWY 04.
2. Left or right turn only after approval of Eindhoven TWR.

4.3.1  Aircraft with a MTOW < 2000 kg

1. Contact Eindhoven TWR in time for an entry clearance for the CTR.
2. Enter the CTR at 1500 ft AMSL and maintain this altitude.
3. Proceed via an indicated VFR route (ZULU, YANKEE, WHISKEY or TANGO) unless otherwise instructed.
4. Join the circuit as instructed by ATC.

4.3.2  Aircraft with a MTOW >= 2000 kg

In order to avoid noise nuisance aircraft with a MTOW >= 2000 kg shall perform an instrument approach.

4.4.1  Aircraft with a MTOW < 2000 kg

Circuit direction (unless otherwise instructed by Eindhoven TWR):

• RWY 22 righthand.
• RWY 04 lefthand.

Circuit altitude: 1000 ft AMSL.

4.4.2  Aircraft with a MTOW >= 2000 kg

Circuit direction (unless otherwise instructed by Eindhoven TWR):

• RWY 22 righthand.
• RWY 04 lefthand.

Circuit altitude: 1500 ft AMSL.

4.6.1  General

Select SSR code 7600.

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 ILS areas.
4. Proceed to an appropriate aerodrome.